Most 90-day readouts are costumes. A deck. A tour of the dashboard. A polite list of what shipped. Nobody kills a stream. Nobody names who will run the weekly in month four. The room applauds a PDF.
An operating readout is shorter and ruder. What was held. What was theatre. Which number moved. Which number was a rumour. What will not continue. Who owns the week when the principal is quiet.
Ninety days is long enough to install a calendar and too short to hide. If independence is not visible — a team that shipped a week without a private thread — you did not install a practice. You rented a person.
The artefacts belong in the room, not in an appendix. Kill list. Claims list. Send graph or editorial calendar. Time-to-launch. Placement or assisted revenue. Duplicate sends. The page a VP can read without a guide.
Agencies love a readout because it is a sales event. A practice treats it as a forcing function for handover. If month three still requires the principal to explain the numbers, month four will too. That is a dependency. Name it.
What to stop putting in the deck: vanity opens, reach without a voice, a roadmap that begins after the meeting. What to start: a decision log. What died. What lived. What the next owner will run on Tuesday.
Finance can attend. They should see the commercial number you picked on day one — not a new model invented for the slides. If you change the number at day ninety, you were decorating.
The 90-day outcome you wrote in the brief is the scoreboard. Portal activation. Booking from email. Off-claim posts. Cycle time. If the brief was vague, the readout will be theatre. That is on both rooms.
Handover language belongs here. Who runs the weekly. Which templates legal already trusts. Which stop rules are written. If nobody can name the next owner, you are hiring a permanent guest. MBX is the wrong shape for that.
Write the readout into the first conversation. Not as a ceremony. As a date. The practice will not invent a second meeting to compensate for a room that will not decide.
A diagnostic mission uses the same standard in a shorter body. Four to eight weeks still ends with architecture, a 90-day plan, and a stack that is instrumented — not a PDF of observations. The clock is a constraint, like any other.
If you want to talk about a readout you already had, send the deck and the admission of what did not change. If you want to talk about the next one, send the brief: team, stack, constraint, 90-day outcome. The form is on Contact.
Camille Edith Baudouin, MBX Consulting