Period Comparison
Incidents - Status
Jul 9, 2026, 01:10 PM
Period Comparison
The Incident resolution process significantly deteriorated, with average duration more than doubling and rework rates increasing by over 50%, despite a large reduction in process variation.
The Incident Management process has significantly deteriorated. Average resolution time increased by 127% and rework jumped from 40% to 60%. These critical degradations are likely driven by a shift to a small number of highly complex incidents, which overshadows any gains from process standardization.
📅 Baseline: 2024-01-02 – 2024-01-15 📅 Comparison: 2024-01-16 – 2024-01-29
▼▼
Overall verdict
Significantly Deteriorated
✓ Confidence: Moderate
The verdict is driven by the catastrophic increase in two key metrics: Average Duration (+127%) and Rework Rate (+51%). These indicate a severe loss of efficiency and effectiveness. The confidence is 'Moderate' instead of 'High' only because the comparison period's sample size (25 items) is extremely small compared to the baseline (1015 items), suggesting the results could be an outlier.
📊
Metric-by-Metric Comparison
Avg Duration
▼ Degraded High impact
249.0 hrs 565.9 hrs
+316.9 hrs (+127.3%)
The time to resolve an incident has more than doubled, severely impacting service levels and user satisfaction.
% Rework
▼ Degraded High impact
39.7% 60.0%
+20.3% (+51.1%)
A majority of incidents now involve rework, indicating significant process instability, incorrect initial assessments, or unresolved underlying issues.
Variants
▲ Improved High impact
161 variants 11 variants
-150 variants (-93.2%)
The process has become dramatically more standardized, which is a positive structural change. However, the remaining paths have become extremely slow.
Avg Flow Efficiency
▲ Improved High impact
11.6% 35.7%
+24.1% (+208.0%)
This indicates that a larger proportion of the (much longer) total time is spent in an 'active' state. This is a 'bad' improvement, suggesting items are stuck in 'Work in Progress' for extreme durations rather than waiting in queues.
Work Items
→ Unchanged High impact
1015 items 25 items
-990 items (-97.5%)
The massive drop in volume is critical context. The comparison period may not be representative and could reflect a focus on a few difficult, lingering incidents.
What Improved
Drastic Process Standardization
Variant Count 161 → 11 -150 (-93.2%)
A massive reduction in process paths makes the workflow more predictable and easier to manage. This is a significant structural improvement, though its benefits are currently negated by performance issues.
Faster Initial Triage
Open -> Work in Progress 64.1 hrs → 28.6 hrs -35.5 hrs
The time from an incident being 'Open' to 'Work in Progress' has been halved, showing the front-end of the process has become more responsive.
What Deteriorated
Resolution Time More Than Doubled
Avg Duration 249.0 hrs → 565.9 hrs +316.9 hrs (+127.3%)
This is a critical failure in performance, indicating the process is taking far too long to deliver value and resolve user issues.
Rework Rate Skyrocketed
% Rework 39.7% → 60.0% +20.3% (+51.1%)
A majority of incidents now require rework, pointing to systemic issues with quality, diagnosis, or resolution effectiveness. This wastes significant effort.
Active Work Time Exploded
Work in Progress -> Completed 23.0 hrs → 248.3 hrs +225.3 hrs
The time spent actively working on incidents increased by over 10x. This is the core bottleneck and suggests severe challenges during the resolution phase itself.
Wait Time in Pending Increased Sixfold
Pending -> Work in Progress 43.3 hrs → 259.8 hrs +216.5 hrs
Incidents are waiting much longer for required information or external actions, significantly delaying the overall process.
Transition Changes
⬆ Improved transitions
Open - Work in Progress 64.07 → 28.55 hrs -35.52
Open - Pending 46.96 → 0.36 hrs -46.60
⬇ Deteriorated transitions
Work in Progress - Completed 23.00 → 248.34 hrs +225.34
Pending - Work in Progress 43.26 → 259.75 hrs +216.49
Absent in comparison period
Start - ClosedCompleted - Work in ProgressStart - Open
Rework volume shift: The overall rework rate increased dramatically from 39.7% to 60.0%. This is reflected in the high proportion of rework variants in the comparison period, where 60% of all work items followed a path with at least one rework loop.
Workflow Path Changes
Variants — baseline
161
Rework share: 39.7%
Variants — comparison
11 ▲ -150
Rework share: 60.0%
Dominant path changed — the most common workflow route shifted between periods.
Baseline: Work in Progress -> Completed -> Closed (28.2% of items)
Comparison: Two paths tied for dominant: 'Pending -> Work in Progress -> Completed -> Closed' and 'Work in Progress -> Open -> Work in Progress -> Completed -> Closed' (20% of items each).
The process became far less diverse, with the number of unique paths dropping by 93%. However, the dominant path changed from a simple, non-rework flow to more complex paths involving rework loops. The consolidation of work into fewer, much slower, and higher-rework variants is a key feature of this comparison.
💡
What Likely Drove the Changes
Shift in Work Mix to Complex 'Problem' Incidents
✓ Confidence: High
The comparison period likely consists of a small number of unusually complex, long-running incidents, which are fundamentally different from the high-volume, transactional work seen in the baseline. This would explain the longer durations, higher rework, and the massive drop in volume.
Work item volume dropped 97.5% (1015 to 25). Field usage data shows a shift from a diverse mix of assignment groups to just two ('Mobile / Cell Phones', 'Computer/Accessories') and new, potentially complex subcategories like 'Re-Image Laptop'.
Resource or Knowledge Gap
✓ Confidence: Moderate
The team(s) handling the incidents in the comparison period may have been understaffed, lacked the specific expertise for these complex issues, or were dependent on a single subject matter expert, causing the massive increase in active 'Work in Progress' time.
The 10x increase in the 'Work in Progress -> Completed' transition duration is a direct measure of active work time, which is a strong indicator of a resolution bottleneck.
Statistical Anomaly Due to Small Sample Size
✓ Confidence: High
With only 25 work items, the comparison period may be a statistical outlier. One or two extremely problematic incidents could be skewing the averages for the entire period, meaning this is not a true reflection of a systemic process change.
The sample size is too small to draw definitive, long-term conclusions about the process health. The standard deviation for duration also increased, suggesting higher variability.
What Stayed the Same
Administrative Closure Delay ~168 hours
The delay between an incident being 'Completed' and formally 'Closed' remained consistent. This administrative step is not the source of the new performance issues.
Process Step Count ~4.8 transitions per item
The average number of steps an incident goes through has not changed, indicating the problem is not more handoffs, but rather the duration of time spent within each step.