The Gap Between Idea and Decision
A workshop can generate twenty strong ideas in a morning. Without a disciplined brief structure, all twenty will be presented in formats that require substantial additional work before an executive can act on any of them. A slide deck needs a cost estimate. A verbal pitch needs a risk assessment. A one-liner needs strategic context. Each of these additions takes time, and time is where ideas go to die.
The strategic brief is the bridge between the workshop and the boardroom. It is the format that allows an executive to read a concept, understand its implications, and make a resource allocation decision — without requiring additional meetings, additional research, or additional documentation.
Getting this format right is not primarily a writing problem. It is a structural problem. The question is not "how do I write about this idea?" but "what does an executive need to know, in what order, to make a decision about this idea?"
What Makes a Strategic Brief Executive-Ready
Executive-ready briefs share four characteristics that distinguish them from the ad-hoc outputs of most workshops.
One-page discipline. An executive who must read a 12-page document to understand a strategic concept will not give it the same quality of attention as a concept presented in a single structured page. This is not intellectual laziness — it is the rational response to a finite attention budget. The one-page constraint forces the brief author to prioritise ruthlessly. Everything that cannot fit on one page is either secondary information (which belongs in an appendix) or unclear thinking (which the constraint exposes).
Risk-first structure. Most brief authors present the opportunity before the risk, because the opportunity is more exciting to write about and more likely to attract initial interest. Executive readers with significant experience have learned to look for the risk before committing their attention to the opportunity. A brief that leads with a clear risk statement — "The principal risk in this concept is X, which we assess as [probability/impact] and can be mitigated by Y" — signals analytical rigour and saves the executive from having to search for the risk in the document.
Clear recommendation. A brief that describes a situation without recommending an action does not enable a decision — it enables a discussion. The recommendation should be explicit: not "we should consider this" but "we recommend allocating £X and 60 days to test assumption Y, with a go/no-go review at day 30." A specific recommendation with a specific ask allows the executive to say yes, say no, or propose a modification. A vague recommendation produces a deferred decision.
Appropriate brevity. The correct length of a strategic brief is the length required to answer the executive's four core questions: What is the opportunity? What is the evidence? What do you recommend? What is the risk? These four questions can typically be answered in 400–600 words. More is not more rigorous — it is usually less disciplined.
The Four-Component Brief Structure
Component 1: Opportunity Statement (80–100 words)
The opportunity statement answers two questions: what is the problem or gap being addressed, and why does it matter now? The "why now" element is critical. An opportunity that has existed for five years without being addressed requires an explanation of what has changed — in the market, in technology, in competitive dynamics, or in the organisation's capabilities — that makes it actionable at this moment.
A strong opportunity statement is specific and falsifiable. "There is an opportunity to reduce supplier onboarding time by 30–40% by restructuring the three-stage validation process, which currently operates sequentially and involves three separate approval authorities" is a specific, evaluable claim. "There is an opportunity to improve operational efficiency in our supply chain" is not.
Component 2: Evidence Base (100–120 words)
The evidence base presents the key data, observations, or validated assumptions that support the opportunity statement. It is not a comprehensive literature review — it is a concise summary of the strongest evidence the brief author has available.
The evidence base should be honest about its limitations. If the key evidence is market research from a comparable market rather than direct customer data, say so. If the financial projection is based on an assumption that has not been validated, flag the assumption explicitly. An evidence base that overstates its certainty loses credibility with experienced executives who will probe its foundations.
Component 3: Recommended Action (100–120 words)
The recommended action specifies what the organisation should do, at what resource commitment, over what time horizon, and with what success criteria. The specificity of the recommendation is directly related to its decision-enabling quality.
The recommended action should include: the specific next step (not a general direction), the resource requirement (budget estimate and time commitment), the decision-maker responsible, the first review milestone, and the criteria for a go/no-go decision at that milestone.
A recommendation structured this way allows an executive to approve a time-bounded, resource-constrained test of the concept rather than making an open-ended commitment. This lowers the decision threshold and increases the probability of a yes — without committing more than is warranted by the current evidence.
Component 4: Risk and Mitigation (80–100 words)
The risk section presents the one or two highest-impact risks associated with the recommended action and the proposed mitigation for each. It does not need to be exhaustive — a brief that lists fourteen risks has not prioritised them.
The risks should be specific and consequential: "If assumption X is wrong, the project fails" is a useful risk statement. "There may be unexpected challenges in implementation" is not. For each material risk, the brief should propose a mitigation that is proportionate to the probability and impact assessment.
Common Brief Failure Modes
Too long. The most common failure. A brief that runs to four pages is not a brief — it is a report. Trim to one page, including the risk section.
Buried recommendation. Executives who must read three pages to find the ask will not find it reliably. The recommendation should be explicit, early, and visible. Some brief formats put it at the top.
No clear ask. "We should explore this further" is not a recommendation. "We recommend a 60-day test with £50k, a go/no-go review at day 30, and a named owner from the operations team" is a recommendation.
Assumed context. A brief written by the person who developed the idea contains contextual assumptions that the reader does not share. Review every brief with the question: "If I had not been in the workshop, would I understand this?" If the answer is no, add the necessary context.
Optimism without evidence. Projections that are not grounded in a stated methodology or comparable benchmark invite scepticism. If you are projecting a 30% improvement, cite the basis for that number.
Producing 20 Briefs from a Morning Session
The operational challenge is producing a large number of executive-ready briefs quickly — before the momentum from the session dissipates. Manual brief writing, post-session, by the facilitation team typically produces 4–6 briefs per day of effort. A morning session that generates 20 strong ideas would require 3–5 days of brief writing before the first executive review is possible.
The alternative is to design the session submission format as a brief pre-structure. When participants submit ideas using the four-component template — filling in the opportunity statement, evidence base, recommended action, and risk section as part of the submission process — the raw brief material is captured during the session itself. The post-session work becomes editing and quality assurance rather than original authorship.
This is the design logic behind platforms like CoVision: participants submit structured ideas that map directly to the brief components, and the synthesis layer produces formatted output documents during the session. The result is that 20 ideas can produce 20 executive-ready brief drafts by the close of the morning session — ready for facilitator review and distribution on the same day.
