← Application Production Support
03 / 6 · 35 MIN

Incidents, communication, and shift change

Coordinate recovery and preserve continuity between teams.

Concept and mechanism

During an incident, coordination and diagnosis are complementary work. Define who maintains overall state, who executes actions, and who communicates with stakeholders. Distribute investigation across components while coordinating changes that can interfere with each other. Maintain a timeline of observations, hypotheses, decisions, and results. For the business, summarize confirmed impact, alternatives, current actions, uncertainties, and next update time. An unsupported recovery estimate does not improve by being precise. When the cause is not yet established, label estimates accordingly and explain what evidence would improve them. Preserving logs and context supports later investigation without preventing authorized mitigation.

Guided application

In a fictional case, Lisbon transfers an incident to the next team with a temporary mitigation active. The record should show that change, rejected hypotheses, risks, and the next decision. Obtain explicit acceptance from the person assuming coordination and announce the transfer. An assigned ticket does not establish that the new owner understood state. After recovery, check the business journey, backlog, and residual limitations before updating status. Keep investigation and preventive actions distinct from already demonstrated recovery. A useful postmortem examines conditions that enabled failure and defines verifiable actions with owners. It does not replace analysis with individual blame or close improvement merely because alerts stopped.

IN PRACTICE

The update “service recovered, cause under investigation, next update at 16:00” is more accurate than declaring a cause resolved without evidence.

Common pitfalls

Uncoordinated simultaneous changes; ETA as a promise; link-only handover; recovery as cause removal.

Related topics: The service, impact, and ownership · Measure what the user receives · Batch, files, and reconciliation

Take this idea with you

Maintain clear ownership, shared evidence, and explicit decisions.

Create account

Reference: Incident Response · DR APS professional curriculum 2026-09; vendor-neutral operational guidance reviewed 2026-09-30