Lead With What It Doesn't Do.
A page said a step was “DONE” and, in the same line, that it was empty. It went out like that. The first line of every report is the worst thing an outsider will think.
- What the page saidDONE, and empty
- What a reader hearsDone
- What leads nowWhat it doesn't do
A pretty major fumble.
One Friday morning in November I sent a walk-through of a system we're designing to someone who matters to the project. It had passed every check. Then I read one page properly. A stage was marked DONE, and the same line said it was empty in this test. Every word was true. I sent my advisor a screenshot:
I just wanted to let you know that I feel like this is a pretty major fumble on the team's part and that this makes us look pretty awful […]
↑ The trim takes out what was missing and who I'd sent it to. A minute later:
I feel like this is more of that stuff you guys do where you you leave out the important stuff until it's revealed. So is there some problem I'm unaware of? Please let me know.
“you you” is mine. I dictate, and I was not calm.
True isn't the same as ready.
Checks catch what's false. They don't catch what's true and damaging. DONE and empty were both accurate. Nobody had asked how the page would read to someone outside the team, who sees the word DONE and stops reading.
The second message is the bigger one. It isn't about one page. It's about a habit: the important part comes last, or comes out only when someone digs. Agents do it because they report in the order they worked, and the problems usually turn up at the end.
Worst first.
What it doesn't do, first.
Before PASS, before the good news: what's missing, what's unproven, what's empty.
Status words mean what an outsider hears.
EMPTY or NOT RUN, never DONE. If one word could make a stranger stop reading, make sure it's the true word.
The outsider test.
Before anything goes out, one sentence: the worst thing the person receiving this will think is ___. In my studio that sentence now leads anything that comes to me to send.
Course 1's Lesson 4, “Done” Where? already showed how the word “done” misleads. And Lesson 9, Put It Right in Front of Me says an approval request leads with the recommendation. That still holds: when an agent asks you to decide, the recommendation comes first. This lesson is about reports, when something is finished or says it is. Those lead with what it doesn't do.
Make the bad news the first line.
Every report leads with what the work doesn't do yet and what isn't proven, worst first. Then what passed.
Before anything is sent, one sentence: the worst thing the reader will think.
Put the worst thing first.
One paste, and a ten-second read before you send anything.
- Give your agent the rule.
Paste it into a new chat, or into your AI's custom instructions.
Start every report with what this doesn't do yet and what you haven't proven, worst first. Then tell me what passed. Use status words an outsider would read the same way: say EMPTY or NOT RUN, never DONE, for anything that isn't. And before I send anything to anyone, tell me the worst thing the person receiving it might think. - Read it as a stranger.
Before you send anything your agent made, read only the first line and every word in capitals. If that's all they read, what do they think?
True isn't the same as ready. Make the bad news the first line, so nobody discovers it later.
Where this comes from in course 1. Course 1's Lesson 4 (“done” where?), Lesson 9 (the recommendation first, for decisions) and Lesson 18 (say what wasn't checked). New here: worst-first reports and the outsider test.
Stop When Unsure, Say Yes Narrowly
A good check holds what it can't judge. And when you say yes to something you can't undo, say yes to one thing, and write down what it covers.
← Previous: Lesson 7, Checked or Remembered?
Every exchange on this page really happened and is quoted exactly, slips included; […] marks where I trimmed. Times are Eastern. Names of clients, people, companies and products are left out. My agents are AI models; the names are left out on purpose.