Learning teams (HOP)
Convene a small team to learn how work actually happens (session 1), design improvements (session 2), and turn insights into preventive CAPAs — conditions, not culprits.
A learning team is a small group that studies how work actually happens — conditions, not culprits. It's the Human & Organizational Performance (HOP) practice: session 1 learns, session 2 improves, and the record deliberately has no blame fields.
Convene a team
- Go to Learning teams and use the Convene a learning team form below the list.
- Choose the Site and give the Topic — the operation, not a person (e.g. "Loading haul trucks at the north pit"). Optionally name a Facilitator.
- The team appears in the list showing its sessions held (0/2 → 2/2), insight count, action count, and status. Click Open to work it.
A potential-SIF event is the classic trigger (see incidents), but any operation is fair game — you don't need something to have gone wrong.
Run the two sessions
- Open the team and use Add participant to record who's in the room.
- Session 1 — learning: what does this work require? What makes it hard? Where do people have to adapt? Type the notes and click Record session 1.
- Let it soak, then reconvene. Session 2 — improvement: what would make the work easier and safer? Which ideas become actions? Click Record session 2.
The two-session structure is encouraged, not enforced — a team can close after one session.
Capture insights and raise actions
- Under Insights, add what the team learned — phrased as a condition, not a culprit. Each insight is dated.
- Turn the best ideas into tracked work: enter an action title and assignee, then click Raise preventive CAPA. This creates a preventive CAPA linked back to the team, and it shows under Improvement actions with a link to the CAPA record.
- When the team is done, click Close learning team. Closed teams keep their notes, insights, and CAPA links, but stop accepting edits.
What happens automatically
- Every step — sessions recorded, insights added, actions raised, closure — is written to the audit trail.
- CAPAs raised from a learning team are tracked in the normal CAPA workflow (due dates, overdue flags, dashboard tiles) like any corrective action.
Related
- Root cause analysis — The formal investigation method for deeper causal analysis
- CAPA (corrective & preventive actions) — Where the preventive actions you design get tracked
- Incidents — The events that often trigger a learning team
- Observations (BBS) — Field signals and SIF potential feeding learning topics
- Stop-work authority — Good catches that surface how work really happens
Want to see this working?
Open a sandbox with your industry's data already in it — no signup, nothing to install.