How to Develop Employees Who Aren't Growing

You've done the work.

You set the goals. You ran the trainings. You did the one-on-ones. You gave the feedback. You invested time, energy, and budget into developing your team — and a year later, half the people you've been pouring into are still in the same place they were when you started.

It's not a confidence problem. You know how to develop people. You've done it before, with other employees, in other roles. But this time, with these specific people, the development isn't taking. And every conversation with management about it ends with you feeling like you're either being too patient or not patient enough.

If that's where you are, here's the answer most leadership content won't give you:

You're not failing at development. You're trying to develop on top of a foundation that was never installed.

Until the foundation is in place, development efforts produce activity but not progress — and the harder you push, the more frustrated everyone gets.

Let me show you what that actually means.

What Most Development Advice Misses

If you've been reading anything about staff development in the last decade, you've encountered the standard playbook:

• Set clear, measurable goals

• Provide regular, specific feedback

• Invest in training and skill-building

• Have career development conversations

• Recognize progress and effort

All of that is true. None of it is wrong. And almost all of it assumes something the playbook never names — that the employee already has a clear picture of what they're being developed toward, has the resources and direction to actually engage with the development, and has personally committed to growth in this specific area.

Strip out those three assumptions and the entire playbook breaks down. You can set goals all day, but if the employee doesn't understand specifically what those goals look like in practice, the goals don't anchor anything. You can give feedback all year, but if the employee never explicitly committed to the standard the feedback is measuring against, the feedback feels arbitrary. You can invest in training, but if the employee doesn't have the supporting resources or environment to apply what they learned, the training fades within weeks.

The reason your development efforts feel like they're disappearing into a void isn't a motivation problem. It's a foundation problem.

The Three Conditions Every Development Effort Depends On

Real, sustained development of a team member requires three structural conditions to be in place between you and them — on the specific area of growth you're trying to develop. I built a framework called AAA — Awareness, Ability, and Agreement — that names them. (You can read the full framework here.)

Each of these conditions has to be true before development can actually take hold.

Awareness — Does the employee specifically know what "good" looks like in the area you're developing them in?

Not generally. Specifically. Could they describe back to you, right now, in their own words, what excellent performance looks like in the role they're being developed for? Could they name the behaviors, the standards, the outcomes that define mastery? If they can't, the development effort is happening in the dark. The employee is being asked to grow toward a target they can't see clearly.

This is the most commonly skipped condition because most managers assume their team members can articulate the standard if asked. They usually can't. They have a fuzzy, general sense of what's expected — but the kind of specific, concrete picture you're holding in your head when you think about excellent performance? They don't have it. And without it, every coaching conversation, every piece of feedback, every training session is missing the anchor that would make it actionable.

Ability — Do they have the resources, support, and environment to actually apply what they're being developed in?

Development without supporting Ability is one of the cruelest dynamics in management. You send someone to training, they learn the skill, they come back energized — and the operation they return to has none of the conditions that would let them apply what they just learned. The tools aren't there. The time isn't there. The supporting workflow isn't there. Within two weeks, the new skill atrophies because there's nowhere for it to land.

Worse, the employee starts to feel something specific: the realization that their employer talks about development but doesn't actually structure work to support it. That's the moment a high-potential employee starts looking for somewhere else to grow. They don't quit because development failed — they quit because the gap between what was promised and what's structurally possible became too obvious to ignore.

If you want development to take, you have to verify that the environment supports the application of what's being developed. Otherwise you're training people for a job they can't do where they currently work.

Agreement — Has the employee explicitly committed to growing in this specific area?

Most managers have never had this conversation cleanly. Development plans get drafted in performance review cycles, goals get cascaded down from leadership, and the assumption is that the employee is on board because nobody's pushed back. That's not Agreement. That's compliance with a process the employee may or may not have actually committed to.

Real Agreement on development sounds like: "Are you willing to commit to growing in this specific direction over the next ninety days, with the understanding that I'm going to hold you to the standards we just talked about?" And the answer is a clear yes — out loud, in their own words, in a moment they can both remember.

Without that explicit commitment, the development plan is the manager's plan, not the employee's. It's something being done to them rather than with them. The compliance shows up — they attend the trainings, they meet the deadlines, they hit the surface metrics. But the internal growth doesn't happen, because they never personally signed up for it.

What Happens When You Try to Develop Without the Foundation

Let me run through what most managers actually experience, in concrete terms.

You identify someone on your team who has potential. You decide to invest in their development. You schedule a development conversation. You set goals. You assign training. You start having weekly check-ins.

Three months in, the trajectory looks something like this:

Month one: They're engaged. They show up to the trainings, they take notes, they have answers when you ask follow-up questions. You feel good about the investment.

Month two: The energy fades. They're still showing up but the questions are getting more surface-level. The feedback you give doesn't seem to land — they nod, but next week the same issue surfaces again. You start to wonder if they're actually committed, or just going through the motions.

Month three: You're frustrated. They're frustrated. You've put real effort into this and the needle hasn't moved. You start asking yourself whether they're actually capable of growth, or whether you're wasting your time. Worse, they're starting to ask themselves the same question — whether you actually believe in their potential or whether you're just running them through a process you don't really expect to work.

By month four, one of two things happens. Either the development plan quietly dies and both of you pretend it didn't, or the employee leaves for a job that promises real growth somewhere else.

That's not a development failure on the employee's part. That's a foundation failure on the operation's part. The development effort was running on top of three uninstalled conditions, and structurally there was nowhere for the growth to take hold.

The Diagnostic Move That Changes Everything

Before you write off an employee as "not coachable" or "not motivated" or "not ready for development," run a different conversation. Not a performance review. A foundation check.

Here's what it sounds like:

Start with Awareness:

"I want to make sure we're aligned on what excellent performance looks like in your role. Walk me through what you understand 'great' to look like in this position — what the standards are, what the outcomes are, what 'mastery' looks like in concrete terms."

Listen carefully. If they fumble, give vague answers, or describe their work in terms of tasks rather than outcomes — you've found an Awareness gap. The development effort has been happening without a clear target. Fix the Awareness gap first. Get specific about what excellent performance looks like, in their language, until they can articulate it back to you. Until that's true, no development plan will land.

Then check Ability:

"Now that we're aligned on the standard — what do you have today that supports you growing toward it, and what's missing? Tools, training, time, information, authority to make decisions. What's actually in your way?"

If they describe missing resources, missing training, dependencies on people who don't deliver, or environmental friction — you've found an Ability gap. Development without addressing the Ability gap is asking someone to grow in soil that won't support the plant. Fix the conditions before you push the development. Otherwise the development effort fails through no fault of theirs.

Then secure Agreement:

"With the standard clear and the conditions in place — are you willing to commit to growing in this specific direction over the next ninety days? I'm going to hold you to it. Can I count on you?"

That's not a soft question. It's a clear one. It requires a yes or a no. And if they hesitate, hedge, or say "I'll try" — you've found an Agreement gap. The development plan was being assumed, not committed to. Either secure the explicit commitment now, or accept that you're not actually in a development relationship with this person yet.

You'll find one of three things. One of the conditions is missing — fix that before continuing. Multiple conditions are missing — work through them in order, Awareness first, Ability second, Agreement third. Or all three are in place — in which case the development isn't failing because of foundation. It's a different problem and a different conversation.

But almost always, when development feels like it's going nowhere, the diagnostic surfaces a foundation gap that nobody named.

The Honest Conversation About Coachability

Here's the part most management content avoids saying out loud, because it's uncomfortable.

Some employees genuinely don't want to grow. The diagnostic comes back clean — Awareness is in place, Ability is supported, and when you ask for the explicit Agreement, they say no. Or they hedge so visibly that you both know it's a no.

That's a real result. And it's not a failure of your development effort. It's the diagnostic doing exactly what it was built to do — giving you clean information about what you're actually dealing with.

When the diagnostic returns "the foundation is intact and the employee is choosing not to engage," you have a different conversation. Not a development conversation. A career-fit conversation. Whether this role is the right place for them, whether the path forward is mutually clear, whether you're in agreement about what continued employment looks like. That's not a punishment. It's honesty about what's true.

The reason most managers can't have that conversation cleanly is they don't actually know whether they're dealing with a true willingness problem or a foundation problem masquerading as one. Run the diagnostic, and the answer becomes clear. Then the next conversation — whatever it is — can be honest.

Why This Matters More Than It Seems

Here's the larger reframe.

Most operations lose their best development opportunities not because their managers don't care about people, but because their development efforts run on broken foundations. The investment is real. The intention is good. The structure underneath isn't there. So six months of effort produces an employee who's slightly more frustrated, an operation that's slightly more cynical, and a manager who starts to wonder whether development is worth the investment at all.

It is. But it requires the foundation to be installed first.

The operations that develop people consistently aren't doing it through better training programs or sharper feedback. They're doing it through a structural commitment to making sure Awareness, Ability, and Agreement are in place between leaders and team members on every important growth area. Once those three conditions are real, development becomes a natural consequence of working in that environment. People grow because the structural conditions of the operation make growth not just possible, but inevitable.

That's the operating principle of operations that develop talent. Not luck. Not charisma. Not heroic management. A foundation that holds.

What to Do Next

If you've been frustrated by development efforts that aren't producing growth, the question isn't "do I need a better development plan." The question is "what foundation conditions are missing that are making the development plan fail?"

Run the diagnostic on your hardest development case. The conversation will tell you what you're actually dealing with — and what to fix first.

If you want to know which condition — Awareness, Ability, or Agreement — is most broken in your operation right now, take the free 5-minute Accountability Diagnostic. Twenty questions. Personalized action plan in your inbox. Tells you exactly which condition to install first if you want development to actually take hold.

If you want the full framework — including the rails of Courage and Consistency that hold the whole system up — Say It Once is the manifesto. Built for leaders who are tired of pouring effort into development that doesn't produce growth.

You're not failing at development. You're trying to develop on top of a foundation that was never installed. Install the foundation, and development becomes a result, not a project.

Kwan Howard is the author of Say It Once and the creator of Foundation-First Accountability — the framework that installs the foundation underneath every accountability conversation, so when you say it, it lands. Once.