Most strategic failure does not happen at the first order. It happens two and three moves downstream, in effects nobody modelled because they were not on the spreadsheet.
The efficiency initiative that hits its savings target and destroys the informal coordination the business actually ran on. The restructure that consolidates reporting lines and quietly dismantles three years of accumulated trust. The hiring discipline that filters out “soft” candidates and leaves the senior team unable to have a difficult conversation. First-order metrics improve. Second-order systems fail. And the cost, reliably, materialises about eighteen months later — by which point the original decision is so embedded that no one is tracing the cause back to it.
Why this is so consistent
The failure mode is not usually a failure of intelligence. Most senior teams are perfectly capable of conceptual systems thinking. What they are less capable of is the specific, uncomfortable, time-consuming work of applying that capacity to decisions that are already under time pressure and already have political momentum behind them.
Strategic decisions arrive at senior tables with first-order logic pre-assembled. The business case shows the direct benefit. The spreadsheet models the primary cost. The stakeholders have been consulted within their respective domains. The question of whether to proceed is framed around the first-order numbers, and the time pressure of the moment makes any request to slow down and model the second order feel like resistance to change rather than diligence.
This is the specific window in which second-order thinking reliably gets skipped. Not because the team lacks the capacity for it — but because the cultural and political cost of asking for it is too high in the moment. The decision is made. The spreadsheet was right about what it measured. It measured the wrong thing.
The practice that catches this
The practice is uncomfortably simple. Before any significant decision, force the decision-makers to answer two questions in writing — not in discussion, in writing, individually, and then compared.
What is this optimising for?
This sounds trivial. It is not. The written answers, compared side-by-side, reveal what the individuals in the room have been privately assuming about what the decision is meant to accomplish. The variance is usually larger than the discussion had suggested. What appeared to be shared alignment is frequently several people optimising for related but meaningfully different goals.
Where will the cost land that is not in the current model?
This is the more generative question, and the one senior teams most resist asking. It requires naming the parts of the system that the current decision will quietly damage, and acknowledging that the spreadsheet does not contain them. The answers, when honestly given, often identify the exact place where the decision will fail in eighteen months.
Discussion tends to smooth over both questions. Written answers surface what discussion obscures. The two questions, together, are frequently the difference between a decision that produces the first-order result and one that produces the second-order collapse alongside it.
Three decision archetypes where this matters most
The efficiency initiative. Almost always optimising for measurable cost reduction, almost always creating invisible damage to the informal systems that had been doing unmeasured coordination work. A written systems check usually surfaces the coordination cost before the decision is made. Discussion-based review usually does not.
The restructure. Almost always optimising for clarity of reporting lines and accountability, almost always damaging the relationships that had been carrying trust across organisational boundaries. The damage is frequently invisible for twelve months, after which turnover begins to rise in patterns that the org design review did not anticipate.
The talent filter change. Almost always optimising for some specific dimension of capability, almost always filtering out other capabilities that were structurally important but not currently being measured. The cost tends to compound slowly — the team loses a specific kind of contribution without realising what it had lost, and gradually becomes less able to do the work the missing capability had been doing.
Why this is not purely a cognitive skill
Systems thinking, as the field usually teaches it, is a cognitive capability. Diagrams, frameworks, feedback loops, causal chains. These are useful. They are also, in the moments they are most needed, frequently the first capacity to become unavailable.
What I have watched consistently in senior leaders is that the capacity to apply systems thinking under pressure is a developmental capacity, not a cognitive one. The leader who has integrated their own tendency to optimise locally and damage globally is materially better at seeing when their current decision is doing it. The leader who has not integrated that tendency can draw the diagrams, teach the frameworks, and still make the first-order decision because the first-order relief is what their nervous system is actually seeking.
This is one of the reasons the AIR phase of the Alchemy sequence exists as a distinct developmental stage. Systems awareness is not something you acquire through training. It is something you become capable of through the integration of what had previously been distorting your seeing.
The question worth asking this week
Look at the significant decisions your senior team has made in the last eighteen months. Pick one where the first-order outcome has been broadly as expected. Now look at what has happened at the second order — in the relationships, the trust, the informal systems, the people who left, the capabilities that have quietly eroded.
If the second-order costs are materially larger than the first-order benefit — which is often the case — that is useful information about how your team is currently making decisions. It is also an argument for doing the written systems check before the next one, even if it feels like friction in the moment.
Friction is cheaper than eighteen months of compounding damage. Almost every time.
The Alchemy of Leadership: Five Elements Workbook
The developmental work that underlies genuine systems awareness — the AIR phase and the capacity to see what a system is asking of you, rather than what you want to project onto it. Available free.