Case Study 1: Cutting a Bloated Status Report in Half

A composite, anonymized example assembled from the kind of weekly status reports that circulate in every large organization. Names and numbers are fictional but realistic.

The situation

Every Friday, Dana Whitfield — a data scientist you'll meet again in the data-communication chapters — has to send a project status update to a distribution list of eleven people: her manager, two stakeholders in Marketing, a product lead, and a handful of peers. She has ninety seconds of each reader's attention, and most of them read it on their phones between meetings. Here is what she sent in week 6, before she'd read this chapter. Read it as one of those eleven readers — on a phone, in a hallway, with three other unread messages waiting.

Subject: Project Update

Hi all,

I hope this email finds everyone doing well as we head into the weekend. I wanted to take a moment to provide an update with regard to the current status of the customer churn analysis project that we have been working on over the course of the past several weeks.

It is important to note that, due to the fact that the data extraction process took considerably longer than was originally anticipated, we have experienced some delays relative to the timeline that was initially established. The reason for this is that there were a number of data quality issues that needed to be addressed prior to the point at which we could proceed with the analysis itself. These issues have now, for the most part, been resolved.

At this point in time, we are currently in the process of conducting the modeling work, and it is anticipated that a preliminary set of findings will be able to be shared at some point during the early part of next week. I would also like to mention that there is a possibility that we may potentially need to schedule a meeting in order to discuss the results in greater detail once they become available.

Please do not hesitate to reach out if you should have any questions whatsoever.

Best regards, Dana

Word count: 248. Now answer the reader's three real questions: Is the project on track? When do I get results? Do I need to do anything? You can find all three answers in there — but you have to dig, and a phone reader won't. The answers are: slightly behind, early next week, maybe a meeting. Twelve words of payload buried in 248.

The diagnosis

Run the clarity checklist's eye over it and the defects are everywhere. Tag them by section of the chapter:

• Freeloader sentences (§3.6 "so what?"): "I hope this email finds everyone doing well" and "I wanted to take a moment to provide an update" do nothing — the subject line and the act of sending already establish all of it. The entire first paragraph survives nothing.
• Empty phrases (§3.4): "with regard to," "it is important to note that," "due to the fact that," "prior to the point at which," "at this point in time," "currently in the process of," "in order to," "do not hesitate," "any questions whatsoever." Nearly one empty phrase per line.
• Nominalizations + passive props (§3.2–3.3): "the data extraction process took longer than was anticipated" (passive, no actor), "findings will be able to be shared" (triple-stacked passive), "the reason for this is that there were a number of data quality issues" (empty "there were").
• Abstraction (§3.5): "considerably longer than originally anticipated," "some delays," "a number of data quality issues" — no reader can tell if the project slipped two days or two weeks. How late? How many issues?
• Empty hedging (§3.10): "there is a possibility that we may potentially need to" — three hedges stacked where the facts are actually fairly definite.

The report isn't wrong. Every claim in it is true. It's buried — which, for a status report read on a phone, is functionally the same as not sending it.

The revision

Dana runs the eight passes. "So what?" deletes the entire opening paragraph and the closing pleasantries. The empty-phrase sweep removes a dozen padding constructions. She frees the verbs, names the actor (the team / I), and — most importantly — makes the vague parts concrete: she goes back to her notes and finds the actual slip (four days) and the actual number of data issues (three). Here is what she sends in week 7.

Subject: Churn analysis — 4 days behind, results Tuesday, no action needed from you

Quick status on the customer churn analysis:

Where we are: Data extraction ran 4 days late because we had to clean up three data-quality issues (duplicate customer IDs, missing signup dates, and a timezone mismatch in the event logs). All three are fixed.

What's next: We're running the model now. I'll send preliminary findings Tuesday.

What I need from you: Nothing yet. Once you've seen Tuesday's findings, I may ask for 30 minutes to walk through them — I'll send a separate invite if so.

Questions before then? Reply here.

— Dana

Word count: 96. A 61% cut.

Why the "after" wins

• The subject line answers the three questions before the body is even opened. A phone reader who reads only the subject — which is most of them — now knows everything that matters: on track within a few days, results Tuesday, no action. That alone is the difference between a report that works and one that doesn't.
• It's scannable. Three bolded labels ("Where we are / What's next / What I need from you") let a reader find the one part they care about in two seconds. (That's a structure move — Chapter 4 — riding on top of the clarity work.)
• It's concrete. "4 days late" and "three data-quality issues (duplicate IDs, missing dates, timezone mismatch)" are facts a reader can act on and trust. The vague "some delays" invited worry; the specific "4 days" closes it.
• It's more confident, not less. Cutting the stacked hedges ("possibility that we may potentially") made Dana sound like someone in control of her project. The bloat was reading as anxiety. Clarity read as competence — and the readers' takeaway was exactly the impression all that padding had been trying and failing to create.
• It respects eleven people's time. 248 → 96 words, times eleven readers, every week. Over a six-month project that's a real, compounding gift of attention — and a far higher chance the report actually gets read.

The takeaway

Not one fact was lost between the 248-word version and the 96-word version. Two facts were added (the specific slip and the specific issues), because being forced to be concrete sent Dana back to check the numbers she'd been too vague to state. The cut didn't shrink the content; it exposed it — and improved it. That is the threshold concept of this chapter, demonstrated on one ordinary Friday email of the kind you will write hundreds of times in your career.

Try it: find the last status update, summary email, or progress note you sent. Count its words. Run the eight passes. Almost certainly you can cut 40–60% and answer your reader's real questions in the subject line. The skill you just watched is entirely transferable — it's the same eight passes every time.