The Board Pack Needs a Record of Decisions Reversed

A board pack can explain why an initiative is late without showing how often leadership changed the decision behind it. The project appears to have an execution problem. The team remembers three different briefs, two budget revisions and a senior intervention that never reached the minutes.

Businesses need the freedom to change their minds. Customer evidence improves, costs move and assumptions fail. The problem begins when a reversal is treated as if it has no history and no operating consequence. Teams are then assessed against the newest expectation while the work created by earlier choices disappears from view.

A short record of consequential decisions reversed can give the board a clearer picture of how the organisation actually behaves.

Record the change in reasoning

The useful unit is a decision, rather than every conversation or passing suggestion. Record the choice made, the person authorised to make it, the assumptions supporting it and the conditions that would justify review. When it changes, add the new evidence and the consequences for work already commissioned.

For example, a leisure operator may approve a premium membership launch, then discover that the promised access would displace too many existing customers. Revising the offer could be excellent management. The record should show that the capacity evidence changed the decision, and that the marketing timetable and operating plan were reset accordingly.

By contrast, a change driven by a director's preference after design work is complete deserves a different discussion. Preference can still influence strategy, but it should not masquerade as a newly discovered fact.

Make the cost visible without inventing precision

Some reversal costs are straightforward: cancelled supplier work, reprinted materials or additional development hours. Others are harder to isolate, including delayed decisions elsewhere and confusion among frontline managers.

Separate amounts supported by records from informed estimates. Where precision is unavailable, describe the consequence rather than manufacturing a number. A delayed launch date and two weeks of duplicated preparation can be useful evidence without assigning an unsupported financial value to every hour.

Also record work avoided. Reversing a poor decision early can protect the business from a much larger commitment. A register that counts only costs will discourage necessary learning and reward stubbornness.

Look for patterns that ordinary project reporting misses

A series of reversals may reveal that customer evidence arrives too late, that finance joins after commitments are made or that directors believe they have overlapping authority. It may show that one individual regularly reopens decisions after the team has begun delivery.

Each pattern requires a different response. Better research will not fix an unclear decision owner. A tighter approval process will not fix a founder who ignores it. More detailed project reporting may simply document the consequences with greater accuracy.

This is why decision debt and decision reversal deserve separate attention. The first concerns choices left unresolved. The second concerns choices whose apparent resolution does not survive the organisation's own behaviour.

Avoid turning the record into a prosecution file

The register should help leaders improve decisions, not build a case against the person whose judgement proved imperfect. Record what was reasonably knowable at the time. Invite the original decision-maker to explain the reasoning and identify what would improve the next decision.

Keep the threshold proportionate. A restaurant group does not need a board entry for every menu adjustment. It may need one when the format, investment case or launch commitment changes materially. Agree the threshold once, then apply it consistently, including to the CEO.

The board should periodically examine a small sample: a reversal that protected value, one that created avoidable work and one decision that should have changed sooner. That comparison prevents the discussion from becoming a simplistic demand for fewer changes.

Give delivery teams an explicit reset

When leadership changes course, the new instruction should name what stops, what remains valid and which commitments are revised. Tell people how their performance will be assessed under the new conditions. Leaving an old deadline intact while changing the work is a decision about capacity, whether or not anyone describes it that way.

A credible leadership team can explain both why it changed its mind and what it did to make the change workable. That is an important part of FUSION: strategic choices, human expectations and operational commitments moving together.

If repeated reversals are consuming more attention than the strategy itself, talk to Q Branch about diagnosing the decision process before buying another project-management tool.