Incident Response Roster Clarity (Roles, Not Heroes)

Every incident has roles. Commander, communicator, investigator, scribe. The role definitions that prevent the hero anti-pattern.

The four roles

Four named roles cover any incident. Commander makes the calls; communicator handles stakeholders; investigator digs into the cause; scribe records the timeline. Each role has a distinct charter; the IC owns coordination, not all four jobs.

• Commander. Named decider per incident. Coordinates response, sets direction, makes calls.
• Communicator. Stakeholder voice per incident. Customers, leadership, other teams.
• Investigator. The digger per incident. Finds the cause, proposes fixes.
• Scribe. The recorder per incident. Timeline, decisions, who did what.

The hero anti-pattern

The hero anti-pattern is one person trying to play all four roles. Burns out the engineer; misses things because no human can hold all four contexts; does not scale beyond small incidents. Healthy incident response needs at least three distinct humans even on small incidents.

• One person, all four roles. Hero pattern per incident. Burns out, misses things, cannot scale.
• Healthy incidents need three or more distinct people. Minimum-staffing rule per incident. Even small incidents.
• Fewer than three: too small or understaffed. Diagnostic per incident. Either the structure is overkill or the team is understaffed.
• Documented role-coverage policy. Published rule per team. Catches the “we just have one person handling it” default.

Rotate roles

Rotation builds the bench. Newer engineers scribe; seniors command; everyone has played every role within a year. Specialisation (only senior X can command) is the brittle-bench failure mode that bottlenecks response.

• Newer engineers scribe; seniors command. Role-by-experience assignment. Drives onboarding.
• Rotation builds skills. Year-long every-role-played goal per team. Everyone has played every role.
• Specialisation is the failure mode. Brittle-bench risk per team. Senior on-call as bottleneck slows response.
• Published role-coverage map. Visible “who has played what” chart per team. Supports rotation planning.