Applying Emergency Room Principles to IT Operations: Kanban, Scrum, and Prioritization

When I took over as the core system IT lead, I noticed many similarities between an emergency room and IT operations: both face a flood of requests, limited resources, and the need to triage urgency.

Unlike an ER where doctors can assess patients directly, IT teams must bridge a knowledge gap across ten countries, often without being on site, making impact assessment difficult.

To address this, we adopted Kanban's WIP‑limit principle and established a one‑to‑one liaison model: each IT engineer is paired with a specific country or region, and each business side appoints a counterpart to prioritize their own queue.

We then imposed a "hidden rule" limiting work in progress per region: for the four high‑volume regions we handle the top two requests, for others only the top request. This ensures we always work on the most critical issue for each region.

Transparency is achieved by publishing the live board (via Confluence and JIRA) so business stakeholders can see which incidents are being addressed.

For major incidents that require immediate attention, the WIP limit can be overridden.

To prevent important but non‑urgent tasks from being neglected, we borrowed Scrum's time‑boxing concept: daily stand‑ups focus on immediate work, while a separate cadence discusses pipeline implementation and other improvements.

Weekly review meetings cover fault analysis, follow‑up on resolved incidents, and tracking of legacy issues, ensuring continuous improvement.

Finally, we apply Scrum principles to personal energy management, breaking the day into short, focused Sprints with brief rests, emphasizing that managing energy—not time—is key to sustained productivity.