Topic guide

Technical Communication

Technical communication that drives decisions: design docs and ADRs, presentations for boards and stakeholders, and storytelling for technical strategy.

3 topics · 14 articles

Written communication

Design docs, ADRs, and documents people actually read.

Live communication

Meetings, boards, and stakeholder presentations.

Technical storytelling

Making technical strategy and roadmaps compelling.

Frequently asked questions

How long should a design doc be?

Between 5 and 15 pages: complete enough to decide, short enough to be read. Beyond that, split it into smaller documents.

Who should review design docs?

Whoever the decision affects: architects, leads of the teams involved, and product. Too many reviewers slow things down without improving the document.

How do I present to non-technical people?

Start with business impact (cost, risk, timeline) and explain the technology only afterwards, if asked.

When should I write vs. present?

Write proposals and decisions, which need careful reading. Present live urgent issues and topics that need a conversation.