Executives and managers constantly face critical choices. The problem isn’t a lack of information but an overload of it. Meetings often stretch for hours while teams sift through dense reports or bloated decks. Decisions stall, energy fades, and nothing concrete emerges. The Five-Slide Decision Brief exists to fix that. It structures information into five focused slides that lead a group to clarity in ten minutes.
This is not a stylistic trick. It is a repeatable method. Each slide has a strict role. Together, they create a funnel that starts broad and narrows to a precise outcome. Used consistently, the model cuts wasted time, keeps leaders aligned, and ensures meetings end with a choice instead of an open question.
Defining the Problem
The first slide frames the core issue. It should be a single sentence, not a paragraph. That sentence captures what changed, what’s broken, or what requires a decision. A good example is: “Support costs increased 40 percent in the last quarter, pushing us over budget.” That line is specific, measurable, and tied to an impact.
The mistake many presenters make is treating the problem slide like an executive summary, filled with context and detail. That misses the point. The job of this slide is to fix the group’s attention.
Providing Context
Once the problem is visible, the second slide provides context. This is not the place for an elaborate history. It should give only the facts that make the problem real: numbers, timelines, benchmarks. If costs are the problem, context might show how those costs compare year-over-year, how they relate to revenue, and where they stand against peers.
When context expands too far, it dilutes focus. Leaders do not need spreadsheets or twenty-row tables at this moment. They need orientation, not education.
Presenting Options
The third slide introduces possible paths forward. Options should be written plainly and kept to three to five. Avoid adjectives, promises, or persuasive language. At this stage, the audience needs visibility into what can be chosen, not a push in one direction.
Example options for the support cost problem could be:
- Invest in automation to reduce headcount.
- Outsource overflow support to a vendor.
- Freeze feature development to reassign staff.
Weighing Trade-offs
The fourth slide moves from possibility to consequence. It spells out the trade-offs for each option. This is the heart of the brief, because leaders want to see not just what can be done but what must be given up to do it.
Automation saves money long-term but requires upfront investment and slower product launches. Outsourcing creates immediate relief but reduces control and introduces vendor risk. Freezing features conserves cash but frustrates customers and slows growth.
This stage benefits from the same principle that applies in other areas of decision-making: focus only on the factors that change the choice. Irrelevant detail wastes time. It’s similar to tools outside business that deliver only what matters. For example, when buying a car, a DMV VIN lookup gives you title history, accident records, and registration data — facts that change your decision. It does not drown you in trivia. The trade-offs slide should follow the same standard. Highlight what changes the decision and cut everything else.
Reaching the Decision
The final slide closes with a clear recommendation. It does not recap the deck or hedge with multiple possibilities. It ties back to the problem and states the option that solves it. For the support cost issue, the decision might read: “Recommendation: Outsource overflow support (Option 2). This addresses the budget overrun immediately. While control decreases, risk can be managed with strict contracts.”
This matters because leaders gather to make choices, not to hear analysis for its own sake. A strong decision slide provides closure. It shows that the process has done its job and directs the team to act.
Applying the Framework in Practice
The model adapts easily across industries and scales. A nonprofit board weighing new programs, a city council evaluating infrastructure bids, or a product team debating feature investments can all apply the same structure. The content changes, but the logic stays constant. Every decision needs a problem, context, options, trade-offs, and a decision.
Teams accustomed to sprawling decks often resist the discipline at first. Compressing information feels uncomfortable. But the results speak quickly. Meetings shorten, leaders feel respected, and decisions arrive faster
Avoiding Common Pitfalls
Misuse often comes in two forms. First, presenters try to pad the brief with extra slides or context that belongs in an appendix. That breaks the flow. If the problem cannot be stated in one sentence, the issue is not ready for a decision. If context requires a deep dive, it belongs in a separate session.
Second, some presenters stop short on the decision slide. They close with “further analysis required” or “several paths are possible.” That undermines the entire purpose. The model demands a recommendation. Even if the final authority rests with the audience, the presenter must show their reasoning by naming a choice.