CC-09
Cross-Team Outlier Concentration
Control Chart
Default severity: medium
ProcessMetricsOutputRisk
What it detects
One team contributes more than the configured share of all UCL-breaching items and total outliers meet the configured minimum.
Detection formula
IF share(team) > config.cc.outlier_concentration_threshold // default: 35% AND total_outliers >= config.cc.min_total_outliers_for_concentration // default: 5 THEN FLAG team as primary dragExamples 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 one team contributes more than the configured share of all ucl-breaching items and total outliers meet the configured minimum while outlier concentration threshold is set to 35%.
Suggested response
Treat the metric as a control signal: confirm limits, windows, and cross-team spread before acting.
Coaching playbook
Symptom
One team contributes more than the configured share of all UCL-breaching items and total outliers meet the configured minimum.
Why it matters
When "Cross-Team Outlier Concentration" 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 "Cross-Team Outlier Concentration" 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.