An analysis can tell you what is the case. It cannot create commitment, and commitment is what decides whether a decision still holds in three weeks. Which is why the meeting is not wasted time, provided the groundwork happened first.
A finance director built her entire strategy process around thorough analysis. Competitor mapping, market trends, financial scenarios. The data was better than anyone else's in the industry.
Three months later the strategy was shelved.
Not because the analysis was wrong. Because she, the chair and the two operations directors had never sat down and talked about what it meant.
A recommendation is not a strategy. It is an input to one.
What the analysis cannot settle
An analysis can read eighteen months of competitor data and establish that your three largest competitors are losing share in a particular segment. That is useful.
It cannot say what you should do about it. Attack? Hold the position? Move somewhere else? Invest defensively?
The answer is not in the numbers. It is in what the organisation can carry, what you want to be, and what you dare risk.
This is where it usually goes wrong: people assume that if the analysis is thorough enough, the decision follows. It does not. The decision exists the moment the management team says this is what we are doing, and means it.
Agreement is not commitment
A chief executive spent three months getting his management team to agree on a new direction. They voted. They signed. A photograph was taken.
Three weeks later everyone was back in the old routines.
Agreement and commitment are not the same, and the difference is not academic. You can perfectly well disagree and still be committed: I would have chosen something else, but I understand the argument, and I am behind this.
The opposite is the dangerous one. People hold their doubts back, wait to see who will really drive it, and think of themselves as having been taken along rather than having taken part.
That is the state that looks like agreement in the meeting and turns into nothing afterwards.
Good groundwork makes the meeting shorter, not longer
It seems backwards, but thorough groundwork makes the meeting itself less meeting-like. Less time presenting, less time working out what this is really about.
A manufacturer had its starting point mapped thoroughly: finances, capacity, customer types, contribution margin per product line, distance to competitors on each line. A few hours of work, where as a spreadsheet exercise it would have been months.
Then the management team sat down. Instead of spending the meeting going through numbers, they could spend it on questions like: why do we keep production in house on the line where the margin is weakest? If we move it out, what happens to our ability to develop new things? And do we dare?
That is a different kind of meeting. It is also one they did not regret three days later.
The facilitator's role
A facilitator does not say what is right. She says: I hear that you disagree about where the threat sits, can you be precise about where the difference is? Or: we have spent forty minutes here without moving, what is it we need to decide?
It sounds simple. It is not, when you are the one with a headache about how to present this to the board.
A facilitator with no stake in the outcome can hold focus on the process while everyone else holds focus on the content. Which is why the role belongs to somebody other than whoever has most riding on it.
The setup that works
- Let the groundwork be thorough. The whole starting point, not an extract. How to do it is in AS IS to TO BE.
- Send the material five days ahead. Participants should arrive with questions, not spend the first half hour reading.
- Let somebody else facilitate. Not you, and not whoever has the largest office.
- Block three to four hours without interruption. Every time somebody checks a phone, you are back at the headlines.
- Write the decision down in the meeting. Not afterwards. Then there is nothing left to interpret.
- Follow up within a week. Not to check, but because doubt that went unsaid usually appears on day four.
Point five is the one most often skipped. Five lines written while everyone is in the room are worth more than minutes written by one person two days later.
What this does not mean
It does not mean using less analysis. The opposite: the better the starting point is mapped, the more time there is for the hard part.
It means not expecting the analysis to become a strategy by itself. It becomes one when people sit together and say yes, and then behave as though they did.
How to structure the conversation itself is in the most important strategic conversation, and why commitment cannot be delegated is in AI can analyse, humans can commit.
Why you can see what the decision rested on
What makes a decision hard to hold to is usually not disagreement. It is that in six months nobody can recall what it was built on.
In 360° Sprint the analyses collect in Insights with run history, so two passes at the same question can be held against each other over time. The nodes are connected, so what a conclusion inherited from what came before it stays visible, and every state change is logged.
That does not make the decision for you. It means that a year later you can tell the difference between an assumption that did not hold and a plan that was not followed. Those are two entirely different problems, and they need different responses.
The four places the handover to operations breaks are in from strategy to action.