Every organisation is installing systems that answer faster than anyone can think. The question usually asked is whether the people are ready for the tools. The question that decides the outcome runs the other way.
Recommendations are on the table and nobody owns them. The analysis is finished; the decision is not.
Responsibility spreads until no one can say who chose — the system, the team, the board.
What is decided is not carried out. The distance between the meeting and the work grows.
For leadership teams that have the analysis and still have not decided — a managing director, a division head, a transformation lead with one question that will not resolve itself. Your team holds the decision rights — not the facilitator, not the software.
A mixed team works through one real decision your organisation is facing — not a case study, not a workshop scenario. People from outside your field are there because a decision looks different to someone who does not share your assumptions.
It ends with the decision made, carried into practice, and with the ability to do the next one without us. If a system does not survive that test, it is not fit for the people who have to work in it.
Six movements around one decision. They are not project phases — the circle turns more than once, and the last point stays open, because a decision that no one revisits teaches nobody anything.
The real decision, named — not the symptom, not the tool. Most of the work is here.
Evidence, constraints, and who actually decides. Often not who the org chart says.
Weighing what cannot be computed: consequence, responsibility, what you can live with.
With an owner and a date. A recommendation is not a decision.
Into implementation, with the people who carry it — not with a slide deck.
We remain past the handover and review what the decision did.
Capability that leaves with the experts was never capability.
Especially when new systems are arriving and nobody is quite sure who decides what any more.
Ask for a founding place