Why digital strategy stalls long before execution begins
By Camilla Wett Fri
Original article in Danish. English translation by M365 Copilot
Let me start with something I have gradually learned to be wary of.
A strategy meeting where everyone agrees.
The direction is clear. The ambitions are high. People nod around the table. The right words are spoken about transformation, prioritization, and necessary change. And when the meeting ends, everyone leaves with the feeling that we have really taken an important step forward.
And yet, not much happens afterwards.
Initiatives are delayed. Decisions are reopened. New considerations emerge. Budgets turn out to be less flexible than expected. One leader begins arguing that her area should be treated differently. Another says that the organization is not mature enough yet.
Six months later, the strategy still exists. But mostly as slides.
It is tempting to call this an execution problem. Sometimes it is. But in my work with change and digital strategy, I often see something else:
Execution could probably take place, if it were not for the fact that someone in the leadership team begins experiencing something very human. Something that all of us have experienced.
A strategy is not just a direction
When we talk about strategy, whether it is business strategy, digital strategy, or any other type of strategy, many people imagine a rational exercise.
We analyze the current situation. We look at opportunities and risks. We decide where we want to go. Then we make a plan for how to get there.
On slides, the journey from the present to the future can be represented by a single arrow.
In reality, it can involve months of conversations, conflicts, doubt, and political negotiations.
This is particularly true of digital strategies. While a business strategy describes where the company wants to go, a digital strategy must translate these ambitions into concrete choices about technology, data, processes, capabilities, and organization. And it is often in this translation that the consequences become visible to the people affected by them.
When ambitions have to be translated into concrete decisions and priorities, the uncomfortable questions appear:
- Which tasks do we need to stop doing the old way?
- Which capabilities become less important?
- Which capabilities are missing?
- Who will need to take on different responsibilities?
- Who gets a voice and a seat in the governance structure?
This is where strategy stops being only about the future.
It also begins to be about what someone risks losing. And that is where resistance emerges.
Most people are not opposed to the strategy itself
I have taken part in strategy processes where the resistance initially seemed irrational.
People rarely resist change itself. More often, they resist what they believe they stand to lose because of it. Control. Competence. Influence. Status. Identity. The person pushing back against the strategy is not necessarily trying to sabotage it. They may simply be protecting something that matters to them.
One leader had helped formulate the ambition, but later began questioning almost every initiative intended to make it concrete. Another asked for a clearer direction, but reacted strongly when that direction meant decisions would have to be made elsewhere in the future. A third was positive about new technology until the conversation turned to how the technology might change the value of that person’s own experience.
It is easy to put labels on this kind of behaviour.
A lack of willingness to change. Silo thinking. Politics. An insufficient strategic mindset.
But labels rarely help us move forward.
Because behind the visible resistance there is often a far more human reaction.
My own understanding is based on practical experience supporting leaders in achieving their goals, as well as research in organizational psychology and change management, inspired by Richard Boyatzis, William Bridges, Robert Kegan, and Lisa Lahey, among others. What they have in common is an understanding that people rarely resist change itself. More often, they react to what they feel they may lose, whether that is control, competence, significance, or part of their professional identity.
The person is therefore not necessarily trying to sabotage the strategy.
The person is simply trying to protect something that feels important. To avoid a loss.
A loss of autonomy, status, routines, structure, familiar tasks, colleagues, or, in the worst case, a job.
When it comes to strategies that create change across an organization, I typically see this fear of loss appear in three forms.
1. Fear of losing control and autonomy
A new direction often means that something needs to be done differently than it was yesterday.
Perhaps data should no longer be owned locally within each business unit. Perhaps technology choices need to be standardized. Perhaps an AI portfolio should be prioritized across the organization rather than growing through local experiments. Perhaps an area that previously had a high degree of freedom must now operate within shared principles.
On an organizational chart, this may look like governance. But for the person affected, it can feel like a loss of control.
When people feel that control is slipping away, they often try, consciously or unconsciously, to regain it. This may happen by questioning decisions, demanding more budget or resources, challenging a colleague’s mandate, insisting on exceptions, or simply avoiding doing what is required to move in the new direction.
From the outside, it looks like delay.
From the inside, it can feel like self-defence.
What is certain is that the organization pays the price. Not only financially through inefficiency and delays, but also in human terms. Because when people experience a loss of autonomy, it rarely affects only them. It also affects the colleagues who encounter conflict, resistance, roadblocks, or a poorer climate for collaboration.
2. Fear of incompetence
The second reaction is quieter.
A new strategic direction does not only change what the organization needs to be capable of doing. It can also change who is perceived as competent.
We see this clearly with AI.
A leader or specialist may have spent twenty years building a professional identity. They are used to being the person others come to for answers. Suddenly, younger colleagues arrive with new tools, new concepts, and a pace that is difficult to keep up with.
So the question does not only become: Can AI create value for the business?
It also becomes: Will there still be a need for me?
That question is rarely asked out loud in a strategy meeting. Instead, it may be expressed as skepticism towards the technology, as very high demands for documentation, or as an insistence that the organization first needs to get a lot of other things under control.
Some of that criticism may be fully justified. There are plenty of overconfident technology projects that deserve to be challenged.
But sometimes the discussion is not only about the quality of the solution. It is also about an individual’s doubts about their own future value.
So the next time someone reacts with demands or skepticism, it may be worth considering whether the new direction is challenging their perception of themselves as competent.
3. The loss of identity, status, or significance
The third form of loss goes even deeper.
We often talk about roles and responsibilities as if they are merely boxes in an organizational model. But for many people, work is an important part of their identity.
I am the person responsible for this area.
I am the person who knows the most about this area.
I am the person who knows the systems.
I am the person leadership turns to.
I am the person who built this function.
I am the expert.
When a strategy changes that, it potentially changes the person’s story about themselves as well.
It may be a tangible loss of budget, employees, or mandate. But it can also be a more intangible loss of status or professional significance.
It is worth remembering this when a leader appears to be fighting unreasonably hard to preserve a particular initiative or area of responsibility.
Perhaps the person is not only protecting a box on the organizational chart.
Perhaps the person is protecting their idea of who they are.
When rational strategy meets the real organization
I have experienced a strategy process where the leadership team agreed on where the company needed to go.
The group was working to define how the company would achieve its objectives. Along the way, one of the leaders contributed input that steered the process in a particular direction. Only later did it become clear that this direction would have significant consequences for his own area. Once he realized this, he began to see problems in the plan and question the direction.
The result was not a straightforward implementation of the recommended direction. It became a compromise. Some systems were changed. Certain organizational consequences were accepted, while other parts of the original ambition were reduced or postponed. As a result, the strategy discussed in the room became one thing, while the actual execution became something else.
This is not an isolated example.
It is also why a strategy can be analytically correct and organizationally impossible.
We often talk about strategies as if they fail during execution. But my experience is that many of them encounter problems much earlier. Not when projects get underway. Not when budgets need to be approved. But while the strategy itself is still taking shape.
This is where fears of losing control, becoming incompetent, and losing part of one’s identity begin to influence decisions. Often so subtly that nobody notices.
And that raises an interesting question: How do you actually recognize the problem before the strategy ends up as an expensive presentation?
Camilla Wett Fri is a Manager in Strategy & Process at VENZO. She works with strategy development and change processes, helping organizations create alignment between ambitions, decisions, and execution.

