OI-02
Operational Issue Inflating Lead Time
Operational Issues
Default severity: medium
Product BacklogProcessMetrics
What it detects
A detected operational tracker issue (OI-01) has been open for longer than the configured threshold — it is actively skewing the team\'s cycle time and lead time distributions upward. When these issues are included in control chart analysis, they create false outliers and widen the standard deviation band artificially.
Detection formula
IF issue flagged by OI-01: IF issue.age_days > config.oi.lead_time_inflation_threshold // default: 60d THEN FLAG lead_time_inflator estimated_ct_impact = (issue.age_days - avg_cycle_time) / avg_cycle_time // how much above avg IF estimated_ct_impact > config.oi.critical_ct_impact // default: 1.0 (doubles the apparent avg) THEN CRITICAL Report: \'Excluding this issue would reduce team average cycle time from X to Y days\' Exclusion recommendation: mark as config.oi.exclude_from_metrics_label and re-run analysisExamples in practice
- A team shows a detected operational tracker issue (oi-01) has been open for longer than the configured threshold while lead time inflation threshold is set to 60d.
- Example signal: A detected operational tracker issue (OI-01) has been open for longer than the configured threshold — it is actively skewing the team\'s cycle time and lead time distributions upward.
Suggested response
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Coaching playbook
Symptom
A detected operational tracker issue (OI-01) has been open for longer than the configured threshold — it is actively skewing the team\'s cycle time and lead time distributions upward. When these issues are included in control chart analysis, they create false outliers and widen the standard deviation band artificially.
Why it matters
When "Operational Issue Inflating Lead Time" 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 "Operational Issue Inflating Lead Time" 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.