strategy and transformation delivery
What goes in an executive decision pack?
Give leaders the evidence, options and implications required to make one consequential call.
Write the decision as a choice
Open with one sentence stating what the leadership team is being asked to decide, by when and why the timing matters. Avoid topic headings such as ‘AI platform update’ or ‘operating model discussion’. A decision statement names the commitment: whether to invest, which route to choose, what to stop or who will own the next phase. Include the consequence of delay so urgency can be judged rather than performed. A precise opening lets every later page earn its place by helping the reader make that choice. If the question changes during the work, update it openly.
Separate evidence, assumptions and unknowns
Summarise the information that materially affects the choice and link to deeper sources rather than reproducing every document. Mark what is known, what has been estimated and what remains uncertain. State the reliability and date of important evidence. This protects the decision from false precision and helps leaders see where another week of analysis could genuinely change the answer. Unknowns do not automatically block progress; some can be handled through conditions, staged investment or review triggers. The pack should make that reasoning visible instead of burying uncertainty in footnotes or optimistic forecasts.
Present genuinely viable options
Include the status quo or do-nothing route when it is a real choice, with its cost and risk made explicit. Describe each option consistently across value, cost, timing, capability, dependencies, risk, reversibility and effect on people or customers. Do not create a weak straw option to make the preferred recommendation appear inevitable. Where routes can be sequenced, show that too: a bounded first move may preserve options while generating evidence. Leaders need to understand the trade-offs they are accepting, not simply the features of each solution. A comparison table is useful when it reflects real criteria rather than decorative scoring.
Connect financial logic to operating reality
Set out investment, ongoing cost, expected value, timing and the assumptions linking activity to benefit. Distinguish cash savings, avoided cost, returned capacity, revenue potential and risk reduction; they behave differently. Explain which workflow, behaviour or customer outcome must change before the value appears. Include implementation effort, specialist support, human review and maintenance. A technology benefit that assumes perfect adoption or free internal time is not decision-ready. Use ranges or scenarios where uncertainty is material, and specify the evidence that will determine whether further funding is released.
State the recommendation and dissent
The author should make a clear recommendation, explain why it best meets the agreed criteria and identify the conditions attached to it. Capture material stakeholder disagreement accurately, particularly where risk, feasibility or operating impact is contested. Consensus is not always possible and should not be manufactured through vague language. Leaders are better served by an honest view of the unresolved trade-off and the person accountable for accepting it. State what would change the recommendation. This keeps later debate focused on new evidence rather than repeatedly reconstructing the original reasoning.
Finish with mobilisation and review
A decision creates value only when it changes work. End with the immediate actions, accountable owner, decision rights, required communication, funding route, dependencies, success measures and first review date. Identify specialist approvals or assurance that must occur before execution. Record the decision in an organisational log with the reasoning and review trigger. The next phase should be proportionate: some decisions need a full programme, while others need a named owner and a two-week test. The pack is complete when somebody can act without arranging another meeting to work out what the decision meant. Circulate the signed-off decision to everyone whose work or expectations change, and retire superseded drafts so the organisation has one authoritative position. At the first review, examine evidence and assumptions rather than rewarding activity. A review date is the point at which the business decides whether to continue, adapt, expand or stop.
Put the answer to work
Use this guidance against one live decision rather than treating it as a general checklist. Name the outcome, owner, evidence and next review point, then record what the business will do differently. Where the choice carries material legal, technical, financial, security or people consequences, bring the relevant specialist into the decision while keeping business ownership explicit.
What to carry into the work
- Open with one precise decision statement
- Separate facts from assumptions and unknowns
- Compare viable options using consistent criteria
- End with ownership, mobilisation and a review trigger