People Development

People development is the most personal part of management. It's about seeing each person clearly, understanding where they are and where they're trying to go, and then doing the work to help them get there. Not by solving their problems, but by building their ability to solve problems themselves.

The arc of growth in this competency moves from learning to have honest conversations to building an organization where growth is inevitable. As a Team Lead, you're figuring out how to give feedback and run a useful 1:1. As an Engineering Manager, you're learning to differentiate your approach for different people. As a Senior Engineering Manager, you're developing the managers who develop people. And as a Director, you're accountable for whether the organization produces great leaders at all. At every stage, the core question is the same: are the people around you growing because of you?

The IC to Manager Shift

As an IC, you experienced development from the receiving end: feedback from your manager, mentorship from senior engineers, stretch assignments that pushed you. Stepping into management inverts that relationship. Your own growth still matters, but now developing others is an official part of your role. The skills that made you a strong IC, solving hard problems, delivering quality work, building technical expertise, are necessary but insufficient. Now you need to learn how to help other people build those same capabilities, which requires patience, honesty, and a willingness to let people struggle productively.

Team Lead

At this stage, you're stepping into your first real people responsibility. You may still be writing code, but your primary job is shifting: the most important thing you build now is trust. You're learning how to have honest conversations, set expectations, and help people feel seen.

This is where a lot of new managers stumble. You might default to solving problems for people instead of helping them grow through problems. You might avoid hard conversations because you still think of your reports as peers. That's natural, but recognizing it is the first step toward doing this work well.

What This Looks Like

You're holding regular 1:1s that are focused on the individual, not just status updates. You're giving timely, specific feedback tied to what you've actually observed, not vague encouragement or delayed criticism. You're learning each person's goals and starting to connect their daily work to their growth. When small performance issues come up, you're addressing them early instead of hoping they'll resolve on their own.

The hardest part is the shift in relationship. You probably came from the same team, and the people you now manage may have been your peers last month. That makes feedback feel awkward. You might overcompensate with niceness, avoiding anything that could create tension. Or you might swing the other way and become overly formal, creating distance where there used to be trust. Neither extreme works. What works is being honest and kind at the same time, which is harder than it sounds.

You'll know you're finding your footing when your direct reports know where they stand and what's expected of them. People feel safe raising concerns or sharing mistakes with you. You're starting to see the difference between managing tasks and developing people. And when you give feedback, it lands, because it's specific, timely, and delivered with care.

The Shift

The fundamental shift at this stage is moving from "I need to make sure everyone's work gets done" to "I need to make sure everyone is growing while doing the work." When you were an IC, your job was to produce great work. Now your job is to help others produce great work, and get better at it over time.

This means resisting the urge to jump in and solve problems for people. Every time you give someone the answer instead of helping them find it, you're optimizing for today's output at the expense of their long-term capability. The best Team Leads learn to ask questions before offering solutions, to coach rather than direct, and to measure their success not by what they personally delivered but by what their team learned.

How to Grow

Start by asking yourself honest questions: Do my direct reports know exactly what I expect from them? When was the last time I gave feedback that was uncomfortable to deliver? Am I solving problems for people, or helping them solve problems themselves?

Build habits around the basics. Prepare for every 1:1 with at least one development-oriented topic. Write down feedback within 24 hours of the event instead of waiting for a review cycle. After giving advice, pause and ask yourself whether you could have asked a question instead. Keep a running doc of each person's goals, strengths, and growth areas so your coaching builds on itself over time.

You'll know you're ready for the next stage when your reports describe you as someone who genuinely invests in their growth, when you're comfortable delivering hard feedback without damaging trust, and when people on your team are visibly improving in areas you've coached. The shift from peer to leader is the hardest part. Start with trust, stay honest, and don't skip the uncomfortable conversations.

At this stage, people development is about building trust and learning to coach, not solve, your way through every conversation.

Engineering Manager

At this stage, you're no longer learning how to manage. You're learning how to manage differently for different people. Your team likely has a mix of experience levels, motivations, and growth edges, and the one-size-fits-all approach doesn't work anymore.

This is where people development gets genuinely hard. You need to differentiate between someone who needs more support and someone who needs more challenge. You need to have performance conversations that aren't just encouragement. Sometimes they're about fit, trajectory, or honest limits. And you're probably starting to develop a lead or two, which means coaching someone on how to coach.

What This Looks Like

You're tailoring your approach to each individual. Different people need different things, and you've stopped treating everyone the same. You run performance conversations that are honest about trajectory, not just current output. You identify high-potential individuals and create stretch opportunities for them. When someone is underperforming, you manage it directly with clear expectations and timelines instead of hoping the situation resolves itself.

The common trap is investing disproportionately in struggling reports at the expense of high performers. Your strongest people are often the most low-maintenance, which makes it easy to take them for granted. But they need development too, and if they don't get it from you, they'll look for it elsewhere. Another trap is delaying difficult performance decisions. You keep giving someone one more quarter, one more project, one more chance, until the situation has cost the team far more than an earlier, harder conversation would have.

You're succeeding when each person on your team has a clear, individualized growth path. When you make hard calls on performance early enough that they're still recoverable. When high performers feel challenged and invested in, not ignored because they're self-sufficient. And when senior ICs on your team start taking on informal mentoring because of your example.

The Shift

The shift at this stage moves from "I develop each person on my team" to "I differentiate my approach so every person gets what they actually need." It's no longer enough to be a good feedback-giver or a caring manager. You have to be a diagnostic one. What's the real issue? Is it a skills gap, a motivation gap, or a fit gap? The intervention is completely different depending on the answer.

This also means being willing to have the conversation no one else will. Sometimes someone is in the wrong role. Sometimes they've plateaued and don't see it. Sometimes the kindest thing you can do is be direct about a trajectory concern instead of letting someone spend another year in the dark. These conversations are uncomfortable, but avoiding them isn't kindness. It's cowardice dressed up as patience.

How to Grow

Ask yourself the hard questions: Who on my team am I avoiding a hard conversation with? Are my high performers getting as much development attention as my struggling ones? Am I building growth plans, or just reacting to performance issues?

Build habits that force differentiation. Maintain a development plan for each report that evolves quarterly. Before a performance conversation, distinguish between a skills gap, a motivation gap, and a fit gap. Create at least one stretch assignment per quarter for someone who's ready. Debrief with your leads after their difficult conversations so they learn from the real thing.

You're ready for the next stage when you've successfully navigated performance management situations that resulted in either real improvement or a clean exit. When someone you've coached is visibly growing in ways they can articulate back to you. When people at different stages of their careers all describe you as invested in their growth. The real skill is seeing each person clearly and giving them what they need, not what's easiest or most comfortable to offer.

At this stage, people development is about differentiation, seeing each person clearly and having the courage to give them what they actually need.

Senior Engineering Manager

At this stage, your job is developing the people who develop people. You're managing managers, or at minimum, managing leads who own real people responsibilities. The quality of your team's growth culture now depends less on your individual conversations and more on whether the managers under you can do this work well.

This is also where you start owning the systems that make people development consistent and fair: calibration, promotion decisions, development frameworks, and hiring bar. You're no longer just coaching. You're building the infrastructure that enables coaching at scale.

What This Looks Like

You're coaching managers and leads on how to have effective development conversations. You own calibration across teams, ensuring consistency and fairness in assessments. You make difficult talent decisions: managing out, reorganizing, advocating for promotions. You build repeatable systems for onboarding, growth planning, and performance management. You identify leadership potential early and create deliberate paths to develop it.

The hardest part is letting go. You see an IC struggling, and every instinct tells you to jump in and coach them directly. But that undermines your manager's development and doesn't scale. Your job is to coach the manager on how to handle it, not to handle it yourself. The exception is when a manager is actively failing at people development and you need to intervene, but even then, the goal is building the manager's capability, not replacing it.

You're succeeding when your managers are running effective development conversations without your involvement. When calibration and promotion decisions across your teams feel fair and defensible. When you've made hard talent calls that others were avoiding, and the outcomes were better for it. The ultimate test: does people development happen when you're not in the room?

The Shift

The shift at this stage moves from "I develop people on my teams" to "I develop the managers who develop people, and I build the systems that make it consistent." Your leverage is now multiplicative. Every manager you develop well creates a ripple effect across their entire team.

This means measuring yourself differently. Your success isn't the quality of your own feedback conversations. It's the quality of your managers' feedback conversations. It's whether calibration produces fair outcomes. It's whether someone three levels below you can describe their growth path and credit their manager, not you, for helping them find it.

How to Grow

Ask yourself: Are my managers having honest development conversations, or are they avoiding them? Is our calibration process producing fair outcomes, or is it theater? Where am I still inserting myself that a manager should be handling?

Build habits around developing your managers. Regularly review their development plans, not to micromanage, but to coach on quality. After every calibration cycle, debrief what went well and what felt off. Ask skip-level reports directly how their manager is supporting their growth. Block time quarterly to assess the overall talent health of your org.

You're ready for the next stage when managers under you are growing into strong people developers on their own. When your org has a reputation for developing talent and people want to work there. When you can articulate the talent health of your org with clarity and honesty. The hardest part is trusting the system you've built and resisting the pull of the direct work.

At this stage, people development is about multiplication, building the managers and systems that make growth happen without you in every conversation.

Director

At this stage, you're accountable for whether the organization produces strong leaders. You're not coaching individuals day to day. You're shaping the environment where people development happens at scale. That means owning the philosophy: what the company believes about growth, how it invests in managers, and what it rewards.

The trap at this stage is treating people development as a program instead of a culture. Frameworks and processes matter, but only if they're connected to real outcomes: retention, leadership pipeline, engagement, and the felt experience of working here.

What This Looks Like

You set the standards for what good management looks like across the organization. You own the leadership pipeline, ensuring the org is developing its next generation of managers. You connect people development to business outcomes like retention, velocity, and engagement. When management quality competes with other priorities for investment, you champion it.

The distance from individual contributors is the biggest risk. You can easily get so far from the ground that people development becomes abstract: slide decks about engagement scores and frameworks that look good on paper but don't match anyone's lived experience. The best directors stay connected to what it actually feels like to be developed in their org, through skip-levels, exit interviews, and honest conversations with ICs.

You're succeeding when the organization has a clear, functioning leadership pipeline that doesn't depend on heroic individuals. When managers at every level see people development as core to their job, not an add-on. When talent decisions across the org are consistent, fair, and connected to real evidence. The real test: do people describe the engineering org as a place where they grew, even after they leave?

The Shift

The shift at this stage moves from "I build systems that develop people" to "I own whether this organization grows great leaders." The question is no longer about your systems or processes. It's about the outcome. Are you actually producing leaders, or just promoting strong ICs and hoping for the best?

This requires holding yourself accountable for gaps you may not directly control. If first-time managers are failing because they weren't prepared, that's your problem. If high performers are leaving because they don't see a growth path, that's your problem. If the org says it values development but managers don't have time for it because they're drowning in delivery pressure, that's your problem too.

How to Grow

Ask yourself the hardest questions: If I left tomorrow, would people development keep happening at the same quality? Are we actually developing leaders, or just promoting strong ICs and hoping for the best? What's the gap between our stated values around growth and what people actually experience?

Build habits that keep you honest. Review leadership pipeline health quarterly: who's ready, who's growing, where are the gaps. Stay connected to the ground truth through skip-levels, engagement data, and exit interviews. Hold your senior managers accountable for the development quality in their orgs. Invest in management development as deliberately as you invest in technical infrastructure.

Your growth at this stage continues through making the culture self-sustaining. The organization should develop great leaders whether or not you're personally involved. The measure isn't whether you're a great coach. It's whether the organization you've built makes great coaching inevitable.

At this stage, people development is about legacy, building a culture where great leadership is the natural outcome, not the exception.