Case Study 1: The Quarterly Report That Told the Truth and Lied

A composite, anonymized scenario built from patterns common in workplace reporting. Names and numbers are fictional but realistic. The point is the mechanism, not any real company.

The document

Priya, a product analyst, is asked to write the customer-success section of a quarterly board report. The board is non-technical and time-pressured—exactly the audience Chapter 2 warned about, the kind that reads the summary and nothing else. Here is what she drafts, after a manager asks her to "keep it positive—the team's morale needs a win."

❌ Before (every sentence true; the whole thing misleading):

"Customer satisfaction reached an all-time high this quarter, with our Net Promoter Score climbing to its best-ever level. Engagement metrics were strong across the board, and our most active users reported record satisfaction. Churn among long-tenured accounts remained low, reflecting the durable value customers find in the platform. The team's investments in customer success are clearly paying off."

Read it the way the board will: fast, trusting, scanning for the takeaway. The takeaway lands as everything is going great. Now read it the way an auditor would, against what Priya actually knows.

What Priya actually knows

  • NPS did climb to its best-ever level—from 31 to 34, a three-point move, well within the quarter-to-quarter noise the metric usually shows.
  • "Engagement strong across the board" rests on daily active users, which rose. Weekly retention of new users fell for the third straight quarter—and Priya didn't mention it.
  • "Churn among long-tenured accounts remained low" is true. But overall churn rose, driven entirely by new and mid-tenure accounts, which are most of the base. The sentence is true about the slice that looks good and silent about the whole.
  • "Most active users reported record satisfaction"—a survey of the top 5% of users by usage. The other 95% weren't surveyed.

Nothing in the draft is false. Every claim would survive a line-by-line fact-check. And the document lies, because it leaves a board responsible for the company's future with the impression that customer health is improving when the most decision-relevant trend—new-user retention and overall churn—is moving the wrong way. This is the §38.1 mechanism exactly: true sentences arranged to mislead, through selective emphasis (the good slice), omission (the bad trend), and overstatement ("all-time high," "clearly paying off") of a three-point move.

The manager's instruction—"keep it positive"—did not ask Priya to lie. It asked her to spin, which feels different and isn't.

Making it honest

Priya rewrites it. She does not gut the good news; the legitimate wins stay. She applies the four obligations: calibrate the claims (accuracy), surface the decision-relevant trend (transparency), keep it readable for a non-technical board (accessibility), and refuse the lie of omission (the dark side).

✅ After (honest, and still usable by a busy board):

"Customer health is mixed this quarter, with one clear strength and one trend that needs attention. Strength: satisfaction among our most engaged users is at a record, and NPS ticked up from 31 to 34. Watch: overall churn rose this quarter—long-tenured accounts are stable, but new and mid-tenure accounts (the bulk of our base) are leaving faster, and weekly retention of new users has now fallen three quarters running. The likely story is an onboarding problem, not a value problem: customers who stay are happy; the issue is getting new ones to that point. We recommend prioritizing onboarding next quarter and will bring a targeted plan to the next meeting."

Why it's better. It still leads (Chapter 4 BLUF) and it still reports the real wins—Priya is not punishing herself for good news. But it states the NPS move at its true magnitude instead of inflating "all-time high"; it surfaces the trend the board most needs (overall churn, new-user retention) instead of hiding behind the long-tenured slice; and it pairs the limitation with a decision (prioritize onboarding), which is §38.6's "limitation plus consequence" in action. A board reading only this paragraph now has a true picture and a next step. The honest version is, if anything, more useful to the board and more credible for Priya—the analyst who flags the problem early is the one whose future reports get trusted.

The pressure, handled

Priya still has the manager's "keep it positive" to deal with. She doesn't escalate to a confrontation; she uses the §38.8 move. She sends the honest draft with one line: "I kept the real wins up front, but I've flagged the churn trend because the board will see it in the data anyway, and it's better coming from us with a plan attached. Happy to adjust the framing, but I don't think we can leave the trend out." That sentence reframes honesty as prudence (the board will find out; better to control the narrative with a plan), creates a record, and offers collaboration rather than a stand. It is the early, in-writing, constructive form of speaking up—and it almost always works, which is why the dramatic version is rarely needed.

The transferable lesson. The most dangerous workplace document is not the one with a false number. It is the fluent, scannable, "positive" one whose every sentence is true and whose overall impression is a lie. The instruction that produces it—"keep it positive," "make it punchier," "we don't need to mention that"—almost never sounds like a request to deceive. The skill is to notice that it is one, and to find the version that keeps the wins, tells the truth, and hands the reader a decision. Honest is not the opposite of persuasive. Spin is.

Back to: Chapter 38 · Case Study 2 · Key Takeaways