A presentation is a path from question to decision
Strong technical stories follow a predictable path: why we did it → what we did → what we found → what it means → what we need from you. Each scene should answer the question the previous one raised.
Pick evidence that proves your point, not everything you collected. Three strong images beat thirty.
- ▸Open with the purpose, not with “Hi, my name is…” alone.
- ▸End with a request, not with “Any questions?” alone.
order
Repair the storyboard
These construction-briefing scenes are shuffled. Drag them into the order a client can follow.
- 1Next steps: next flight and the decision we need
- 2Project objective: weekly progress maps of the east wing
- 3Findings: what's complete, what's preliminary
- 4Mission planning: aircraft, altitude, airspace
- 5Progress comparison: week 1 vs week 3
- 6Site overview: where, what's being built
- 7Data collection: flights and conditions