“Leadership development is often judged by the wrong person, at the wrong time, using the wrong standard.”
This week, I asked my brand strategy students for early feedback on the course. Some of them said it felt more intense than they expected. It’s a 5 EC elective — they’d assumed it would be lighter. Instead, it was demanding more from them than some of their 10 EC courses.
What they weren’t questioning was whether they were learning. They could see that they were. What unsettled them was the weight of the process. It was asking more than they had budgeted for.
That gap — between what development feels like and what it’s actually doing — is exactly where most leadership decisions go wrong.
Development gets judged in the middle of it
One of the most consistent patterns in leadership and education is that people evaluate development while they’re still inside it.
At that stage, the thinking still feels slow. The repetitions still feel heavy. The value hasn’t surfaced yet because it isn’t built yet. So the experience gets assessed in the middle of the process, before what it’s building has had the chance to show itself.
This is why meaningful development gets misread so often.
What feels demanding in the moment looks like excess. What feels slow looks like inefficiency. What asks for more rigor, more attention, or more patience gets read as a design flaw rather than the design itself.
In most cases, the problem isn’t that development is failing. It’s that development is being measured before it’s finished.
Growth is not a comfort experience
We like the idea of growth more than the experience of it.
From a distance, it sounds inspiring. In practice, it is usually less elegant. It feels repetitive. Unclear. Occasionally frustrating. This is especially true in fields where the most important learning is the kind you can’t point to directly.
You can point to a finished design. You can’t point to judgment becoming sharper. You can see a completed report. You can’t see observation becoming more precise. Pattern recognition, critical thinking, the discipline to stay with a problem instead of reaching for the nearest shortcut — these are the things that actually matter, and none of them are visible while they’re forming.
When leaders optimize for how development feels, they often optimize against what development is doing. That’s not a minor calibration error. It’s a structural one.
Not all difficulty is good design
None of this is an argument for hard-for-its-own-sake.
Some difficulty is just poor design. Vague instructions are difficult. Inconsistent feedback is difficult. Unclear standards, unnecessary complexity, moving goalposts — all of these are difficult. That kind of friction doesn’t build capability. It drains it.
The goal isn’t to make development harder. The goal is to design the right kind of challenge — one that demands better thinking, not just more strain. One that asks for concentration rather than endurance. That forces people to stay with a problem a little longer because the problem genuinely requires it. That builds capacity instead of producing fatigue.
That’s a different standard. And it requires the person designing the environment to hold it clearly, especially when the people inside the experience are pushing back.
The gym is a useful frame here
In Brazilian Jiu-Jitsu, progress is built through repetition, resistance, and structured discomfort. You improve by showing up consistently, especially when you’d rather not. The sessions that exhaust you are often the ones that change you most.
But exhaustion is not the goal. The goal is adaptation. And adaptation only happens when the resistance is calibrated — not so low it produces nothing, not so high it just breaks you.
Your coach knows the difference. More importantly, your coach holds that standard even when you’re on the mat telling them you’ve had enough. That’s not indifference. That’s the job.
The classroom — or the organization — is not fundamentally different. Research on deliberate practice makes the point precisely: improvement doesn’t come from repetition alone. It comes from structured effort designed to push capability past its current edge. What that requires is someone who can tell the difference between productive discomfort and pointless strain; and who doesn’t let an uncomfortable process collapse under the weight of immediate feedback.
Capability usually shows up later
Here’s the part that doesn’t make development easier to defend in the moment: the real value almost always appears after the fact.
Not during the assignment. Not during the milestone. Sometimes not even at the end of the course. It appears years later, in a meeting where someone notices a pattern they would have missed before. In a difficult decision, when they realize they can reason with more structure than they once could. In a moment of pressure, when what felt like an overly demanding experience turns out to have been preparation.
This is why immediate comfort is such a poor proxy for long-term value.
What matters isn’t how the process feels while someone is inside it. What matters is what the process enables them to do when they’re on their own — in situations you cannot anticipate and for which no checklist will save them.
Leadership designs the conditions for growth
This is where the responsibility lands.
Development isn’t only a matter of encouragement. It’s a matter of design. Leaders shape the standards, the pace, the expectations, the quality of feedback, and the structure of support around challenge. Those choices directly determine whether difficulty becomes productive or just stays difficult.
This matters especially early in someone’s development. Every expectation teaches something. Every piece of feedback does. Every standard that gets reinforced, avoided, or quietly diluted sends a signal. Over time, those signals don’t just influence performance — they shape judgment, habits, and someone’s relationship with effort, uncertainty, and quality itself.
What you build in someone early tends to compound. That’s true in both directions.
When decision drift takes hold in organizations, it’s usually not dramatic. It’s gradual misalignment — small interpretations that accumulate until the original intent is unrecognizable. The same dynamic plays out in development. Quietly lowered standards, avoided friction, feedback that prioritizes comfort over calibration — these accumulate too. The erosion is invisible until the capability gap surfaces, usually at the worst possible moment.
The same pattern shows up in AI literacy work: the failure is rarely about the technology. It’s about leaders who didn’t design the conditions for real thinking to happen. Development is the same problem, one layer deeper.
The right question
The wrong question is whether people feel comfortable today.
The right question is whether the way you’re developing them is building the capacity they’ll need later.
Those two questions don’t always have the same answer. Most leadership development environments are optimized for the first one. That’s why so much capability gets built in spite of the system, not because of it.
The task isn’t to make development feel easy. It isn’t to make it arbitrarily hard. The task is to design it well enough that its value becomes undeniable later — even when it isn’t appreciated now.
That’s the job. And it’s harder than it looks, especially when the feedback in front of you says to make it lighter.
