A learning team after a near miss: how the work really happens
After conduit falls at a transit project, the required response and incident process are underway. The superintendent also wants to understand the delivery work from the people who perform it. A reminder to be careful would not explain the reported conflicts between deliveries, access and the current landing arrangements.
A learning team is a facilitated conversation about work and its conditions. An employer’s published guide describes gathering different perspectives before selecting improvements. This approach complements the required response, reporting and investigation; it does not replace them or establish a cause by agreement. Allow suitable time and follow-up rather than promising that two short meetings will resolve every near miss.
Turn the concern into a workable site routine
- Agree the scope and the separate processes. Establish the specific work to understand, the facilitator and how the conversation connects to the responsible incident review. Confirm that urgent protection and reporting are already being handled appropriately. Explain what can be recorded and shared, including privacy or investigation limits. Do not offer immunity, confidentiality or freedom from employment consequences that you are not authorized to promise.
- Bring the people with relevant experience. Include workers who perform and support the task, with other perspectives needed to understand the interfaces. Use a facilitator who can invite accounts without deciding the answer in advance, and arrange a record of the discussion. Technical expertise may help clarify a question; it should not become a lecture that prevents workers describing their actual experience.
- Map normal work before drawing conclusions. Ask people to describe the preparation, sequence, handoffs and difficulties, then what was different around the event. Record different accounts and questions that require checking. Avoid turning the first explanation into the cause or asking only who departed from a rule. Do not visit an unsafe location or recreate the event to make the conversation more vivid.
- Separate suggestions from accepted changes. After the conditions are understood, invite improvements and identify the assessment, resources and approvals each would need. Use another session if useful; the structure should fit the work. Assign owners and dates for decisions, with the affected work status clear. A popular suggestion cannot authorize a landing alteration, remove required protection or replace a competent design review.
- Return the findings and check the response. Give participants a usable account of what was learned, what was verified, which suggestions were accepted and which remain unresolved. Connect actions to the responsible incident and corrective-action records without inventing a second contradictory version. Review the changed work with appropriate verification and worker feedback. Meeting attendance is not evidence that a control was implemented or that recurrence is impossible.
Common mistakes
- Replacing required investigation with a team discussion.
- Treating agreement as proof of the event’s cause.
- Authorizing a technical alteration through a popular vote.
Checklist
Keep learning and actions traceable
- Scope, response and incident process connected.
- Relevant perspectives and a facilitator included.
- Normal work and differing accounts recorded.
- Suggestions assessed and decisions owned.
- Findings returned and implementation verified.
Check your understanding
The team agrees that changing the landing would help. Can it approve that alteration?
.jpg){kind=link}