FL-06
Column Accumulation Bottleneck
Flow
Default severity: high
ProcessMetricsOutputRisk
What it detects
Average time in a specific column exceeds the configured multiplier of the average time across all columns. avg_time_all = AVG(time_in_column, all_columns)
Detection formula
IF AVG(time_in_column\[C\]) > avg_time_all * config.flow.bottleneck_time_multiplier // default: 2x THEN FLAG column C as bottleneckExamples in practice
- Board policy limits are exceeded or status movement patterns look artificial.
- Work piles up in one column or moves in bulk instead of flowing steadily.
- A team shows average time in a specific column exceeds the configured multiplier of the average time across all columns while bottleneck time multiplier is set to 2x.
Suggested response
Inspect board policy, WIP, and status hygiene so flow matches how work actually progresses.
Coaching playbook
Symptom
Average time in a specific column exceeds the configured multiplier of the average time across all columns. avg_time_all = AVG(time_in_column, all_columns)
Why it matters
When "Column Accumulation Bottleneck" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Inspect board policy, WIP, and status hygiene so flow matches how work actually progresses.
Facilitation questions
- What system change would stop "Column Accumulation Bottleneck" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.