FL-10
Excessive Dwell Between Configured Workflow Stages
Flow
Default severity: medium
ProcessMetricsOutputRisk
What it detects
calendar days between stage A exit and stage B entry exceed `stage_pair_sla_days`; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples 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 calendar days between stage a exit and stage b entry exceed `stage_pair_sla_days`; tests; catalogue during analysis.
Suggested response
Inspect board policy, WIP, and status hygiene so flow matches how work actually progresses.
Coaching playbook
Symptom
The "Excessive Dwell Between Configured Workflow Stages" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Excessive Dwell Between Configured Workflow Stages" 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 "Excessive Dwell Between Configured Workflow Stages" 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.