Explaining Technical Trade-offs to Non-Technical Stakeholders
Updated · Tech checked
The working pattern: lead with the decision and its business consequence, give two options max with costs in their units (time, money, risk), state your recommendation and what you need from them. Analogies are allowed; lies and jargon are not.
The short answer
Stakeholders don't need your architecture; they need to understand its business impact. Convert technical options into outcomes (time, money, risk, reversibility) and make a recommendation. Presenting three options with no recommendation is delegation, not communication.
The 5-sentence script
- Decision needed: "We must choose how the sync recovers after outages."
- Options, two max: "Reprocess everything (safer data, ~2 days delay) vs skip-and-report (fast, small chance of gaps)."
- Consequence in their units: "Gaps could mean ~20 misapplied invoices/week until reconciled."
- Recommendation: "I recommend reprocess - the invoice risk is worth 2 days."
- What you need: "Your OK to move the go-live from the 14th to the 16th."
Translations that work
| Technical | Business |
|---|---|
| "Idempotency prevents duplicate writes" | "Prevents customers being charged twice when systems retry" |
| "p95 latency 2.3s" | "1 in 20 users waits over 2 seconds" |
| "Tech debt in the parser" | "Every new supplier format costs ~3 days; a rewrite makes it half a day" |
| "No test coverage on legacy module" | "Changes there are 'edit and pray'; we find out from customers" |
Rules that keep trust
- Never lie by omission. If option B risks data gaps, say the word "risk."
- Numbers over adjectives. "Slow" is nothing; "adds ~40 min/day across the team" decides itself.
- Own the recommendation. "Both work; I recommend A because..." - you're the expert they hired.
- Write it after saying it. The 5-sentence script in an email creates the paper trail that protects everyone.
Practice
Take your last real trade-off, rewrite it through the script, and deliver it to a non-engineer friend until they can repeat the consequence back. The interview guide includes this as a mock round.
Continue: Customer-facing questions · Presenting failures