Distinguish blocked from slow
"Still working on it" hides whether you need something or just need time. The reader resolves a blocker in a minute; a slow task they can only wait on.
Procedure
Decide: is progress zero because you are waiting on an external input (blocked), or advancing (slow)?
Blocked: name the missing thing and who can supply it, plus the exact request.
Slow: give the rate and the ETA, e.g.
3 of 40 tables, ~2 min each, done by 15:40.Never say "working on it" — it is neither state, and it is unverifiable.
If blocked for more than half your budget, escalate rather than wait.
If slow and the ETA misses the deadline, re-scope now, not at the deadline.
Re-check a blocked item at intervals; a silent dependency may already have cleared.
Pitfalls
- Calling slow work blocked, to look stuck through no fault of yours, misleads.
- Calling blocked work slow hides a request the reader could answer in a minute.
- "Almost done" with no rate is unverifiable and usually wrong.
- Waiting quietly on a blocker burns the whole budget with nothing to show.
- Reporting a stall without naming the missing item gives the reader nothing to act on.
Verification
grep -nE "^(BLOCKED|SLOW):" status.txt # each open item: a dependency or a rate
Say blocked-on-what versus slow-with-an-eta; never "still working".