intermediate

Technical communication

Explain context, constraints, options, recommendation, evidence, and open risks clearly enough for teammates to act.

Technical communication explains context, constraints, options, recommendation, evidence, and open risks so teammates and stakeholders can decide or act. Formats include design docs, RFCs, PR descriptions, Slack updates, and interview narration—the structure is similar.

					Context: checkout errors rose 12% after deploy X
Constraints: cannot break mobile SDK v3; fix before Friday peak
Options: rollback vs hotfix cache TTL vs disable feature flag
Recommendation: flag off new tax module (reversible, 5 min)
Evidence: trace shows timeout on tax service; flag default off
Risks: partial refunds still manual until Monday

On interviews: outline a one-minute verbal RFC for a caching change or API versioning decision.

Common pitfalls: jargon without audience fit; recommendation without alternatives; missing risks; walls of text without headings.

The trade-off is time writing versus repeated meetings explaining the same decision.

Checklist:

Lead with context and decision needed.
List constraints before options.
Recommend with evidence and reversibility.
State open risks and follow-ups.