A useful decision paper makes the choice easier to understand without making the uncertainty disappear.
An executive paper can contain substantial analysis and still leave the reader unsure what they are being asked to decide. Background occupies the opening pages. The preferred option appears inevitable. Implementation consequences emerge only after approval.
The discipline is to organise the paper around the decision rather than around the work undertaken to prepare it. Readers should be able to see the choice, the reasons for it and the obligations it creates without reconstructing the author's argument.
The Financial Reporting Council's guidance emphasises timely information, constructive challenge and attention to the quality of decision-making. Its guidance is a useful reference for paper design; the approach below is an editorial framework, not a statement of the requirements applying to every organisation. FRC: Corporate Governance Code Guidance.
State the decision on the first page
Begin with a precise request. Identify what should be approved, by whom, by when and within what limits. Make clear whether the paper seeks a decision, advice, endorsement of a direction or permission to investigate further.
“Support the transformation” leaves too much open. A more useful illustrative request would ask leaders to approve a defined discovery phase, assign an accountable sponsor and confirm the questions that must be answered before implementation is considered.
The wording should match the authority of the forum. A committee that can recommend a choice should not be asked to treat that recommendation as final approval. If another decision follows, show the sequence and explain what this meeting can settle.
Explain why the choice is needed now
Set out the problem in terms the decision-maker can test. What is happening? What evidence indicates that action is needed? What is the consequence of waiting?
Separate urgency created by an external constraint from urgency created by an internal target. Both may matter, but they carry different implications. A date should not become the justification for a proposal merely because it has appeared in previous plans.
Keep the background proportionate. Include the history that changes the decision, then move supporting chronology and technical detail to an appendix. The main paper should preserve the line of reasoning.
Distinguish evidence, assumptions and judgement
Explain which statements are observed facts, which are planning assumptions and which represent management's assessment. The reader should not have to infer the level of confidence from the tone of the writing.
For each material assumption, identify its basis, the owner responsible for testing it and what would change if it proved wrong. Where estimates depend on incomplete information, show a credible range or describe the uncertainty instead of presenting unsupported precision.
Include evidence that challenges the preferred option. A paper becomes more useful when leaders can see where reasonable people might disagree and which unresolved issue could alter the recommendation.
Compare alternatives on a consistent basis
Present options that could credibly be chosen. Do not make one option fully developed while describing the others so weakly that they function only as a backdrop.
Agree the comparison criteria before scoring. Depending on the decision, these might include strategic fit, service impact, implementation capacity, dependencies, reversibility and exposure to uncertainty. Explain any weighting that materially affects the conclusion.
Include the current course or minimum-change option where it is feasible. If it is not viable, explain why. Treating inaction as an alternative does not mean assuming it is consequence-free; it means making those consequences visible.
A score can help organise a discussion, but it should not hide a decisive trade-off. Explain why an option remains preferable when it performs less well on an important criterion.
Test the recommendation against a difficult scenario
Ask what could happen that would most seriously weaken the case. The purpose is to expose fragility before approval and decide whether it can be managed.
In a hypothetical service redesign, the recommendation might depend on another team accepting work. Test the consequence of that team being ready later than planned. Would the organisation maintain the current service, reduce the first phase or postpone implementation? Who would make that call?
Distinguish a manageable variation from a condition that invalidates the proposal. Where uncertainty is material, a staged decision may be more useful than a single approval covering the whole programme. State the evidence and authority needed to move between stages.
Show what approval commits the organisation to do
A recommendation should make its operating consequences explicit. Identify who will lead implementation, what capacity is needed, which decisions follow and what must stop or change elsewhere.
Separate resources already available from resources that still need agreement. Name critical external dependencies and describe the position if they do not materialise. Do not treat expressions of support as confirmed commitments.
The paper should also define how the decision will be reviewed. What evidence will show whether implementation is working? Which change in circumstances would trigger reconsideration? A review point is useful when it has a decision purpose, not simply a reporting date.
Design the meeting for challenge
Use the paper to prepare the discussion, then use the meeting to resolve the judgement. A presentation that repeats the full document can consume the time needed to examine the choice.
Open with the decision request, the most important trade-off and the matter on which leadership judgement is required. Invite challenge to the assumptions that carry the recommendation. Clarify unresolved issues before moving to approval.
Record the decision as it was actually made, including conditions, boundaries, dissent where relevant and the person responsible for follow-through. If the forum has asked for more evidence, identify the question to be answered rather than commissioning a general rewrite.
A final editorial review
Before circulation, ask a colleague unfamiliar with the analysis to read the opening page. Can they explain the choice and its consequences accurately? If not, the paper still relies too heavily on knowledge held by its authors.
Then check the full document against five questions:
- Is the requested decision specific and within the forum's authority?
- Are the alternatives credible and compared consistently?
- Are assumptions and areas of uncertainty visible?
- Are the recommendation's operating consequences explicit?
- Is there a clear owner and review point after approval?
Conciseness should come from removing repetition and sharpening the argument. It should not come from omitting the evidence or trade-offs needed to make an informed choice.
Executive questions
- Which unresolved issue could change our recommendation?
- Have we made a real choice visible, or only presented a preferred solution?
- What will the organisation be committed to do the day after approval?
- What would cause us to revisit the decision, and who would bring it back?
JP Associates helps Boards and executive teams frame strategic choices, test operating implications and develop concise decision material that supports informed challenge and practical action.