Done, Next, Stuck: The Status Note That Earns You More Trust

There’s a particular kind of Monday morning dread that comes from a one-line message: ‘Where are we with the Henderson rollout?’ You know the project is fine. You know you’ve been busy. So you write four paragraphs, in order, starting with the thing you did on Tuesday and ending with a vague promise to ‘keep pushing’. Your manager reads it, sighs, and asks the only question that matters: ‘So are we on track?’

The problem isn’t your work rate. It’s the shape of the update. Most status reports are diaries: a chronological account of everything you touched. A manager doesn’t need a diary. They need a heading and a handhold — the headline, and the one thing they can do to help. In 2026, when half the team is on a video call and the other half is deep in a chat thread, that shape matters even more.

The two-sentence shape

Here’s the format. It fits in a Slack message, an email or a project check-in.

Done: [what is finished]; next: [what happens next] by [date]. Handhold: I need [specific thing] from [person] by [date], otherwise [consequence].

Two sentences. The first gives the heading: where we are and where we’re going. The second gives the handhold: what’s in the way and what you need. If there’s no blocker, the second sentence becomes: ‘No handhold needed — I’ll flag it by [date] if that changes.’

The labels are doing quiet work. ‘Done’ stops you burying the achievement. ‘Next’ stops you sounding busy without being clear. ‘Handhold’ gives your manager a job, which is usually what they want. It also stops you from hinting. Hinting is the enemy of autonomy.

Why it keeps a manager calm

Managers are not usually short of information. They’re short of certainty. A diary-style update creates more questions: What’s the risk? What are you waiting for? Should I be worried? A two-sentence update answers those before they’re asked.

It also signals reliability. If you say ‘next: send the draft by Thursday’ and then send it by Thursday, you build a track record. If you say ‘handhold: I need the final logo file by Wednesday, otherwise print slips’, you’ve given your manager a chance to act before the problem becomes a crisis. That’s not noise. That’s the opposite of noise. It’s the kind of clarity that makes people comfortable giving you more room.

In Slack

Slack rewards the first line. If your update begins with ‘Quick one — just wanted to give you a quick update on…’, you’ve already lost the room. Start with the heading. Put the two sentences in one message, not three. Use a thread if context is needed. Tag someone only in the handhold sentence, so the notification means something.

For example: ‘Done: pricing table signed off by legal; next: send to print by Friday. Handhold: I need the final logo file from design by Wednesday, otherwise print slips to the following week.’ That’s it. No ‘sorry to bother you’. No ‘just checking in’. The message respects the reader’s time and makes the ask impossible to miss.

In a Friday email

The Friday status email is where diaries go to breed. A subject line of ‘Update’ is a small act of cruelty. Try ‘Status: Henderson rollout — on track / at risk / blocked’. Then the two sentences. If the project is at risk, the handhold names the risk and the ask. If it’s on track, say so plainly. ‘No handhold needed’ is a complete sentence, and a reassuring one.

You can attach the detail. You can link to the spreadsheet. You don’t need to narrate every meeting. The two-sentence update is the summary; the attachments are the evidence. If someone wants the diary, they can read the appendix. Most people won’t. That’s the point.

In a project check-in

At the start of the meeting, go round with the same shape. ‘Done: user research finished; next: prototype by 20 November. Handhold: I need two volunteers for testing by Friday, otherwise the prototype review slips.’ It takes thirty seconds. The rest of the meeting can focus on exceptions, decisions and the handholds people have named. You’ll often find the meeting gets shorter.

This works because it separates status from discussion. Status is a heading. Discussion is what happens when the heading shows a risk. When everyone uses the same format, the room stops performing busyness and starts solving the actual problem.

A few traps

Don’t hide the ask in sentence three. If you need something, it belongs in the handhold. Don’t use ‘in progress’ as a next step; it’s a feeling, not a milestone. ‘Draft sent to legal by Tuesday’ is a next step. Don’t over-format either. Two sentences should not become two paragraphs of bold labels and bullet points. The format is a scaffold, not a personality.

And don’t use brevity as an excuse to omit something important. If the detail changes the decision, include it. The two-sentence update is a headline, not a gag order. You can always add a link, a note or a quick call.

A small habit

The two-sentence update takes about ninety seconds to write. It saves your manager a reply, saves you a follow-up, and makes you look like someone who knows where the project is. That’s not about being noisier. It’s about being easier to trust. Clearer words, calmer managers — and a bit more room to get on with it.