OI-07
Metric Exclusion Advisory — Operational Issues Impact Report
Operational Issues
Default severity: medium
Product BacklogProcessMetrics
What it detects
Generates a report showing what team metrics would look like if all detected operational tracker issues were excluded from analysis. This gives the team and coach a clear before/after picture of how much these issues are distorting the real delivery signal. oi_issues = issues WHERE OI-01 flagged
Detection formula
FOR each_metric M IN \[avg_cycle_time, median_cycle_time, UCL, LCL, stddev, WIP, throughput, velocity_sp\]: M_with_oi = compute_metric(M, all_issues) M_without_oi = compute_metric(M, all_issues EXCLUDING oi_issues) delta(M) = M_with_oi - M_without_oi delta_pct(M) = delta(M) / M_without_oi Report: side-by-side comparison table — \'with operational issues\' vs \'without operational issues\' IF delta_pct(avg_cycle_time) > config.oi.significant_impact_threshold // default: 0.15 (15% distortion) THEN CRITICAL — operational issues are significantly distorting team metricsExamples in practice
- A team shows generates a report showing what team metrics would look like if all detected operational tracker issues were excluded from analysis while significant impact threshold is set to 0.15 (15% distortion).
- Example signal: Generates a report showing what team metrics would look like if all detected operational tracker issues were excluded from analysis.
Suggested response
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Coaching playbook
Symptom
Generates a report showing what team metrics would look like if all detected operational tracker issues were excluded from analysis. This gives the team and coach a clear before/after picture of how much these issues are distorting the real delivery signal. oi_issues = issues WHERE OI-01 flagged
Why it matters
When "Metric Exclusion Advisory — Operational Issues Impact Report" 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
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Facilitation questions
- What system change would stop "Metric Exclusion Advisory — Operational Issues Impact Report" 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.