Technical Portfolio: 3 Formats (Audience-Tested)
12 weeks · 4 milestones
Milestone map
Milestone map
3 milestones
Gather 4–5 examples of technical communication you have produced in the last 12 months: code comments, technical documentation, design documents, architecture decisions (ADRs), technical emails, Slack messages to non-technical colleagues, or verbal explanations you can reconstruct. For each, assess three criteria: audience fit (is it pitched at the right level of technical knowledge?), context provision (does the reader know WHY before the HOW?), and actionability (is it clear what the reader should do or understand next?). Write a 200-word diagnosis naming your single most consistent weakness.
Proof required
Submit your audit: 4–5 real examples of your technical communication with three-criterion ratings (audience fit / context provision / actionability, each 1–5) and a one-sentence specific observation per criterion per piece. Append a 200-word diagnosis naming one recurring weakness with evidence from at least 3 pieces.
What gets checked
- 4–5 real examples from your own work — not sanitised or polished for the audit; representative of your actual output
- Ratings vary across pieces and across criteria — uniform scores indicate the rubric was not applied with real attention
- Diagnosis names a specific recurring failure (e.g. 'assume the reader already knows the context', 'explain implementation before purpose') not a generic category ('I am too technical')