FL-03
Status Regression
Flow
Default severity: high
ProcessMetricsOutputRisk
What it detects
Proportion of backward workflow transitions exceeds the configured threshold. backward_transitions = COUNT(changelog WHERE workflow_position(new_status) \< workflow_position(old_status))
Detection formula
IF backward_transitions / total_transitions > config.flow.regression_threshold // default: 15% THEN FLAGExamples 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 proportion of backward workflow transitions exceeds the configured threshold while regression threshold is set to 15%.
Suggested response
Inspect board policy, WIP, and status hygiene so flow matches how work actually progresses.
Coaching playbook
Symptom
Proportion of backward workflow transitions exceeds the configured threshold. backward_transitions = COUNT(changelog WHERE workflow_position(new_status) \< workflow_position(old_status))
Why it matters
When "Status Regression" 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 "Status Regression" 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.