The One-Page Decision Log That Stops UK Boards Repeating Themselves
UK mid-market boards rarely suffer from a shortage of strategy documents. They suffer from a surplus of unresolved decisions. The same agenda item returns quarter after quarter, framed as a fresh discussion but carrying the same unanswered question: who decided what, and by when?
This is decision debt. It accumulates quietly. A board debates a pricing change but does not record the decision. A management team agrees to pursue an acquisition but leaves the review trigger vague. A committee notes a risk but does not assign an owner. Months later, the organisation is still debating the same issue, while the cost of delay has moved from the meeting room to the operating business.
The problem is not usually a lack of strategic ambition. Most mid-market leaders can describe their priorities with clarity. The gap is in the machinery between strategy and execution. Decisions are discussed, socialised and softened, but not recorded in a form that allows the business to act, test and review.
Why decision debt builds up
Decision debt has several causes. Matrix governance can blur accountability between group functions and subsidiary boards. Consensus cultures can make it uncomfortable to record a decision before everyone is fully aligned. Meeting minutes often capture discussion rather than resolution, leaving future readers to infer what was actually agreed. And in fast-growing companies, the informal decision-making that served the founder well at an earlier stage becomes a bottleneck as the organisation adds layers.
The result is predictable. Meetings become revisiting rooms. Management teams prepare papers that reopen old ground. Boards ask for more information without specifying what would be sufficient to decide. Execution slows, not because the strategy is wrong, but because the organisation has not converted intent into a recorded commitment.
The one-page fix
A decision log is not a new governance framework. It is a single page that records the decisions that matter, in a format that can be reviewed and tested. At its simplest, it captures five fields: the decision, the decision owner, the date, the deadline for implementation and the trigger for review.
The discipline lies in the fifth field. A review trigger can be a date, an event or a threshold. For example, a decision to invest in a new regional sales team might be reviewed after two quarters, or earlier if pipeline conversion falls below an agreed level. A decision to renew a major supplier contract might be reviewed if the supplier’s service credits breach a stated threshold. The trigger turns a decision from a one-off event into a managed commitment.
A useful decision log also records the evidence relied on and the options rejected. This need not be lengthy. A short note that the board considered a lease extension, a purchase and a managed exit, and chose the lease extension for cash-flow reasons, is often enough to prevent the same debate returning without new information.
How Williams Nicolson uses the log
In client projects, Williams Nicolson introduces the decision log at the start of the engagement rather than as a closing document. The log sits alongside the workplan and is reviewed at each steering group or board checkpoint. Decisions are captured in the meeting, not reconstructed afterwards. Owners confirm their commitments before the meeting closes.
This changes the rhythm of the project. Meetings become shorter because the purpose is to decide, not to rehearse positions. Accountability improves because each decision has a named owner and a date. And the board gains an audit trail that is useful for internal review, lender conversations and future governance handovers.
The log also gives senior leaders a way to manage upward. When a decision sits with a parent board, an investor or a lender, the log records that dependency explicitly. This reduces the risk of a project stalling while everyone assumes someone else is progressing the matter.
Making it stick
The failure mode for decision logs is over-engineering. A twenty-field template will not be maintained. A single page, reviewed at every meeting, is more likely to become a habit. Boards should start with one committee or one project, run the log for a quarter and then review whether it has reduced repetition and improved delivery.
It is also important to distinguish decisions from updates. A status report is not a decision. A request for further analysis is not a decision unless it specifies what analysis is needed, who will provide it and by when. The log should be reserved for commitments that change the direction or allocation of resources.
Decision debt is not inevitable. It is a governance choice. For UK mid-market firms operating in a demanding economic environment, the ability to decide clearly and review deliberately is a competitive advantage. A one-page log will not solve every execution problem, but it will make the organisation’s commitments visible. That is usually the first step towards keeping them.
