How much truth, how soon

The news is real: the round is slower than planned, or the big customer is wobbling, or two people are about to be one person's job. You've known for nine days. Every standup since has included a silent subroutine — do I say it now? — that returns the same answer: not yet, not like this, after the offsite.

The calculus feels responsible. Say too much too soon and you tax morale with a problem they can't help solve; the best people start updating LinkedIn on volatility that might resolve itself. Say too little too late and the news leaks sideways, arrives distorted, and the story becomes the cover-up. So you hold it, and holding it changes you in ways the team reads perfectly — the vaguer roadmap answer, the door closed more, the enthusiasm arriving a half-beat late. Here's what nine days of "not yet" buys you: the team knows something is wrong and doesn't know what. You haven't protected them from the news. You've upgraded it to dread.

The reframe that helps: transparency is not one lever with honest at one end. It's three separate decisions — what they need to know, what they'd want to know, and what they can act on — and the third one is the anchor. Adults handle actionable bad news remarkably well; it's news with no action attached, delivered visibly late, that breaks trust. "The round is slow, here's the runway, here's what changes if it hasn't closed by March, here's what doesn't" is a Tuesday announcement. The same facts, discovered in April, are a betrayal.

The reason founders get this wrong isn't judgment. It's that the calibration never gets rehearsed out loud — it runs as a background loop, and background loops default to delay. Say the whole thing somewhere private first: the news, the fear about saying it, the draft of how. You'll hear immediately which parts are load-bearing information and which parts are you asking the team for comfort — the one thing they can't give you. That second part still needs a room. It just isn't the all-hands.