Presentation Skills
Presenting architecture so a specific audience can make a decision — which requires knowing which decision and adapting everything to it.
Definition
The skill is not slide design. It is selecting the right content and altitude for a specific audience and a specific decision.
Start from the decision
What do you want this audience to do? Approve funding, choose between options, understand a risk, change a priority. Everything follows from that, and a presentation without a decision attached is a status update.
If nobody needs to decide anything, write a document instead. A meeting to convey information is a document read aloud.
Adapt to the audience
| Audience | Lead with | Avoid |
|---|---|---|
| Executive | Outcome, cost, risk, timeline | Component diagrams |
| Product | Capabilities enabled and constrained, sequencing | Infrastructure detail |
| Engineering | Structure, contracts, trade-offs, first steps | Business framing they cannot act on |
| Security | Trust boundaries, data flows, controls | Implementation minutiae |
| Finance | Cost model, unit economics, commitments | Technology names |
Presenting the engineering view to all five is the most common failure in architectural communication.
Structure for a decision audience
Conclusion first. Executives want the recommendation and then the reasoning; building up to a conclusion loses the room and risks running out of time before reaching it.
Then: the problem in their terms, the options with costs, the recommendation, the risks, and what you need from them.
Practical points that matter more than they should
- One idea per slide. A slide with four ideas conveys none.
- No diagram the audience cannot read in ten seconds. If it needs explaining, it is the wrong altitude.
- Numbers with context. "£140,000 a month" means nothing; "£0.004 per order against a £28 order value" is actionable.
- Anticipate the objection and address it before it is raised.
- Know what you will cut if you have half the time, which is a common occurrence.
Failure scenarios
- The technical deep-dive to executives.
- No decision requested, so the meeting concludes with "thanks, interesting".
- Diagrams designed for a document, projected and unreadable.
- Running out of time before the recommendation, having built up to it.
Interview question
"You have ten minutes with an executive team to get approval for an architectural investment. How do you structure it?"