hardScenarioBehaviouralSeniorStaffLead
The line has been stopped for twenty minutes and everyone in the room believes it is your system. How do you run the next hour?
6 min readUpdated 2026-08-15
Answer
Short answer
Your first deliverable is a fast, evidenced answer to whether you are in the path, measured at the station rather than on your own dashboards. Restoring production outranks diagnosis, so take a cheap evidence snapshot and then get yourself out of the path.
In a strong incident response answer, the the line is stopped and they detail should connect the decision to a visible consequence.
Was this answer helpful?
Likely follow-ups
- Your dashboards are all green and the station is timing out. What is the most likely explanation?
- What would you capture in the sixty seconds before someone restarts your service?
- Who decides whether the line restarts, and what is your role in that decision?
- The trigger turns out to have been a product changeover. How does that change the postmortem?
Related questions
- You are on call, a deploy went out twenty minutes ago and production is degraded. Talk me through what you do.hardAlso on incident-response and postmortem7 min
- You get paged, the service is down, and nobody else is online yet. How do you run the incident?mediumAlso on incident-response and postmortem5 min
- Tell me about a time you broke something in production. What happened?mediumAlso on incident-response and postmortem5 min
- You need to deploy a change to a system a running production line depends on. How is that different from a normal release?hardAlso on change-control and availability6 min