Growing People: How to Actually Develop the People You Lead

A person on your team is quietly stuck. Maybe they're doing fine on paper, hitting their numbers, never a problem. But the spark has dimmed. They've stopped asking questions in meetings. They're doing the job, not growing into a bigger one. You can feel it, and so can they.

Most of us, when we notice this, reach for the wrong tools. We sign them up for a course. We send a link to a webinar. We promise to "carve out time for development" next quarter, and next quarter never quite arrives. None of that is bad, exactly. It's just not where growth actually comes from.

Growth comes from the ordinary, daily relationship between a person and whoever they answer to. That's you. And the data on this is hard to argue with.

You matter more than the program

Gallup has spent decades measuring what makes people thrive at work, across millions of employees and tens of thousands of teams. One number from that research keeps showing up: managers account for roughly 70 percent of the variance in how engaged a team is. Seventy percent. Not the perks, not the mission statement, not the training catalog. The person they report to.

That can land as pressure. Read it the other way. It means you have far more power to help someone grow than any program your company could buy, and you can use it in the small moments you're already in. A two-minute conversation in a hallway. A piece of work you hand off instead of keeping. A question you ask instead of an answer you give.

The same research found something specific about where to point that attention. When people strongly agree that their manager focuses on their strengths, about 67 percent of them are engaged. When they feel their manager fixates on their weaknesses, that number collapses. The instinct most of us have, to find what's wrong with someone's work and fix it, turns out to be the slow road. Building on what someone is already good at is the fast one.

Strengths first, not weaknesses only

This gets misread, so let's be clear. "Focus on strengths" doesn't mean ignore real problems or hand out empty praise. If someone is missing deadlines or treating colleagues badly, that needs a direct conversation, kindly and soon.

What it means is where you choose to invest. Imagine someone on your team who is a brilliant writer and a clumsy presenter. You can spend a year dragging their presentations from a four to a six. Or you can spend that year turning their writing from an eight into the thing your whole team relies on, and find someone else to carry the big presentations. The second path produces more, and the person feels seen rather than corrected. They start the day knowing what they're for.

So before you build a development plan for anyone, you have to know them. Not their resume. Them. What kind of work makes them lose track of time? What do they do easily that others find hard? Where do colleagues already go to them for help? What did they want to be good at when they took this job? You can't grow a person you haven't actually noticed, and most people, asked directly and without judgment, will tell you exactly where they want to head. We rarely ask. We assume. The assuming is where a lot of quiet stuckness begins.

Stop giving answers

Here's the habit that changes the most, and it's the hardest to break.

When someone brings you a problem, the fastest thing you can do is solve it. You know the answer. You've seen this before. Telling them takes thirty seconds. It feels like leadership, and it feels like help.

It's also how you keep people small.

Harvard Business Review writers Herminia Ibarra and Anne Scoular put this plainly in a widely cited piece on the manager's shift from boss to coach. The old model was simple, the manager knew the answers and handed them down. That worked when the work was stable and the boss really did know best. It doesn't work now, when the people closest to a problem often understand it better than you do, and when your job is less to have answers than to grow people who can find their own.

The shift is from telling to asking. Not therapy. Not endless open-ended musing. Just a genuine question before your advice. Try these in your next conversation:

• "What have you already tried?"
• "What do you think is really going on here?"
• "If I weren't here, what would you do?"
• "What's the part you're least sure about?"

Then wait. The silence will feel long. Let it. Most people, given two seconds and a sincere question, will walk most of the way to the answer themselves. When they do, two things happen at once. They solve the problem, and they get a little bigger. Do that a hundred times over a year and you've built someone who doesn't need you for every decision. That is the whole game.

There's a quieter benefit for you. A team that brings you problems pre-chewed instead of raw is a team that gives you your time back.

Hand over real work

You can't grow inside your comfort zone, and neither can anyone else. People stretch when they're handed something a little bigger than what they've done before, with enough support that they don't drown and enough room that they can actually own it.

This is where most well-meaning managers stall. We delegate the boring stuff and keep the interesting, visible, high-stakes work for ourselves, because that work is where mistakes hurt. But that visible work is exactly what grows people, and exactly what they need on their record to move up.

A few ways to do this without setting someone up to fail:

1. Give a whole thing, not a sliver. Owning a small project start to finish teaches more than doing one slice of a big one. People grow from holding the outcome.
2. Be clear about the goal, loose about the method. Tell them what "done" looks like and why it matters. Then let them get there their own way, even if it's not your way.
3. Name it as a stretch out loud. "This is bigger than what you've done, and I gave it to you on purpose because I think you're ready. I've got your back if it gets hard." That one sentence turns fear into a vote of confidence.
4. Stay close without hovering. Set a check-in or two so they're not alone, then get out of the way between them.

The hard part is letting them do it imperfectly. They will make choices you wouldn't. Unless something is truly going off the rails, let it ride. The mistakes are where the learning lives. And there's a trap worth naming: the moment things get tense, the urge to snatch the work back is overwhelming. Resist it. Taking it back at the first wobble teaches a person that you never really trusted them with it, and they will believe you next time.

The thing that makes all of it possible

None of this works in a climate of fear. You can ask the best questions and hand over the best projects, and if people are scared of you, it all curdles. They'll tell you what they think you want to hear. They'll hide the early mistakes until those mistakes are expensive. They'll play it safe, which is the opposite of growing.

Harvard's Amy Edmondson named the condition that makes growth possible: psychological safety, the shared sense that you won't be punished or humiliated for speaking up with a question, a concern, a half-formed idea, or a mistake. It isn't softness, and it isn't about lowering the bar. It's the opposite. As Edmondson's work shows, the teams that learn fastest are the ones where people feel safe enough to be honest about what isn't working, so the team can actually fix it.

You build it in how you respond to the small stuff. When someone admits a mistake, does your face stay open, or does it tighten? When someone disagrees with you, do they pay for it later? When someone asks an obvious question, do you make them feel stupid? People are reading you constantly for the answer to one question: is it safe to be honest with this person? Everything you hope to teach them depends on the answer being yes.

The simplest move is to go first. Say "I don't know" when you don't. Admit your own mistakes out loud. Thank someone for telling you something hard. Each time you do, you give the whole team permission to do the same.

What to actually do this week

Developing people sounds like a big initiative. It's really a handful of small habits, repeated. Pick one or two to start:

• Have one real conversation with someone about where they want to go, not just what's due Friday. Ask, then mostly listen.
• Catch yourself about to give an answer, and ask a question instead. Once a day is plenty to start.
• Find one piece of work you're hoarding and hand it to someone who'd grow from it.
• Notice out loud something a person is genuinely good at. Be specific. "You're good at your job" does nothing. "The way you cooled that client down on the call was masterful" lands.
• The next time someone brings you a mistake, lead with "thanks for telling me."

None of these takes a budget or a meeting on the calendar. They take attention, which is the actual currency of growing people.

A word on the weight of it

There's a quieter side to all this. Carrying other people's growth, on top of your own targets and your own life, is real weight, and it's easy to pour yourself into developing everyone else while running yourself into the ground. You can't be a steady, safe presence for your team if you're depleted and on edge. Your own footing comes first, not out of selfishness, but because it's the source of everything you're trying to give.

And notice the limits of your role. You can develop someone's skills and open doors for them. You can't fix what isn't yours to fix. If a person on your team is struggling in a way that goes beyond work, withdrawn, overwhelmed, clearly not okay, the kindest and most useful thing you can do is not to coach harder. It's to be human, to ask gently how they're really doing, and to point them toward real support, a doctor, a counselor, your organization's employee assistance program if it has one, or a crisis line if it's urgent. Knowing the edge of what you can carry for someone is its own kind of leadership.

Growing people is slow, mostly invisible work. You rarely get to see the full arc of it. But years from now, someone will tell a story about the boss who believed they could do the hard thing before they believed it themselves, and asked the question instead of giving the answer, and let them try. You can be that story for somebody. You probably already are for someone, whether you've noticed or not.

Sources

• Gallup, Strengths-Based Employee Development: The Business Results
• Gallup, Employees Want a Lot More From Their Managers
• Harvard Business Review, The Leader as Coach (Herminia Ibarra and Anne Scoular)
• Harvard Business Review, What Is Psychological Safety? (on Amy Edmondson's research)