How do I structure slides when I have to explain a complicated process?
Quick answer
Build the deck around the audience’s journey through the process: why it matters, what starts it, the stages in order, where decisions change the path, and what counts as completion. Give each slide one job. Use a simple process map for orientation, then explain stages and checkpoints in sequence. Make branches visible, label who acts, and end with the outcome and next action.
The question, the details, the next step.
I have to explain a complicated process in a presentation. How do I decide what goes on each slide without overwhelming people?
Start by writing the process as a plain-language sequence before opening your slide software. Identify the intended outcome, the starting event, the main stages, any decisions that create different paths, and the finish. Then give each slide one purpose. A useful order is: outcome and audience; process overview; stages in sequence; decision points; completion criteria; and next action. If two slides seem to do the same job, combine them or clarify the difference.
Use the opening slide to name the outcome in terms your audience cares about and say who the process is for. On the next slide, show the whole route at a glance: a short sequence of labeled stages, including the start and finish. Treat this overview as a map, not the full explanation; later slides can unpack the stages.
How do I explain the stages clearly, especially when there are approvals or a route back for changes?
Give each stage a consistent mini-structure: what triggers it, who does what, what information or item moves forward, and what result lets the process continue. Use an action heading such as “Review the request,” rather than a vague heading like “Step 2.” Group small actions under a meaningful stage, and show details when they clarify a handoff or checkpoint.
Show decisions as visible branches with a clear question. Label the routes with their outcomes, and make a return route reconnect to the relevant earlier stage. For each checkpoint, state who checks what and what happens if the condition is not met. If an exception changes what someone must do, don’t hide it in a small note.
Could you show me a short example storyboard? My process is a hypothetical request that gets reviewed, approved, or sent back for changes.
Assuming this is a simple illustrative process, a storyboard could be:
- Outcome and audience: “This guide shows requesters and reviewers how a request reaches a decision.”
- Route at a glance: Submit → completeness check → review → decision → notify requester.
- Checkpoint: complete? The reviewer checks the required fields. If something is missing, return it to the requester for changes, then reconnect to the completeness check.
- Review: Explain what the reviewer considers, using the criteria your organization actually uses.
- Decision checkpoint: Show the available outcomes, such as approved or not approved, only if those are the real options.
- Finish: State what the requester receives and what action, if any, follows.
Replace the assumed stages and outcomes with the actual process. The example illustrates a slide structure, not a recommendation about approval rules. On detailed slides, keep stage names consistent with the overview.
How can I check that the finished deck is understandable before I present it?
Review it in two passes. First, read only the slide titles and see whether they tell a coherent story from purpose to outcome. Then follow every branch: can you tell what triggers the process, who acts at each stage, what is checked, and where each route goes? Remove details that do not help the audience follow or apply the process. If you cannot explain a branch in a few plain sentences, simplify the slide or divide the explanation.
A reusable structure is: slide 1, outcome and audience; slide 2, start, stages, and finish at a glance; later slides, one stage or grouped stage at a time, with trigger, owner, action, and handoff; checkpoint slides, question, checker, routes, and next step; final slide, completion signal and next action. You can also ask someone unfamiliar with the process where they would hesitate. That is a clarity check, not proof that every audience will interpret the deck the same way.
A practical checklist
Write the process outcome, audience, and starting event in plain language.
List the stages in order, including handoffs and the finish.
Mark each decision and show every route, including returns for changes.
For each checkpoint, name who checks what and what happens next.
Give each slide one clear purpose and use consistent stage labels.
Follow every path through the deck and remove details that do not help explain it.
A few more useful answers
Should I put the full process diagram on one slide?
Use one slide for a readable overview, not necessarily every detail. Explain complex stages and branches on follow-up slides, while keeping their labels consistent with the overview.
How many stages should one slide cover?
Use as many as the audience can follow without losing the sequence. Split a slide when it needs to explain several distinct actions, handoffs, or decisions at once.
What if the process has exceptions?
Show exceptions that change an action or route as visible branches. For rare details that do not change the main explanation, use a clearly labeled note or separate reference material.