Incident Lake

RESEARCH REPORT

Survey on Individual Dependency in Incident Response 2026

We surveyed 250 SRE leads, engineering managers, VPs of Engineering and tech leads involved in system incident response about how dependent their incident response is on specific individuals: the current state, causes, risks, countermeasures and interest in tools. Many teams think, "we depend on a few people, but it won't fall apart tomorrow." Across 11 questions, this report shows what is really happening behind that assumption.

Survey periodMarch 2026

Valid responsesn=250

FormatPDF, 14 pages (Japanese)

Download the full report

KEY FINDINGS

Individual dependency in incident response, by the numbers

72.0%

say incident response depends on one or two specific people

88.9%

say those key people may leave, change jobs or transfer within 1–2 years

32.4%

tried to reduce this dependency, but saw no improvement

69.6%

are open to adopting a dedicated tool to reduce this dependency

"Tried but saw no improvement" was the most common answer to that question.

INSIGHTS

Five takeaways from the survey

01

Dependency spans every phase of response

The tasks most dependent on individuals are root-cause investigation and log analysis (56.1%) and first-line alert handling and triage (51.7%). Recovery leadership and escalation also reach about 40%.

02

The causes are linked, not separate

"No time to train people" (43.6%), "knowledge isn't shared" (40.0%) and "one person's skills stand out" (37.6%) are nearly tied, and they reinforce each other in a vicious cycle.

03

Documentation alone doesn't fix it

The most common measures were wikis, runbooks and postmortems. Yet "tried but saw no improvement" (32.4%) is about twice "mostly resolved" (16.8%).

04

The biggest barrier is leadership attention

The top reason for not tackling dependency is that it isn't an organizational priority (low leadership interest), at 32%. Front-line awareness isn't reaching decision-makers.

05

The answer: systems people actually use

The most important factors were "a way to share knowledge" (28.0%) and "AI and automation tools" (25.2%). Together, 53.2% put technology-based solutions first.

CONTENTS

What's in the report

Q1Is your incident response dependent on specific individuals?

Q2Which areas of incident response depend most on individuals?

Q3How likely are key people to leave or transfer?

Q4What causes this dependency?

Q5What is the single biggest cause?

Q6What efforts have been made to reduce it?

Q7Which measures were tried?

Q8Why can't the dependency be reduced?

Q9What are the risks if it continues?

Q10What matters most in reducing it?

Q11Is there a need for a dedicated tool?

Survey overview: Respondents: SRE leads, engineering managers, VPs of Engineering and tech leads involved in system incident response / Valid responses: n=250 / Questions: 11 / Survey period: March 2026 / Method: Freeasy online survey / Conducted by: SIGQ, Inc. You may quote or republish this survey with the credit "SIGQ, Inc. Survey on Individual Dependency in Incident Response 2026."

DOWNLOAD

Download the full report

The full report (PDF, 14 pages, in Japanese) includes charts and analysis for all 11 questions, from which tasks depend most on individuals and why, to which measures worked and the risks of doing nothing. It's ready to use in internal discussions.

Thank you for your request

You can download the report from the link below.

SIGQ_Survey on Individual Dependency in Incident Response 2026 (Japanese PDF)

For questions about the report or advice tailored to your organization, feel free to contact us at info@sigq.co.jp.

Submission failed. Please check your entries and try again later.