# Critical Incident Participants analyze past operational challenges using a structured four-part framework. In small groups, they examine causes, choices, and consequences to identify practical systemic improvements. **Time:** 60 minutes. Source recommends 45 to 90 minutes. UWT standardizes on 60 minutes for up to 24 participants. **People:** 4 to 24. Individual reflection, then parallel breakout groups of 3 to 5 people (subdivide any room count from 4 to 24 into groups of 3, 4, or 5; for instance, 4 or 5 form a single table, 7 divides into 4 and 3, 11 into 4, 4, and 3, and 24 into six groups of 4), followed by whole-room debrief. ## Choose this exercise **Purpose:** Extract actionable operational lessons and decision patterns from past difficult events without assigning individual blame. **Use it when:** Use during project retrospectives, post-crisis reviews, or team training workshops where people need to evaluate past operational mistakes safely. **Skip it when:** Skip when the incident is the subject of an open legal dispute, active disciplinary inquiry, or fresh interpersonal conflict. ## Materials and tools - One printed Critical Incident Worksheet per participant - One printed Sample Incident Prompts sheet per small group - One flip chart pad per small group - One large central whiteboard or flip chart for the facilitator - One pack of sticky notes per small group - Two markers per small group - One digital countdown timer - Access to a shared virtual whiteboard tool (e.g., Miro, Mural) for remote or hybrid sessions ## Before participants arrive 1. Arrange the room with separate tables seating 3 to 5 participants each. 2. Place one flip chart pad, sticky notes, markers, and one Sample Incident Prompts sheet on each table. 3. Distribute one printed Critical Incident Worksheet to each seat. 4. Position the central whiteboard or facilitator flip chart at the front of the room. ## Say this to open We will look back at specific challenging situations from our work to extract practical lessons. This is not about assigning fault or blame. You will document an incident, break it down into causes, choices, and consequences, and then compare notes in small groups to identify patterns. ## How to run it ### 1. Introduce purpose and ground rules (5 minutes) Read the opening script. Establish ground rules: keep names anonymous, focus on process and systemic causes rather than personal blame, and listen without interruption. Point out the worksheet and the sample prompts sheet on each table. Start the digital countdown timer for each phase to keep the room on track. ### 2. Draft individual incidents (10 minutes) Each participant works silently on their worksheet to draft what happened, contributing causes, decisions made, and direct consequences. Anyone who prefers not to analyze a personal work event may select one scenario from the Sample Incident Prompts sheet. Set the digital countdown timer to 10 minutes. ### 3. Analyze in small groups (20 minutes) Form groups of 3 to 5 participants. Set the countdown timer to 20 minutes. Each person gets up to 2 minutes to summarize their incident. The group spends the remaining time (10 to 14 minutes) identifying common themes across the stories, focusing directly on two core questions: What alternative actions could have been taken at key decision points (Worksheet section 5)? What systemic factors, policies, or constraints influenced the outcome (Worksheet section 6)? ### 4. Chart key lessons (10 minutes) Each small group agrees on two or three practical preventive measures or systemic improvements. They write each item on a separate sticky note and post them clearly onto their group flip chart pad. Set the timer to 10 minutes. ### 5. Consolidate whole-room insights (15 minutes) Call the room back together. Invite each table to share one key preventive practice aloud (maximum 60 seconds per table). Record and group these points on the central facilitator board. Close by asking up to two selected debrief questions to the full room. ## Debrief questions - What common patterns appeared across the different incidents shared today? - Which decisions were heavily shaped by systemic limits or missing information rather than individual choices? - What is one concrete check or process update our team can implement to prevent a similar issue next quarter? **Finished output:** Flip chart sheets displaying small-group preventive actions and a central board summarizing shared systemic lessons. ## Remote Run plenary in the main room and divide into breakout rooms of 3 to 5 participants. Share digital copies of the worksheet and prompt sheet. Each breakout records their preventive actions on a designated frame of a shared virtual whiteboard before returning to the main room for plenary. ## Hybrid In-person attendees form table groups of 3 to 5; remote attendees work in dedicated virtual breakout rooms of 3 to 5. Remote and in-person tables both post their final sticky notes to a single shared digital whiteboard that is projected in the physical room. ## Access and participation choices - Participants may analyze a provided neutral scenario instead of sharing an actual personal work incident. - Participants may choose to contribute silently through written notes or pass during the oral group debrief without explanation. ## If the session gets stuck **A participant starts naming specific colleagues and assigning personal blame.** Intervene immediately and redirect to process: 'Let us pause on individuals and examine the context. What workflow, timeline pressure, or information gap enabled that error?' **A group gets stuck debating the factual accuracy of a past event.** Remind the table: 'Treat the scenario as described by the speaker for this exercise. Our focus is analyzing decision alternatives and systemic factors, not litigating past facts.' ## Terms used here - Critical Incident: A specific past event where a significant challenge, error, or breakdown occurred that provides practical learning. ## Participant material: Critical Incident Worksheet 1. What Happened: Briefly describe the situation, setting, and operational context (keep all personal names anonymous). 2. Contributing Causes: What circumstances, technical constraints, communication gaps, or timeline pressures contributed to the incident? 3. Decisions Made: What critical choices were made, when, and under what conditions? 4. Consequences: What was the tangible impact on delivery, safety, budget, or team function? 5. Alternative Actions: What alternative action could have been taken at that critical decision point? 6. Systemic Prevention: What policy, tool, training, or check would prevent this type of breakdown in the future? ## Participant material: Sample Incident Prompts If you prefer not to use a personal or recent work event, select one of these scenarios to analyze: Scenario A: The Communication Blackout A product team releases a major software update without notifying customer service. Support staff receive hundreds of calls about changed features without documentation or training. Response times quadruple, and internal team frustration escalates. Scenario B: The Compressed Schedule An external partner requests delivery two weeks ahead of schedule. Leadership commits without consulting the delivery team. To meet the date, quality testing is reduced, resulting in a system outage on release day. Scenario C: Role Confusion in an Emergency A field facility loses power and network connection during a severe storm. Two team supervisors give conflicting instructions regarding evacuation and equipment preservation, leading to operational delays and compromised equipment. ## Sources and adaptation Observed in the Participatory Methods library (participatorymethods.com), which formats critical incident analysis into a participatory workshop exercise. Retained the four-part incident analysis framework (causes, choices, consequences, lessons) and small group reflection from Participatory Methods. UWT added exact 60-minute pacing, explicit group partition rules for counts from 4 to 24 using groups of 3 to 5, pre-written neutral scenarios to protect psychological safety, explicit timer integration across steps, and virtual whiteboard instructions for remote and hybrid delivery. [Participatory Methods](https://participatorymethods.com/activities/critical-incident/) [Participatory Methods](https://participatorymethods.com/activities/critical) [Participatory Methods](https://participatorymethods.com/activities/critical-incident/#) Current run sheet: https://unitedwetransform.com/exercises/critical-incident/