The people closest to the work often know things the organization does not.
They know:
- which procedures are difficult to use,
- which equipment behaves differently in certain conditions,
- where jobs routinely slow down,
- which controls actually help,
- where employees have to improvise,
- which problems keep returning, and
- what experienced workers do to keep difficult jobs successful.
Much of that knowledge never appears in a safety report.
It may not appear in an audit.
And if the organization waits for an incident before asking about it, an enormous amount of useful information can remain hidden.
They can be used after an event.
But they do not require an incident.
A Learning Team can also be used proactively to understand normal work before something goes wrong.
What Is a Learning Team?
A Learning Team is a facilitated conversation with people who understand the work.
Its purpose is to explore how work actually happens, including:
- what normally goes well,
- what makes the work difficult,
- how conditions change,
- where people adapt,
- which controls are effective,
- where uncertainty exists, and
- what could improve the system.
Learning Teams are strongly associated with Human and Organizational Performance—HOP—and operational learning.
The approach has been developed and popularized through the work of Dr. Todd Conklin and subsequent practitioners.
The important part is not simply gathering workers into a conference room.
The important part is creating a structured environment where people can explain the reality of work.
A Learning Team Is Not Just Another Safety Meeting
A normal safety meeting may involve:
- presenting information,
- reviewing incidents,
- discussing metrics,
- communicating new requirements, or
- delivering training.
Those activities can be useful.
But they are usually designed to transfer information to employees.
A Learning Team primarily attempts to obtain information from and with the people who know the work.
The facilitator is not there simply to teach.
The facilitator is there to learn.
That changes the conversation.
Learning Teams Are Not Simply Incident Investigations
This distinction is important.
An incident investigation and a Learning Team can work together.
They are not necessarily the same process.
A formal investigation may need to:
- preserve evidence,
- establish what happened,
- develop a timeline,
- collect records,
- interview witnesses,
- examine equipment,
- evaluate controls,
- test competing explanations, and
- establish a supported account.
A Learning Team can then explore the work more deeply:
- How is this task normally performed?
- What makes it difficult?
- Where does variation occur?
- What adaptations are common?
- What do experienced workers know?
- How do controls function during real work?
- What conditions made the event situation different?
The investigation establishes what the evidence supports.
The Learning Team can help the organization understand how the broader work system operates.
Learning Teams Can Also Begin Without an Incident
You do not have to wait for someone to get hurt.
This is one of the most useful aspects of Learning Teams.
Suppose employees tell you:
“Loading this type of equipment is always difficult.”
That may be enough reason to learn.
Or:
“That procedure doesn't really match the equipment anymore.”
Learn.
Or:
“This job is completely different when we are short staffed.”
Learn.
Or:
“Everybody has their own way of doing this.”
Learn.
Or:
“That control works fine in the shop, but not in the field.”
Learn.
Operational learning does not need an injury as permission to begin.
Why Learning Teams Fit HOP
Human and Organizational Performance asks organizations to understand how conditions influence behavior.
Learning Teams provide a practical way to do that.
Consider the five HOP principles.
Error is normal
Learning Teams can explore where mistakes are likely and how workers detect or recover from them.
Blame fixes nothing
The conversation focuses on understanding work rather than finding someone to accuse.
Context drives behavior
Workers describe the actual conditions surrounding their decisions.
Learning is vital
The process exists specifically to improve organizational understanding.
How leaders respond matters
Employees watch what leaders do with the information they provide.
The philosophy and the method fit naturally together.
Work-as-Imagined and Work-as-Done
One of the most useful concepts in operational learning is the difference between:
work-as-imagined
and:
work-as-done.
Work-as-imagined is how the organization expects the job to happen.
It appears in:
- procedures,
- training,
- policies,
- job plans,
- risk assessments, and
- management expectations.
Work-as-done is what actually happens when people encounter:
- real equipment,
- changing conditions,
- customers,
- weather,
- deadlines,
- missing tools,
- interruptions,
- staffing problems,
- physical constraints, and
- unexpected situations.
The difference between the two is not automatically evidence of misconduct.
Sometimes the procedure is incomplete.
Sometimes conditions changed.
Sometimes employees discovered a more effective method.
Sometimes the adaptation creates risk.
The organization needs to understand the difference before deciding what it means.
Learning Teams help expose that gap.
The Center Line
One useful way to think about normal work is as a Center Line.
The Center Line represents the way the task generally happens when people successfully manage the normal conditions, variability and demands of the work.
Real work rarely follows a perfectly identical path every time.
People may make small adjustments because of:
- equipment,
- environment,
- staffing,
- sequence,
- workload,
- customer conditions, or
- other operational realities.
Those variations may remain close to the Center Line.
At other times, conditions can pull the work farther away.
A Learning Team can help explore:
- what the Center Line looks like,
- what normal variation looks like,
- what causes movement away from it,
- which controls keep the work within acceptable boundaries, and
- where the organization may be drifting into greater exposure.
The goal is not to eliminate every variation.
The goal is to understand variation well enough to manage what matters.
Start With How the Work Normally Happens
A common mistake is starting a Learning Team with:
“Tell us what went wrong.”
That immediately frames the conversation around failure.
Instead, begin with normal work.
Ask:
“Walk me through how this job normally happens.”
Then explore:
- What happens first?
- What happens next?
- Who is involved?
- What equipment is used?
- Where do conditions change?
- What normally makes the job successful?
- Where does it become difficult?
- What do experienced workers pay attention to?
Build the picture before focusing on the problem.
Ask What Makes the Work Difficult
This may be one of the most valuable questions in safety:
“What makes your job difficult?”
The answers may reveal:
- poorly positioned equipment,
- conflicting procedures,
- inadequate staffing,
- unreliable tools,
- scheduling problems,
- communication gaps,
- visibility limitations,
- weak interfaces,
- maintenance issues, or
- controls that are difficult to use.
None of those issues requires an incident to exist.
Workers may have been managing them successfully for years.
The organization simply may not know.
Ask What Workers Have to Adapt
Adaptation is normal in complex work.
Procedures cannot anticipate every condition.
Employees may:
- change sequence,
- reposition equipment,
- wait,
- ask for help,
- substitute tools,
- communicate informally,
- create extra checks, or
- adjust how the task is performed.
Some adaptations increase safety.
Some introduce risk.
Some do both depending on the circumstances.
Do not automatically label every adaptation a violation.
Understand it first.
Learn From Successful Work
Imagine a difficult operation is completed safely 1,000 times and produces one incident.
Traditional investigation focuses heavily on the one failure.
It should.
But the 1,000 successful performances contain information too.
Ask:
“What normally keeps this from happening?”
Workers may describe:
- experienced positioning,
- informal signals,
- extra spotters,
- careful sequencing,
- slowing down,
- checking clearances,
- equipment feedback, or
- stopping under particular conditions.
Those practices may represent hidden capacity in the system.
Or they may reveal that success depends too heavily on human compensation.
Either finding is valuable.
Look for Controls
Learning Teams should not stop with interesting stories.
Connect learning to controls.
Ask:
- What prevents this hazard from producing harm?
- What control matters most?
- Is it always available?
- Does it function as intended?
- How do workers know it is working?
- Can it be bypassed?
- What happens when it fails?
- Does another control provide backup?
- Is success dependent on someone remembering the right thing at exactly the right time?
This helps move from conversation toward risk reduction.
Workers Often Know Where Controls Are Weak
A procedure may say:
“Use a spotter.”
The worker may explain:
“We can't see the spotter from the operator position at this point in the maneuver.”
A policy may say:
“Maintain separation.”
The worker may explain:
“The layout forces pedestrians through this area.”
A checklist may say:
“Verify the guard is in place.”
The worker may explain:
“You cannot see the guard after the machine is assembled.”
That is operational knowledge.
The organization needs it.
The Facilitator's Job
A Learning Team facilitator should not dominate the discussion.
The facilitator helps the group:
- describe the work,
- slow down the story,
- clarify differences,
- explore context,
- identify assumptions,
- distinguish facts from interpretations,
- examine controls,
- surface different perspectives, and
- keep the discussion focused on learning.
The facilitator does not need to be the technical expert.
In many cases, not being the expert can help.
It encourages questions.
Ask Curious Questions
Useful Learning Team questions include:
- Walk me through the job.
- What normally happens?
- What changes?
- What makes this difficult?
- Where do you have to adapt?
- What surprises people?
- What do experienced employees know that new employees do not?
- What usually keeps this job safe?
- What controls do you rely on?
- Which controls are difficult to use?
- What worries you?
- Where could this fail?
- What would make the work easier to perform successfully?
- Where else does this condition exist?
The goal is not to work through a checklist mechanically.
The questions should help the group tell the story of the work.
Avoid Turning the Learning Team Into an Interrogation
The process will fail if employees believe they have been invited to help management build a disciplinary case against them.
Avoid questions that sound like accusations.
Instead of:
“Why weren't you following the procedure?”
ask:
“Walk me through how this task is normally performed.”
Instead of:
“Who decided to do it this way?”
ask:
“How did this way of working develop?”
Instead of:
“Why didn't someone stop the job?”
ask:
“What did the situation look like to the people involved?”
Better questions produce better information.
Different Perspectives Are Useful
A Learning Team does not require everyone to agree.
In fact, disagreement can be valuable.
An operator may see the job differently from:
- maintenance,
- supervision,
- engineering,
- safety,
- dispatch,
- planning, or
- management.
Those differences may reveal how the system actually functions.
One person rarely possesses the entire picture.
The objective is not to vote on whose version is correct.
It is to understand the different perspectives and determine what they reveal.
Psychological Safety Matters
People must be able to describe the work with reasonable confidence that honest participation will not automatically be used against them.
That does not require promising absolute immunity.
It does require leaders to think carefully about the environment they create.
If employees believe:
“Anything I say will become evidence that I violated a rule,”
they will describe work-as-imagined.
If they believe:
“The organization genuinely wants to understand how the job works,”
you are more likely to hear about work-as-done.
That difference determines the quality of the learning.
Leaders Should Listen Before Solving
Leaders often want to fix things.
That is normally a strength.
During a Learning Team, it can become a problem.
An employee says:
“The equipment is difficult to position.”
A manager immediately responds:
“We can retrain everyone next week.”
Learning stops.
The group has jumped from:
problem identification
to:
solution
without understanding the problem.
Stay in learning mode longer.
Ask:
“Tell me more.”
Separate Learning From Problem Solving
A useful Learning Team structure separates two activities.
Learning mode
Understand the work.
Explore:
- sequence,
- conditions,
- variation,
- adaptations,
- controls,
- difficulties, and
- perspectives.
Do not rush to corrective actions.
Problem-solving mode
After the group has developed a better understanding, identify:
- improvement opportunities,
- potential control changes,
- experiments,
- owners,
- follow-up actions, and
- measures of effectiveness.
Separating the two reduces the temptation to solve the first problem someone mentions.
Do Not Automatically Recommend More Training
Training is one of the most common corrective actions in safety.
Sometimes it is exactly what is needed.
Sometimes it is not.
If employees already know what to do, retraining them may not change:
- equipment,
- staffing,
- layout,
- conflicting priorities,
- unavailable tools,
- unreliable controls, or
- procedure design.
Before recommending training, ask:
“Is lack of knowledge actually the problem?”
If not, solve the condition that is.
Small Improvements Can Matter
A Learning Team does not have to produce a million-dollar engineering project.
Useful improvements might include:
- relocating equipment,
- changing sequence,
- improving a visual indicator,
- revising a checklist,
- removing an unnecessary step,
- improving communication,
- clarifying a decision point,
- changing staging,
- adding a verification,
- improving access, or
- testing a better tool.
The measure is not how impressive the corrective action looks.
The measure is whether it improves the work.
Test Improvements
Do not assume a corrective action works because it sounded good in a meeting.
Try it.
Ask the people performing the work:
- Did this help?
- Did it create another problem?
- Is it easier?
- Is the control more reliable?
- Are people actually using it?
- Did the work move closer to the intended condition?
- What did we learn?
Improvement should create another learning loop.
Follow Up
A Learning Team without follow-up can damage trust.
Workers spend time explaining problems.
Management records them.
Then nothing happens.
Employees learn:
“Talking doesn't change anything.”
Not every suggestion can be implemented.
That is fine.
But close the loop.
Tell participants:
- what was changed,
- what is being tested,
- what cannot be changed,
- why,
- what remains under review, and
- what the organization learned.
Leader response matters after the meeting too.
Where Should You Use a Learning Team?
Good candidates include work that is:
- difficult,
- variable,
- unfamiliar,
- changing,
- dependent on coordination,
- dependent on human adaptation,
- associated with recurring problems,
- controlled differently across locations, or
- capable of producing serious consequences.
You can also use Learning Teams following:
- incidents,
- near misses,
- successful recoveries,
- operational surprises, or
- significant changes.
You do not need to use one for everything.
Choose opportunities where deeper understanding has value.
Learning Teams and Serious Injury and Fatality Prevention
Learning Teams can be particularly useful around high-consequence hazards.
Suppose the organization has identified a critical control for:
- hazardous energy,
- working at height,
- vehicle movement,
- lifting operations, or
- another potentially fatal exposure.
Do not ask only:
“Do we have a procedure?”
Ask workers:
- How does this control work in the field?
- When is it difficult to use?
- What conditions reduce its effectiveness?
- How do you know it is functioning?
- What happens when it is unavailable?
- What workarounds occur?
- Where else could it fail?
That conversation can reveal the difference between a control that exists on paper and one that provides reliable protection.
What a Learning Team Should Produce
The output does not need to be a massive report.
It should capture enough information to preserve the learning.
Useful outputs can include:
- a description of normal work,
- important variations,
- difficult conditions,
- worker adaptations,
- control strengths and weaknesses,
- improvement opportunities,
- decisions,
- action owners,
- follow-up dates, and
- unresolved questions.
Documentation should support learning.
It should not become the purpose of the process.
What Learning Teams Should Not Become
Avoid turning Learning Teams into:
A disguised investigation
Workers should not discover halfway through that the real purpose was assigning fault.
A complaint session
Problems matter, but the discussion needs structure and connection to work.
A management lecture
Leaders should listen more than they speak.
A corrective-action race
Understand before solving.
Another checklist
Facilitation requires curiosity, not simply reading questions.
A one-time initiative
Operational learning works best when it influences how the organization routinely thinks about work.
How Do Learning Teams Improve Workplace Safety?
Learning Teams do not improve safety merely because a meeting occurred.
Their value comes from what they allow the organization to discover.
They can reveal:
- weak controls,
- normal workarounds,
- hidden dependencies,
- recurring difficulties,
- differences between procedures and reality,
- successful adaptations,
- changing conditions,
- operational knowledge, and
- opportunities to improve the system.
That information can improve decisions.
Better decisions can improve controls.
Better controls can make successful work more reliable.
That is the pathway.
The Bigger Benefit: Operational Intelligence
Safety is not the only potential benefit.
The same conversation may reveal problems affecting:
- quality,
- productivity,
- equipment reliability,
- scheduling,
- customer service,
- maintenance, and
- employee frustration.
That is because workers do not experience separate “safety systems” and “production systems.”
They experience work.
Learning about work can improve more than one outcome.
Start Small
You do not need to launch a company-wide Learning Teams initiative tomorrow.
Choose one meaningful piece of work.
Bring together several people who understand it.
Find a capable facilitator.
Ask them to explain:
How does this work actually happen?
Then become curious.
Where is it difficult?
Where does it vary?
What do people adapt?
What controls matter?
What makes it successful?
What could make it better?
Listen before solving.
Then act on what you learn.
That is a Learning Team.
And that is how an organization can begin moving from managing safety primarily through rules and outcomes toward learning how successful work is actually created.
For a closer look, read The Five Principles of HOP Explained.
Go Deeper: Human Organizational Performance (HOP) Tools for Individuals
Human Organizational Performance (HOP) Tools for Individuals introduces practical ways individuals can apply HOP principles, improve conversations about work, and strengthen operational learning.
Available in paperback and Kindle on Amazon.
Coming Next: The Learning Teams Field Guide
A separate Learning Teams Field Guide and companion toolkit are being developed as practical resources for organizations that want to move beyond the concept and establish a repeatable Learning Team process.
The Field Guide goes deeper into facilitation, the Center Line, Learning and Problem-Solving modes, governance, follow-up, and practical application.