The board decision brief that forces execution

Most board decision briefs are built to be approved. Not to be executed. And that is exactly where they fail after the signature.

Whoever searches for a board decision brief as a template finds a dozen forms in minutes: title, situation, options, recommendation, resolution proposal. They are tidy, and they are complete for their one purpose: getting a signature. The signature releases budget. It does not make the organisation capable of action. Between the agreement on the slide and the first reliable execution lies a gap, and into that gap fall more approved decisions than any board meeting would admit.

The reflex looks for the cause in execution: too few resources, the wrong team, a vendor that does not deliver. From 124 projects in finance, industry and transport I know the pattern from inside, and the cause almost never sits there. The cause sits in the brief. More precisely: in what the brief leaves out. A decision brief is not a receipt for an idea. It is the place where a decision is made executable before the first franc flows. If that place is only half played, execution becomes the place where the decision must be made a second time – this time without a mandate, by the wrong people, at the most expensive moment.

Approved is not executed: what the usual pattern leaves out

The standard pattern is not wrong. Situation, options, recommendation, resolution proposal: all belong in. It is only half the brief. It documents the choice and is silent about the conditions under which the choice becomes execution. Approval and operational decision readiness are not the same. One costs a meeting and a signature. The other costs preparatory work that is uncomfortable because it makes disagreement visible while it still costs nothing.

How expensive this gap becomes shows the documented Blockbuster case. When John Antioco led Blockbuster, he made the decision that could have saved the chain: end the hated late fees, plus an online offering called Total Access. It seriously pressured Netflix. The decision was approved, funded and executed – around 200 million dollars for dropping the fees, as much again for the online platform. It worked. Then Antioco clashed with the board and investor Carl Icahn over his bonus and left the company in 2007; he later described the conflict himself. His successor reversed course to protect short-term profitability. Three years later Blockbuster was insolvent. The decision was not wrong. It was simply never anchored in the company. It was Antioco’s personal conviction, not the shared insight of board and organisation why exactly this path secures the chain’s future. As long as Antioco was in office, he carried it alone. When he left, nobody carried it. Approved, executed, and in the end still not held.

Decision-to-Execution rests on three pillars: decision architecture, fact base and execution mechanics. The usual board pattern carries the first pillar halfway and the other two not at all. That is why it gets approved, and why it sits idle. A brief that is meant to carry leads all three pillars. What that means concretely is in the next sections, and it is less bureaucracy than it sounds.

First pillar: decision architecture

Decision architecture is the part most people take for the whole decision. It is only its beginning, and it itself has three parts, in this order: motivation, clarity, opportunities and risks.

Motivation: the link to the breakthrough goal

The first part of a brief is not the options. It is the why. A vision gives direction like a fixed star, a breakthrough goal makes it concrete, and the decisive question is: What happens if we achieve that? If that answer is not in the brief, the board decides on a means whose purpose nobody has spoken. Such a decision gets approved, but nobody pulls on it.

The why includes the frame: the values the path must not violate and that it should ideally make visible. In the brief, values are not mission-statement text. They work as an admission criterion and decide which variants are even eligible before weighting. The test is hard: A value that cannot exclude any variant is decoration. And a decision that violates lived values rarely fails openly. The organisation executes what it carries and quietly leaves what contradicts it.

Do not confuse this with enthusiasm. Motivation in the sense of the brief is not mood but goal reference: the verifiable chain from this decision to the overarching goal. And this goal reference must be shared, not private. If only one person carries the link between decision and vision, the decision is only as stable as their tenure. That is exactly where Blockbuster broke: the path was right, but nobody except the sponsor linked it to the company’s future, so it disappeared with the sponsor. Where this chain is missing or stays private, no kick-off helps. You cannot talk an organisation into motion if only one person knows where to.

Clarity: the decision question and the option space

The second part is the method. Clarity begins with a decision question that stands in one sentence and forces a choice: “Does the institute stay in the SAP stack for its analytics and AI capabilities over the next 36 months, with BDC, Datasphere and the embedded Databricks integration, or does it migrate step by step to an open lakehouse approach with SAP only still as a source system?” That is how I recently formulated the question for a real platform decision. Only when it stands that sharp does it become visible whether a decision is being made at all or whether a direction is only being approved.

That includes an option space worthy of the name: at least three seriously meant options, and the most uncomfortable one belongs in, the one nobody internally wants to represent because it touches vested interests. A preferred solution flanked by two deliberately weak alternatives is not a search space. That is theatre with a resolution proposal. And discarded alternatives do not disappear: they return as doubt as soon as the first difficulty appears.

How that ends shows the same case. My recommendation in the end was neither of the two poles from the question, but the third variant: hybrid. The SAP stack keeps the data with strong SAP context – cost-centre hierarchies, for example – the open lakehouse carries everything else, and both are linked via Delta Sharing, the open standard for data exchange, on the SAP side via the Business Data Cloud. A binary brief would never have found that answer. The option space forced it.

Opportunities and risks: the view that withstands headwind

The third part is the honest flip side. A brief that only shows opportunities is a sales slide, not a decision basis. Robustness comes from the inverted question: How does this decision fail for sure? That includes a risk register with countermeasures and owners and kill criteria set before the investment, not rationalised afterwards. How do we recognise that this direction was wrong, and what happens then? Whoever answers that question before release buys the organisation permission to stop later without losing face.

This flip side is only as valuable as the numbers it stands on. That leads to the second pillar.

Second pillar: the fact base with which the decision can be defended

Opportunities and risks hang on numbers, and numbers in the meeting room are rarely what they pretend to be. The fact base is the pillar that makes a brief testable: reliable, navigable, traceable data that work as mirror, navigator and touchstone. The hardest check before the signature is a single question: Does the same question next week lead to the same number, and who in the room can explain the derivation?

Where the answer is “we would have to look it up”, the brief is not evidence but a liability risk. An approved number nobody can reproduce becomes an attack surface as soon as a committee, an auditor or a supervisory body asks. A decision must be defensible: the number can be reproduced, the derivation explained, the choice justified. In regulated houses that is not a luxury. It is the difference between a decision that holds and one that is withdrawn at the first headwind.

Third pillar: execution mechanics from ownership, gates and cadence

The third pillar is the one that stands in no standard pattern, and the only one that turns a resolution into change. Its three elements are called ownership, gates and cadence, and all three belong in the brief, not in the project.

Ownership first. Approval is not a decision. Ownership is a decision. The difference shows in a single moment of the release meeting. Someone asks the room: “Who takes responsibility for this topic?” Either a person now answers with a full sentence: “I will ensure the new steering logic is productive on 31 March.” Or nobody answers, eyes wander, and the minutes finally say “responsible: team”. A committee can agree. Only a human can take responsibility – one, with a name, with the mandate to say no as well. If that name is missing in the brief, responsibility after the meeting wanders back to where nobody can grasp it, and the decision dissolves into responsibilities. Before release the name question is a clarification question. After release it is a power question, and power questions are not solved in project meetings – they are sat out.

Then the gates. In daily work a gate is nothing exotic: a fixed date with a single question – continue or stop – with criteria, date and an owner. More important is what a gate is not. It is not control from above. Trust motivates, distrust demotivates, and whoever sniffs after the team harvests cover instead of progress. A gate is previously agreed control: it checks outcomes instead of behaviour and is therefore experienced as a resource, not a threat. The team keeps full freedom in the how. What is checked at the agreed date is the what. Without such dates an initiative cannot fail and therefore also cannot succeed: it runs on long after it is clear it should have stopped.

Finally cadence. Translated: fixed dates before it burns. The same beat, the same deliverables, the same decision points, whether the sponsor sits in the room or not. Pace without cadence is haste. Cadence is leadership. It is the quietest of the three elements and the most consequential, because only it keeps the decision alive when the sponsor changes and the original energy is long elsewhere. You recognise a real cadence by a simple feature: the meeting still happens when the boss is missing.

What it costs: the calculation behind the sequence

These three pillars feel like avoidable effort until you calculate. Take a platform decision worth 5 million whose benefit starts on the day of productive use. If the operational half is clarified “in the project” and execution therefore shifts by six months, what counts is not the project budget but the missed benefit per month. In the regulated and data-intensive houses I work with, this cost of delay has an experience-based range: several hundred thousand to over a million per month. Six months of shift in that order of magnitude is a seven-figure loss, and it appears in no post-calculation because nobody carries it as a line item. That is a model calculation with a range from real decision situations, not a measurement.

This sum is the price of the half brief. It is also why “we’ll clarify that in the project” is the most expensive sentence in many release meetings. How you determine the range for your own house is on our offering page on cost of delay.

Where the full brief would be wrong

Not every decision deserves this effort. Jeff Bezos described the difference in the 2015 shareholder letter as doors: some swing back easily, others open only one way. For the first kind, fast release with clarification in doing is the right choice. The three pillars apply to the second: for decisions with high stakes, long commitment and hard reversal – for the platform that carries five years, for the steering logic a group hangs on. There the complete brief is not bureaucracy but the cheapest insurance there is.

Not the platform is wrong. It is premature. Whoever implements before the brief stands makes technology the answer to a question nobody asked. Afterwards the organisation aligns to the vendor’s roadmap, not to its own judgement. Why that costs more than money – money comes back, authority does not – is set out there.

What these initiatives rarely lack is enthusiasm. What is missing is the goal reference that carries the enthusiasm, and the mechanics that survive it. Both belong in the brief, and both are cheapest before the first franc. Take the next board decision-brief pattern on your desk and check it against these five elements: Is the why with reference to the goal in there, including the values the path must not violate? Is the decision question in one sentence, with three seriously meant variants? Are opportunities and risks built on numbers that still hold next week? Does one person carry the outcome? Do gates and a cadence run that hold without the sponsor? Where you hesitate, you have found the place where the decision is just being made a second time – in the project, by the wrong people.

If you want the one-page pattern with which I make these five elements testable before release, book a short conversation. I will send you the Decision Brief, the decision template that turns an approval into an executable decision.