Plan the reading order
Supply the audience, decision, source material and required coverage. Review the outline before generating. For a QBR, keep results, variance, risks and next decisions distinct instead of mixing them into a status collage.
How to Structure a Consulting Deck
A consulting deck has one job: to make an executive audience act on your recommendation. The firms that do this best follow a defining rule — lead with the answer — and a repeatable slide sequence built on the pyramid principle, action titles, and one idea per slide. Here is that structure, slide by slide, plus how to build it fast in Gixo Lumen.
Lumen · real output
Read the deck before you choose the workflow.
Open an actual exported deck, then compare its outline, source constraints and slide choices with the job you need to finish.
Grid-Scale Battery Storage: Where the 2026 Buildout Is Concentrated
A 12-slide client strategy deck on where planned U.S. solar and battery storage additions concentrate in 2026, built only from two EIA articles: the national buildout, the leading states for solar and for storage, the named projects, and a recommended order of attention. It reaches its answer at the end.
Inspect the source brief or data
A consulting-style handoff for the leadership team of an electricity business that is deciding where to look first as new solar and battery storage capacity is built; no client is named and none is described. Frame the situation, the analysis the supplied pages support, a recommendation and an action plan. Every figure must come from the supplied pages. The client's own numbers are not known, so recommend in terms of what the pages show, and use no placeholders and no made-up client metrics. Workflow: Consulting and strategy. 12 slides requested. Documents supplied as text (EIA, "Solar, battery storage to lead new U.S. generating capacity additions in 2025 (Today in Energy)", https://www.eia.gov/todayinenergy/detail.php?id=64586; EIA, "New U.S. electric generating capacity expected to reach a record high in 2026 (Today in Energy)", https://www.eia.gov/todayinenergy/detail.php?id=67205).
Read the sample review notes
A separate reviewer agent read the deck’s 74 claims, slides and speaker notes, against the two EIA articles: 53 are supported, 5 loosen or go a little beyond their wording, 16 are in neither article and none contradicts one. All 16 are advice or a judgement about which market to take first, such as “Start the solar market scan in Texas.” It is not a person’s review.
Refine at the right scope
Edit structured slide fields, preview field alternatives or review a whole-slide rewrite. Ask Lumen can propose wider changes; inspect and select the changes before applying them to the saved deck.
Inspect the actual handoff
Check charts, speaker notes, images and contrast in presentation view and the downloaded file. A new-period deck is a separate draft with changed values and sources to review.
Outline planning and field alternatives
Choose a creation mode and workflow profile, supply source material and review the planned coverage. Slide fields have layout-specific budgets. Field assistance offers alternatives with rationale and word counts; whole-slide refinement shows field-level changes. Ask Lumen can propose wider structural edits, which require a reviewed preview before application.
Data, themes and the next reporting period
Paste spreadsheet rows, choose header handling and preview replacement chart data. Where offered, select Business metrics explicitly and inspect their source receipt. Review changes in values and sources before accepting a next-period draft. Theme controls cover brand colors, type, logo placement, background and contrast choices; a custom theme still needs visual review.
Presenting and the exported deck
Inspect full-screen and audience views, speaker notes, next-slide preview, navigation and timer. Check PDF and PowerPoint separately. Supported elements can become native editable shapes or charts; complex visuals can use a flattened fallback. Speaker notes and per-slide handoff choices should be inspected in the actual file.
PowerPoint export is hybrid: supported content may remain editable while complex visuals can be flattened. Conversion between a responsive story and slides requires a preview; it is not lossless.
Start fast from a topic, or plan from notes and reference material
Outline-first workflow with citations and evidence checks before delivery
34 active themes across 8 workflow profiles
Present, share, and export from the same finished deck
Additional product example
The three rules that define a consulting deck
Answer first. Barbara Minto's pyramid principle is the backbone of every great consulting deck: state your recommendation up front, then support it with grouped, MECE arguments, then back those with evidence. Executives do not want a mystery novel that builds to a reveal — they want the conclusion, then the reasons. If a partner read only your executive summary, they should already know what you are recommending and why.
Action titles. Every slide's headline should state the takeaway as a full sentence — "Two accounts drive 60% of churn; concentrate retention there" — not a label like "Churn analysis." Read the titles top to bottom and they should tell the whole story on their own. This is the single biggest difference between an amateur deck and a firm-quality one.
One idea per slide. Each slide makes exactly one point, and the body proves the title. When a slide tries to say three things, the audience remembers none of them. The sequence below applies these rules from the cover through the appendix — adapt the number of slides per section to your engagement, but keep the order.
One more discipline separates firm-quality work: a consulting deck usually has to work in two modes at once. It has to support a live read-out, where you talk over lean slides and the room follows your voice, and it has to stand alone as a leave-behind — the document a sponsor forwards to people who were never in the room. Those two jobs pull in opposite directions, and the action title is what reconciles them. When every headline states its takeaway as a sentence, the argument survives without a presenter: a reader who only skims the titles still gets the whole story, while the live audience gets the detail beneath each one. Write the deck for the skim-reader first, and the presented version takes care of itself.
The consulting deck, slide by slide: the executive summary slide, then the proof
Nine sections from framing to roadmap. Each is one to a few slides, with an action title.
1
Cover & engagement context
Client, engagement, audience, and date, with a one-line statement of what this readout delivers. Orient the room on whose decision this informs and what stage of the engagement they are seeing. Keep it clean — the cover sets the tone for whether this reads as a credible, firm-quality document.
2
Executive summary — the answer, first
State your recommendation in the first content slide, with the two or three reasons that support it. This is the pyramid principle in practice: conclusion at the top, governing arguments beneath. A time-pressed executive should be able to act on this slide alone; everything that follows is proof for those who want it.
3
Situation & complication
Frame why the client is here using the SCQA pattern — the stable situation, the complication that disrupted it, and therefore the question that must be answered. This builds shared context and earns agreement on the problem before you propose a solution. Done well, the audience is nodding before you reach a single finding.
4
The governing question & scope
State the central question the work answers and the boundaries of scope — what is in, what is out, and the success criteria. A crisp question keeps the deck disciplined and pre-empts the "but what about…" tangents. It also signals rigor: you defined the problem before you went looking for answers.
5
Approach & analytical framework
Show how you got to the answer: the framework, the MECE workstreams, the data sources, and the analyses run. Keep it to the logic, not the project plan. The point is to give the recommendation credibility — the audience should trust the answer because they trust the method behind it.
6
Findings & insights
The evidence, one insight per slide, each with an action title that states the so-what. Resist the urge to dump every analysis — show the findings that drive the recommendation and move the rest to the appendix. Each chart exists to prove its title; if it does not, cut it.
7
Recommendations
Translate findings into a prioritized set of recommendations, each with its rationale and the trade-offs you considered. Sequence them by impact and feasibility so the client sees where to start. This is the heart of the deck — make the recommendations specific enough to act on, not platitudes.
8
Implementation roadmap
A phased plan: workstreams, owners, milestones, dependencies, and the quick wins that build momentum in the first 90 days. Recommendations without a path to execution rarely survive contact with the organization. Showing the "how" and "when" is what turns a strategy deck into a mandate.
9
Business case, risks & appendix
Quantify the expected value, the investment required, and the payback, then name the key risks and mitigations. Put the detailed models, methodology, and supporting analyses in an appendix so the core deck stays tight. The appendix is your credibility reserve — it answers the deep-dive question without cluttering the argument.
Common consulting-deck mistakes to avoid
- Building up to the answer. Saving the recommendation for the end is the most common error. Lead with it — this is not a thriller.
- Descriptive titles. "Revenue analysis" says nothing. The title must state the insight as a sentence.
- Framework theatre. A 2x2 or a five-force chart for its own sake adds no value. Use a framework only when it sharpens the argument.
- Data without a so-what. Every chart needs a conclusion. If you cannot write the action title, the slide does not belong.
- Recommendations with no roadmap. "What" without "how and when" rarely gets executed.
What people mean by “McKinsey slides”
Search for McKinsey slides and most of what comes back is a look: dense charts, a lot of grey, a red accent. The look is the least transferable part. What actually distinguishes slides from the big strategy firms is a set of writing disciplines that any team can adopt, and they are the same disciplines this page has been describing.
The title is the argument. Every headline is a full-sentence takeaway, so the deck can be read by titles alone. This is Minto's pyramid principle applied at slide level, and Minto developed it at McKinsey — which is why the two ideas travel together.
The body proves the title, and nothing else. One idea per slide. Any chart that does not support its own headline either gets a new headline or moves to the appendix. It is a brutal test and it removes about a third of most first drafts.
The structure is MECE. Groupings are mutually exclusive and collectively exhaustive, so a reader can tell that nothing overlaps and nothing is missing. That is what makes a firm deck feel rigorous rather than merely thorough.
The deck is storyboarded before it is built. Consultants sketch the sequence as empty slides — a ghost deck — with the intended title on each one and a note of the exhibit that will prove it. The argument gets reviewed while it is still cheap to change, which is exactly what the outline-first workflow below is for.
Every exhibit says where it came from. A source line under each chart is not decoration; it is what lets a client challenge a number without challenging your credibility. Decks that skip it are the ones that lose a meeting to a single unanswerable question.
The visual signature is a house style you should not copy — your client's brand, not the firm's. The five habits above are the part worth taking.
Build the consulting deck in Gixo Lumen
Lumen's consulting workflow shapes the deck around answer-first structure — so you spend your time on the thinking, not the formatting.
Source Grounding & Evidence Checks
Keep decks grounded to source material and approved web research when needed. Gixo extracts key claims, highlights what needs verification, and surfaces citations, attribution, and trust status inside the deck viewer.
Consulting-aware structure
8 workflow profiles across consulting, finance, startup, sales, executive, product, training, and general business decks. The consulting workflow drafts the situation-to-recommendation arc above, not a generic slide template.
Start from your analysis
Build from a topic, notes, briefs, articles, and uploaded reference material. Bring your findings and Lumen drafts the framing, findings, and recommendation slides for you to sharpen.
Finish in one workspace
Create a client-handoff presentation in one workspace, with outline planning, workflow-specific structure, slide editing, citations, presenter tools, and export attached to the same deck.
Deliver client-ready
present mode, speaker notes, timer, and shareable delivery. Export to PPTX, PDF, HTML, and slide images for the client read-out and the leave-behind.
Why consultants use Lumen for client-ready decks
The job is not to generate slides once. The job is to hand off a deck another person can actually open, review, and use.
Workflow fit
The deck starts from a consulting, finance, fundraising, sales, executive, product, or general-business workflow instead of generic slide filler.
Outline first
Structure stays reviewable before full generation, so the first pass is shaped like a real deck instead of a prompt experiment.
Editability
Theme switches, layout swaps, slide edits, and regeneration all happen after the deck exists without forcing a rebuild.
Evidence
Decks are grounded in your sources, and evidence — citations, trust checks, source review — has a built-in home in the workspace instead of being bolted on after generation.
Delivery
Speaker notes, present mode, shareable delivery, and exports stay on the same finished deck when it is time to ship.
From analysis to client-ready in four steps
1
Bring your findings and recommendation
Add your analysis, the question you answered, and your headline recommendation. Lumen uses it to draft the deck in answer-first order.
2
Generate the structured deck
Get a draft with executive summary, situation, approach, findings, recommendations, and roadmap — in a clean, professional theme.
3
Write the action titles and attach evidence
Sharpen each title into a takeaway, drop in your charts, and attach citations so claims are traceable for a skeptical client.
4
Present and leave behind
Present with speaker notes, then export the deck as the client leave-behind in the format they expect.
Consulting deck structure: FAQ
What is the pyramid principle in a consulting deck?
The pyramid principle, from Barbara Minto, means leading with your conclusion, then supporting it with grouped, mutually exclusive arguments, then backing those with evidence. In practice it means putting your recommendation in the executive summary up front rather than building to it at the end — executives want the answer first, then the reasons.
What are action titles?
Action titles are slide headlines written as full-sentence takeaways — "Two accounts drive 60% of churn; concentrate retention there" — rather than labels like "Churn analysis." If you read every title in order, they should tell the whole story. Action titles are the clearest marker of a firm-quality consulting deck.
How long should a consulting deck be?
Keep the core narrative tight — often 10–20 slides for the live read-out — and move detailed models and supporting analysis to an appendix. The discipline of answer-first structure plus one idea per slide naturally keeps the main deck focused. The appendix can be as long as the rigor demands.
What is the SCQA framework?
SCQA stands for Situation, Complication, Question, Answer. It is a storytelling pattern for the opening of a consulting deck: describe the stable situation, introduce the complication that changed it, state the question that follows, and then give your answer. It builds shared context and earns agreement on the problem before you recommend a solution.
What are McKinsey slides?
The phrase usually describes a look — dense charts, a lot of grey, a red accent — but the transferable part is a set of writing disciplines: full-sentence action titles so the deck reads by titles alone, one idea per slide with a body that proves the title, MECE groupings so nothing overlaps and nothing is missing, a storyboard or "ghost deck" reviewed before slides are built, and a source line under every exhibit. Adopt those five and the deck reads like firm work regardless of the visual style you use.
How do you write the executive summary slide of a consulting deck?
Lead with the recommendation as a full sentence, then the two or three governing arguments that support it, each one a line rather than a paragraph. Assume it is the only slide a time-pressed partner or client executive reads in full, and that it will be forwarded on its own. Write it after the findings exist: an executive summary drafted first summarises intentions rather than conclusions, and that gap shows in the first question from the room.
Can Gixo generate a consulting deck automatically?
Lumen generates a structured first draft in answer-first consulting order from your findings, with workflow-specific structure and fully editable slides. It is a strong first pass you refine with your real analysis, action titles, and judgment — the deck is yours to finish and defend in front of a client.
Updated
More from Gixo