Quiz — Chapter 19: Emails That Get Read and Get Results

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

Section 1 — Multiple Choice

1. The chapter's threshold concept is best stated as: - A) An email should contain everything you know about the topic - B) An email is a tool for getting one specific action, not a record of everything you know - C) Email is less important than reports and papers - D) The longer and more thorough the email, the better

Answer**B.** An email is a tool with a job—usually to get one specific action from one reader—so you write the ask and prune everything that doesn't serve it. (A) and (D) describe the novice "info-dump" mindset the chapter warns against; (C) is backward—email is the *highest-leverage* writing you do. (§19.1)

2. Which part of an email is the only part guaranteed to be read, and therefore the highest-leverage text? - A) The greeting - B) The signature block - C) The subject line - D) The closing pleasantry

Answer**C.** The subject line wins or loses the triage decision—the reader decides whether to open from it alone. That's why "Touching base" or a blank subject forfeits the email's best chance. (§19.3)

3. The three properties that should drive your choice of channel (email vs. chat vs. call vs. meeting) are: - A) Length, formatting, and font - B) Speed needed, permanence needed, and emotional load - C) Time of day, recipient's seniority, and your mood - D) Word count, attachment size, and CC list

Answer**B.** Map a message on how fast you need a response, how permanent the record must be, and how much emotional/interpersonal load it carries, and the right channel usually announces itself. (§19.5)

4. You've exchanged more than three emails on a topic and you're not converging. The chapter's single most valuable channel rule says you should: - A) Send a longer, more detailed email - B) Add more people to the CC line - C) Stop typing and switch to a call - D) Wait a day and resend the thread

Answer**C.** A thread going in circles is a five-minute call you haven't made yet. Email is bad at untangling live, multi-turn disagreement; a real-time call resolves it fast. Then send a short email to record the outcome—*talk to decide, write to record.* (§19.5)

5. In a request email that gets a "yes," the first sentence should contain: - A) A warm pleasantry about the reader's week - B) Several paragraphs of background context - C) The specific ask - D) An apology for bothering them

Answer**C.** Purpose first: the specific ask leads, so a scanning reader knows immediately what's wanted. Warmth can ride alongside (after), but it shouldn't block the purpose. Apology-padding actually makes a request *easier to ignore*. (§19.4)

6. The CC ("carbon copy") line is properly used for: - A) People who must take action on the email - B) People who should see the email for awareness but aren't being asked to act - C) Secretly looping in someone the other recipients shouldn't know about - D) Applying pressure by copying someone's boss

Answer**B.** CC signals "for your awareness, no action needed." (C) describes BCC's worst misuse (a trust landmine); (D) is a recognized passive-aggressive tactic; (A) describes the To: line. (§19.6)

7. BCC ("blind carbon copy") has which two legitimate uses? - A) Secretly watching a conversation, and applying pressure - B) Protecting recipients' privacy on a large send, and cleanly removing people from a thread - C) Hiding typos, and shortening the email - D) Replying faster, and avoiding reply-all storms

Answer**B.** Legitimate BCC: (1) emailing a large group without exposing everyone's address to each other, and (2) moving people off a thread so they're not spammed ("moving Jordan to BCC"). Using BCC to *secretly* loop someone into a live conversation is a trust landmine, not a legitimate use. (§19.6)

8. Research on email communication suggests that email tone: - A) Comes across exactly as the sender intends - B) Tends to read more positively than the sender intended - C) Tends to read more negatively than the sender intended, because text strips tone of voice - D) Is irrelevant as long as the facts are correct

Answer**C.** Senders consistently overestimate how clearly warmth and humor come across; what feels neutral can read as curt, what feels mildly annoyed can read as hostile. So calibrate *warmer* than feels natural, especially for critical content. (§19.6)

9. The four-move structure for a bad-news email is: - A) Apologize at length → bury the news → blame circumstances → vague timeline - B) News early (framed) → owned, non-defensive context → the plan with a real date → what you need - C) Background → methodology → results → discussion - D) Good news → bad news → good news (the "sandwich")

Answer**B.** Surface the news early in one framed sentence; own your part in a sentence (not a paragraph of excuses); lead with a concrete, dated plan (bad news + a credible plan = a manageable situation); say what you need. (§19.7)

10. When you must decline a request, the worst option is: - A) A prompt, clear no with an alternative - B) Saying no and giving one brief reason - C) Going silent and never replying - D) Offering to revisit it later

Answer**C.** Silence is the rudest option—it leaves the asker hanging, nudging, and eventually concluding you're disorganized or dismissive. A prompt, kind no (even a quick "I can't, but here's an alternative") is far better. (§19.8)

11. Which subject line best lets a recipient triage without opening the email? - A) Quick question - B) Update - C) Approval needed by Wed: production deploy Thursday 6pm - D) Re: Re: Fwd: stuff

Answer**C.** It states the action (approval), the deadline (Wed), and the substance (Thursday deploy)—the reader can prioritize correctly in two seconds. A, B, and D force the reader to open the email just to find out whether they need to care, which defeats the subject line's purpose. (§19.3)

12. The corollary "talk to decide, write to record" means: - A) Never use email - B) Use a call/meeting to resolve live disagreement, then an email to capture the outcome - C) Always summarize calls in writing, even trivial ones - D) Decisions should never be put in writing

Answer**B.** Real-time channels (call, meeting) are good at *reaching* a decision through fast back-and-forth; email is good at creating a permanent, scannable *record* of it. Use each for what it does well. (§19.5)

Section 2 — True/False with Justification

T/F 13. Because email is casual and high-volume, it doesn't really matter if your emails are a bit sloppy.

Answer**False.** Email is the *highest-leverage* writing you do—frequency means small flaws compound across thousands of messages, and reputation means colleagues judge your competence by the writing they actually read. It's also permanent and forwardable, so a "quick, sloppy" email can resurface in a review or a dispute. Casual medium, real stakes. (§19.1)

T/F 14. Putting your purpose in the first sentence means your email has to be cold and impersonal.

Answer**False.** Purpose-first is not warmth-free; it's warmth that doesn't make the reader wait. You lead with the purpose and let the warmth ride *alongside* it ("…by the way, hope the launch is settling down!") rather than blocking it with five sentences of windup. (§19.4)

T/F 15. A deadline in the subject line measurably raises the odds of getting a response.

Answer**True.** The reader's decision happens at the *triage* layer—deciding what to prioritize and when. A deadline ("by Friday") lets them slot your email onto a real timeline instead of the undifferentiated "later" pile where emails die. You're doing their triage for them. (§19.3)

T/F 16. Leading a bad-news email with the plan (rather than the problem) is spin that hides how bad the news is.

Answer**False.** The facts are identical either way—leading with the plan doesn't change the news, it changes the *experience*. Bad news triggers the reader's "what now?" question; answering it immediately with a credible plan moves them from anxiety to confidence. It's not spin; it's giving the reader the thing they actually need. (§19.7)

T/F 17. You should reply-all by default so that everyone stays informed.

Answer**False.** Reply-all should be a *conscious choice*, not a default. Reflexive reply-all ("thanks!" to 40 people) wastes collective attention and can trigger reply-all storms. Ask "does *everyone* on this thread need my reply?"—usually no. (Note the reverse error exists too: replying only to sender when a key person needed to see it. The discipline is choosing recipients every time.) (§19.6)

T/F 18. When something makes you angry, the best move is to write your honest reply and send it immediately while the points are fresh.

Answer**False.** Never send an email angry. The hot reply is permanent and forwardable, and you'll likely regret it. Write it, save it as a draft, walk away, reread in an hour. For genuinely charged matters, switch channels—call, don't type—so it isn't in the permanent record at all. (§19.6)

Section 3 — Short Answer

19. Name the four working parts of an effective professional email, and give the one-line job of each.

Model answer**Subject line** — tell the reader what the email is for and whether it needs them, before they open it. **Opening (first sentence)** — state your purpose / what you want, up front. **Body** — give exactly the information the reader needs to act, scannable and no more. **Close (the ask)** — name one clear action and a deadline. *Rubric: all four parts named with a correct job each.*

20. A teammate is about to email a 60-person list to ask one specific colleague for a file. What's wrong with the channel/recipient choice, and what should they do instead?

Model answerEmailing 60 people to reach one is a reply-all/recipient failure—it wastes 59 people's attention and risks a reply-all chain. They should email (or chat) the one colleague directly. If it's a quick "do you have X?", chat is even better than email. *Rubric: identifies the recipient over-scope + names a correct fix (direct to the one person, or chat). (§19.5–19.6)*

21. Give the four moves of a clean "no" email and state which move most protects the relationship.

Model answer(1) Acknowledge/thank them for the ask; (2) the no, clearly and early (a plain no, not a false "maybe"); (3) a brief reason, optional, one sentence; (4) an alternative or open door (another person, a different timeline, a smaller yes, "check back later"). The move that most protects the relationship is **(4) the alternative/open door**—a no *with a path forward* preserves goodwill far better than a flat refusal. *Rubric: four moves + correctly identifies (4).*

Section 4 — Applied Scenario

22. You're handed this email draft. Rewrite it (subject + body) so it gets read and gets a response, then in one sentence name the single biggest change you made.

Subject: hi "Hey Alex, hope you're well! I know it's been a busy stretch for everyone with everything going on. I wanted to circle back on the analytics integration we were talking about a while ago because I think there are a few things that have come up that we should probably sort out, and I was thinking it might be good to find some time to chat about it if you're around at some point this week or maybe next, no big deal if not, just whenever works for you really. Let me know your thoughts!"

Model answer + rubric**Rewrite:** > *Subject: 20 min this week? Need to settle 2 analytics-integration questions (by Thu)* > *"Hi Alex — can we grab 20 minutes this week? I need to resolve two open questions on the analytics integration before Thursday's check-in. I'm free Tue 2–4 or Wed AM [calendar link]; a quick reply works too if that's easier. Hope things are easing up on your end!"* **Biggest change:** Moved a vague, deadline-free request for "some time… at some point" to a specific ask (20 min, two named questions) with a real deadline (by Thursday) in the subject line and first sentence. *Rubric (4 pts): (1) subject states topic + action + timing; (2) purpose/ask is the first sentence; (3) a real deadline appears, with a reason; (4) friction removed (specific times/easy-out) and windup cut. Full marks = all four + correctly names the purpose-first/specific-ask move.*

23. ⭐⭐⭐ Write a bad-news email (subject + body). Scenario: you must tell a client that a deliverable promised for Friday will now arrive Wednesday of next week, because of a problem your team should have caught sooner. Use the four-move structure.

Model answer + rubric**Sample:** > *Subject: [Deliverable] will slip to Wed 6/18 (was Fri) — plan inside* > *"Hi [name], heads-up: the [deliverable] will miss Friday. Realistic delivery is Wednesday, June 18 — three working days late, and I'm sorry for the slip. I wanted you to know now, with a firm date you can plan around. What happened: [one-sentence owned cause — 'we underestimated X']; that's on our side and we should have flagged it earlier. The plan to hit Wednesday: [fix done Mon] → [QA Tue] → [deliver Wed AM], and I'll send a go/no-go update Tuesday EOD. If you need something for Friday, I can send an interim summary or hop on a call to talk options — just say which helps. — [name]"* *Rubric (5 pts): (1) news appears in subject + first 1–2 sentences, framed not buried; (2) a firm, specific new date (not "next week sometime"); (3) context owns the team's part in ~one sentence, not a paragraph of excuses; (4) a concrete, dated plan with a checkpoint leads; (5) an offer to help / what's needed. Strong = all five, warm but not grovelling.*

Scoring & Next Steps

Score What to do
< 50% Re-read §19.2–§19.4 (anatomy, subject line, the request). Redo Section 1.
50–70% Re-read the sections behind your missed items; redo Part B in exercises.md.
70–85% You're ready for Chapter 20. Do the Project Checkpoint email chain if you haven't.
> 85% Strong. Try Extension exercises E1–E3 (build your templates; propose team norms).

Back to: Chapter 19 · Exercises · Key Takeaways