Thread 3 - standup blockers surface too late
Platform
Link
Post Text (Key Excerpt)
I’ve noticed a pattern in our daily standups: someone says “still working on X” for 3 days straight before anyone realizes they’re actually stuck.
By the time it’s brought up, the sprint is at risk.Why It Matches Ryva ICP
This is high-signal standup theater: updates are happening, but real state is hidden until late. It reflects weak ownership signals and delayed blocker visibility in day-to-day dev execution.
Underlying Problem
Status rituals report activity but fail to expose stalled work early enough to intervene.
Suggested Public Response (Copy)
This is exactly why teams feel “busy but surprised.” The issue is not meeting frequency, it is missing state-change signals (new dependency, no progress delta, unresolved blocker owner).Suggested DM Idea (Copy)
Your “3 days of same update then sprint risk” example is painfully common. If useful, I can share a simple blocker signal rubric teams use to catch stagnation before it turns into end-of-sprint escalation.Snapshot
- Subreddit: r/EngineeringManagers
- Author: u/thatDev890
- Posted: 2026-03-25 (1d ago at capture; within 14 days)