Case Study 1: A Strong Finished Portfolio, Walked Through
A composite example, fictional but realistic, assembled from the patterns that recur in portfolios that get their owners hired.
Naomi Adeyemi finished the book with a subject she'd chosen in week one: a home air-quality monitoring system she'd built and run for a year. Her Chapter-1 charter named it in one sentence, listed three audiences (fellow makers, a potential employer's hiring manager, curious neighbors), and admitted the one thing she couldn't do yet—"explain why anyone who isn't already into air quality should care." This is what her assembled portfolio looked like when she sent it for a junior data-engineering role. Read it as the hiring manager did: with twenty minutes and the question can this person write?
The front door
She hosted it as a single static page. The first thing the reader meets:
Communication Portfolio — Naomi Adeyemi Seven documents, all built from one project: a year of running a home air-quality monitor. Each is written for a different reader—an engineer, a manager, a neighbor—so you can see the same work reshaped for whoever needs it. Start anywhere; the technical report and the data memo are the best showcase of the data work.
Two sentences and a pointer. It answers whose, what, why read on, and—applying Chapter 19's and Chapter 20's first-sentence discipline—it tells the reader where to go for what they came for. No "passionate communicator." The front door is a piece of writing, and it's already demonstrating audience awareness (theme 2) by naming the readers the pieces serve.
The order, and why
Because she was applying for a data-engineering role, she led with strength for that reader:
- Technical report (load and accuracy testing of the sensor array) — her strongest piece, and the one the reader cares most about.
- Data-analysis memo (a finding about indoor air quality during cooking, recommendation-first).
- User documentation (how to build and calibrate the monitor).
- Project proposal (extending the system to a neighborhood mesh).
- Email chain (negotiating sensor donations from a manufacturer—a real "ask" with a near-rejection turned into a yes).
- Presentation (the deck she gave at a local maker meetup).
- Blog post ("What the air in your kitchen is actually doing to you") — last, because it's distinctive and shows range the other six don't.
Strongest first, distinctive last, the weaker proposal buried in the middle (§40.3). A reader who quits after two pieces has still seen her best work.
The annotations that interpret
Each piece carried a two-sentence annotation. The data memo's:
A one-page memo for a non-technical household decision-maker: should you run the kitchen exhaust fan, and when? Note how it leads with the recommendation and demotes the cohort analysis to a footnote—the "so what?" comes first, the method second.
That annotation does what a figure caption does (Chapter 9, Chapter 27): it tells the reader the skill to watch for—recommendation-first ordering—so they see it in ten seconds instead of reading the whole memo to discover it. This is the move Dana Whitfield's churn memo taught in Chapter 27, and Naomi borrowed it twice: once in the memo (the structure) and once about the memo (the annotation).
The evidence of revision
Every piece had been revised at least once, and one carried a visible before/after. Her technical report's original opening (saved from a Chapter-13 exercise) had buried the headline result under three paragraphs of sensor-calibration methodology. The revised version led with it: "The low-cost sensor array tracked the reference instrument within 8% across the full range we tested—accurate enough for household decisions, not for regulatory reporting." The before/after sat in an expandable panel labeled "How this report changed." It's the single most persuasive thing in the portfolio, because it shows what no polished piece can: that she can see and fix her own writing (§40.5). An expert reader sees a writer who'll keep improving without supervision.
The presentation: invisible
The site was plain. System font, generous white space, one link per piece, fast load, no animation. The reader never thought about the container (theme 7)—they looked at the writing. Naomi, who could have built an elaborate site (she's an engineer), deliberately didn't, because the role wasn't front-end and the cleverness would have upstaged the work (§40.6's warning). The restraint is itself a signal: a writer who reaches for substance over polish.
The cover letter that shows
Her growth narrative, half a page, opened:
My Chapter-1 charter described this project in a sentence I rewrote four times, because I kept writing what the monitor was made of instead of what it was for. That instinct is all over my early drafts: my first technical report opened with calibration methodology before it said whether the thing even worked (you can see the original in the before/after on the report page). My first blog draft used "particulate matter" six times before the second paragraph. The portfolio here is the same project, written by someone who now leads with the finding, spends a jargon budget instead of blowing it, and knows the difference between a draft and a finished piece. The clearest proof isn't any one document—it's that before/after, where you can watch me cut a problem I couldn't even see when I wrote it. I'm still working on technical persuasion; the proposal is the piece I'd most want to push further.
It shows (the four-try sentence, the six-times jargon, the named before/after), it's honest about the start, it names what's still unfinished, and it performs the post-growth skill—clear, concrete, reader-focused—while describing the pre-growth state (§40.7). A reader believes it because every claim points somewhere they can check.
Why it works
Lay the whole thing against the seven themes and each one is present in the artifact, not asserted: she thought her way to clarity on the page (1); curated and ordered for the hiring manager (2); kept expert jargon in the report and spent a budget in the blog (3); revised every piece and showed it (4); structured the collection and each piece for how the reader reads (5); cut the padding and the methodology wall (6); made the container disappear (7). The hiring manager didn't have to take anything on faith. In twenty minutes, the portfolio answered its own question.
Back to: Chapter 40 · Case Study 2 · Exercises