Capstone Project B — The Translation Challenge
A focused capstone. Take one technical topic and write it four ways, for four readers, across four genres. The narrowest of the three capstones and the purest test of the book's central skill: audience is everything.
Which capstone is this? One of three briefs in this part, all graded by
capstone-rubric.md. This one is tight and deep where the Portfolio (capstone-project-portfolio.md) is broad. Choose it if you want to prove one thing exceptionally well: that the same information becomes a completely different document when the reader changes.
Purpose
Pick one technical topic you understand well. Now explain it to four different readers: a fellow expert, your manager, a client or non-specialist customer, and the general public. Same facts. Four documents that share almost no sentences.
This is the book's second theme — audience is everything — isolated and stress-tested. Most writers have one register, the one they learned in school, and they aim it at everyone. The expert finds it slow; the public finds it impenetrable; the manager can't find the decision. The skill this capstone proves is the one a technical career actually rewards: reading the reader first, then choosing the vocabulary, the structure, the length, and the level of detail that serves that reader and no one else. You will feel the curse of knowledge (Chapter 2) most sharply in the public-facing piece, where every term you take for granted is a wall — and you will learn that clarity is not the enemy of precision (theme 3); jargon is, when the audience doesn't share it.
The Topic
Choose something you genuinely understand and that has real depth — a method, a system, a result, a technology, a process. Good candidates: how a particular machine-learning model makes a prediction; why a bridge design uses the cross-section it does; how a drug clears the body; how a database index speeds a query; what a clinical trial's primary endpoint actually measures. Avoid topics so simple they don't change much across audiences, and avoid topics you'd have to research from scratch — the point is translation, not learning.
State your topic in one sentence at the top of your submission. If you can't say it in one sentence, you don't understand it well enough yet to translate it (theme 1: writing is thinking).
The Four Deliverables
All four explain the same core idea. What changes is everything about how.
1. For a fellow expert — a technical abstract or methods note (~250–400 words). Assume shared vocabulary and shared context. Use the field's terms precisely; don't define what an expert already knows (defining "p-value" to a statistician insults them). Be dense, exact, and complete on the points that matter to a peer who could replicate or critique your work. Genre: an abstract (Chapter 14), a methods paragraph (Chapter 13), or a short technical note. The skill: precision and economy for a reader who shares your frame.
2. For your manager — a decision memo (~1 page). Your manager is busy, not technical in your sub-specialty, and reads to act. Lead with the "so what" — the decision, recommendation, or implication — not the method (Chapter 27, Chapter 20). Translate the technical detail into consequences in their units: cost, risk, timeline, headcount, customer impact. Bury the method or push it to a closing line. Genre: the recommendation-first memo. The skill: leading with the decision, translating detail into stakes.
3. For a client or non-specialist customer — an explanatory note or FAQ (~300–500 words). The client cares what it means for them — what it does, what it costs, what they need to do, what could go wrong. They are intelligent but outside your field, and they may be making a purchase or trust decision. Plain language, no unexplained jargon, a reassuring and honest tone (Chapter 7's register; Chapter 36's patient-facing plain language if your topic is medical). Genre: a client-facing explainer or an FAQ with real reader questions. The skill: plain language under a trust constraint, anticipating the reader's real questions.
4. For the general public — a blog post or popular-science piece (~600–1,000 words). The reader has no stake and no background and will leave the moment they're bored or lost. You need a hook, exactly one analogy carrying the hard idea, and a strict jargon budget — spend a term only when you've earned it and defined it in passing (Chapter 28). Make them care before you make them understand. Genre: science communication / a blog post. The skill: the analogy, the hook, and the jargon budget for a reader with zero obligation to keep reading.
The analogy is the heart of this challenge. Somewhere across the four pieces — most visibly in the public one — you must carry the hard idea with a single, accurate analogy. A good analogy is the most powerful tool in the science communicator's kit and the easiest to get subtly wrong. Name, in your reflection, what your analogy captures and where it breaks down, because an analogy that's pushed past its limit misleads (Chapter 28).
Constraints and Honesty
- One topic, one set of facts. You may not change the underlying claims between versions — only how you present them. If the expert version says the effect is modest and uncertain, the public version may not say it's a breakthrough. Translating across audiences never licenses overclaiming. This is a citation-honesty and ethics constraint (Chapter 38): the dark side of clarity is that a smooth, confident sentence can hide a weak result. Keep all four versions true, even as they differ in depth.
- Label any composite or illustrative example as such (fictional but realistic, anonymized). If you invent a client or a manager scenario to frame a piece, that's fine — say so.
- Cite real sources honestly if your topic draws on published work. No invented studies, DOIs, or years; an attributed claim ("research on X suggests…") is fine when you can't pin the exact citation.
Deliverables Summary
Submit one document containing, in this order:
- The topic sentence and a two- or three-line note on why each audience needs a different treatment (your audience analysis — Chapter 2).
- The four pieces, each labeled with its audience and genre.
- A short reflection (~300–400 words) answering: Which version was hardest, and why? What did you have to cut for the public that the expert needed? What does your central analogy capture, and where does it break down? Where did the curse of knowledge bite hardest? This reflection is itself assessed for the metacognition it shows.
Evaluation
Graded with capstone-rubric.md, with the weight tilted toward audience fit — the dimension this capstone exists to test. A few criteria sharpen for this brief specifically:
| What strong work looks like | What weak work looks like |
|---|---|
| The four pieces are genuinely different documents — different openings, structures, vocabulary, lengths. A reader could not guess they share a topic from the first sentence alone. | The four pieces are one document with the jargon swapped in or out. Same structure, same opening, "dumbed down" rather than re-conceived. |
| Each piece leads with what its reader cares about: the expert with the method/result, the manager with the decision, the client with "what it means for me," the public with a hook. | Every piece leads with the same thing (usually the method), regardless of reader. The manager memo buries the decision; the public post opens with a definition. |
| The analogy is accurate, does real explanatory work, and its limits are named. | No analogy, a clichéd one, or one pushed until it misleads. |
| All four are true. Differences are in depth and framing, never in the claims. | The public version overclaims certainty the expert version withholds. |
| The reflection names a specific, real difficulty and what was cut for whom. | The reflection is generic ("I learned a lot about audience"). |
The test the whole capstone reduces to: hand any one piece to its intended reader, and they get exactly what they need at exactly the depth they can use — no more, no less. Four readers, four documents, one truth. If you can do that, you have proven the skill this book is named for: think clearly enough about the subject that you can re-explain it for anyone who needs it.