Product & Engineering
Production breaks. What happens in the next hour matters more than what happens after.
This is the domain where communicating honestly while things are still broken, and reviewing without blame afterward, matter as much as the fix itself.
Other typical workflows in this domain: bug and defect triage, release management, and roadmap development & tracking.
Sample workflow: Technical incident & outage response
Automation = deterministic, rule-based. AI = judgement at the step level — drafting, scoring, matching. Human = decision, relationship, or anything that sets a precedent.
01Detection
AutomationIncident detected by monitoring, ideally before customers report it.
02Declaration
HumanIncident declared at a severity level that drives the response.
03Roles
HumanCommander coordinates; others fix — the commander doesn't debug.
04First update
AIFirst external update published fast, honest, and jargon-free.
05Ticket linking
AIInbound tickets linked to the incident, answered with current status.
06Diagnosis
AIDiagnosis run against recent changes; mitigation prioritised over root cause.
07Restoration
HumanService restored by the fastest safe route.
08Verification
HumanRecovery verified against real user experience, not just dashboards.
09Resolution comms
HumanResolution communicated; affected customers contacted directly.
10Postmortem
HumanBlameless postmortem held — timeline, causes, actions, no scapegoats.
11Action tracking
AutomationPostmortem actions tracked to completion like any other committed work.
12Metrics review
AIFrequency, MTTR, and recurrence reviewed at the operating cadence.