Managers Accelerate, HR Sharpens: Turning Leadership Development Into a Business System
- Eric Herrenkohl

- Jul 14
- 8 min read
Leadership development stalls when the business treats it as something HR owns by itself.
HR may build the process. HR may run the talent review. HR may coordinate assessments, coaching, development plans, succession slates, and learning programs.
All of that matters.
But leaders are developed in the work.
They are developed in operating reviews, customer issues, cross-functional conflicts, delegation conversations, priority decisions, executive updates, and moments when their manager either reinforces the next-level behavior or lets the old pattern continue.
That is why the partnership between HR and line leaders matters so much.
Managers accelerate development because they control the work, the feedback, the assignments, and the day-to-day reinforcement.
HR sharpens development because it brings assessment, calibration, structure, process, and a broader view of the talent system.
When those two forces separate, leadership development becomes fragmented. The business talks about succession, but managers keep leading in ways that prevent readiness from growing. HR identifies potential, but the line does not create the experiences that convert potential into evidence. Coaching happens, but the manager does not reinforce the same behavior in real meetings.
The result is familiar.
High-potential leaders stay almost ready too long. Succession slates look better on paper than they feel in practice. Managers say they need stronger leaders, but do not always develop the leaders underneath them. HR works hard, but the system does not produce readiness fast enough.
Leadership development has to become part of the operating system of the business.
That requires managers and HR to play different, connected roles.
Why leadership development stalls when HR and line leaders separate
Leadership development often stalls when HR and line leaders are having different conversations.
HR may be focused on readiness, succession, assessment, and development planning. The line leader may be focused on delivery, margin, customer commitments, quality, staffing, and execution.
Both perspectives are valid.
The problem comes when they do not connect.
A CHRO may look at a high-potential leader and say, “This person needs broader exposure, stronger executive communication, and a chance to lead across functions.”
The operating executive may look at the same person and say, “I need them exactly where they are because they are critical to getting the work done.”
That tension is real.
But if the business always chooses immediate execution over development, the bench never deepens.
The leader stays in the same box. The manager keeps depending on them. HR keeps naming potential. Succession planning keeps identifying the same gap.
This is how organizations create a hidden talent management problem. They may have strong people, but they are not building enough readiness at the pace the business requires.
Another way the separation shows up is in feedback.
HR may hear from senior leaders that someone is “too tactical,” “not confident enough,” or “not quite ready.” But the leader’s manager may not be giving feedback that specific. The leader hears, “You are doing a good job.” Then they are surprised when the next role does not materialize.
That gap is costly.
When readiness concerns stay in the talent review and do not become coaching conversations, development slows.
A third pattern is disconnected coaching.
A leader may work with an executive coach on delegation, communication altitude, or credible confidence. But if the manager is not reinforcing those behaviors in real work, progress is harder to sustain.
For example, a leader may be working on delegating responsibility. Then the manager bypasses them or pulls the decision back during pressure. That teaches the opposite lesson.
Or a leader may be working on executive communication. Then no one helps them prepare for the senior team meeting where that communication needs to show up.
That is why HR and line leaders need to work together.
HR can sharpen the development agenda. Managers have to activate it in the business.
What managers own in readiness development
Managers own a large part of leadership readiness because they control the environment where development actually happens.
They decide what work gets assigned.
They decide how much authority moves with that work.
They decide whether the leader gets exposure to senior stakeholders.
They decide whether feedback is vague or specific.
They decide whether to coach through a hard moment or take over.
This is why managers accelerate development.
A manager who is serious about readiness does not simply ask, “Is this person doing well in the current role?”
They ask, “What does the next role require, and what experiences will help this person build evidence of readiness?”
That is a different question.
If the next role requires leading leaders, the manager has to stop using the person only as a strong individual operator. They need to give them responsibility for developing managers, setting priorities through others, and building accountability one layer down.
If the next role requires enterprise influence, the manager has to create cross-functional assignments where the leader cannot rely on direct authority.
If the next role requires stronger executive presence, the manager has to help the leader prepare for real senior-level conversations and then debrief afterward.
Managers also own the quality of feedback.
Good feedback is specific enough to change behavior.
“Be more strategic” is weak feedback.
“In the next operating review, start with the business issue, give your recommendation, name the tradeoff, and hold the technical detail unless asked” is useful feedback.
The manager’s role is to convert vague readiness concerns into observable leadership behaviors.
Managers also own reinforcement.
If a leader is trying to shift from problem solver to priority setter, the manager should ask different questions. What matters most? What should move down? What are we deciding too slowly? What should stop?
If a leader is trying to shift from doing the work to owning outcomes, the manager should stop praising only heroic problem solving. They should also notice when the leader builds capability in others, moves decision rights, and creates results through the team.
People learn what matters by what their managers inspect, praise, challenge, and protect.
That is why managers cannot outsource readiness development.
They can partner with HR. They can use coaching. They can rely on assessments. But they cannot step away from the development work itself.
What HR adds: assessment, calibration, process
HR adds value that line leaders often cannot create on their own.
The first value is assessment.
Managers know their people, but they also see them through the lens of current business needs. They may overvalue someone who is indispensable today. They may undervalue someone who is ready for a different kind of role. They may confuse loyalty, effort, or technical strength with next-level readiness.
HR brings tools and perspective to widen the view.
Assessments, 360 feedback, interview data, performance patterns, and leadership frameworks help make readiness more objective. They do not remove judgment. They improve judgment.
The second value is calibration.
A manager may think their leader is ready because they are comparing that person to the current team. Another executive may have a very different standard. HR helps the organization compare talent across functions, levels, and future roles.
This is essential in succession planning.
Without calibration, each function may define readiness differently. Finance looks for one thing. Operations looks for another. Engineering looks for another. Sales looks for another. The senior team then struggles to compare leaders fairly.
HR helps create a shared language.
What does ready mean for this role?
What evidence do we have?
Where is the person strong?
Where is the risk?
What development move would increase confidence?
The third value is process.
Strong talent management requires rhythm.
Talent reviews need structure. Succession slates need follow-up. Development plans need owners. Coaching goals need alignment. Progress needs to be revisited. Assignments need to be tracked. Readiness concerns need to move from conversation to action.
HR helps the organization sustain that rhythm.
The fourth value is pattern recognition.
Because HR sees across the enterprise, it can spot repeated issues. Maybe multiple high-potential leaders are struggling with executive communication. Maybe managers are not delegating real responsibility. Maybe succession slates are weak because leaders are not getting enough cross-functional exposure. Maybe the business keeps buying talent because it is not developing technical leaders fast enough.
That broad view is critical.
Line leaders often see the pressure inside their own operating area. HR can see the system.
The best HR leaders are not simply administrators of process. They are strategic partners who help the business build leadership capacity before the lack of capacity becomes an operating constraint.
How to create a sharper development system
A sharper development system starts with a simple principle: every development plan should connect to a business need and a readiness gap.
Too many development plans are generic.
Improve executive presence.
Build strategic thinking.
Develop influence skills.
Delegate more.
Those are reasonable phrases, but they are not sharp enough by themselves.
A better development plan identifies the next role or next level of work, the specific gap, the assignment that will create practice, the sponsor support required, and the evidence that will show progress.
For example:
A high-potential engineering leader needs to move from technical problem solver to cross-functional priority setter. The business assignment is to lead a customer implementation reset across engineering, operations, and sales. The sponsor will help prepare the executive update and debrief stakeholder conversations. Progress will be measured by decision speed, stakeholder alignment, and the leader’s ability to present a clear recommendation to the senior team.
That is a sharper plan.
It ties development to real work.
It gives the manager a role.
It gives HR something to track.
It gives the leader clarity.
It gives senior stakeholders evidence.
A sharper system also requires better talent conversations.
Instead of asking only, “Who is ready now, ready in one to two years, or ready in three to five years?” the organization should ask:
What is the next role we are preparing this person for?
What transition must they make?
What signal needs to change?
What visible win would strengthen their case?
What is the manager doing to reinforce the development goal?
What support does HR need to provide?
What date will we revisit progress?
These questions turn succession planning into an active development system.
The system also needs accountability.
If a leader is identified as high potential, someone should own the next development move. If a role is succession-critical, someone should own the bench risk. If a manager says a person is not ready, they should be able to say what readiness would require.
That does not mean every person gets promoted.
It means the organization stops letting readiness remain vague.
What a coordinated approach looks like in practice
A coordinated approach brings HR, the manager, the leader, and sometimes an outside coach into alignment around the same development goal.
Start with the business risk.
For example, the organization may have a promotion bottleneck in a key operating role. The current leader is strong, but no obvious successor is ready. The business needs more bench depth before the next growth push or succession event.
HR and the operating executive should define the role clearly.
What does success require?
What makes the role difficult?
Which leadership transitions matter most?
What signals does the next leader need to send to the CEO, senior team, board, or customers?
Then they should identify the likely internal candidates and assess them against those requirements.
One candidate may have strong technical credibility but weak lateral influence.
Another may have strong presence but limited experience leading leaders.
Another may have operational strength but too little enterprise exposure.
Now the development work can become specific.
The manager creates the assignment. HR supports the process. A coach may help the leader build the skill. The sponsor creates exposure and feedback. The leader practices in real business moments.
For example, if a leader needs to influence laterally, the development assignment might be a cross-functional initiative with real stakes. HR helps define what readiness evidence will be captured. The manager helps the leader prepare. The coach works on point of view, rationale, and ask. The sponsor observes the executive committee interaction and gives feedback afterward.
That is coordinated talent management.
Everyone is pulling in the same direction.
The leader is not guessing.
The manager is not isolated.
HR is not running a side process.
The business is building readiness through the work.
This kind of coordination is especially important in complex organizations where growth depends on technical leaders becoming business leaders. The external talent market may be thin. The internal bench may be promising but underdeveloped. The cost of waiting may be high.
That is why managers and HR need each other.
Managers accelerate because they shape the day-to-day leadership environment.
HR sharpens because it brings structure, calibration, assessment, and system discipline.
Together, they create a development system that can actually build the leaders the business needs.
Ready to align HR and the business around a bench risk?
If you have a promotion bottleneck, a thin succession slate, or a high-potential leader who is not moving fast enough, the issue may be coordination.
A focused conversation can help align HR and business leaders around one specific bench risk, clarify what readiness requires, and define the next development move.

Comments