The Room Is Not the Route: Turning Board Approval Into Delivery

A board resolution has a certain satisfying finality. The paper has been debated, the questions have been answered, the vote has been taken and the minute records the outcome. For many UK boards, that is the moment the decision is considered made. In practice, it is the moment the decision becomes vulnerable.

Between the boardroom and the business, a decision passes through several hands: the chair, the chief executive, the executive team, the programme office, functional managers and, eventually, the people who must change what they do. At each stage, something is lost or added. The nuance of the board’s discussion gives way to a short action line. The conditions attached to approval become a passing reference. The assumptions that made the proposal credible are rarely written down, let alone monitored. Within a month, the organisation is delivering something that resembles the original proposal, but not necessarily the decision the board believed it had taken.

That gap is not usually caused by bad faith. It is caused by the absence of a deliberate handover. Boards are good at reaching decisions; they are less disciplined about transferring them. A short post-decision protocol can close much of that gap without adding another layer of bureaucracy.

Why the first 72 hours matter

The first three working days after approval are disproportionately important. Memory is fresh, the implementing team is still attentive and the board’s expectations have not yet been flattened into a routine action log. If the decision is not translated into delivery terms quickly, it will be interpreted by default. Default interpretation is rarely generous: it tends to favour what is easiest to measure, what protects existing budgets, or what the loudest operational voice considers sensible.

The purpose of a 72-hour handover is not to re-run the debate. It is to fix the decision in a form that can survive contact with the organisation. Four elements are enough to make a material difference.

Name the implementing owner, not just the sponsor

Every board decision should leave the room with a named implementing owner. This is not the same as the executive sponsor. The sponsor champions the decision at board level; the implementing owner is accountable for turning it into operational reality. The distinction matters because sponsorship is often shared, ceremonial or senior enough to be remote from delivery. Implementation requires a single name.

That name should be recorded in the minute or in an accompanying decision record, together with the date by which the implementation note is due. A useful discipline is to ask the implementing owner to confirm in writing within 24 hours that they understand the decision, the boundaries set by the board and the assumptions on which approval depended. This is not a request for a project plan. It is a request for confirmation that the decision has landed.

Write one page, not a programme pack

The most effective post-decision document is usually a single page. It should state the decision in plain language, the outcome the board expects, the non-negotiables, the principal assumptions and the first three milestones. It should also identify what the board does not want to see: the scope that should not drift, and the compromises that would require a return to the board.

A one-page note is more likely to be read than a forty-page implementation plan. It also forces the implementing owner to distinguish between the board’s decision and their own delivery preferences. Where the two differ, that difference should be visible and resolved early, not discovered at the next quarterly review.

Make assumptions explicit and give them triggers

Every decision rests on assumptions: customer demand will hold, a key supplier will renew, a regulator will not object, a system will be ready, a senior hire will be in post. Boards often test these assumptions during debate, but rarely attach them to the decision itself. Once the meeting ends, they become background context that no one owns.

A better approach is to list the three to five assumptions that must remain true for the decision to hold. For each, define a trigger: the observable event or threshold that would indicate the assumption is no longer valid. Assign a named person to monitor the trigger and state what they must do if it is breached. The response need not be elaborate. It may simply be to notify the implementing owner and the board chair within a defined period, with a recommendation on whether the decision needs revisiting.

This is not risk management theatre. It is a practical way of preventing the board from discovering six months later that a decision was overtaken by events that were visible within weeks.

Hold a 30-day review that tests the decision, not just the plan

Most organisations review implementation progress. Fewer review whether the decision itself still holds. A 30-day review should do both. The implementing owner should provide evidence of progress against the first milestones, but also confirm whether the assumptions remain valid and whether any trigger has been activated.

The board’s role at this review is not to micromanage delivery. It is to test whether the decision that left the room still resembles the one now being pursued. If it does not, the board should decide explicitly whether to reaffirm, adjust or stop. That is a far healthier conversation than an eventual post-implementation review that explains, with the benefit of hindsight, why the original decision was never really implemented.

Keep it proportionate

A 72-hour handover should not become a parallel governance system. It can sit alongside existing assurance and reporting. The one-page note can be attached to the decision record. The assumption triggers can be incorporated into the risk register. The 30-day review can be an agenda item on an existing executive or board committee meeting.

The discipline lies in the consistency, not the volume. Boards that adopt this approach often find that the most valuable part is the simplest: naming one person and writing down what the board actually decided. That alone reduces the scope for drift.

Approval is not the finish line. It is the point at which the board’s judgement must be carried into the business without losing its shape. A short, structured handover gives that judgement a better chance of surviving the journey.