Most strategy decks are built from a small set of recurring slide types. This is the working catalog — the issue tree, the 2x2, the waterfall, the roadmap, the driver tree — with what each one is for and how to build it so it survives a partner review.
Strategy slides are not a genre of design. They are a set of arguments with standard shapes. A consultant reaching for a 2x2 or a waterfall is not decorating; they are choosing the form that makes a specific kind of point land. Learn the handful of forms and when each applies, and building a strategy deck stops being a blank-page problem.
The mistake juniors make is picking a chart because it looks impressive, then bending the message to fit it. The order runs the other way: decide the claim, then choose the slide type that proves it in the fewest moves. Below are the strategy slides that do most of the work in a real engagement.
The issue tree
An issue tree breaks a big question into mutually exclusive, collectively exhaustive (MECE) branches. "How do we grow revenue?" splits into price, volume, and mix; each splits again. It is the slide you use early to show you have scoped the problem completely and are not cherry-picking.
Build it left to right, root question on the left. Keep each level MECE — no branch overlaps another, and together they cover the whole question. Three or four branches per node; more and it stops being legible. The value of the tree is that a skeptical reader can check for the branch you conveniently ignored, and not find one.
The 2x2 matrix
The 2x2 sorts options along two decision-relevant axes — say, strategic fit against ease of execution — and reads the recommendation off the quadrant. It works because it forces a choice: everything lands somewhere, and the top-right quadrant becomes the shortlist.
The whole slide lives or dies on the axes. Choose two dimensions that actually drive the decision, label both ends, and place items honestly. A 2x2 where everything clusters in one corner is not insight; it means your axes do not discriminate. Do not add a third variable through bubble size unless you genuinely need it — clarity is the point.
The waterfall
A waterfall bridges from one number to another, showing what drove the change: starting EBITDA on the left, a series of up and down bars for each driver, ending EBITDA on the right. It is the standard slide for "why did the number move" and for decomposing a target into its parts.
Order the bars deliberately — largest drivers first, or grouped by theme — and label each with its value. Color increases and decreases consistently, with the start and end totals visually distinct. The action title should state the takeaway ("Two of five drivers explain 80% of the margin decline"), not just "EBITDA Bridge."
The roadmap or timeline
A roadmap sequences initiatives over time — phases, workstreams, milestones — to show what happens when and in what order. It is how you turn a recommendation into a plan the client can actually resource.
Keep the time axis honest and the swim lanes few. Show dependencies where they matter (this cannot start until that finishes) rather than dressing every task with a marker. A roadmap that lists forty tasks is a project plan, not a strategy slide; the board wants the shape of the sequence and the two or three decisions that gate it.
The value driver tree
A driver tree decomposes a financial outcome into the levers beneath it: revenue into customers times average value; average value into price and units. It is the analytical cousin of the issue tree, used to show where value is created and which levers are worth pulling.
Build it so the arithmetic is visible — a reader should see how the boxes multiply or sum to the top number. It pairs well with a sensitivity view: which lever, moved a realistic amount, changes the outcome most. That is usually where the recommendation is hiding.
The market map and the competitive landscape
A market map places players on a field — by segment, by positioning, by size — to show where the white space is. A landscape slide does similar work for competitors. Both answer "where does everyone sit, and where is the gap."
Resist cramming every logo on. Choose the framing that surfaces your point — the underserved segment, the crowded middle — and let the map argue it. A map with no visible gap and no crowding is a directory, not an argument.
The rules that apply to all of them
Whatever the type, the same discipline makes a strategy slide read as consulting-grade:
- Action titles. The headline states the takeaway as a full sentence, not a label. "Two segments hold 70% of the profit pool" beats "Profit Pool Analysis."
- One idea per slide. If a slide makes two points, it is two slides. Density is not rigor.
- Source lines. Every exhibit cites its data source in a small footer. It signals the number can be traced.
- Restraint. One accent color, consistent type, real white space. The polish comes from what you leave off.
- Claim first, chart second. Decide the point, then pick the form that proves it — never the reverse.
How AutoPresent helps
Knowing which strategy slide to reach for is judgment a tool cannot replace. Turning the choice into a clean, editable PowerPoint slide is where the time goes, and where a tool can help.
AutoPresent produces fully editable PowerPoint, so you can describe the slide you need and generate a first draft — a 2x2, a waterfall, a roadmap — laid out in a restrained, board-appropriate style, then adjust every element in PowerPoint as usual. It reads from source material too: point it at a model or a Word report and it drafts the exhibit and a headline slot you rewrite into your real claim. The theme switcher rebrands to client colors in one step. There is a free tier and paid plans from $25 a month if you want to test it on a live deck.
The tool draws the slide. You still decide the argument and choose the form — which is the part that was always the actual work.
The takeaway
Strategy slides are a small vocabulary of shapes, each matched to a kind of claim: the issue tree scopes the problem, the 2x2 forces a choice, the waterfall explains a change, the roadmap sequences the plan, the driver tree finds the lever. Learn the set, choose the form after you know your point, and hold the same discipline — action titles, one idea per slide, sources, restraint — across all of them. That is what turns a stack of charts into a strategy deck.