After a service failure or operational mistake, people remember different moments. One person recalls an alert, another a rushed handover, and another the customer complaint that finally made the impact clear. A useful review starts by putting those observations in order.
Google’s incident-management guidance describes learning through open, blameless postmortems after an incident is resolved. Its technical context is specific, but the discipline of examining detection, coordination and communication offers a useful model for other teams.
Mark evidence and uncertainty separately
Create a timeline with time, event, source and unresolved question. Distinguish a recorded message from somebody’s recollection. If the exact time is unknown, say so. Do not make the sequence look more precise than the evidence supports.
Ask what information was available to the person at the time. A decision that looks obviously wrong after the outcome may have been made under different visibility or competing instructions. Understanding that context is necessary for changing the system that produced the decision.
Move from explanation to a small number of actions
Once the team agrees the sequence as far as possible, examine where a different control or communication route could have helped. Avoid ending with “be more careful”. An action should describe a change someone can implement and another person can check.
A fictional example is replacing an ambiguous handover message with a required acknowledgement before responsibility changes. Assign an owner and review date, then test whether the acknowledgement works during an ordinary busy period. Do not assume that publishing a new document means behaviour has changed.
Keep the review proportionate and protect sensitive information. Accountability and a learning-focused discussion can coexist; blaming a person prematurely can prevent the team from discovering the conditions that need fixing. The timeline gives everyone a shared object to examine, rather than asking the meeting to choose between competing memories.