The Last Hundred Metres: Translating Boardroom Advice into Operational Practice

A board can receive sound specialist advice, test it properly, resolve to act, and still find months later that little has changed in the operating business. The advice was not wrong. The decision was not necessarily ignored. What failed was the last hundred metres: the distance between a boardroom conclusion and the ordinary routines of the organisation.

This is the advisory air gap. It opens in the lift lobby, not in the meeting room. By the time directors have returned to their diaries and executives have returned to delivery pressure, the nuance of a specialist recommendation can be reduced to a slide title, a budget line or a general instruction to "take this forward". The result is predictable: partial adoption, inconsistent interpretation and a board that believes it has acted while the business continues largely as before.

For UK boards commissioning specialist advice, the air gap is not primarily a communications problem. It is a governance problem. Advice that is meant to change practice needs an owner, a decision trail, checkpoints and a review. Without those, a well-drafted report becomes an artefact of a meeting rather than an instrument of change.

Why advice loses force after the meeting

The boardroom is a controlled environment. Specialist advisers present evidence, answer challenge and refine recommendations in the presence of decision-makers. The operating environment is different. Managers may have had no sight of the advice until a summary arrives. Responsibilities may be contested. Existing incentives may reward the status quo. Local judgement may be exercised by people who were not in the room and who have legitimate operational reasons to adapt the recommendation.

None of this is necessarily resistance. It is translation. The difficulty is that boards often leave translation to chance. A resolution is passed, an executive is asked to progress the matter, and the specialist engagement is treated as complete. The advice has been received, but it has not been converted into decisions, accountabilities and routines.

The gap widens when the recommendation cuts across functions. A specialist view on procurement governance may require finance, legal, operations and commercial teams to change their sequence of work. A board advisory review may recommend a different escalation route for risk. Each function can agree with the principle while disagreeing about who must change first. Without a named owner and a decision log, those disagreements remain unresolved and the advice quietly loses authority.

Treat translation as a board-level deliverable

The first discipline is to stop treating the specialist report as the end of the engagement. The board should treat translation as a distinct deliverable with its own governance. That means deciding, at the point of commissioning, how the advice will be carried into the organisation if it is accepted.

A useful translation protocol has four elements: a named owner, a decision log, adoption checkpoints and a short post-engagement review. None is elaborate. Together they give the board a visible chain between its resolution and operational practice.

Name an owner, not a channel

"Communications" is not an owner. Neither is a committee, a steering group or a distribution list. The board should identify a single accountable individual for the translation of the advice into practice. That person should have sufficient seniority to resolve cross-functional tension and sufficient proximity to delivery to know where the recommendation will meet friction.

The owner's role is not to defend the adviser's report word for word. It is to preserve the intent of the board's decision while allowing sensible local adaptation. The owner should be able to explain which elements are non-negotiable, which are adaptable and which require a further board decision if they are to change. This distinction is often missing from the original advice and is precisely what operational teams need.

Keep a decision log

A decision log is not a minutes substitute. It is a short, living record of what has been decided about the advice after the boardroom. It should capture the decision taken, the owner, the operational changes required, the dependencies, the date of the next checkpoint and any deviations from the original recommendation.

The log matters because the air gap is filled with small, reasonable-looking decisions. A team may decide to phase implementation differently. Another may decide that an existing process already meets the intent. A third may decide that the recommendation does not apply to its area. Individually, these decisions may be defensible. Collectively, they can hollow out the advice. A decision log makes those choices visible and allows the board or its delegated committee to test whether the cumulative effect remains consistent with the original resolution.

Set adoption checkpoints

Adoption checkpoints should be scheduled before momentum fades. A single review six months after the engagement is usually too late; by then, workarounds have hardened. A short checkpoint at 30 days, a second at 90 days and a final review at six months is often sufficient for a specialist advisory engagement.

Each checkpoint should ask three questions. First, what has actually changed in practice, not merely in documentation? Second, where has the advice been adapted, and is that adaptation consistent with the board's intent? Third, what remains unresolved, and who must decide it? The answers should be recorded in the decision log and reported to the board in a form that distinguishes progress from activity.

Hold a short post-engagement review

The post-engagement review is the board's opportunity to learn. It should be brief and should focus on the translation process rather than re-litigating the advice. Did the owner have enough authority? Were operational teams engaged early enough? Did the decision log capture the right issues? Were checkpoints held? Did the board's commissioning brief anticipate the implementation burden?

The review also gives the board a disciplined way to close the engagement. A specialist advisory relationship that ends without a review tends to leave ambiguity about whether the advice was adopted, adapted or abandoned. A short review creates a record and improves the next commission.

The board's continuing role

The board does not need to manage translation in detail. It does need to insist that translation is governed. That means asking for a named owner before the engagement closes, reviewing the decision log at least once, and treating adoption checkpoints as board-level assurance rather than administrative follow-up.

The advisory air gap is not closed by better presentations. It is closed by a deliberate chain of accountability from the resolution to the routine. Boards that build that chain protect the value of specialist advice and ensure that good thinking survives the journey from the boardroom to the place where work is actually done.