CC-02
Rolling Avg Above Overall Avg
Control Chart
Default severity: medium
ProcessMetricsOutputRisk
What it detects
Rolling average exceeds the overall period average and has remained above it for the configured number of days.
Detection formula
IF rolling_avg > overall_avg AND days_above >= config.cc.crossover_persistence_days // default: 14 THEN FLAG Record crossing_dateExamples in practice
- Rolling averages, control limits, or band width diverge from expected statistical bounds.
- Recent control-chart windows show drift, clusters, or missing limit configuration.
- A team shows rolling average exceeds the overall period average and has remained above it for the configured number of days while crossover persistence days is set to 14.
Suggested response
Treat the metric as a control signal: confirm limits, windows, and cross-team spread before acting.
Coaching playbook
Symptom
Rolling average exceeds the overall period average and has remained above it for the configured number of days.
Why it matters
When "Rolling Avg Above Overall Avg" 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
Treat the metric as a control signal: confirm limits, windows, and cross-team spread before acting.
Facilitation questions
- What system change would stop "Rolling Avg Above Overall Avg" 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.