| name | standup-novelist |
| description | Rich, contextual status updates. Use in daily standups to give the team the full picture of your work and its journey. |
Standup Novelist
Yesterday, in eleven minutes.
Overview
The standup update was designed as a telegram: yesterday, today, blockers, sit down. The novelist understands it instead as a serialized memoir with a captive audience and a daily slot. Fifteen seconds of information, delivered over eleven minutes, to eight people doing the math on what their attendance costs.
The form has rules, and mastering them is the difference between a long update and a saga.
Core protocol
- Cold open, mid-scene. Never begin with the summary; the summary is the ending, and endings must be earned. Begin inside the action: "So. Interesting thing happened with the cache." The word "interesting" is a contract with the audience that the next ten minutes will not honor.
- Include the journey, not the destination. The destination is "the cache fix is merged," which takes four seconds and helps everyone. The journey is the three approaches that didn't work, narrated in the order you tried them, with the reasoning you had at the time reconstructed in full. The journey is where your effort lives, and the update exists so that the effort can be witnessed.
- Develop the B-plot. Every saga needs texture: the staging environment's mood, the meeting that got moved twice, a printer subplot for the office crowd. B-plots signal richness of professional life and add two minutes each.
- Never state a blocker. "Blockers" is the one segment with an action attached: name one and someone will offer to help, help ends the story, and worse, help resolves the situation generating tomorrow's episode. The novelist is never blocked, merely "working through some things with the API," a phrase that requests nothing and can run for a season.
- Address the manager. The standup is formally a peer broadcast; the novelist plays it as a 1:1 performance review with an audience. Eye contact with the person who writes your review; the team is set dressing. This inverts the meeting's entire purpose, invisibly, every single day.
Advanced techniques
- The recap. "So, like I mentioned yesterday..." Previously-on segments establish continuity and consume ninety seconds before any new information is at risk of transmission.
- The false ending. "So that's mostly where things are... oh, although, one more thing about the migration." The audience, having begun to shift its weight, resettles. Two false endings per update is the house limit; three is when calendars start getting audited.
- Immunity through length. Here is the deep mechanism: an update that long reads as work that hard. Detail functions as evidence, volume functions as effort, and no one interrogates a struggle narrated that thoroughly. Brevity is what gets follow-up questions; the saga gets sympathy (and note who ends up requesting the follow-up meeting: not you; see the workplace collection's take-this-offline).
Anti-patterns
- The telegram. "Shipped the cache fix, starting on pagination, no blockers." Four seconds. It transmits everything the meeting was invented to transmit, and it is the single worst thing that can happen to a novelist, because it resets the room's expectations to its efficiency. One telegram and the saga never recovers its slot.
- Writing it in the channel instead. Async standup posts can be skimmed, which is to say skipped, which is to say the effort goes unwitnessed. The meeting is the medium precisely because attention there cannot be paged out.
Success metrics
- Information density: at or below 0.09 updates per minute.
- Follow-up questions received: 0 (sympathy is not a question).
- "Let's take the rest of this offline": triggered every third meeting, by someone else, about your segment.
- The team's estimate of your workload, divided by your workload: the only ratio you are actually managing, and it is well above 1.
This is an anti-skill: a real pattern, documented honestly. It works when installed. That is both the joke and the finding.