Quick Healthcheck

Chaotic-1

Generated Jun 28, 2026, 11:51 AM

The process is undermined by a high rework rate (60%), extreme fragmentation (222 variants), and a majority of incidents (67%) breaching SLAs.

222 variants detectedCycle time and rework not available

What's not working

Majority of SLAs are breached

67% of incidents with SLAs are breaching their response or resolution targets.

The process is unpredictable and fails to meet its service commitments.

Rework is extremely high

Over 60% of all incidents involve rework steps, adding delays and effort.

This signals unclear requirements or frequent handoff problems between states.

No standard process exists

The process has 222 distinct paths, with the most common one used for only 14% of incidents.

This fragmentation leads to inconsistent handling and unpredictable outcomes.

Incident workload is diluted

Work is spread across 45 assignment groups, with no single team handling more than 2.7%.

This may indicate a lack of specialized teams or unclear routing rules.

What is working

Active work is efficient

Flow efficiency is high at 80.2%, with most time spent in active work states.

Data capture is consistent

Core classification fields like priority and contact type are 100% populated.

Initial triage is structured

All incidents consistently move from 'New' to 'Active' in an average of 3.27 hours.

Quick wins

Clarify user info requests

Standardize information requests for the 'Work in Progress' to 'Pending User' transition.

Expected benefit: Reduce the most common rework loop affecting 43% of incidents.

Strengthen assignment criteria

Review why 36% of incidents bounce from 'Assigned' back to 'Active'.

Expected benefit: Improve first-time assignment accuracy and reduce handoff delays.

Promote the 'happy path'

Document and promote the most common non-rework variant as the standard process.

Expected benefit: Reduce process fragmentation and improve team consistency.