Most strategies do not fail because the content is wrong. They fail in the handover from decision to everyday life, and it happens in four specific places. All four can be closed without new systems, but they have to be closed deliberately.
There is a particular kind of disappointment. The strategy was thorough, the management team was on board, the material was good. Six months later nobody can point to what has actually changed.
It is rarely the content that fails. It is the handover.
The four places it breaks
The decision was never made. There were nods. That is not the same thing. A nod commits nobody, and you discover that only when it becomes inconvenient.
The understanding was not shared. Everyone heard "we need to be more digital" and translated it into their own department. Two months later two managers have acted in opposite directions in good faith.
Nobody owns anything. It says what should happen, but not who does it, when it is finished, and how you would know it worked.
The basis disappeared. A year on nobody can recall why the choice fell as it did, which alternatives were on the table, or what was assumed. So the discussion starts over.
The four look like four problems. They are really one: the handover from conversation to operations was never made explicit.
Decision is not agreement
This is the most important distinction in the whole subject.
Agreement means nobody objected. Commitment means somebody said out loud that they are behind it, including if they would have chosen otherwise.
You can perfectly well disagree and be committed. The dangerous state is the opposite: people hold their doubts back, wait to see who really drives it, and regard themselves as having been taken along.
That state looks like agreement in the meeting and turns into nothing afterwards. How to surface it before the decision is in the best decisions are made in a room.
The disagreement belongs before, not after
The conversation most management teams never have is not about what you should do. It is about what each person is afraid it means.
When people disagree about strategy, they rarely see different numbers. They are afraid of different things. One about cash flow, another about losing position, a third about not having enough people.
All three can be right at once. The strategy consists of acknowledging all three and prioritising anyway.
If that conversation does not happen before the decision, it happens after, as slow execution nobody can explain. The method is in the most important strategic conversation.
Every item needs an owner and a criterion
This is the most mechanical part and the one most often skipped.
Not "we need to be more innovative", but: this person starts this, with that budget, and we will know it worked if this number looks like that by this date.
Three questions per item is enough:
- Who does it?
- When is it finished?
- How do we know it worked?
If the third cannot be answered, the item is not finished. It is an intention, and intentions do not survive a busy month.
The basis has to stay
This is the least noticed of the four and the most expensive over time.
Write five lines the same day: what did we decide, why, which alternative did we rule out, and what would have had to be different for us to choose the other.
It takes five minutes. Without it you stand a year later with a result and no explanation, unable to distinguish between an assumption that did not hold and a plan that was not followed. Those are two entirely different problems with different fixes.
Why that distinction is the whole difference is covered in AI can analyse, humans can commit.
Try it on one item
You do not have to redesign the process to test this.
Take the decision from last quarter that is least clearly delivered. Ask four questions:
- Can everyone in the management team state it the same way?
- Is there a person's name on it?
- Is there a criterion that can be settled rather than debated?
- Can anyone explain why we chose it over the alternative?
Two or more noes and you have found why it has not happened, and it has nothing to do with the content.
This does not remove disagreement
Nor should it. There are genuine conflicts of interest between an owner thinking about return, a chief executive thinking about operations, and a management team thinking about staffing.
The purpose is to make the conflict visible and settled by somebody with the mandate, rather than repeated every month in a new form.
How to make sure all four parties work from the same basis is in decision basis in leadership.
Why an approval has a consequence on our side
A requirement with no consequence in the system is a statement of intent, which is exactly what a strategy becomes when the handover is not built.
In 360° Sprint approval is therefore built as a gate. Approving it marks that layer's models complete, so the progress figure reflects a decision that was taken rather than a box that was ticked. Who may approve is a setting on the organisation rather than a matter for the individual, and every state change is logged.
That is not what makes people do the work. It is what lets you see afterwards when the decision was made, and by whom.