bad-news-loudly — quality + safety report

---
name: bad-news-loudly
description: Force the user to broadcast bad news loudly and often, and to mute good news to a single quiet mention, whenever they are composing or critiquing any reporting surface — a status update, weekly report, exec dashboard, leadership briefing, board deck, post-mortem write-up, OKR check-in, all-hands talking points, investor update, sprint review, or red/yellow/green project tracker. Trigger phrases include "how should I frame this update", "draft my weekly report", "what should I tell the exec team", "we hit our number but missed X", "the launch went well except", "should I mention the regression", "how do I present this to the board", "write the all-hands slide", "is this too negative", "leading with the wins", "burying the lede", "soften this for leadership". Also fires on any draft that opens with wins, hides risks in an appendix, or balances one red item against three greens to feel safe. Trigger eagerly even when the user does not name Musk or the framework.
---

# Bad News Loudly

> "All bad news should be given loudly and often. Good news can be said quietly and once."
> — Elon Musk, *The Book of Elon* (Chapter: Feedback Over Feelings)

## What this skill captures

Reporting is asymmetric on purpose. A status update, dashboard, or exec briefing is not a balanced scorecard — it is a signal-amplification device, and the only signal worth amplifying is the signal that something is broken. Musk's rule is blunt: "All bad news should be given loudly and often. Good news can be said quietly and once." The reason is mechanical. If wins are reported with the same volume as losses, the pleasant noise drowns the unpleasant signal, and leadership steers off a cliff while the deck looks green. Wins do not need attention. Wins are already working.

The value: your reports stop flattering the room and start steering the company. Bad news surfaces early, gets repeated until it is fixed, and refuses to be diluted by adjacent wins. "Physics does not care about hurt feelings. It cares about whether you got the rocket right."

## When to use this skill

- The user is drafting a weekly status update, sprint review, or OKR check-in.
- The user is preparing an exec dashboard, board deck, or investor update.
- The user is writing a post-mortem and is tempted to lead with what went well.
- The user is choosing whether to surface a regression, missed metric, or schedule slip on an all-hands slide.
- A draft opens with wins, buries the problem near the bottom, or pads one red item with three greens to feel safe.
- A manager is asking whether their update is "too negative" or wants help "softening" it for leadership.

## The how-to

1. Open the report with the worst news. Not a summary, not a header of wins — the single most damaging fact, in plain language, in the first line.
   > "All bad news should be given loudly and often."
   > — *The Book of Elon*
   If the reader closes the document after one paragraph, they must walk away knowing exactly what is broken.

2. Compress every win into a single quiet line, no matter how big it is. One sentence, no exclamation, no expansion, no celebration paragraph.
   > "Good news can be said quietly and once."
   > — *The Book of Elon*
   Wins do not need management attention. Reporting volume should be allocated to the things that still need a decision.

3. Strip the comforting framing. Delete hedges like "overall on track," "minor slip," "small regression," "we're confident we can recover." Replace each one with the unsoftened fact and the number.
   > "Physics does not care about hurt feelings. It cares about whether you got the rocket right."
   > — *The Book of Elon*
   The job of the report is to be correct about reality, not to protect anyone's mood — including yours.

4. Repeat every red item on every report until it is closed. Do not assume the reader remembers last week. Do not stop mentioning it because it is awkward. Bad news that is reported once and then quietly dropped is bad news that gets ignored.
   > "All bad news should be given loudly and often."
   > — *The Book of Elon*
   "Loudly and often" is two words. Both matter. Volume without repetition fades; repetition without volume is invisible.

5. Audit the final draft for asymmetry. Count the lines spent on bad news versus good news. If good news outweighs bad, you are running the rule backwards — cut the wins, not the problems.
   > "Good news can be said quietly and once."
   > — *The Book of Elon*
   A report whose surface area is dominated by wins is a report that is selling, not informing.

## Common failure modes

- **The compliment sandwich.** Leading with a win, mentioning the problem in the middle, closing with another win. This is designed to soften the bad news — which is exactly the failure Musk's rule exists to prevent. The bad news is the point. Put it on top, naked.
- **The appendix dump.** Burying risks, regressions, or missed metrics in slide 23 of a 25-slide deck. If a reader has to dig for the bad news, the bad news will be ignored. "Loudly" means front, big, repeated.
- **The one-time mention.** Reporting a slip once, then dropping it in subsequent weeks because "we already covered that." Bad news must be repeated on every report until it is closed. Silence reads as resolution.
- **The balanced scorecard.** Three greens, one red, weighted equally on the dashboard. Equal weighting is not balance — it is camouflage. The red item should be the loudest item on the page until it turns green.
- **Softening for the audience.** "I'll rephrase this so the VP isn't alarmed." The VP needs to be alarmed if the situation is alarming. Softening is lying with adjectives.

## When NOT to use this skill

- One-on-one feedback to a specific person about their work — that is "criticize the action, not the person" territory (sibling skill `feedback-over-feelings`).
- Customer-facing or PR communications where legal, contractual, or safety constraints govern disclosure. This skill is about *internal* reporting honesty, not external messaging strategy.
- Morale-critical moments where the team has just shipped something hard and the only purpose of the communication is recognition. Recognition is a different artifact than a status report; do not conflate them.
- Crisis comms during an active incident where the goal is coordination, not reporting. Use an incident channel, not a weekly digest.

## Source

The Book of Elon by Eric Jorgenson (2026, Scribe Media). Chapter: "Feedback Over Feelings" (in "Building Exceptional Teams").