Career & professional · a life skill
Advanced Status Updates
one bottom line, cut to four depths
The hard part of a status update isn't the news. It's that a VP, a sponsor, the support desk and the people doing the work each need a different amount of it. Write the bottom line once, then add layers for each reader: the decision and its date for the people who decide, every owner and date for the team.
- Challenging
- Life-Changing impact
- Learn it: 30 days
- Four readers, one draft
The same first sentence opens all four. The people who decide get a short note with one question and a date; the people who follow every step get the full detail.
The method
Write the top once, then cut it to fit each reader.
-
Write the bottom line first
One sentence everyone gets: the news, and what it means for them. If they read nothing else, this is enough.
-
Ask for one decision, with a date
For the people who decide: what you need from them, and by when. A question with no date waits.
-
Offer options, and pick one
Two or three choices with your recommendation marked, so the answer can be a single word.
-
Tell the edges what changes for them
Support and sales don't need the story. They need what's different for them, and from when.
-
Keep the full detail for the team
The people doing the work get every date, owner and risk, below the same bottom line.
One bottom line, cut to fit each reader.
Example: When the logo files ran late, Sam wrote one bottom line and cut it four ways. The VP of product got 40 words: the news, one decision (launch with the current logo) and a date (Tue 23 Mar). The sponsor got the same plus three options with Sam's pick marked, 80 words. Support and sales got 43 words on what changes for them, and the launch team got all of it, 165 words. Every version opened with the same sentence.
The four-depth writer
Write it once, and see each reader's version.
1 · Everyone
2 · The people who decide
Options · up to three, with your pick
3 · The people around it
4 · The people doing the work
5 · Pick a reader
- To
- Subject
Before you send it
Your draft is kept only in this browser. Nothing is sent anywhere; copying puts the version you picked on your clipboard for you to paste.
The research behind it
Busy readers answer short messages.
Todd Rogers and Jessica Lasky-Fink describe an experiment in which 7,002 school board members across the US got one of two emails asking them to fill in a short online survey. One email was 127 words; the other said the same in 49.
The short email got 4.8% of its readers to respond, against 2.7% for the long one: nearly twice as many, for 78 fewer words. And it was the same five-minute survey either way, yet among the people who answered, 29% of those sent the short email expected it to take under five minutes, against 15% of those sent the long one. A long message reads as a big ask.
When they asked working professionals which of two work emails they would deal with first, 165 of 166 picked the shorter one.
The step from a survey request to a status update is ours: the study tested emails, not updates. But an update to a VP is the same kind of message. It asks a busy person for a few minutes, and the reply you need is one decision. Putting that decision and its date up top, in the fewest words, is the version most likely to be read first and answered.
The idea
Why it works.
Every reader starts at the top, and most stop early. So the top has to carry the news on its own, and each layer below it is for a smaller group of readers who need more. Cutting a version down never touches the first sentence; it removes layers from the bottom.
It also keeps four versions honest with each other. They all open with the same sentence, so the VP and the team never hear two different stories. Work out who sits where before you write, with a stakeholder map, and keep the weekly version going with deliberate status updates.
When it goes wrong
Habits that help.
- Bad news goes first too. A bottom line that hides the slip under three good things is the one a VP remembers you for.
- One ask per note. Two decisions in one update get one answer, usually to the easier one.
- A date, not “soon”. “By Tuesday 23 Mar” gets a reply by Tuesday. “Soon” gets a reply when it's convenient.
- Don't forward the team version up. If the VP needs the detail, they'll ask for it. Offer it in one line instead.
Keep this going in the app.
HourLife turns these ideas into a daily system — goals, habits, focus, and reflection in one private place.
