Flow is one of those Lean words that sounds abstract until you see it broken. On a shop floor, a bottleneck is obvious: inventory piles up in front of one machine while the rest of the line waits. In a digital improvement system, the pile-up is just as real, but it's invisible unless you know exactly where to look.

There are four places in a typical KaiNexus workflow where work stalls, and each one erodes your CI culture in a slightly different way.

New items that sit unassigned

When someone submits an idea, it stays in New status until a leader reviews and assigns it. If that review doesn't happen quickly, the person who submitted the idea gets a clear, if unintended, message: leadership isn't listening. The best practice threshold here is tight, 24 to 48 hours, because that early window is when someone's enthusiasm for their own idea is highest. Let it sit past that, and you're not just delaying a project, you're teaching people not to bother submitting next time.

The usual root cause isn't a bad process, it's a habit. Leaders batch their reviews for a weekly meeting instead of triaging as ideas come in. That's an easy habit to coach, but only if someone's watching for it.

Items that go overdue and stay overdue

Overdue status means the due date passed without the work being completed. On its own, that happens. The problem is what it signals when it becomes a pattern: either the team lost track of the work, the original due date was unrealistic, or nobody's actually supporting the team with the time to do it. Each of those has a different fix, and each fix targets a different person. Coach the team if they've disengaged, coach the leader if their estimates are consistently off, and check resourcing if the team genuinely doesn't have the bandwidth you assumed they had.

Items that go quiet without being closed

Every Item shows a "Last Updated" date. If that date is old but the Item's still technically active, something's wrong, either the work stopped without anyone formally closing it out, or the work is continuing somewhere outside the system and nobody's logging it. The second case is worth watching for specifically, because it means your data no longer reflects reality, and any report built on top of it is quietly wrong.

Resolutions stuck waiting for approval

This is the bottleneck that costs you the most without being obvious. The work is done. The impact hasn't been recorded because nobody's approved the resolution yet. Every day that sits unapproved is a day your ROI reporting understates what your program actually delivered, and a day the person who did the work doesn't get credit for it.

Finding bottlenecks before they become a pattern

You don't have to wait for these to surface anecdotally. KaiNexus has three built-in ways to catch them: the Activity Over Time Report (which shows how many Items are sitting in each status over time), the Reports Snapshot status bars, and a dedicated Bottleneck filter you can apply to any Item List, so you can see exactly which Items have been stuck in New, Overdue, or Resolution Submitted longer than your own threshold allows.

Full setup instructions for all three, including how to configure the Bottleneck filter's logic and timeframes, are in Bottlenecks in the Help Center.

The habit that actually fixes it

None of these bottlenecks get solved by a configuration change alone. They get solved by a leader who checks the Bottleneck filter on a schedule, the same way they'd walk the floor looking for a growing pile of inventory. Set that check up as a recurring five minutes, not a fire drill you run when someone complains.

Next up: Respect for People, and the two decisions in KaiNexus that either build trust or quietly erode it.