
The Pre-Read That Actually Gets Read
A meeting pre-read short enough that people finish it, the version for a team that will not read in the room, and the one that failed at eleven pages.
Write the thing that replaces the meeting.
The written artifacts of work: status updates, decision docs, briefs, handoffs, channel norms, and what the notetaker is allowed to record. Every post ships the actual document.

A meeting pre-read short enough that people finish it, the version for a team that will not read in the room, and the one that failed at eleven pages.

Nobody read your document. Four diagnoses, the exact re-send message for each, and the one case where getting people to read it will not help.

A status update for an executive two levels up, written against a fixed reading budget — and the one line that survives being forwarded without you.

An async standup format short enough to survive: three lines, one posting deadline, and the three ways a written standup quietly turns back into a meeting.

The update that says a project is at risk, written before anyone asked — with the ask that makes it act, and the sentence most people delete out of fear.

Four diagnostic questions for an update that gets ignored, with the specific repair for each — and the fourth reason, which no rewrite will fix.

One weekly update to a manager, shown before and after a rewrite for a reader who reads the first line and stops. The rewrite is mostly reordering.

A written status update that does the standup's job: filled in for a late project, stripped down for a quiet week, and shown in the version that failed.