This is the yearly Christmas letter from Kristian Sørensen to clients, colleagues, partners and friends.
“What is the best approach to creating an IT strategy?” This is a question that I have been asked many times – along with a “What is your best practice strategy template?”. The reality is, however, not that it is not that simple – and there is no specific and final answer.
In the following will be scrutinized five concrete behavior patterns (typologies) that can come into play in touch with conflicts or negotiations. The tool is based on Thomas-Kilmann Conflict Mode Instrument (TKI). For the sake of clarity, the term ‘negotiation styles’ will be utilized throughout the rest of this article.
Self-management is about attitudes, qualities and the way we meet the outside world. Strong self-management has a direct effect on the ability to utilize own – and other’s – skills effectively and create common results.
As a follow-up on my blog post “Forget Disruption! Instead, focus on innovation and create results through good conflicts and innovation culture”, I think it could be interesting to give some examples of innovations that most of us know. Innovations that in many cases have been down to change the world.
Forget disruption! Instead, focus on innovation and create results through good conflicts and innovation culture
Most disruption consultants should stop talking and take action, and the words “disrupt or die” have been repeated several times. My message is: Forget disruption. Instead, focus on how you can create a foundation for innovation in your organization.
Constructive conflicts create innovation, propulsion and change. The project manager’s job is to ensure a good conflict environment, which prevents and handles unnecessary conflicts and promotes constructive disagreement.
Interpersonal relationships and the ability to work together are crucial to a project’s success. Understanding the intentions behind the behaviour of others can provide common ground for collaboration across national borders and cultural diversity.
Achieve win-win decisions in your projects Project managers can use the natural decision-making process to disarm and deal with resistance and conflicting opinions in a constructive and proactive manner and establish a win-win perspective that promotes cohesion and ownership in the project A survey among Danish project managers (Projektlederundersøgelsen 2014) showed that motivating project participants…
The procurement foundation contains essential elements that must be defined and accepted amongst key stakeholders of a procurement project prior to starting the procurement process. The more impact the IT system has in an organisation, the more important the foundation becomes.
This article provides a simple and powerful approach to establish a solid procurement foundation for IT procurement projects.
Retrospective generally means to take a look back at events that already have taken place and performing a retrospective is a natural part of all projects whether or not it is done formally or informally.
The process helps reduce tension and is motivating to the people involved.
One of the continuous major challenges for project managers is getting sufficient resources with needed competences. This is particular apparent in the project initiation or when taking over an existing project.
This article discusses a “reverse engineering”-approach to solving this challenge, which will make you gain momentum, deliver results fast and build a happy project team.
There is a need for increasing the focus on leadership in projects. But what are the key qualities of the perfect project manager? This is what we will discuss in this article.
Engaged leadership creates results. However, results in projects do not come from leadership alone; management skills and domain expertise are just as important qualities.
Mostly making a budget for an IT project starts with estimation. This article discusses the pitfalls in estimation and gives insight on how to avoid and handle unrealistic budgets in IT projects.
We cannot make things cost less by inventing low estimates, but we can easily do the opposite and invite Parkinson for coffee.
The evolution of the way we do projects have been very slow when compared to e.g. the parallel evolution in technology. A project is rarely “by the book” simply because projects are complex by nature and thus there is no straight road to success.
This article discusses the historic drivers for success in projects and suggests the upcoming drivers that increase the chance of project success.