A strategy can perfectly well be adopted without being understood. The difference shows up two months later, when two managers act in opposite directions on the same decision. The conversation that prevents it is not about reaching agreement, but about surfacing the disagreement while it can still be used.
You have read the analysis. You have the material. You call the management team together.
Presentation. Silence. A couple of questions. More silence. So that is decided?
People nod. Somebody asks what happens to the project started in February. Somebody else notes it will require saying no to something. The meeting ends.
The strategy is adopted. But is it understood? Will people act on the same understanding once they are back at their desks?
Usually not.
Information is not shared understanding
This is where most strategy processes fail, and it happens quietly.
Information means you now know something you did not know before. Shared understanding means you agree on what it means, and act on the same thing.
Five managers can read the same analysis and leave with entirely different readings:
- "We need to be more digital." Does that mean systems development or marketing?
- "We have a capacity constraint." Do we hire, or do we prioritise harder?
- "Innovation matters now." Does that mean fewer resources for the core business, or something running alongside?
Those ambiguities do not surface in the meeting. They surface two months later, when two departments have acted in opposite directions in good faith. And the time is gone.
A meeting is not a conversation
We say meeting, but we usually mean presentation with questions.
A meeting is built around input. One person talks, the rest listen. There is an agenda and an end time, and the conclusion often exists before it starts.
A conversation is built around exploration. Several people examine the same problem together, there is no finished conclusion in advance, and changing your mind is permitted.
Strategy needs the second. It takes longer once and saves two months afterwards.
The four parts
1. The shared picture
Do not start with recommendations. Start with the situation.
Here is what we see in the market, here is what the numbers say about customers, here is what competitors are doing. Do you see the same?
Not "we should do X", but "this is what the landscape looks like".
If you do not agree on the picture, the conversation is not ready for recommendations. And the disagreement is rarely about the numbers. It is about experience and blind spots, and it is worth fifteen minutes.
2. The uncomfortable questions
Once the picture is shared, the work begins.
If this is right, what does it mean? And what are we afraid it means?
The second question is the most important one in the meeting. When people disagree about strategy, they rarely see different pictures. They are afraid of different things.
One says you cannot bet on innovation because cash flow has to stay stable. Another says you cannot wait, because you lose position meanwhile.
Both are right. The strategy consists of acknowledging both concerns and prioritising anyway, not of establishing whose worry is more justified.
3. The unspoken assumptions
Part of the management team may come from a traditional industry, part from a faster environment. They hold different relationships to risk, and it governs their judgement without anyone saying so.
The purpose of surfacing it is not to make everyone think alike. It is so the strategy gets designed with those differences rather than despite them.
4. Clear ownership
A strategy without ownership is a document.
Test it simply: ask five managers the next day what you decided. If you get three different answers, there was no conversation. There was a decision.
What it looks like in practice
An advisory firm with 60 employees had to decide whether new clients should be served digitally by default.
The shared picture: clients' IT environments are complex from day one, and we have not been especially good at getting started well in that kind of environment. Everyone agreed.
The uncomfortable questions: who is afraid of what?
The practice lead was afraid they would get worse at hearing what the client actually needed, if the technology set the terms. The operations lead was afraid of not having the people to deliver it. The sales lead was afraid of losing some of the most profitable clients, who work traditionally.
The unspoken assumptions: here it got interesting. The practice lead was not worried about delivery at all. The operations lead was not worried about losing those clients, because she did not believe they were as profitable as sales claimed. The sales lead was worried about both.
That was the real disagreement, and it turned on a number nobody had looked up.
The ownership: the practice lead took defining what digital-first means without losing client understanding. The operations lead took mapping which capabilities were missing.
Try it at the next meeting
You do not need to redesign the process. Change three things:
- Send the material five days ahead, not the night before.
- Spend the first fifteen minutes on one question: does anyone disagree with the picture of the situation?
- Ask directly what each person is afraid of, before anyone proposes a solution.
Point three feels awkward the first time. It is also what surfaces the real disagreement, and that disagreement surfaces either way, now or in two months.
How to make sure the basis is shared before the meeting is covered in decision basis in leadership, and why the decision still belongs in a room with people is in the best decisions are made in a room.
Why the decision is bound to a role on our side
A conversation with nowhere to land becomes another conversation.
In 360° Sprint approval is built as a gate with a consequence: approving it marks that layer's models complete, so progress reflects a decision that was taken. Who may approve is a setting on the organisation rather than a matter for the individual.
That does not make the conversation better. It ensures it ends somewhere, and that it can be seen afterwards who said yes.
What it then takes for the decision to hold is covered in AI can analyse, humans can commit.
The whole handover from decision to operations is collected in from strategy to action.