The Ledger of Almost: Recording the Decisions Your Leadership Team Didn't Take

Most leadership teams keep a reliable record of what they decided. Far fewer keep a record of what they nearly decided, why the alternative lost, or which quiet concern was set aside in the room. Yet those are often the details that determine whether a strategy holds when conditions change.

The case for a decision register is not new. What is often missing is a practical, lightweight discipline that captures the judgment behind the decision without turning into another layer of bureaucracy. The image worth borrowing is the summit register: a simple log left at the top of a climb, recording who passed, when, and in what conditions. It is not a monument. It is a cairn for the next party.

Why minutes miss the point

Board minutes and action logs are accountability instruments. They record motions, approvals and owners. That is necessary for governance, but it is not sufficient for learning. The most instructive information usually sits in the gap between the option chosen and the option rejected: the assumption that made one route look safer, the dissent that was noted but not resolved, the trigger that would have sent the team back down.

In the UK, boards are rightly expected to demonstrate robust challenge and effective decision-making. A well-kept register does not replace formal governance. It supplements it with evidence of how judgment was exercised, not merely that a decision was taken. It also helps when a non-executive director asks, months later, why a particular course was chosen. Memory flatters. A short written record does not.

The summit register in practice

A useful register is deliberately small. It should cover material decisions only: those that are costly to reverse, reputationally significant, safety-critical, or likely to shape the operating model for more than a year. For each, four fields are enough.

• The decision considered. Record the chosen route and the serious alternative that was not taken.
• The assumptions. State what had to be true for the chosen route to make sense.
• The dissent. Note the concern raised, by whom if they are content to be named, and how it was addressed or set aside.
• The review trigger. Define the condition that would cause the team to reopen the decision: a change in demand, a regulatory signal, a cost threshold, a capability gap.

One page per material decision is usually sufficient. The register should be readable by someone who was not in the room. That is the test. If it requires a decoder, it will not be used.

What to record that a minute will not

Minutes tend to record consensus. A register should record provisionality. For example: 'We assumed the supply contract would hold through the next financial year; if the renewal slips, the phased rollout is no longer viable.' Or: 'Operations favoured the slower route; the concern was that the customer-facing teams would be trained after launch rather than before.'

These are not confessions. They are the working parts of judgment. When a strategy is reviewed, the team can ask which assumptions have changed rather than reconstructing the original debate from memory. When a new executive joins, they inherit reasoning rather than only outcomes. When a project fails, the register makes it harder to rewrite history around a single scapegoat or a single hero.

There is a cultural dimension here. Some teams will resist recording dissent because it feels like keeping score. The remedy is tone. The register should name concerns as contributions to judgment, not as objections to be settled later. The chair and chief executive have to model this. If they treat the register as a compliance artefact, it will become one.

Making it stick

The failure mode is a beautifully designed template that nobody completes. Start smaller. After the next material decision, ask the team to spend ten minutes capturing the almost: the option not taken, the assumption that carried the most weight, the concern that was heard, and the trigger for review. Assign an owner. Set a date to revisit.

At the following quarterly review, ask a simple question: has any trigger fired? If not, the register is still doing useful work by showing which assumptions remain live. If it has, the team has an early signal rather than a post-mortem.

For UK leadership teams operating in uncertain conditions, the discipline is less about record-keeping than about humility. The decisions not taken are part of the route. A summit register does not guarantee a better climb. It does give the next party a clearer view of the conditions, the choices and the weather that shaped the ascent.