Why knowing what to do rarely changes what leaders actually do.

A leader receives thoughtful feedback. The pattern is clear: she needs to listen longer, delegate more fully, or invite dissent before announcing her view. She understands the feedback, agrees with it, and intends to change.

Then the next consequential meeting arrives. Time is short. The decision matters. Someone challenges an assumption. Without choosing it consciously, the leader returns to the response that has worked—or at least protected her—in similar moments before.

This is often described as a lack of self-awareness or commitment. Sometimes it is. More often, it reveals a basic problem in how leadership development is designed: insight has been treated as if it were behavior change.

Knowing creates possibility. Practice, feedback, and reinforcement determine whether that possibility becomes reliable behavior.

Insight is an event, not a change mechanism.

Insight matters. A leader cannot intentionally change a pattern she cannot see. Assessments, feedback, reflection, and conceptual frameworks can all create a more accurate understanding of what is happening and why.

But understanding lives in one domain; behavior has to survive in another. Leadership is enacted through repeated choices inside relationships and operating pressure. The relevant test is not whether a leader can explain the better response after a program. It is whether that response appears when the old one is faster, safer, or more familiar.

This distinction is especially important for leadership because the skills are open and contextual. There is no single script for building trust, exercising judgment, holding accountability, or navigating conflict. The leader must read a situation, choose an appropriate response, and adapt while the interaction is unfolding.

The problem is not learning. It is transfer.

Leadership training can work. Meta-analytic research has found positive effects on learning, transfer, and results—particularly when development includes a genuine needs analysis, feedback, multiple learning methods, practice, and sessions distributed over time.

That finding should shift the question from whether leadership development works to what the design expects leaders to transfer. A generic program may produce useful language and shared understanding. It is less likely to change behavior if participants cannot connect that learning to the specific situations in which their leadership currently helps or constrains performance.

Transfer also depends on the work environment. A leader may be motivated to delegate, for example, while operating in a system that routinely escalates decisions upward and penalizes reasonable mistakes. The program is asking for one behavior; the organization is teaching another.

Design around the moments that matter.

Durable development becomes more likely when the unit of change is not a broad quality—be more strategic, empowering, courageous, or collaborative—but a recognizable moment in the leader's real work.

For one leader, the moment may be the first ten minutes of a decision meeting, when stating a preferred answer too early narrows the discussion. For another, it may be the conversation after a missed commitment, when concern for the relationship causes accountability to become ambiguous. For a third, it may be the instant disagreement appears among peers and the impulse is to move the issue offline.

Once the moment is clear, the desired behavior can become equally precise: ask for disconfirming evidence before stating a view; describe the missed commitment and agree on a consequence; keep the disagreement in the room long enough to identify the real tradeoff.

Practice has to remain close to the work.

Practice is sometimes dismissed as artificial, especially with experienced executives. Poorly designed practice can feel that way. The answer is not to eliminate it; it is to make the practice more faithful to the leader's actual context.

A difficult conversation can be prepared before it happens. A recurring team meeting can become a deliberate experiment. A leader can rehearse the opening of a decision discussion, notice the response it produces, and adjust the next week. Reflection after a consequential moment can distinguish what the leader intended from what others likely experienced.

Feedback is useful here when it is specific enough to guide another attempt. “You need to listen more” describes a judgment. “You responded to each concern before asking a second question” identifies behavior the leader can test.

Coaching helps the experiment continue.

Coaching is valuable not because conversation itself changes behavior, but because it can keep attention on the transfer process across time. The leader prepares for a real moment, tries a different response, examines the consequences, and decides what to retain or adapt.

This cadence matters. Behavior change is rarely linear, and senior roles generate constant reasons to postpone it. Coaching creates a structured place to reconnect the development goal to current work rather than allowing it to become an intention remembered only at the next formal review.

The organization is always part of the intervention.

Leaders shape the environment around them, but they are also shaped by it. Decision rights, executive-team norms, performance measures, senior-leader behavior, and consequences all influence whether a new leadership practice feels credible.

An organization cannot sustainably ask leaders to take thoughtful risks while treating every miss as evidence of poor judgment. It cannot ask for candor while powerful people make disagreement costly. It cannot ask leaders to develop successors while rewarding indispensable expertise and constant personal intervention.

Leadership development becomes organizational change when the surrounding system begins reinforcing the behavior the development is meant to produce.

Measure what becomes different.

Completion, satisfaction, and insight are reasonable indicators of a development experience. They are not the outcome. The stronger evidence is what begins to happen differently in decisions, conversations, accountability, and coordinated work.

The leadership principle may be broadly applicable. The behavior change is always contextual. Development becomes durable when it is designed for the leader, the moments that matter, and the organization in which the new behavior has to survive.