Leadership Development Programs Don't Fail Because People Are Stubborn
What J. Richard Hackman can teach boards and executives about why frameworks do not change behavior
The Line That Always Gets Applause
I have spent a meaningful portion of my professional life in leadership development rooms. Some were energizing. Some were intellectually rich. A few were so polished and conceptually elegant that everyone left feeling sharper than when they arrived. And yet, a quarter later, the same defensive routines reappeared in the boardroom. The same capital allocation debates hardened. The same reluctance to revisit earlier assumptions quietly shaped major decisions.
Every so often, someone summarizes the frustration with a cutting observation:
It lands. It feels brave. It implies we have located the culprit, namely fragile egos in senior roles.
But through the lens of J. Richard Hackman, the diagnosis shifts in an important way. Hackman would not start by critiquing personality. He would start by examining the system.
Personality Is a Convenient Explanation
It is easy to conclude that senior leaders simply lack humility. They defend their positions. They rarely concede in public. They protect their earlier judgments. From a distance, this looks like ego. From inside the system, it could be interpreted as rational self-preservation.
Hackman’s 30 years of research on team effectiveness consistently showed that behavior is heavily shaped by enabling conditions. Before asking why someone resists admitting error, he would ask what happens to leaders who do. Does recalibration strengthen their standing, or quietly weaken it? Is dissent treated as a contribution to decision quality, or as a signal of insufficient alignment?
If the cost of being wrong is reputational or political, defensive behavior is not surprising. It is predictable.
Admitting Error Is a Structural Risk Calculation
In senior teams, especially those making high-stakes capital deployment decisions, admitting error is not merely a personal act. It has consequences. It can affect investor confidence, internal authority, and succession trajectories.
Hackman would likely probe the underlying architecture. Who retains escalation power when conviction splits? Are consequences shared across the team, or attached to individuals? Does the board visibly update its collective view when new evidence emerges? Or does momentum make recalibration increasingly difficult?
If vulnerability carries asymmetrical risk, then reluctance is not stubbornness. It is rational behavior shaped by system design.
Frameworks Detached From Real Work Become Theater
I say this with some self-awareness. I appreciate well-constructed frameworks. I build them. I refine them. I can get overly enthusiastic about decision architecture and disciplined trade-offs (I am such a nerd).
But Hackman was skeptical of development that floats above consequential work. When leadership programs are disconnected from live strategic decisions, they risk becoming intellectual theater. Psychological safety is discussed in the morning. Irreversible capital commitments are defended in the afternoon. The workshop and the boardroom operate on different incentive structures.
Without integration into real strategic trade-offs, frameworks rarely alter behavior. They enhance vocabulary, not conduct.
The Compounding Damage of Generic Leadership Development
Generic leadership development programs - and there are so many of them polluting the world of work - introduce an additional problem. Standardized curricula, often designed for broad applicability, tend to abstract leadership into universal competencies. They minimize power dynamics. They treat governance complexity as background noise.
For boards navigating activist pressure, regulatory scrutiny, or volatile markets, generic models are insufficient. They fail to account for the specific decision architecture, capital allocation realities, and portfolio coherence challenges facing that system.
Worse, generic programs can deepen the gap between rhetoric and reality. Leaders become fluent in the language of humility and inclusion. They can articulate adaptive leadership principles convincingly. But if escalation structures, incentive systems, and consequence mechanisms remain unchanged, the underlying behavior does not shift.
Now you have something more corrosive than overt defensiveness. You have performative alignment with development language. That gap erodes trust.
Enabling Conditions Outweigh Conceptual Sophistication
Hackman identified several conditions that reliably drive team effectiveness: a compelling direction, clear boundaries, real interdependence, a supportive organizational context, and well-timed expert coaching. Notice what is absent. There is no requirement for conceptual complexity. There is no mandate for elegant models.
If senior team members are not genuinely interdependent, if they can protect their individual standing without engaging dissent, humility remains optional. And optional behaviors do not compound into institutional norms.
In other words, without redesigning enabling conditions, leadership development operates at the margins.
Senior Teams Are Status Systems
One element many programs avoid discussing directly is status. Senior teams are not neutral discussion circles. Hierarchy shapes voice. Reputation shapes influence. Career trajectories shape risk tolerance.
If the CEO models certainty as strength, if the Chair curtails dissent to preserve momentum, if alignment is implicitly rewarded more than disciplined challenge, then the informal curriculum is clear. Admitting error is risky.
Under those conditions, expecting a workshop to produce durable behavioral change is unrealistic. The system is teaching something stronger than the program.
My Own Complicity
There is a slightly uncomfortable admission here. Earlier in my advisory work, I sometimes believed that more precise frameworks would unlock better leadership behavior. If only the board understood option value more rigorously. If only the executive team grasped the structural dynamics of risk-adjusted return more deeply.
The frameworks were sound. The insight was incomplete. The enabling conditions were untouched. And intact systems are resilient to surface-level intervention.
That realization has been instructive and has been eye opening.
A More Accurate Diagnosis
The original critique, that programs fail because leaders cannot admit they are wrong, contains partial truth. But a Hackman-informed reframing is more precise. Leadership development fails when it attempts to modify behavior without altering the conditions that make that behavior costly.
It also fails when it relies on generic models detached from the real capital allocation pressures and governance structures of the organization.
The issue is not simply ego. It is architecture.
Implications for Boards and Senior Teams
For boards and executive teams concerned with decision quality and long-term competitive advantage, the evaluation criteria for development need to change. Instead of asking whether participants enjoyed the program or found it insightful, more structural questions are required.
Do we visibly update strategic positions when evidence shifts? Does dissent meaningfully influence portfolio decisions? Are irreversible commitments stress-tested by disciplined disagreement? Is humility rewarded in practice, or quietly penalized?
Are our development efforts embedded in live strategic decisions, or safely insulated from them?
If the honest answers are uncomfortable, that discomfort signals a design issue.
Leadership Development Misses the Point Hackman Already Clarified
Hackman did not define leadership as inspiration. He defined it as design. In his framework, leadership effectiveness rests on four core responsibilities:
Establishing a compelling direction
Creating and maintaining a strong team structure
Ensuring a supportive organizational context
Providing expert coaching at the right moments
Three of the four are structural. Only one involves coaching. Now compare that to the dominant themes of modern leadership development. Most programs emphasize:
Emotional intelligence
Self-awareness
Executive presence
Personal resilience
Communication style
Mindset
These are psychologically sophisticated. They are also largely detached from Hackman’s central claim: leadership is about building the conditions that enable collective performance. Where, in most programs, do we rigorously train leaders to:
Design real interdependence at the executive or board level?
Align compensation with long-term capital allocation discipline?
Clarify decision rights and escalation authority?
Build information systems that surface weak signals early?
Create reward architectures that make disciplined dissent rational?
These are not soft skills. They are governance skills. They determine enterprise value. If leadership development does not train leaders to architect compelling direction, enabling structure, and supportive context, then it is operating at the periphery of performance. This is where the return-on-investment question becomes unavoidable.
Organizations invest heavily in executive development and coaching, often at six-figure levels annually. Yet relatively little of that investment goes toward strengthening the structural levers that determine capital deployment quality, portfolio coherence, and risk-adjusted return. From a board perspective, that should raise eyebrows.
If leadership is primarily about designing enabling conditions, then development programs that focus predominantly on personal psychology are misaligned with the work that matters most. They may produce more self-aware leaders. They may reduce interpersonal friction. They may improve tone in meetings. But without structural competence, they do not materially alter decision architecture.
And decision architecture is where long-term value is created or destroyed. Hackman’s guidance is not anti-coaching. It is anti-misallocation. Develop leaders who can design direction, structure, and context. Then coach them to execute with precision. Reverse that order, and you get leaders who can describe adaptive leadership beautifully while operating inside systems that quietly punish it. That is not a talent problem.
It is a governance problem.
The Real Work
Leadership programs do not fail because people are inherently stubborn. They fail because systems reward certainty more reliably than learning. They fail because generic interventions layered onto intact power structures do not change the underlying risk calculus.
Hackman would likely observe that we are trying to produce different outcomes without modifying the conditions that drive behavior. Durable change requires redesigning escalation dynamics, aligning incentives, embedding feedback into real work, and ensuring that adaptive behavior is rational rather than heroic.
That path is harder than refining slides. It is less glamorous than launching a new curriculum. But it is where meaningful improvement in governance and decision quality actually lives.
Call to Action
If this resonates, do not start by commissioning another generic leadership course. Start by examining the design of your board or executive system. Where is dissent constrained? Where is recalibration quietly penalized? Where does escalation power concentrate in ways that suppress learning?
If you are a Chair, director, or senior executive, take one upcoming strategic decision and deliberately test the enabling conditions around it. Invite disciplined dissent. Clarify escalation pathways. Make it safe, and expected, to update positions as evidence evolves.
If you would like to rigorously assess whether your leadership development efforts are embedded in real governance and capital allocation work, rather than layered on top of it, I am always open to a serious conversation.
Durable improvement in decision quality does not come from better slides. It comes from better system design.
#BoardGovernance #LeadershipDevelopment #DecisionQuality #CapitalAllocation #OrganizationalDesign #Leadership #AdaptiveLeadership #LeadershipEffectiveness #LeadershipDevelopment #ExecutiveLeadership



“Enhancing vocabulary, not conduct” is such a precise critique.
If leaders pay a price for transparency, vulnerability, or trade-off clarity, no framework will override that. Development has to intersect with real consequences.
…Otherwise it’s cosmetic at best.
This is precise and useful. The Hackman reframe — behavior as rational response to system design — is the right move away from personality diagnosis.
Where I'd push further: the enabling conditions are themselves a product of something deeper. Organisations develop their own implicit belief systems, encoded in structure, incentive, and what gets tolerated. Most people inside them don't know this exists.
Leadership can declare new intent sincerely. But if the implicit belief system hasn't changed, employees read both signals and trust the one with the track record. The gap between declared belief and embedded belief is where most transformation dies — and it's largely invisible to the people with the most power to close it.