Common Thread
Fourteen things break at once? Find the one shared thread, and clear the innocent.
The job
Detect when complaints across many services or partners are really one failure in a shared dependency, route one incident upstream instead of fourteen downstream, tell the innocent they are not at fault, price the shared failure, and verify recovery.
The moment
Fourteen service tiles flicker amber together, then collapse on screen into one card: Probable cause: national SMS gateway, 91% (n=2,310), with a meter reading 4,200 citizen-hours lost so far. One tap opens the platform incident and sends 14 service owners stand down, it's not you; the next morning every tile is grey, stamped Looks over, and the month's ledger shows the gateway at the top of the SLA-credit claim.
What it does
- Open one platform incident
- Stand down service owners / tell partners 'it's not you'
- Send the vendor one evidence pack
- Draft and deliver the holding line for the AI agents
- Correct partner attribution for the window
What you see
A radar sweep with services on the outer ring and shared components at the centre, arcs that light as symptoms converge, and a thread card that pulls the strands into one node; grey by default
What it moves
Hours from first co-spike to a single upstream incident, number of services or partners wrongly blamed per incident, and citizen or customer hours lost per shared component per month
Built for
- Product & digital
- QA, training & knowledge
- Partners & ecosystem
