Ana Reyes had every reason to feel proud.
Her leadership-development team had taken a messy list of requests and turned it into one polished program. Operations wanted performance management. HR wanted competency mapping. Talent Management wanted a six-month academy. Technology wanted leaders prepared for AI. Senior executives added coaching, accountability, engagement, and strategic thinking.
Ana found a way to include them all.
The program began with assessments. Supervisors attended foundation workshops, monthly masterclasses, and coaching sessions. Selected managers earned certificates. AI readiness and change leadership were added to the calendar. Application plans and dashboards promised follow-through.
Every department saw something it wanted.
Operations saw performance. HR saw competencies. Talent Management saw an academy. Technology saw AI. Executives saw accountability and engagement.
Nobody had to lose.
The proposal was approved.
The Numbers Looked Good
The program launched with energy.
Attendance was high. Participants praised the facilitators. Knowledge scores improved. Supervisors completed application plans and posted photographs of their certificates. One executive called it the company’s most complete leadership initiative.
By the measures Ana’s team had agreed to track, the program was working.
Then the supervisors returned to work.
Queues still formed. Customer concerns still travelled from one inbox to another. Schedule problems waited for approval. Quality errors created the same rework. Some supervisors held useful coaching conversations, but others delayed them until the pressure passed.
The leaders knew more.
The work had not moved.
That was the uncomfortable truth at Meridian Customer Operations, the fictional composite organization in Impact-First Leaders. The program succeeded by the measures designed for the program, but Meridian could not yet show that it had changed the business problem that justified the investment.
This is not unusual.
Leadership programs often produce exactly what they were built to produce: attendance, completion, knowledge, confidence, and positive reactions. The problem is that organizations quietly expect something else.
They expect fewer errors, faster decisions, stronger retention, better customer recovery, clearer accountability, or more consistent execution.
The program measures learning.
The business waits for movement.
The Dangerous Comfort of Green Numbers
A green dashboard is comforting because it tells us that the plan is under control.
The sessions happened. The participants came. The facilitators delivered. The forms were submitted. The scores improved.
Nothing appears broken.
That is why this kind of failure is difficult to see. The program does not collapse. People do not complain. Executives do not walk out. The initiative may even win internal awards.
It continues because every visible sign says it is succeeding.
Meanwhile, the original problem remains in another system.
Turnover sits in HR data. Repeat errors sit in Quality. Customer complaints sit in Customer Experience. Delayed decisions sit inside operations meetings. Leadership Development reports completion because completion is what it owns.
No one is lying.
Everyone is measuring a different part of reality.
The gap appears when someone asks the question the dashboard cannot answer.
That happened during Meridian’s quarterly review.
Ana presented attendance, satisfaction, completion, and assessment gains. She shared comments from supervisors who felt more confident.
Then Elena Cruz, the chief operating officer, asked:
“This tells me the program worked. Did it help us keep good people?”
Ana paused.
“We do not know yet.”
It was the most honest answer in the room.
The Program Was Not the Business Result
Ana could have defended herself.
Turnover has many causes. Employees leave because of pay, schedules, workload, job fit, career opportunities, personal circumstances, and the labor market. No responsible leadership-development team should promise that one program will control retention.
That argument would have been correct.
It would not have answered Elena’s question.
The real question was not whether the program controlled turnover. The real question was whether it helped leaders influence something close enough to turnover that the company could observe.
Did supervisors respond earlier when employees raised workload or schedule concerns?
Did someone clearly own the concern?
Did the supervisor follow up?
Did the employee know what would happen next?
Did the organization remove any recurring cause that leaders could not solve alone?
Those questions bring leadership development closer to the work.
“Improve retention” is too distant for one training program to own. But “respond to employee concerns within two working days, assign an owner, and close the loop” is close enough to practice, observe, and improve.
Leadership development does not need to promise the final business result.
It must show a credible contribution to it.
More Support Became the Automatic Answer
When application looked uneven, Meridian did what many organizations do.
It added more.
Managers needed support, so another coaching session was proposed. Executives wanted stronger evidence, so the team added assessments. A new business concern appeared, so another module entered the plan. More forms were created to document application.
Each addition made sense on its own.
Together, they created more work around the program without showing whether the work itself had changed.
This is how a development portfolio becomes heavy.
More problems create more programs. More programs create more coordination. More coordination creates more reporting. Soon, the leadership-development team spends much of its energy maintaining the system it built.
The program becomes too important to question because many people have invested money, status, and credibility in it.
The organization does not lack activity.
It lacks a clear center.
A Hospital Could Make the Same Mistake
Imagine a hospital receiving complaints about delayed patient handoffs.
The hospital responds with a communication workshop for nurses and unit supervisors. Participants learn active listening, clear messaging, feedback, and conflict management. They enjoy the program and perform well during simulations.
But the handoffs remain slow.
A closer look shows that the outgoing team records information in one system while the incoming team uses another. Nobody knows who must confirm that the patient file is complete. A supervisor cannot correct the delay because no single unit owns the entire handoff.
The communication workshop may have been useful.
It simply had no chance of repairing the broken path.
The hospital had treated the people as the problem before examining the work around them.
This is the same pattern Ana faced. Meridian had invested in stronger leaders without first defining the specific movement those leaders were expected to create—and the conditions required for them to create it.
Begin With the Movement
Before building a leadership program, ask one question:
What should leadership development help move?
Not, “Which competencies should we include?”
Not, “How many modules should the academy have?”
Not, “Which provider has the most impressive certification?”
Those questions may matter later. They should not organize the investment.
Begin with the business reality.
Perhaps repeat errors are costing the company money. Perhaps experienced employees raise concerns but nobody closes the loop. Perhaps customer problems travel through several teams without a clear owner. Perhaps decisions are delayed because supervisors lack authority.
Choose one movement close enough for leaders to influence.
Then work backward.
What should leaders do differently? In which moments? What tools do they need? What authority must they have? What system barriers must be removed? What early proof will show that the new response is becoming real?
Now you can decide whether the organization needs a workshop, coaching, a checklist, a practice challenge, a redesigned escalation path, or some combination of them.
The program is no longer the center of the decision.
The work is.
That is the discipline behind leadership training designed to move real work. The goal is not to make the learning journey look complete. It is to help leaders make a visible contribution where the business needs them most.
Do Not Confuse Learning With Movement
People can learn without applying.
They can apply without producing the expected result.
They can also do everything right while a broken system blocks them.
That is why attendance and satisfaction are not useless measures. They are simply incomplete. They tell us whether people entered the experience and how they responded to it.
They do not tell us what changed when pressure returned.
Ana’s program did not necessarily fail. It produced knowledge, confidence, and shared language. Those may become useful assets.
But Meridian had not yet earned the right to say that the investment had moved the business.
That distinction changes the next decision.
Instead of asking, “How do we improve the program?” Ana had to ask, “What problem are we asking leaders to help solve?”
The first question keeps the program alive.
The second gives it a reason to exist.
A leadership program may run perfectly. The facilitators may deliver. The participants may learn. The dashboard may turn green.
But when everyone returns to work, one question still matters:
What moved?
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.