Your organization may be spending three days teaching what a supervisor needs to do in eleven minutes.
The program may be professionally designed. It may include respected models, participant workbooks, guided practice, observation, and certification. Managers may enjoy the experience and appreciate the opportunity to develop.
But the business problem may not require the entire competency.
It may require a supervisor to recognize one recurring error, examine what made the mistake easy, correct the next move, assign the barrier to someone who can remove it, and check whether the next output is right.
For CEOs, this is an investment question. Are you funding the response the work requires, or buying the most complete program available?
For L&D leaders, it is a design question. Are you helping people perform a critical move, or teaching everything that belongs under a broad training topic?
A three-day program is not automatically wasteful. An eleven-minute intervention is not automatically enough. The real question is one of proportion:
What is the smallest complete response to the problem in front of us?
The Complete Coaching Proposal
At Meridian Customer Operations, a fictional composite in Impact-First Leaders, the proposed coaching program looked impressive.
It offered three days of instruction, six documented coaching sessions, observation by an external coach, and an internal certificate. Selected managers could later proceed to a higher level of certification.
The program promised a common language. It gave managers a recognised process they could apply across different conversations. Participants could also show that they had completed something substantial.
Mira from HR liked the structure. Ana, Meridian’s L&D leader, understood why the certificate mattered. A visible credential made development appear serious and complete.
Then Ramon from Operations raised a problem.
Some of his supervisors had already completed a coaching program. They understood the GROW model and had learned to ask questions rather than immediately provide answers.
But when operators repeated a production error, some supervisors continued asking questions until the employee discovered an answer the supervisor already knew.
That approach could support reflection when an employee needed to think through a goal or explore possible options. It was less useful when the next defective output could appear within minutes.
Mira asked Ramon what he actually needed supervisors to do.
Ramon pointed to an error that had appeared fourteen times in one month. Supervisors corrected the output each time, but nobody consistently sat with the operator, investigated why the wrong code remained easy to select, and checked whether the correction survived the next attempt.
“After the second error,” Ramon said, “the supervisor should see the pattern, examine the cause with the operator, agree on the correction, and check the next output.”
“How long should that take?” someone asked.
“Fifteen minutes. Thirty if the cause is not obvious.”
The three-day answer was now sitting beside a fifteen-minute problem.
Grace Finished the Response in Eleven Minutes
Ramon named three supervisors who already handled repeating errors well. One of them was Grace Bautista, a night-shift supervisor whose team had one of the lowest repeat-error rates in the plant.
Grace had no coaching certificate.
The next evening, Ana, Mira, and Ramon joined her at the packing line. A new operator named Ben had selected the wrong package code.
Grace placed the correct and incorrect labels beside each other. The product descriptions were almost identical. The inactive package code still appeared above the current one on the screen.
“So what happened?” Grace asked.
“I chose too quickly,” Ben answered.
“Maybe. What made the wrong choice easy?”
Ben showed her the screen.
Grace called the team lead. They marked the inactive code, assigned someone to ask the system owner to remove it, and asked Ben to process the next item while Grace watched.
Eleven minutes had passed.
Grace had corrected the immediate work, identified a likely system cause, created ownership for removing it, and checked the next output. She had not solved every possible coaching need in Meridian. She had completed the response this moment required.
Mira called it coaching.
Ana said it was partly coaching. It was also problem-solving, communication, instruction, judgement, accountability, and follow-through.
The competency catalogue separated those subjects. Grace used small parts of all of them in one real workplace moment.
Complete the Response, Not the Curriculum
L&D often receives a request in the language of a topic.
“We need coaching.”
“Our managers need problem-solving.”
“Our supervisors lack accountability.”
Once the topic becomes the starting point, the natural next move is to define the entire competency. The team identifies models, behaviours, learning objectives, assessments, and content. The program grows until it feels complete.
The curriculum may be complete while the response remains unfocused.
Grace did not need to use every coaching model. She did not need to discuss the history of problem-solving or complete an assessment of her communication style.
She needed to run a few moves well:
See the repeat. Find what made the wrong action easy. Correct and assign the next move. Check the proof.
That small sequence crossed several competency categories. Its value came from helping her respond to a consequential moment, not from staying within one training subject.
This is the impact-first discipline. Begin with what must move, then work backward to the behaviour, judgement, tool, and conditions required to move it.
Do not begin with everything a good coach could know. Begin with what this supervisor must become able to do.
Why Organizations Prefer the Three-Day Answer
Large programs provide visible evidence of effort.
Executives can see the schedule, participant list, provider, modules, and certificates. L&D can show that managers received substantial development. Participants may feel that the organization invested in them.
A short intervention can appear too simple.
If the answer is a four-step play practised in thirty minutes, leaders may wonder whether it is serious enough. An internal practice discovered from Grace can seem less impressive than an internationally recognised framework.
Professional identity also matters. L&D people are trained to build learning. Consultants are paid to bring expertise. Providers sell programs that have names, modules, and established methods.
A small response can make expertise look smaller than it is.
Ana felt that tension. She had spent much of her career making programs complete. If Meridian could study Grace, capture four moves, and help supervisors practise them quickly, what exactly was L&D contributing?
The answer was not more content.
L&D could locate the useful performance, make its judgement visible, design practice, prepare observers, identify where the play did not fit, and follow the evidence across shifts. It could help a working response travel beyond one excellent supervisor.
Simplicity did not make L&D less valuable. It demanded a different kind of expertise.
Eleven Minutes Did Not Solve Everything
Grace’s intervention was strong, but it did not permanently remove the problem.
Three days later, another operator on another shift selected the same inactive code.
The team had requested its removal, but the request entered a general Technology queue. No response time applied because removing an old product code did not belong to a priority category. A printed reminder had been placed beside one workstation, but the next shift used another station.
The old code remained active.
Ana asked whether they should coach the next operator.
“We can,” Grace said. “But we will be coaching people to survive a bad list.”
The eleven-minute conversation had helped Ben. It corrected his next output and exposed the system problem. But coaching alone could not remove the obsolete code, create a response owner inside Technology, or make the warning travel across shifts.
This is why the lesson is not simply “make all training shorter.”
The right response may include a short supervisor practice and a cross-functional system repair. One does not replace the other.
The eleven-minute move helps the leader respond well. The organization must still remove the condition that keeps producing the problem.
Small Does Not Mean Incomplete
A small response is incomplete when it ignores an important part of the problem.
It becomes complete when it does the job assigned to it and connects what it cannot do to the right owner.
Grace’s response worked because it addressed several layers. She corrected the immediate output, helped Ben understand what happened, found the condition making the error easy, assigned the system request, and checked the next result.
She did not personally repair the software. That action belonged elsewhere. But she did not allow the problem to disappear merely because Ben’s next output was correct.
This is an important distinction for L&D.
A short practice should not be promoted as a complete solution to a complex business result. Supervisors cannot guarantee that repeat errors will disappear. They do not control Technology queues, system design, staffing, and every cross-functional handoff.
They can make a credible contribution.
They can recognize the repeat, respond appropriately, create a usable handoff, and check the next comparable output. The organization can then inspect whether the rest of the system received and completed the work.
The intervention remains small. Its line to the business becomes stronger.
When Three Days May Be the Right Answer
There are times when a three-day program is justified.
Managers may need to coach across many types of development conversations. They may need supervised practice, ethical boundaries, deeper diagnosis, and feedback across several situations. The organization may be building an internal coaching capability rather than solving one recurring operational problem.
Depth deserves time when the job requires depth.
The mistake is assuming that every immediate performance problem requires the entire discipline.
Before approving the three days, ask what people must be able to do afterward that they cannot do now. Identify the moments where that capability should appear. Examine whether all participants need the same depth.
Perhaps every supervisor needs the eleven-minute repeat-error play, while a smaller number need advanced coaching capability. One response addresses a common operational moment. The other develops people for a broader role.
The organization no longer has to choose between shallow shortcuts and complete curricula. It can match the depth of development to the depth of the work.
What CEOs Should Ask
When a training proposal arrives, CEOs should not judge it by duration alone.
A short intervention can be weak. A long one can be necessary. The question is whether the proposed investment matches the contribution the business needs.
Ask what keeps happening. Ask what leaders should do when it happens. Ask who already performs that move well. Ask what prevents others from doing the same. Then ask what proof would show that the new response reached the work.
These questions may reduce the program. They may also reveal that the problem is larger than training and requires several functions to act together.
Either discovery is valuable.
The goal is not to spend less at all costs. It is to spend in proportion to the problem and the evidence.
What L&D Should Design
L&D should resist the urge to prove value through volume.
More modules, models, assessments, and credentials do not automatically produce a more useful response. Sometimes the strongest design is one play, several realistic cases, repeated attempts, clear feedback, and a workplace check.
The play must remain close to real work. The practice should include the pressure, ambiguity, and decisions people will face. The tool should be simple enough to use when the facilitator is no longer present.
This is what practical leadership development should accomplish. It should help leaders run useful plays in consequential moments, while making visible the authority, systems, and cross-functional conditions the play depends on.
The objective is not to make the program appear complete.
It is to make the response usable, visible, and repeatable.
Match the Answer to the Problem
Meridian’s three-day coaching proposal was not foolish. It offered depth, structure, and a common language. Those benefits may have deserved investment for leaders who needed broader coaching capability.
But the repeating packing error had a more immediate requirement.
Grace showed what that requirement looked like in eleven minutes.
She noticed the repeat, investigated what made the mistake easy, corrected the next move, assigned the system barrier, and checked the proof.
The lesson is not that every three-day program should be reduced to eleven minutes.
The lesson is that a program should not become large merely because the subject is large. Begin with the moment that matters. Identify the smallest complete response. Build enough capability to run it well. Then add depth only when the work has earned it.
Do not confuse the complete curriculum with the complete solution.
Match the answer to the problem.
About Jef Menguin
Jef Menguin is a leadership development consultant and motivational speaker. He created The Leader’s Game and Supervisor Factor, practical leadership-development systems that help organizations turn priorities into everyday leadership behavior.
Explore his work in leadership training, discover his motivational speaking programs, or connect with him on LinkedIn.