Capstone Project A — The Communication Portfolio

The flagship capstone. Build, revise, and present the complete seven-piece Communication Portfolio you have been assembling across the book. This is the project Chapter 40 brings home; the spec below is the formal brief if you want a graded or self-directed version of it.

Which capstone is this? This part offers three capstone briefs and one shared rubric (capstone-rubric.md). This one — the Portfolio — is the broadest and the default. If you took a single track and want a tighter, more focused capstone, see The Translation Challenge (capstone-project-translation.md) or The Documentation Sprint (capstone-project-documentation.md). All three are graded by the same rubric.

Purpose

A résumé claims you can write. A portfolio proves it. The difference is the entire reason this capstone exists: it puts the work in front of a reader and lets them verify, in the time they actually have, that you can take a complex technical subject and make it land with a specific audience. That is the rare lever Chapter 1 named — communication is highly valued and barely contested — and the portfolio is where you cash it.

You are not starting from zero. If you worked the Project Checkpoints, you already drafted seven pieces, one increment at a time, and revised most of them at least once. This capstone is the assembly: turn seven scattered files into one coherent artifact, judge each piece against a rubric, revise the weakest dimension of each, present the whole so a busy reader reaches your strongest work first, and write the growth narrative that compares your Chapter-1 charter to your work now. The goal is not seven good documents. It is one demonstration that you can read a situation and match the form to it — the meta-skill the whole book has been teaching.

The Seven Deliverables

Build all seven from one shared subject wherever you can. A reader who watches you reshape the same material for experts, managers, and the public sees the skill most résumés only claim. Each piece must pass its one quality test and must have been revised at least once (see the Revision Requirement below).

Every piece descends from more than one chapter — the report is Chapter 13's structure built out of Chapter 6's sentences and Chapter 8's paragraphs, revised by Chapter 12's hierarchy. The portfolio is where the parts of the book reconnect.

The missing-piece rule. If your track de-emphasized a source chapter and a piece is genuinely thin, you have three honest options, in order of preference: (1) build it now from the source chapter — one focused afternoon produces a real draft; (2) substitute a stronger piece in the same family (a blameless postmortem from Chapter 34 for a workplace report; a policy brief from Chapter 37 for a business proposal); or (3) curate around it and say so in your cover letter. A focused five beats a padded seven. What you must never do is include a piece you didn't actually revise and hope no one reads it closely. A reader reads it closely — that is what a portfolio is for.

Milestones and Timeline

A four-week cadence works for a course; compress or stretch it for self-study. The order matters more than the dates: assess before you revise, revise before you assemble, and write the growth narrative last.

The key checkpoint is the end of Week 1: if your inventory honestly marks two or three pieces "draft," that discomfort is the most useful signal in the project — the gap between where the piece is and where the rubric says it needs to be.

The Revision Requirement (non-negotiable)

Every piece must have been revised at least once, and the revision must change the meaning or the structure, not just the surface. This is theme 4 — revision is where the writing happens — stated as a hard rule, and it is the rule most portfolios silently break. People assemble first drafts, run a spell-check, and call it done. A reader who knows what good writing costs detects an unrevised draft in a paragraph: the buried point, the method-first order, the sentence that excavates instead of delivering. Clean spelling hides none of it.

For each piece, make the revision the one your self-assessment pointed to — the repair of the single weakest dimension — and descend the hierarchy from the top (content → structure → paragraphs → sentences → words → proofreading). Never start at the bottom. A structural fix often deletes the need for a dozen sentence fixes: leading the data memo with the recommendation instead of the Kaplan-Meier method fixes order, length, and the "so what?" in one move, exactly as Chapter 27 walked through with Dana Whitfield's churn memo.

Keep the before/after for at least one piece. For most professional portfolios you show only the polished result. But one visible before/after — the Chapter-1-era draft beside the revised final — demonstrates the meta-skill underneath all the others: that you can see and fix your own writing. An expert reader is buying future performance, and visible revision is the most reliable signal that the next document, written on the job under deadline, will also be revised into shape. Reference it in your growth narrative as your clearest single piece of evidence.

The Cover Letter: Your Growth Narrative

The cover letter is the one piece of the portfolio explicitly about you, which is why it must obey the book's discipline most strictly: it must show, not claim. It does for the portfolio what an abstract does for a paper — it frames the whole and tells the reader what they are about to see and why it matters.

Anchor it in the comparison this capstone is built on: your Chapter-1 portfolio charter (and your earliest exercise drafts) beside your work now. Read the charter as the honest reviewer the page always is. You will find the evidence the narrative needs — not "I improved," which a reader can't check, but the specific, demonstrable ways the writing changed.

Four principles, each a callback to a theme:

• Show, don't claim. Every assertion of growth points to evidence the reader can verify. Not "I learned to lead with the finding" but "see the report's revised opening on page 4."
• Be honest about the starting point. The narrative is more credible when it admits what you couldn't do — the charter sentence that took four tries, the report that buried its point. Honesty about the before is what makes the after believable.
• Name what you'd still like to improve. A writer who thinks they've finished growing has stopped. One honest sentence about the next thing you're working on signals a practitioner, not a graduate.
• Keep it short. Half a page to a page. It frames; it does not recapitulate. The pieces are the evidence; the letter is the caption.

Write it last, after the pieces are assessed and revised, because only then do you know the true story the evidence tells. And write it about the actual gap, not a flattering one: a portfolio hands the reader the evidence, so an inflated narrative is the one piece that can be disproven by the others. If the letter claims "clear writing for any audience" and the blog post is jargon-choked, the narrative is contradicted on the spot. Under-claim and over-show. Let the work carry the claim.

Submission and Presentation Guidance

How you present the portfolio is itself a design decision (Chapter 10) and an audience decision (Chapter 2). The format shapes the reader's first thirty seconds.

• A simple hosted web page is the strongest default — a static site, GitHub Pages, Notion, or a personal site, with the intro, the seven annotated entries, and a link to each piece. One shareable link; the reader meets your curation immediately. For software and CS readers, a clean repository or site quietly demonstrates Chapter 25's skills: a good README is the landing page.
• A single well-designed PDF suits readers who want one file to download, print, or attach — common in academic and some business contexts. A cover page, a one-page contents, the cover letter, then each piece with its annotation. Apply Chapter 10's hierarchy and white space; resist the PDF's invitation to dump everything.
• A linked folder is the last resort. If you must use one, add an index file at the top (a README — Chapter 25) that introduces the subject, orders the pieces, and links them. Never make the reader meet your work as an unsorted directory listing.

Three principles hold whatever the format, each a theme made physical: each piece readable on its own terms (a reader may jump straight to one), nothing between the reader and the work (no password walls, no clever interface to learn — the best writing is invisible), and a clear front door (two sentences answer "whose portfolio, what subject, why read on?" — the email's first-sentence discipline, Chapter 19).

Warning — the container that upstages the work. The common failure among technically capable people is to over-engineer the presentation: animations, a clever theme, a portfolio that is really a demo of front-end skill. Unless front-end skill is the job, this is a mistake, and a revealing one. The best presentation is invisible — clean, fast, conventional enough that the reader doesn't think about it. If the reader remembers your animations and not your prose, the container won a fight it should have lost.

If you present live (a showcase, a portfolio review), open with the growth narrative in ninety seconds — the charter, the gap, one before/after — then walk the reader to the single piece that best fits their interest. Don't tour all seven; show the one that answers their question and let them ask for more.

What You Submit

1. The assembled portfolio — landing page or single PDF — with all seven pieces (or a deliberately curated subset), each annotated.
2. The growth-narrative cover letter, with at least one visible before/after referenced from it.
3. portfolio/00-inventory.md — the inventory and self-assessment table, including each piece's weakest dimension and the revision you made.

You are assessed with capstone-rubric.md. Read it before you start — it is the external criterion that lets you see your own work past the curse of knowledge (Chapter 2). When you finish, you will hold the artifact this book set out to help you build: not seven files, but one coherent demonstration that you can take a complex technical subject and make it land with any reader who matters.