Executive Communication for Architects and CTOs

Communicating technology to executives and boards: pyramid principle, one-page briefs, framing trade-offs and options, and handling difficult conversations.

Executive explanation

Executives decide with limited time. Effective technology leaders lead with the answer, frame decisions as business options with costs, benefits and risks, and avoid jargon.

Techniques

  • Pyramid principle (Barbara Minto): conclusion first, then supporting arguments, then data.
  • SCQA: Situation, Complication, Question, Answer.
  • Options with a recommendation: usually three options (do nothing, recommended, ambitious) with cost, value, risk and timeline.
  • One-page brief with an appendix for details.
  • Numbers in business units: revenue, cost, customers affected, risk exposure, time.

Example one-page brief

Section Content
Decision needed Approve $2.4M to move checkout to a multi-region architecture
Why now Two outages last quarter cost an estimated $1.8M in lost orders; peak season in 5 months
Options A: Do nothing (risk persists). B: Warm standby region, $2.4M, 4 months, RTO 15 min (recommended). C: Active-active, $5M, 9 months, RTO near zero
Recommendation B: best risk reduction per dollar before peak season
Risks Timeline tight; mitigated by phased rollout and vendor support
Ask Funding approval today; quarterly progress report

Difficult conversations

  • Bad news early, with a plan.
  • Separate facts, impact and actions.
  • Own the problem; avoid blaming teams or vendors publicly.

Interview questions and answers

Explain microservices to a board member in one minute.

"We are splitting our large system into smaller parts owned by separate teams. Each team can improve its part without waiting for others, which lets us launch features faster and limit the impact of failures. It costs more to run and requires stronger engineering practices, so we do it only where speed or scale justify it."