Looking for workflows where everyone agrees but nothing moves
Sometimes the blocker is not the decision.
The decision exists.
The owner exists.
The deadline exists.
Everyone agrees on the direction.
Yet nothing moves.
Because nobody defined:
- who moves first
- what gets delivered first
- what officially starts execution
The workflow is not blocked.
The workflow is waiting.
Looking for examples where agreement existed, but movement never started.
Trending on Indie Hackers
The handoff to next action gap is even more dangerous in automated workflows because there is no human watching. A person waiting on a teammate might eventually ask. A system waiting on another system just stays waiting until someone notices revenue stopped moving. Have you seen this gap vary more by team size or by workflow complexity?
Exactly — the waiting pattern is more dangerous than a block because everyone can see a block. "Soon" is the most expensive word in cross-team workflows because it lets everyone off the hook without anyone committing. A defined response time turns a vague expectation into a measurable commitment. The teams that do this well don't track velocity, they track handoff time.
Tracking handoff time instead of velocity is where the real execution leakage becomes visible.
Velocity only measures active work. It rarely captures the waiting time between one person finishing and the next person actually starting.
"Soon" is risky because it creates the feeling of alignment without defining a commitment.
I've found that measuring the gap between "handoff" and "next action" often explains more about execution speed than velocity alone.
Exactly. The silent stall pattern is more dangerous than an explicit block because nobody flags it as blocked. A blocked workflow gets attention and gets resolved. A waiting workflow just sits there slowly losing urgency until someone finally asks "is anyone working on this?" and the window has already passed. The most effective fix I have seen is adding a simple rule: if no movement within 48 hours, escalate to X. The escalation is rarely needed, but knowing it exists changes how people prioritize the handoff.
That silent stall is exactly where time and money leak without anyone noticing.
People don't realize a workflow is dying because it still looks active.
Your 48-hour rule is necessary.
It forces teams to treat a handoff as a commitment rather than a casual pass.
When there is no clear trigger or consequence for sitting on a task, "soon" turns into next month.
It's less about coordination itself and more about making inactivity visible.
The most common version I see is when the execution start depends on someone getting back to someone else, and nobody defined the expected response time. Agreement exists, everyone is waiting for the other person to move first, and the workflow enters a silent stall. The fix is usually not a better decision process, its a rule about who initiates and by when. I have seen this pattern more in cross-team workflows than within a single team.
I agree.
The expected response time is a big part of it.
I've seen cases where everyone assumed the next person would move soon, but nobody defined what "soon" actually meant.
The workflow wasn't blocked.
It was waiting.
And everyone thought someone else was about to move it forward.