You have a problem that matters, but nobody in the room can confidently tell you how to solve it.
Customer complaints are taking four days to resolve. Customer Service says the delay comes from Operations. Operations points to approvals. Managers say frontline employees need to become more proactive. Employees say they are willing to act, but they are not sure what they are allowed to decide.
You can bring everyone into a workshop and discuss the problem. You can teach a problem-solving model or ask an expert for recommendations. Those approaches may help. But sometimes the organization does not yet know the answer. People need to enter the work, test what they believe, act on what they discover, and learn from what happens next.
That is where Action Learning becomes useful.
Action Learning brings a small group together around a real, important, unresolved problem. The group questions what it thinks it knows, takes meaningful action, examines what happens, and learns while working to move the problem.
The real problem matters. So does the learning.
A task force may solve a problem. Action Learning should do something more: move the problem while increasing the group’s ability to tackle the next one.
Let the Problem Become the Practice Field
Return to the four-day customer delay.
The easiest response would be to accept the first diagnosis. If managers believe employees lack initiative, perhaps the company should run an empowerment program. If Operations believes approvals are slow, perhaps the organization should streamline the approval process. If frontline employees want more authority, perhaps management should simply give it to them.
Any of those responses could eventually prove useful. The difficulty is that the team does not yet know which explanation deserves its confidence.
An Action Learning group stays with the real problem long enough to investigate it. Members ask questions, compare perspectives, examine assumptions, gather information from the work, and decide what they can try before the next conversation. The meeting matters, but the learning cannot remain inside the meeting. The group needs opportunities to act and bring something back from reality.
Suppose the team follows several customer cases from beginning to end. Members discover that many frontline employees already know what they would recommend. The delay often appears at a particular moment: the employee reaches a customer request that falls outside the normal procedure and does not know whether making the decision will later be held against them.
That discovery changes the conversation.
The problem may not be simply, “How do we make employees more proactive?”
A better question appears:
Which customer decisions should employees be able to make without waiting for another approval?
The work has begun teaching the group.
This is one reason Action Learning fits naturally with Build Learning Systems and Proof. Learning does not have to sit beside the work as a separate event. When the challenge is real and the answer is genuinely uncertain, the work itself can become the practice field.
Work the Problem, Not Just the Conversation
A group can meet around a real business problem and still fail to do Action Learning well.
People can ask intelligent questions for two hours, reflect deeply, agree that they learned a great deal, and return the following week with no new information from the work. The real problem gives the conversation relevance, but it is action between conversations that gives the group something new to learn from.
So our customer-resolution team has to make a move.
Perhaps it identifies one common category of customer request and agrees on a clearer decision boundary. For the next two weeks, employees handling that type of case may decide without another approval when three specific conditions are met. Managers remain available when the situation falls outside those conditions.
That is a bet.
The team does not need to pretend it has solved the entire four-day-delay problem. It has found one part of the work it can change and observe.
What happens?
Some routine escalations disappear. Several customers receive answers on the same day. Employees begin making decisions without waiting for their managers. But another pattern also appears: employees in one unit are still escalating cases that fall clearly inside the new boundary.
The group could interpret that as resistance. Instead, members investigate again and discover that those employees are measured partly on avoiding exceptions. The company has given them more authority while leaving an older measure that makes exercising that authority feel risky.
The problem has moved, and the group’s understanding has moved with it.
This is the discipline that keeps Action Learning from becoming a thoughtful discussion club. If the group cannot take meaningful action on the problem, it may have something important to discuss, but it does not yet have a strong Action Learning challenge.
Move the Work and Build Capability
Now imagine that customer-resolution time falls from four days to one.
That would be valuable.
But if we stop there, we have only measured what happened to the problem. Action Learning also asks what happened to the people working on it.
At the beginning, perhaps the group quickly accepted familiar explanations. Customer Service blamed Operations. Managers blamed initiative. Employees blamed approval rules. Over several cycles, members learned to slow down their first diagnosis, trace problems into real work, surface assumptions, ask what evidence would change their minds, and test smaller responses before recommending large solutions.
Those capabilities can travel to the next problem.
That is what distinguishes Action Learning from simply assembling intelligent people and giving them a project. The project team may produce a solution. An Action Learning group should become better at learning while it solves.
This can be especially valuable in developing leaders. Leaders regularly face problems for which there is no answer key. They need to listen to competing explanations, distinguish symptoms from causes, act without complete certainty, and adjust without treating every change of course as failure.
That is why Action Learning can support Build Leaders Who Move Work. Leadership development does not always need a simulation when the workplace already contains problems worth learning from.
But leadership development should not become the excuse for inventing an Action Learning project.
Start with something worth moving.
Then let responsibility for moving it become part of the development.
Follow the Problem Into Critical Moments
Large problems become more actionable when the group finds the moments where they actually happen.
“Customer service is too slow” is difficult to practise.
“The employee knows what she recommends but pauses because the request falls outside the usual procedure” is a moment people can examine.
That shift matters because execution happens in moments. A handoff occurs. A manager responds to a mistake. An employee decides whether to escalate. A salesperson discovers that a promised date cannot be met. Something happens, and the response either helps or hinders what the organization is trying to achieve.
Our customer-resolution group has found one such moment. Now it can test a practical response there.
In Strategic Learning, we sometimes call a small response worth testing in a recurring critical moment a Minimum Lovable Play. The purpose is not to design the perfect procedure before anyone uses it. The group creates something useful enough to try, watches what happens, and improves it from evidence.
That connects Action Learning naturally to Make Execution Daily. The group is no longer talking only about “empowerment” or “customer centricity.” It is changing what someone can do when a customer is waiting and a decision has to be made.
But the response itself is only part of the learning. The group also needs to notice what the surrounding system does to it.
If managers continue reversing reasonable frontline decisions, employees will learn to wait again. If an old measure punishes exceptions, new authority may remain unused. If information arrives too late, clearer decision rights will not fix the entire delay.
Real work reveals these conditions in ways a discussion sometimes cannot.
The action changes the system just enough for the system to answer back.
Follow Proof, Then Make the Next Move
Reflection is central to Action Learning, but reflection becomes more useful when it stays close to what actually happened.
A group might say, “We learned that trust is important,” or, “Communication needs to improve.” Those may be sincere conclusions. But before accepting them, ask what the work showed.
Did escalation decrease?
Were the decisions made closer to the customer?
Were those decisions sound?
Did resolution time improve?
Where did the new response still break down?
What surprised the group?
Those questions produce a simple learning movement:
Real problem → action → proof → learning → next move
Proof does not mean waiting for perfect research before making another decision. It means giving reality a voice in the conversation.
Our customer-resolution team might discover that the new decision boundary works well in two units but poorly in a third. Instead of declaring either success or failure, the group has something better: a new question. What is different in that unit?
Perhaps the next move is another experiment. Perhaps the group changes the play. Perhaps leaders need to remove an old measure. Perhaps the evidence shows that the original diagnosis was only partly correct.
The aim is not to defend the first solution.
It is to make the next move better.
This is also where Action Learning can extend a strategy workshop that moves work. Leaders may leave a strategy workshop with a clear choice—to win through faster, simpler customer resolution, for example—while still facing important questions about what must change in the organization for that choice to work.
The strategy workshop answers: What have we chosen?
Action Learning can then ask: What do we still need to learn to make that choice work in real life?
That is a productive relationship between strategy and learning. Strategy gives direction. Real work gives feedback.
Know When Action Learning Earns Its Place
Action Learning is not the right design for every business problem or every learning need.
If employees need to learn a known safety procedure, teach the procedure and let them practise it. If leadership has already decided exactly what must be implemented, do not pretend the group is discovering the solution. If participants have no access, influence, or sponsorship to change anything, repeatedly asking them to solve the problem can become frustrating theater.
Before creating an Action Learning project, ask four questions:
- Does this problem matter? Would moving it create meaningful value?
- Is the answer genuinely unresolved? Is there something important the group still needs to discover?
- Can this group take meaningful action? Can members test ideas, influence the work, or obtain the support required to act?
- Do we want capability to grow while the problem moves? Is learning how to handle problems like this part of the value?
When those conditions come together, Action Learning has something worth working on.
Let the Work Teach You
The four-day customer delay may begin with several competing explanations. The team may first believe that employees lack initiative, then discover an unclear decision boundary. A small change may reduce some escalations and expose an old performance measure. The next experiment may reveal another constraint.
That is not a detour from Action Learning.
That is Action Learning.
The group does not need to know the answer before it begins. It needs a problem worth moving, the ability to act, and enough discipline to learn from what the work gives back.
The strongest Action Learning projects leave two things behind: a problem that has moved and people who are more capable of moving the next one.
So do not create an Action Learning project merely because you want people to learn. Find something that matters enough to work on. Put capable people around it. Let them question what they think they know, take meaningful action, and follow the evidence into the work.
Work the problem. Follow the proof. Make the next move better.
