Looking for 1 workflowstuck between different decisions.
Sometimes the workflow is not stuck.
It is simply being interpreted differently.
One person thinks approval happened.
Another still thinks alignment is pending.
Meanwhile, everyone keeps working.
The workflow is moving.
The decision is not.
That is usually why the same workflow keeps reopening.
Send 3–5 lines:
- the workflow
- what is still waiting
- what keeps reopening
I'll show where decision friction is forming.
24h turnaround.
$39
Trending on Indie Hackers
Interesting framing — “the workflow is moving, the decision is not” is exactly where most systems quietly fail.
I’ve seen this a lot while working on automation-heavy pipelines and contributing to open-source ML/dev tooling — the breakdown usually isn’t execution, it’s ambiguous state, ownership, or implicit approvals that never get formalized.
Your approach of isolating “decision friction” as a layer is solid. It feels like something that could evolve into a systemized diagnostic tool rather than a one-off service.
If you’re building this into a product or need help structuring it into scalable workflows (logic, state tracking, or automation), I’d be interested in collaborating on a paid basis.
WhatsApp: +1 (361) 332-6512