Quiz — Chapter 3: Clarity

Target: 70%+ before moving on. Answers and explanations are hidden — try each before expanding.

Section 1 — Multiple Choice

1. What is the primary reason to cut bloat from a draft? - a) Shorter documents always look more professional - b) The cut words carry fog, not information, so cutting clarifies without losing content - c) Readers prefer documents under 500 words - d) Long words are harder to spell

Answer **b.** This is the chapter's central idea (the threshold concept): most first-draft words carry no information. (a) is sometimes true but it's not the *reason*, and shorter isn't always better. (c) and (d) are distractors. See §3.1 and §3.6.

2. Which sentence contains a nominalization that should be freed into a verb? - a) "We analyzed the customer data." - b) "The team conducted an analysis of the customer data." - c) "Evolution shaped the human eye." - d) "The cache reduced latency."

Answer **b.** "Conducted an analysis of" hides the verb *analyze* and props it up with the weak verb *conduct* → "The team analyzed the customer data." (a) and (d) already use strong verbs. (c) contains "evolution," an abstract noun, but no verb is being suppressed — it's the right word. See §3.2.

3. In which case is passive voice the better choice? - a) "It was decided by the committee to delay the launch." - b) "The bug was fixed by Priya." - c) "The samples were stored at −80 °C until analysis." - d) "An improvement was made to the algorithm by our team."

Answer **c.** The actor (whoever stored the samples) is irrelevant; the storage temperature is the reproducible fact, and methods convention favors passive. The other three name a known, relevant actor and only add words by hiding them at the end — all should be active: "The committee decided…," "Priya fixed the bug," "Our team improved the algorithm." See §3.3.

4. "It is important to note that the deadline is Friday." The best revision is: - a) "It should be mentioned that the deadline is Friday." - b) "Please note the important fact that the deadline is Friday." - c) "The deadline is Friday." - d) "It is worth noting the deadline, which is Friday."

Answer **c.** "It is important to note that" asserts nothing — if it's in the document, it's already noted. Just say the thing. (a), (b), and (d) all swap one empty opener for another. See §3.4.

5. Which phrase should you replace with "because"? - a) "in order to" - b) "due to the fact that" - c) "in the event that" - d) "with regard to"

Answer **b.** "Due to the fact that" (and "owing to the fact that") = "because." For the record: "in order to" → "to"; "in the event that" → "if"; "with regard to" → "about/for." See the §3.4 table.

6. A sentence is "concise but unclear." This is possible because: - a) It can't happen — concise and clear are the same thing - b) Concision means using no excess words; clarity means the reader gets it on the first pass — a short sentence can still be vague or ambiguous - c) Concise writing is always too short to be clear - d) Clarity only applies to long documents

Answer **b.** They're twins, not identical. "Optimize per spec before merge" is concise but unclear — which spec, optimize how? You can be concise and unclear, or clear and slightly long. When they conflict, clarity wins. See §3.1.

7. Why is "the checkout flow was slow; pages took 8 seconds to load" better than "the system experienced performance degradation"? - a) It uses more words, which signals thoroughness - b) It's more concrete — the reader can picture it, measure it, and act on it; abstraction is where vagueness hides - c) "Degradation" is a banned word - d) Passive voice is always wrong

Answer **b.** Concrete, specific language (8 seconds) is visible and actionable; "performance degradation" is true but invisible and could mean anything. It's also more *honest* — it commits to a claim. (a) is backwards. (c) and (d) are false rules. See §3.5.

8. Your reader is a cardiologist. You write "the patient had a heart attack affecting the bottom of the heart muscle due to a blocked artery" instead of "the patient presented with an inferior STEMI." This is: - a) Good — you avoided jargon - b) Bad — for this audience the jargon is the clear, precise, concise choice, and spelling it out is slower and condescending - c) Good — shorter words are always better - d) Bad — the long version isn't accurate

Answer **b.** Jargon is clarity *when the audience shares it*. For cardiologists, "inferior STEMI" is faster and more exact; the plain-language version wastes their time. Clarity is audience-relative. See §3.7.

9. What does the "so what?" test evaluate? - a) Whether the wording of a sentence is tight - b) Whether a sentence should exist at all — does it deliver a fact, support a claim, or move toward a decision? - c) Whether you used active voice - d) Whether the document is formatted correctly

Answer **b.** "So what?" operates *on* the sentence (should it exist?), while the cutting moves operate *within* a sentence (is it tight?). Run "so what?" first — don't polish sentences you'll delete. See §3.6.

10. Which is the strongest counter to "I can't write clearly because my field is too complex — clarity is dumbing down"? - a) "Complex fields don't need writing" - b) "Simplicity removes complexity; clarity removes obstacles to complexity — you can keep all your precision and still write clearly" - c) "Just use shorter words" - d) "Experts don't read carefully anyway"

Answer **b.** The objection confuses simplicity (removing detail) with clarity (removing fog). You can write something fully as complex as your subject and still write it clearly. Dense prose is often *less* precise, because vagueness hides in it. See §3.8.

11. Roughly how much should you expect to cut from a typical first draft? - a) 0–5% - b) 5–10% - c) 20–40% - d) 70–90%

Answer **c.** Expect 20–40% (bloated drafts can lose half). If you cut almost nothing, you didn't run the checklist honestly — drafting and editing are different jobs, so first drafts always carry inert words. See §3.6 and §3.9.

12. In the clarity checklist, why does the "so what?" pass come before the wording passes? - a) It's alphabetical - b) There's no reason to polish a sentence you're going to delete - c) Wording passes are harder - d) It doesn't matter what order you use

Answer **b.** Deleting a sentence makes tightening it moot, so decide existence first, then polish the survivors. See §3.9.

Section 2 — True/False with Justification

State true or false and justify in one sentence.

T1. "Passive voice is always a sign of weak writing and should be eliminated from technical documents."

Answer **False.** Passive is the *better* choice for unknown/irrelevant actors ("the server was compromised at 3:14 a.m."), methods sections, and given-new flow; the rule is "default to active, switch to passive on purpose." See §3.3.

T2. "Cutting words from a draft necessarily means cutting some of its content."

Answer **False.** The cut words are usually inert packaging (empty openers, nominalizations, redundancy); information lives in the nouns, verbs, and numbers, which you keep. This is the chapter's threshold concept. See §3.1.

T3. "All hedging ('the data suggest,' 'may indicate') is empty padding that should be cut for clarity."

Answer **False.** *Honest, calibrated* hedging is necessary and precise when the evidence genuinely only suggests; the sin is *empty, stacked* hedging ("could potentially possibly maybe"). Keep one honest hedge, cut the rest. See §3.10.

T4. "If two writers describe the same outage, the one who uses more technical jargon is being more precise."

Answer **False.** Jargon is precise *only when the audience shares it*; with the wrong reader, unshared jargon carries no information and is the opposite of precise. Precision is audience-relative. See §3.7 and §3.8.

T5. "You should run the clarity checklist on each sentence as you write your first draft."

Answer **False.** Clarity work is *revision* work; running it mid-draft makes you freeze, because you can't generate and critique at once. Draft messily first, then run the passes ([Chapter 5](../chapter-05-writing-process/index.md)). See §3.10.

T6. "Short words are always clearer than long words."

Answer **False.** Usually, but not always — swap for *more accurate* words, not just shorter ones. "Utilize" is bloat for "use" 95% of the time, but it has a narrow correct meaning where the longer word is the precise choice. See §3.10.

Section 3 — Short Answer

S1. Define nominalization and give one example with its fix.

Model answer + rubric A nominalization is a verb (or adjective) turned into a noun, which then needs a weak verb to prop it up — e.g., "make a *decision*" (the verb *decide* frozen into a noun + the weak verb *make*) → "decide." **Rubric:** correct definition + a valid example showing the trapped verb freed.

S2. Name the three legitimate jobs of passive voice.

Model answer + rubric (1) The actor is unknown, irrelevant, or obvious; (2) methods sections / procedures, where the procedure is the subject; (3) managing given-new flow, keeping the topic at the front of the sentence. **Rubric:** all three for full credit; two for partial.

S3. Explain the difference between the "so what?" test and the wording passes (free the verb, sweep empty phrases), and why order matters.

Model answer + rubric "So what?" decides whether a sentence should *exist* (does it carry a fact/claim/decision?); the wording passes make an existing sentence *tight*. Run "so what?" first because there's no point polishing a sentence you'll delete. **Rubric:** captures the existence-vs-tightness distinction and the ordering rationale.

S4. Why is "performance degradation negatively impacted the user experience" a less honest sentence than "pages took 8 seconds to load and 12% of checkouts timed out"?

Model answer + rubric The abstract version commits to nothing — it could describe any problem of any size — so it can't be checked or challenged; the concrete version makes a falsifiable, measurable claim. Vagueness hides behind abstraction. **Rubric:** connects abstraction to unfalsifiability/evasion.

S5. State the chapter's central theme in one sentence: what is the real enemy of precision?

Model answer + rubric Clarity is *not* the enemy of precision — jargon (used with the wrong audience) and bloat are, because they hide the precise statement; clarity is what *delivers* precision to the reader. **Rubric:** names jargon/bloat (not clarity) as the enemy and frames clarity as precision's ally.

Section 4 — Applied Scenario

AS1. (Graded by rubric) Revise this paragraph for clarity. Aim to cut at least 35%. Annotate at least four cuts with the defect each one fixes.

"It is important to note that, due to the fact that the migration of the database was not completed within the originally allotted timeframe, a determination has been made by the engineering team that there are a number of additional steps which will need to be undertaken prior to the point in time at which the system can be considered to be fully operational."

Sample strong revision + rubric **Sample (≈60 → ≈22 words, ~63% cut):** *"Because the database migration ran late, the engineering team identified several more steps needed before the system is fully operational."* Defects fixed: "it is important to note that" (empty opener — deleted); "due to the fact that" → "because"; "a determination has been made by the engineering team" (passive + nominalization → "the engineering team identified," active verb, named actor); "there are a number of additional steps which" → "several more steps" (empty "there are," "a number of" → "several"); "prior to the point in time at which" → "before"; "can be considered to be fully operational" → "is fully operational." **Rubric (5 pts):** ≥35% cut (1) · at least one nominalization freed (1) · at least one empty phrase swept (1) · passive flipped or justified (1) · four defects correctly named (1).

AS2. (Graded by rubric) You're writing one sentence about a bug fix that goes into release notes read by both developers and non-technical users. The fix: the app no longer loses unsaved work when the network drops mid-save. Write the developer version and the user version, then justify why neither is "dumbed down."

Rubric **Rubric (4 pts):** developer version uses shared jargon appropriately (1) · user version uses concrete concepts with no unshared jargon (1) · both are accurate to the same fix (1) · justification correctly invokes audience-relative clarity / "precise for its reader" (1). See §3.7–3.8.

Scoring & Next Steps

Score What it means Do this
< 50% Core moves not yet solid Re-read §3.2 (verbs), §3.3 (voice), §3.4 (empty phrases); redo Section 1.
50–70% You know the moves but miss edge cases Redo Exercises Part B (Revise This) and Section 2 here.
70–85% Solid — ready to proceed Move to Chapter 4 (Structure). Do the Project Checkpoint first.
> 85% Strong command Try Exercises Part D/E and the Deep Dive; you're ready to edit others' writing.