Quiz — Chapter 40: The Communication Portfolio

Q: What does the *range* of seven pieces prove that any single strong piece cannot? that you can write quickly that you have good design taste that you can read a situation and match the form to it (the meta-skill) that you have worked on many projects

C. §40.1–40.2: one piece proves you can write that one genre; the seven together prove you can identify what a situation needs and produce it—the through-line of the whole book. That meta-skill is what transfers to a job, where you'll write emails, memos, and docs, not just reports.

Q: The single non-negotiable rule of the portfolio is: it must have exactly seven pieces every piece must be hosted on a custom website every piece must have been revised at least once, changing meaning or structure every piece must include a before/after

C. §40.5, theme 4. This is the rule most portfolios silently break (assembling first drafts and spell-checking). A is false (curate honestly; five can beat seven). B is false (a clean PDF or simple page is fine). D is recommended for at least one piece, not required for all.

Q: Why should the growth-narrative cover letter be written *last*? it's the least important piece so it tells the true story the assembled, revised pieces actually support because it's the shortest to save the hardest task for the end

B. §40.7: the narrative's job is to frame the evidence, and you only know the true story once you've seen which pieces ended up strong and what the before/after shows. Write it first and you risk claiming a growth the pieces don't back up—and in a portfolio, the next page can disprove the letter.

Q: The best portfolio presentation is described as "invisible." This means: the portfolio should be hard to find the container (site/PDF) should be clean and conventional enough that the reader looks at the writing, not the interface the writing should be subtle you shouldn't put your name on it

B. §40.6, theme 7: nothing should stand between the reader and the work—no password walls, no learning-curve interface, no animations that upstage the prose. If the reader remembers your particle effects and not your writing, the container won a fight it should have lost.

Q: "A portfolio with seven mediocre pieces is always better than one with five strong pieces, because range matters most."

False. §40.3, §40.9: range matters, but padding—keeping weak pieces to hit a number—drags the reader's estimate of the whole; a focused five beats a padded seven. Curate honestly and lead with strength.

Q: "You should include a before/after for every piece in your portfolio."

False. §40.5: for most pieces, show only the polished result (the reader wants to see what you produce). Include at least one before/after to demonstrate you can see and fix your own work—but every piece would clutter the portfolio and bury the finished work.

Q: "The growth narrative should hide what you couldn't do at the start, so you look as skilled as possible throughout."

False. §40.7: honesty about the starting point is what makes the growth believable—naming the charter sentence that took four tries, or the report that buried its point, gives the "after" something to be measured against. Hiding the before flattens the narrative into an unverifiable claim.

Q: "If your track skipped the chapter that built a particular piece, the honest move is to leave that slot empty and say nothing about it."

False. §40.2: the honest options are to build the piece now (you have the skills), substitute a strong piece from the same family, or curate around it and say so in the cover letter. Silent gaps read as oversights; a named, deliberate choice reads as judgment.

DataField.Dev

Quiz — Chapter 40: The Communication Portfolio

Target: 70%+ before moving on. This is the capstone quiz, so it leans reflective and checklist-style: it tests whether you can judge a portfolio (yours and others') against the principles, not whether you can recite them.

Section 1 — Multiple Choice (8–12)

1. The fundamental advantage of a portfolio over a résumé is that a portfolio: - A) is longer and contains more detail - B) demonstrates skill the reader can verify, rather than claiming it - C) is more visually impressive - D) lists more accomplishments

Answer

**B.** §40.1: a résumé *claims* ("strong communicator"); a portfolio *demonstrates*, putting the work in front of the reader to verify in the time they have. You can fake a résumé bullet; you can't fake a clear technical report. A and C and D miss the point—length, visual impressiveness, and accomplishment-count don't bridge the claim/proof gap.

2. What does the range of seven pieces prove that any single strong piece cannot? - A) that you can write quickly - B) that you have good design taste - C) that you can read a situation and match the form to it (the meta-skill) - D) that you have worked on many projects

Answer

**C.** §40.1–40.2: one piece proves you can write that one genre; the seven together prove you can identify what a situation needs and produce it—the through-line of the whole book. That meta-skill is what transfers to a job, where you'll write emails, memos, and docs, not just reports.

3. In ordering a portfolio, where should the weakest piece you're keeping go? - A) first, to get it out of the way - B) last, so it's freshest - C) in the middle, since first and last are the positions the reader remembers - D) it shouldn't be kept at all

Answer

**C.** §40.3: primacy and recency ([Chapter 30](../../part-06-presentations-oral-communication/chapter-30-slide-design/index.md)'s instinct) mean the reader remembers the first and last pieces most, so lead with your strongest and end with your most distinctive; bury the weakest-but-kept piece in the middle. D is too absolute—a piece weak relative to your best may still be worth including for range; the *padding* error is keeping a genuinely poor piece to hit the number seven.

4. The single non-negotiable rule of the portfolio is: - A) it must have exactly seven pieces - B) every piece must be hosted on a custom website - C) every piece must have been revised at least once, changing meaning or structure - D) every piece must include a before/after

Answer

**C.** §40.5, theme 4. This is the rule most portfolios silently break (assembling first drafts and spell-checking). A is false (curate honestly; five can beat seven). B is false (a clean PDF or simple page is fine). D is recommended for *at least one* piece, not required for all.

5. A portfolio annotation should interpret rather than label because: - A) longer annotations look more professional - B) it borrows Chapter 9's caption discipline—telling the reader what to notice, since a busy reader told nothing notices nothing - C) the reader can't read the pieces themselves - D) it fills space on the landing page

Answer

**B.** §40.3: "Technical report" labels; "note how the recommendation leads and the methodology is demoted" interprets, telling the reader the skill to watch for in their first ten seconds. It's the figure-caption lesson ([Chapter 9](../../part-02-building-blocks/chapter-09-visuals-and-data/index.md), [Chapter 27](../../part-05-software-data-writing/chapter-27-writing-about-data/index.md)) applied to the piece—the "so what?" of the document.

6. Why should the growth-narrative cover letter be written last? - A) it's the least important piece - B) so it tells the true story the assembled, revised pieces actually support - C) because it's the shortest - D) to save the hardest task for the end

Answer

**B.** §40.7: the narrative's job is to frame the evidence, and you only know the true story once you've seen which pieces ended up strong and what the before/after shows. Write it first and you risk claiming a growth the pieces don't back up—and in a portfolio, the next page can disprove the letter.

7. An inflated growth narrative is uniquely risky in a portfolio (compared to a résumé) because: - A) cover letters are graded more harshly - B) the portfolio hands the reader the evidence, so the letter can be disproven on the spot by the very pieces it introduces - C) portfolios are read more carefully than résumés - D) it makes the writer look arrogant

Answer

**B.** §40.1, §40.7: on a résumé, "improved dramatically" can't be easily checked; in a portfolio, if the letter claims "clear writing for any audience" and the blog post is jargon-choked, the claim is contradicted by the next page. The safe move is under-claim, over-show. (C and D may be true but aren't the *structural* reason.)

8. The best portfolio presentation is described as "invisible." This means: - A) the portfolio should be hard to find - B) the container (site/PDF) should be clean and conventional enough that the reader looks at the writing, not the interface - C) the writing should be subtle - D) you shouldn't put your name on it

Answer

**B.** §40.6, theme 7: nothing should stand between the reader and the work—no password walls, no learning-curve interface, no animations that upstage the prose. If the reader remembers your particle effects and not your writing, the container won a fight it should have lost.

9. When self-assessing a piece, the chapter advises you to find: - A) an average overall score - B) everything that's wrong with it - C) the single weakest dimension, because its repair most improves the piece - D) the strongest dimension, to lead with it

Answer

**C.** §40.4: assess dimension-by-dimension, top-down ([Chapter 12](../../part-02-building-blocks/chapter-12-editing-and-revision/index.md)'s hierarchy), and find the one weakest dimension—the load-bearing problem whose fix often cascades (e.g., fixing method-first order also fixes length and the "so what?"). Averaging into "pretty good" tells you nothing to act on.

10. A portfolio for a research lab and one for a developer-relations role should: - A) be identical, since both show writing skill - B) be curated and ordered differently for the two readers, even from the same seven pieces - C) never share any pieces - D) both lead with the blog post

Answer

**B.** §40.3, theme 2: same seven pieces, different reader → different selection and order (the research portfolio leads with the report and proposal; the DevRel portfolio leads with the docs and README/blog). The fifteen-minute re-curation routinely decides the read. This is Dana's churn-memo lesson ([Chapter 27](../../part-05-software-data-writing/chapter-27-writing-about-data/index.md)) one level up, on the collection.

Section 2 — True/False with Justification (4–6)

For each, mark T/F and give one sentence of justification.

11. "A portfolio with seven mediocre pieces is always better than one with five strong pieces, because range matters most."

Answer

**False.** §40.3, §40.9: range matters, but *padding*—keeping weak pieces to hit a number—drags the reader's estimate of the whole; a focused five beats a padded seven. Curate honestly and lead with strength.

12. "You should include a before/after for every piece in your portfolio."

Answer

**False.** §40.5: for *most* pieces, show only the polished result (the reader wants to see what you produce). Include *at least one* before/after to demonstrate you can see and fix your own work—but every piece would clutter the portfolio and bury the finished work.

13. "The growth narrative should hide what you couldn't do at the start, so you look as skilled as possible throughout."

Answer

**False.** §40.7: honesty about the starting point is what makes the growth *believable*—naming the charter sentence that took four tries, or the report that buried its point, gives the "after" something to be measured against. Hiding the before flattens the narrative into an unverifiable claim.

14. "Because a blog post and a requirements spec are different genres, it's fine for them to look and read like the work of two different writers."

Answer

**False (with a nuance).** §40.3, [Chapter 7](../../part-02-building-blocks/chapter-07-word-choice-tone-voice/index.md): register *should* differ by genre (a blog isn't a spec), but the markers of a careless writer—inconsistent heading styles, different terminology for the same subject, uneven finish—must be uniform. The reader should sense one writer with one standard expressing it appropriately, not two different people.

15. "If your track skipped the chapter that built a particular piece, the honest move is to leave that slot empty and say nothing about it."

Answer

**False.** §40.2: the honest options are to *build* the piece now (you have the skills), *substitute* a strong piece from the same family, or *curate around it and say so* in the cover letter. Silent gaps read as oversights; a named, deliberate choice reads as judgment.

Section 3 — Short Answer (3–5)

16. In two or three sentences, explain why a revised piece signals more skill to an expert reader than an equally-polished piece that came out well on the first try.

Model answer + rubric

The expert reader is inferring the *process* and buying *future* performance, not judging the artifact in isolation. A piece bearing the marks of deliberate revision (a structure reorganized for the reader, a recommendation moved up) signals a writer who will also revise the next document, written on the job under deadline; a merely-clean piece could be a fluke. Revision is evidence of a *habit*, which predicts future quality better than any single outcome. *Rubric: names the process/future-performance inference (§40.5, Why Does This Work?).*

17. Name the three decisions that turn a pile of seven documents into an assembled portfolio, and the one-word principle behind each.

Model answer + rubric

**Curation** (what's in/out — *audience*, theme 2), **order** (what the reader meets first — *structure*/primacy, theme 5), and **coherence** (seven pieces reading as one writer with one standard — *consistency*, [Chapter 23](../../part-04-professional-workplace-writing/chapter-23-collaborative-writing/index.md)). *Rubric: all three named with a defensible principle each (§40.3).*

18. Your portfolio's cover letter and one of its pieces appear to contradict each other. What does §40.7 say about resolving this, and which should you trust?

Model answer + rubric

Trust the *evidence* (the pieces) and revise the *claim* (the letter) down until it's true—the portfolio hands the reader both, so an inflated letter is disproven by the page that follows. Under-claim and over-show: make the evidence exceed the claim, never fall short of it. *Rubric: trusts the pieces over the letter; cites the disprovability risk (§40.7).*

19. Give one concrete example, from any portfolio piece, of each of these themes operating: #2 (audience) and #4 (revision). Be specific, not abstract.

Model answer + rubric

*Examples will vary; they must be specific.* Strong #2: "I dropped the grant proposal because my DevRel reader doesn't care about it." Weak #2: "my portfolio is audience-aware." Strong #4: "I reordered the data memo to lead with the recommendation, cutting it from 2.5 pages to one." Weak #4: "I revised my pieces." *Rubric: each example is a specific decision or change, not a restatement of the theme (§40.8).*

Section 4 — Applied Scenario (1–2)

20. You have your seven pieces assembled but unannotated, in upload order, hosted as a shared folder with no index. A hiring manager for a data-analytics role will spend ten minutes on it. In a short paragraph, describe the three highest-impact changes you'd make in the next thirty minutes, in priority order, and justify the priority. (Graded by rubric.)

Rubric

- **Strong:** (1) Add a front door + index so the reader knows what this is and reaches the right piece (the file-dump fix, §40.3/40.6—highest impact because without it the reader judges by a random file); (2) re-curate and reorder to lead with the data memo and the technical report for *this* analytics reader (theme 2, §40.3); (3) add interpreting annotations, at least on the lead pieces (§40.3). Priority justified by reader's scarce time and the thirty-second decision. - **Adequate:** names the three changes but with weak or missing priority justification. - **Needs work:** reaches for polish (fonts, a custom site) before fixing curation and the front door, or doesn't tailor to the analytics reader.

21. Write the opening two sentences of a growth-narrative cover letter for your own portfolio that show one specific change (not "I improved"). Then, in one line, state what evidence in your portfolio a reader could check to verify it. (Graded by rubric.)

Rubric

- **Strong:** the two sentences name a *specific, concrete* before-state and the changed after-behavior (e.g., "My first report opened with three paragraphs of method; the version on page 4 leads with the finding"), and the evidence line points to an exact, checkable place. Performs the post-growth skill while describing the pre-growth state. - **Adequate:** shows a change but vaguely, or the evidence is hard to locate. - **Needs work:** claims growth without a specific before, or the evidence can't actually verify the claim (the §40.7 risk).

Scoring & Next Steps

Score	What it means	Do this
< 50%	The portfolio concepts haven't landed	Re-read §40.1 (why it beats a résumé), §40.3 (assembly), §40.5 (revision rule). Then redo Section 1.
50–70%	You know the parts but not the judgment	Redo Part B and the Section 4 scenarios—they test applying the principles to real artifacts, which is the skill that matters here.
70–85%	Solid—proceed to build	Do exercise C2 and C3 (assemble + cover letter) for real. The quiz tested whether you can judge a portfolio; now build yours.
> 85%	You can judge a portfolio well	Do Part E—critique a real public portfolio (E3) and build the before/after exhibit (E2). Then assemble yours to that standard.

This is the last quiz. Whatever your score, the real assessment is the artifact: a finished, revised, presentable portfolio and the cover letter that frames it. The quiz checks whether you can see what good looks like. The portfolio proves you can build it.