Roles and decision authority during disruption

When an order path stops, everyone may know a technical task yet nothing happens because no one owns the decision to switch to an alternative. Naming a “continuity team” is not enough. Map the decisions and actions for this service: detect the disruption, estimate impact, activate an alternative, carry out the work, approve communications and verify return. Assign one accountable authority to each critical decision and a delegation path when that person is absent. The specialist designs and checks this map with service owners; writing one's own name in a table does not confer operational authority.

A RACI matrix can clarify who performs an activity, who is accountable for its approval, who is consulted and who is informed. The letters are a management aid, not a universal mandate. The practical test is whether a critical decision has someone authorized to make it on an actual shift. Equally, recording two final approvers without a rule for resolving their disagreement can delay activation while each waits for the other. Record roles rather than employee names alone, then keep current deputies and contact methods in a controlled contact register. A role's authority may continue after its holder changes.

Separate “recommend,” “approve” and “execute.” An impact analyst can recommend switching to an alternate call center after a thirty-minute outage, but the designated incident lead or service owner decides under the approved activation criteria. An IT specialist can confirm that a system does not respond; this does not make that specialist the owner of a decision to stop taking calls. Communications staff may need approval for a customer message before technical repair finishes. These distinctions prevent an incomplete analysis from becoming an unauthorized operational command.

Test the matrix with an after-hours scenario. In a controlled exercise that sends no live messages, follow the path from the person receiving the alert to the approver and then the executor. If a deputy is absent or a contact path is obsolete, the matrix works only on paper. Record decision handoff time and the minimum situation brief the approver needs: affected service, known extent, start time, available alternative and its risks. If information is insufficient, the decision owner should request a bounded check and a next update time instead of leaving the incident without an owner.

Test delegation in three distinct situations because “the deputy takes over” can hide important boundaries. First, the manager is absent but impact facts are complete; the deputy can decide on activation. Second, the manager is present but the alternative requires spending above that role's authority; higher approval or a bounded interim path is required. Third, data safety conflicts with rapid intake; the manager seeks the qualified owner's input rather than unilaterally removing a control. State the type and financial or operational limit of each decision and the fallback when each role is absent. “Emergency authority” with no defined decisions may be useless under time pressure.

Connect the role matrix to the actual duty roster. A diagram can name “operations lead” while no one occupies that role between midnight and six. Sending an email to a shared inbox during business hours is no proof of night coverage. Test reachability when disruption could occur. If there is no coverage, the owner may need a changed roster or a different out-of-hours service promise. Preserve test evidence: alert time, role-holder response time and receipt confirmation. A telephone number on a card alone does not prove that an authorized person can be reached when needed.

At shift handover, transfer service state and pending decisions, not just staff names. The incoming lead needs to know what was done, what was rejected and why, and what condition would trigger another alternative. Ask them to restate the next decision in one sentence to confirm understanding. If authority moves during the incident, record the time and who told participating teams so opposite decisions are not issued. This makes the matrix a coordination tool rather than a static list of names.