the hard morning
What to say in standup when you feel like you did nothing
You almost certainly did something. Reading code, ruling out a cause, sitting in reviews, answering three people so they could keep going: that is work, it just leaves no artefact, so it feels like nothing by 9:04.
The fix is to report the process instead of the output, and to say the day count out loud. Below is wording for the six versions of this day. None of it inflates anything, because a padded update is the only kind that will actually hurt you.
Put down whatever you have, even one line. It is more than you think.
5 free a month. No signup to try the first one.
scraps
Half sentences are fine.
Sat 31 Oct
Nothing to report.
Nothing planned yet.
Nothing blocking.
Paste anything on the left. Half sentences are fine.
5 of 5 free updates left in October. the Pass
Statusly rewrites what you actually did. It does not invent work, and it never will.
Six versions of the day, in words you can post
Pick the one that is true and change the nouns.
*Done* • Chased the flaky checkout test. Ruled out timing and the fixture, so it is not either of those. • Wrote what I ruled out into the ticket so nobody repeats it. *Next* • One more hour on it, then I bring in a second pair of eyes. *Blocked* • Nothing blocking.
*Done* • Roadmap review, 2 interviews, the security walkthrough. No code today. • Wrote up the security decision so it is not lost in the call. *Next* • Back on the retry queue with a clear morning. *Blocked* • Nothing blocking.
*Done* • Read through the export path end to end. Found the CSV writer duplicated in 3 places. • Sketched the shared writer in the ticket. *Next* • Start on the shared writer. *Blocked* • Nothing blocking.
*Done* • Reviewed 4 PRs, 2 of them long. Unblocked Ravi on the migration ordering. • Answered the on-call question about the retry limits. *Next* • My own branch, first thing. *Blocked* • Nothing blocking.
*Done* • Day 3 on the billing refactor. Split the invoice writer out of the charge path. • 4 tests around the split, all green. *Next* • Proration logic across, then delete the old path. Expect to finish tomorrow. *Blocked* • Nothing blocking. Say something if the 3 days worries you.
*Done* • Little to report. Environment was broken until after lunch, then I was in support. *Next* • The retry tests, before anything else. *Blocked* • Nothing blocking.
Three rules for the nothing day
The goal is to stay legible to your team without claiming work you did not do.
Report the elimination
"Ruled out timing and the fixture" is a real result. Investigations produce knowledge, and knowledge is reportable.
Say the day count
Day 3 on the same task is fine. Day 3 disguised as three different vague updates is what erodes trust.
Never pad
Do not turn a meeting into an achievement or an intention into a Done. One inflated line costs more than ten quiet days.
A template still leaves you an empty box tomorrow.
This page helps once. What makes the morning stop hurting is that Statusly keeps yesterday, so what you said you would do next is already sitting in today’s Done, waiting for you to confirm it or correct it.
The blocker you never cleared is still flagged, because you never said it cleared. Correcting an update takes 30 seconds. Writing one from nothing is what you have been avoiding.
carry-over
You said you’d write the retry tests. Done?
Still blocked on Priya, 3 days.
The scraps box is empty, and optional.
Is it bad to say I did nothing in standup?
Saying "nothing" is worse than saying what actually happened. "Environment was broken until after lunch" is specific, true and hard to argue with.
Can I just skip my standup that day?
Skipping is the option most people take, and it is the one that makes your work invisible. A two-line honest update beats silence every time.
How do I stop this happening every morning?
Write things down as they happen rather than trying to recall them at 9:04. That is what the log below is for.