8 May 2026
Honest bad news: writing leadership updates that don't lie
Most status updates are written to manage the reader's feelings, not to inform their decisions. The blocker is buried three paragraphs down, the slip is dressed up as a minor timing adjustment, and the line that should read “I need a decision from you by Thursday” never appears at all. We write them the other way around. Every update leads with the bad news, states it plainly, and pairs every blocker with the options for clearing it.
The reason updates lie is rarely malice. It is incentive. The person writing the update is, in practice, graded on the update, so the update gets optimised and the project it describes does not. A slip becomes a “minor timing adjustment.” A risk that should stop the room becomes “something we're monitoring closely.” None of it is technically false. All of it is arranged so the reader feels better and knows less.
The cost lands on the reader, who cannot act on what they cannot see. A blocker buried three paragraphs down is a decision delayed by a week. The update did its job for the sender and failed its only real job: to inform a decision.
Lead with the line you least want to write
So invert the order. Open with the thing the reader needs in order to act, which is almost always the bad news. State it in one sentence with no softening clause: “We will miss Thursday's date.” Then, immediately, the options, because a blocker without options is a complaint, and a complaint is not an update. “We can cut scope and still hit Thursday, or hold scope and move to Tuesday. I recommend the first.” That sentence turns “I'm stuck” into a decision the reader can actually make.
We hold our own systems to this literally. When an agent in the NOMARK harness fails the same approach twice, the protocol is not to try a third time and report progress. It is to stop and write a blocked entry: the reason in plain words, routed to whoever can clear it. Not “still investigating.” Not “should be resolved shortly.” Blocked, why, and who decides. The session record is built so the honest bad line is the required line.
An update is not a performance. It is an instrument for someone else's decision.
The audit at the end of every session works the same way. A claim that something is done is checked against the actual output that proves it. Saying “done” without that evidence is not a rounding error to be smoothed over in the write-up; it is a graded breach. The whole structure is arranged so the comfortable lie costs more than the uncomfortable truth, which is the only arrangement under which people reliably tell the truth.
Honesty is faster
The counterintuitive part is that honest bad news builds trust faster than good news does. A sender who tells you the bad thing plainly, early, with options, is a sender you can stop double-checking. Hedging does the opposite: it trains the reader to translate everything you write, to assume the real status is somewhat worse than the words, and to spend time finding out how much worse. That tax is paid on every future update, not only the one that hedged.
There is a single test for whether an update is honest. Would the reader make a different decision if they knew what you know? If the answer is yes and you left it out, the update lied by omission, which counts. Lead with the worst true line in the document. Especially when it is the line you would most like to bury.