Despite broad agreement that developing people is a core management responsibility, most managers invest far less in it than they intend to, and far less than organizations need. This article examines the structural and psychological barriers that prevent even well-intentioned managers from consistently developing their teams, the specific behaviors and conditions that make development conversations effective rather than performative, and what organizations can do to build the infrastructure that turns development intent into development reality. We draw on research in leadership development, coaching effectiveness, and organizational learning to identify the practical levers that make the difference between organizations where people grow and organizations where people stagnate despite good intentions at every level.
The good intentions problem
Ask most managers whether they believe developing their people is important and they will say yes. Ask them how many hours in the last month they spent in deliberate, focused development conversations with their direct reports - not performance conversations, not project updates, not feedback delivered in passing - and the number is usually very low. This is not a cynical observation. It reflects a genuine structural problem that organizations consistently underdiagnose.
Day (2000) distinguished between leader development - building the capabilities of individual leaders through training, coaching, and feedback - and leadership development - building the collective leadership capacity of an organization through systems, culture, and deliberate investment. Most organizations focus intensively on the first and neglect the second. The result is that individual managers who genuinely want to develop their people operate in systems that make it difficult: performance management processes that are compliance-oriented rather than development-oriented, meeting cadences that leave no time for developmental conversation, and cultures that signal implicitly that delivering results now matters more than building capability for later.
McCall, Lombardo, and Morrison (1988) established what is now a foundational finding in leadership development: roughly 70 percent of meaningful development happens on the job, through stretch assignments, new responsibilities, and challenging experiences. About 20 percent happens through coaching and mentoring. About 10 percent happens through formal training. The implication is that the most powerful lever for developing people is not sending them to a course. It is how managers assign work, how they structure feedback, and how much they invest in understanding what each person needs to grow.
Why development gets deprioritized
The structural pressure against development is real and worth taking seriously. Managers face competing demands that are urgent, visible, and immediately consequential: hitting the quarter's numbers, resolving the current crisis, managing up to senior stakeholders who are focused on short-term outcomes. Development work is rarely urgent, often invisible, and its consequences are diffuse and delayed. Kahneman (2011) described the general principle at work: humans are systematically biased toward the immediate and visible over the distant and abstract, even when the distant and abstract matters more. Development conversations get scheduled and then bumped for the thing that is on fire right now.
There is also a skills gap that organizations rarely acknowledge honestly. Developing people requires a specific set of capabilities that are distinct from the capabilities that get people promoted to management in the first place. Technical expertise, project execution, and individual performance are what most managers are promoted for. The ability to diagnose what a person needs to grow, to have direct and useful developmental feedback conversations, to assign work in a way that stretches people without overwhelming them - these are skills that many managers have never been taught and are not evaluated on in any meaningful way. Feedback that is intended to help people grow but is vague, generic, or focused on personality traits rather than specific behaviors does not produce development. It produces confusion and, over time, disengagement.
What actually makes development conversations effective
The research on coaching and developmental conversation effectiveness is more specific than most management training implies. Locke and Latham (2002) established that feedback needs to be connected to specific, observable behaviors and clear goals in order to change behavior. Hattie and Timperley (2007) found that feedback is most effective when it addresses the task level (what specifically needs to be different), the process level (how to approach the work differently), and the self-regulation level (how to monitor and adjust one's own performance) - and significantly less effective when it addresses the personal level (vague attributions about character or attitude).
This has a direct practical implication: most feedback conversations that managers have are less effective than they could be because they operate at the wrong level. "You need to communicate more proactively" is a personal-level feedback statement. It gives someone no information about what to do differently on a specific task in a specific context. "In this week's project update, the timeline change was not surfaced until I asked about it - what would have needed to happen for you to have raised it earlier?" is a process-level conversation that gives someone something concrete to work with.
A useful distinction: The goal of a development conversation is not to make someone feel assessed. It is to help them build an accurate model of their own behavior and its effects, so they can make better choices going forward. The manager's job in that conversation is to be useful, not to be evaluative.
The role of stretch and challenge
Given that most meaningful development happens through experience, the most important development decision a manager makes is often not what feedback to give but what work to assign. McCall (1998) documented the specific types of experiences most associated with leadership development: assignments that require managing for the first time, assignments that involve significant unfamiliarity, assignments that create high stakes and real consequences, and assignments that require working across organizational boundaries and influencing without authority.
The barrier here is again structural. Managers tend to assign important or challenging work to the people who have already demonstrated they can handle it, because the cost of an underperforming assignment is immediate and visible while the developmental cost of never giving stretch assignments is diffuse and delayed. The result is a Matthew effect in organizational development: the people who are already strong get the experiences that make them stronger, and the people who have not yet demonstrated capability do not get the experiences that would build it.
Kegan (1994) argued that development requires a level of challenge that exceeds current capability by an appropriate margin - not so far beyond current capability that it produces failure and demoralization, but far enough beyond it that it requires genuine stretching. Managers who understand this calibration, and who invest in providing the scaffolding - the coaching, the check-ins, the honest feedback - that makes stretch assignments genuinely developmental rather than just stressful, are doing the work that actually builds organizational capability over time.
What organizations need to change
Individual managers operating in development-hostile systems will not, on average, develop their people effectively regardless of how much they intend to. The organizations that consistently develop talent are the ones that have built the systemic conditions that make development the path of least resistance rather than an additional burden on already-stretched managers. This means performance management systems that evaluate managers on how well they develop their people, not just on whether their teams hit their numbers. It means building development conversations into the standard operating cadence rather than leaving them to individual initiative. It means giving managers the feedback tools, the coaching skills, and the time to do development work without sacrificing delivery.
Charan, Drotter, and Noel (2011) described the leadership pipeline problem precisely: organizations fail to develop their next generation of leaders not because they do not care about it, but because they never build the infrastructure that makes development consistent and systematic rather than dependent on the occasional exceptional manager. The organizations that solve this problem are not the ones that find more exceptional managers. They are the ones that build systems where ordinary managers - well-intentioned, busy, doing their best - are supported to develop their people reliably, as a normal part of how the organization runs.
- Charan, R., Drotter, S., and Noel, J. (2011). The leadership pipeline: How to build the leadership powered company (2nd ed.). Jossey-Bass.
- Day, D. V. (2000). Leadership development: A review in context. The Leadership Quarterly, 11(4), 581-613.
- Hattie, J., and Timperley, H. (2007). The power of feedback. Review of Educational Research, 77(1), 81-112.
- Kahneman, D. (2011). Thinking, fast and slow. Farrar, Straus and Giroux.
- Kegan, R. (1994). In over our heads: The mental demands of modern life. Harvard University Press.
- Locke, E. A., and Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation. American Psychologist, 57(9), 705-717.
- McCall, M. W. (1998). High flyers: Developing the next generation of leaders. Harvard Business School Press.
- McCall, M. W., Lombardo, M. M., and Morrison, A. M. (1988). The lessons of experience: How successful executives develop on the job. Free Press.