Leadership Development: A Complete Guide

Most organizations spend real money on leadership development and get disappointing results.

That’s not because leadership development doesn’t work. It’s because most leadership development programs aren’t actually designed to develop leaders.

Here’s what I mean.

Why Leadership Development Programs Fail

The research on leadership development effectiveness is sobering. Studies consistently show that most training investments don’t produce lasting behavior change. Leaders attend programs, get energized, return to work — and within 90 days, old habits are back.

Three root causes show up over and over:

They start without a real diagnosis.

Most organizations design leadership programs around general best practices — communication skills, emotional intelligence, strategic thinking. These are worthwhile topics. But they may or may not be what’s actually limiting your leaders.

Real development starts with understanding the specific gaps creating friction in your organization right now. Not what the industry says leaders generally need. What your leaders actually need.

The design doesn’t connect to real work.

Leadership is learned by doing. Classroom training — even excellent classroom training — can build awareness and vocabulary, but it rarely changes behavior on its own. The learning has to be applied in actual work contexts, with real feedback on real decisions.

Programs that create meaningful behavior change build learning into the work itself: action learning projects, executive coaching, peer advisory groups, stretch assignments. The classroom component is small. The applied component is large.

There’s no measurement that matters.

Most organizations measure leadership development by completion rates. That’s a measure of attendance, not development.

What should you measure? Behavior change. Are leaders doing things differently six months after the program? Are their teams performing better? Are retention rates improving in high-potential talent pools? These metrics are harder to collect. They’re worth it.

A Framework That Works

Over 25 years of leadership development work, I’ve identified four things that distinguish programs that produce results from programs that don’t.

1. Diagnose first.

Before designing anything, get clear on what’s actually limiting your leaders. This means conversations, 360 assessments, performance data, and honest discussions with executives about where they’re seeing breakdowns. The diagnosis takes time. It’s the most valuable part.

2. Design for application.

Build the learning into the work. Use real business challenges as the curriculum. Assign coaches, not just instructors. Create peer learning cohorts that continue after the formal program ends. The goal is habit formation, not training completion.

3. Build in accountability.

Development doesn’t happen without accountability. Who is supporting each leader’s development? What are the specific commitments they’ve made? How are those commitments being tracked? The best programs create accountability structures that outlast the program itself.

4. Measure what matters.

Define your outcomes before you start. What does success look like? How will you know if behavior has changed? Build measurement into the program design from the beginning — don’t try to evaluate impact after the fact.

The Role of Senior Leadership

Here’s something most leadership development conversations miss: the biggest variable in whether a program works isn’t the program.

It’s senior leadership modeling.

If your executives aren’t visibly developing themselves — seeking feedback, acknowledging development needs, making time for coaching — the leadership development message is undermined from the top. Leaders watch what senior leaders do, not what the learning department says.

The organizations that develop great leaders have senior executives who model growth as an ongoing practice, not a career phase they’ve graduated from.

What Good Looks Like

The best leadership development I’ve seen shares a few characteristics.

It’s ongoing, not episodic. Development isn’t a program you send leaders to once. It’s an ongoing investment in the capabilities required to drive organizational performance.

It’s personalized, not generic. Different leaders have different gaps. The most effective development is tailored to where individuals actually are, not a curriculum designed for the average leader.

It’s connected to business outcomes. The strongest programs are explicitly linked to organizational priorities. Leaders aren’t developing skills in the abstract — they’re developing capabilities the business needs to execute its strategy.

And it’s supported, not just delivered. Development requires ongoing coaching, peer accountability, manager reinforcement, and regular check-ins. Programs that deliver training and disappear produce compliance. Programs that provide ongoing support produce growth.

Getting Started

If your organization is investing in leadership development and not seeing results, start with an honest diagnosis.

What’s actually limiting your leaders right now? What behaviors are getting in the way of performance? Where are the gaps between the leadership culture you have and the one you need?

The answers to those questions are the foundation of a program that works.

If you want to go deeper, we work with organizations on exactly this kind of assessment. The conversation starts with understanding what you’re actually dealing with — not with selling you a program.

See our approach to organizational culture assessment. Read our guide to change management and organizational change. Explore gothamCulture’s leadership development services.

Overcoming Resistance to Change: The Cultural Dynamics Leaders Miss

Leaders love to say “people are resistant to change.” It’s lazy thinking.

People aren’t resistant to change. They’re resistant to being changed — especially when nobody’s explained why, asked for their input, or addressed what they’re actually worried about.

That shift in framing matters. A lot.

Resistance Is Rational, Not Defiant

Here’s what I’ve learned working with organizations through transformation: resistance isn’t a character flaw. It’s a survival response. And it’s actually intelligent feedback if you’re willing to listen to it.

When employees are unclear about what’s changed, how to execute, or where to get help, resistance isn’t dysfunction — it’s rational self-protection. Your brain detects ambiguity and threat, and it defaults to “stay put.” That’s not defiance. That’s biology.

Ford & Ford (2009) nailed this: resistance isn’t a property of the person. It’s a conversational construct between the change agent and the recipient. The resistance exists between you and them, not in them. Which means you’re partly building it with how you communicate the change.

Too many leaders treat resistance as an obstacle to overcome — as if people are just being difficult. What if instead, resistance was information? What if it told you something important about your change design?

The Psychology Behind It (And Why Logic Fails)

I need to be direct: you can’t think your way past these barriers. Logic alone won’t move the needle.

Kahneman and Tversky showed us something fundamental: people weigh potential losses roughly twice as heavily as equivalent gains. This is loss aversion, and it’s hardwired. When change happens, people don’t focus on what they might gain. They focus on what they might lose — competence, status, security, identity.

I’ve watched this play out at every level. A senior director who’s spent fifteen years building a process hears it’s being replaced. On paper, the new system is better. But that director’s expertise, reputation, and daily routine are built around the old way. You’re not asking them to learn new software. You’re asking them to become a beginner again — in front of their team, in front of their peers. That’s a threat to professional identity, and it triggers a defensive response that looks like resistance but is actually self-preservation.

Breakwell’s research identified four things change strips away: self-esteem, competence, continuity of identity, and distinctiveness. Change can threaten all four simultaneously. No wonder people push back.

Then there’s status quo bias. Even when the current state isn’t working, the known feels safer than the unknown. People would rather live with a problem they understand than risk an outcome they can’t predict. This isn’t laziness. It’s a deep cognitive preference for certainty — and organizational change is the opposite of certainty.

These forces operate unconsciously. They’re not beliefs people can argue themselves out of. They’re drives. And they explain why the standard playbook — “just communicate better” — falls short. Communication addresses awareness. It doesn’t address loss, identity, or fear.

Resistance as Organizational Intelligence

This is where it gets interesting. When leaders treat resistance as feedback instead of opposition, they uncover blind spots in change design, misaligned incentives, and implementation barriers they missed.

Ford & Ford put it this way: “Resistance can be an important resource in improving the quality and clarity of objectives and strategies.”

I’ve seen this in practice. The resistance that shows up — whether it’s pushback in town halls, skepticism in working groups, or quiet non-adoption — often points to real problems. Maybe the change doesn’t align with how work actually gets done. Maybe you’re asking people to embrace a process that’s slower than the old one. Maybe the technology is poorly designed for how people actually use it.

The cultures that transform successfully aren’t those that bulldoze resistance. They’re the ones where leaders actually listen to it, learn from it, and adjust.

What’s Actually Driving Resistance (The Data)

Let me give you the real drivers. This matters because most organizations focus on the wrong levers.

Trust in leadership is the #1 factor. 41% of resistance stems from lack of trust in leadership — that’s the biggest predictor (ChangingPoint, 2025). When people don’t believe their leaders, they don’t believe the change is genuine or in their best interest.

After that: 39% lack awareness about WHY change is happening. People will resist what they don’t understand. 38% fear the unknown. 28% report insufficient information about how to execute. 27% are anxious about changes to job roles.

Here’s the bigger picture: 79% of employees report low trust in change initiatives (Gartner, 2025). And 73% of HR leaders report employee fatigue from continuous change.

You can’t inspire your way past these numbers. This isn’t about enthusiasm deficit. It’s about trust and clarity deficit.

Change Fatigue Is Real — And Inspiration Doesn’t Fix It

I’m going to say something that runs counter to how we typically talk about change: the inspirational approach doesn’t work in low-trust environments. In my experience, it actually backfires.

Think about it from the employee’s perspective. They’ve been through three reorganizations in five years. Each one came with a kickoff meeting, a new vision statement, and a promise that “this time it’s different.” Each one disrupted their work. Maybe each one cost them a colleague who didn’t make the cut. And now here comes the CEO with another town hall and another slide deck about “transformation.”

This isn’t cynicism. It’s pattern recognition. People learn from experience. And when experience teaches them that change initiatives come with cost and rarely deliver on promises, they stop expending emotional energy on the next one.

Gartner’s research confirms this: 73% of HR leaders report their employees are fatigued from change. And 74% say their managers aren’t equipped to lead it. That’s not a communication problem. That’s a structural problem.

What’s the alternative? Gartner found that making change routine is three times more effective than the inspirational approach (Gartner, 2025). Instead of asking people to get excited about each new initiative, the organizations that succeed treat adaptation as a normal part of how work gets done. Change isn’t an event with a launch date. It’s an ongoing capability that’s built into how the organization operates.

The old playbook — get people excited, paint an inspiring vision, hope enthusiasm carries the day — doesn’t account for cumulative fatigue. It doesn’t account for the fact that organizations are running multiple concurrent change initiatives, each competing for the same finite pool of employee attention and goodwill.

The move is different: focus on making adaptation routine, not heroic. Build predictable rhythms. Acknowledge what’s hard. Make it normal, sustainable, and manageable instead of dramatic and exhausting.

The Role of Organizational Justice

There’s one more dimension that doesn’t get enough attention: fairness.

Research on organizational justice (Frontiers in Psychology, 2021) shows that when employees perceive fairness in the change process — procedural fairness, distributive fairness, and interactional fairness — resistance drops significantly. The quality of the leader-member exchange relationship acts as a buffer against defensive reactions.

What does this look like in practice? It means people need to feel that the process by which decisions were made was fair, even if they disagree with the outcome. They need to feel that the burdens and benefits of change are distributed equitably. And they need to feel that their leaders treated them with dignity and respect throughout the transition.

When I see organizations where resistance is particularly fierce, one of the first things I look at is whether people feel the process was fair. Often they don’t — and that’s not because the decision was wrong, but because no one bothered to explain how it was made or who was consulted.

Participatory approaches help here. When employees have genuine input into how change is implemented — not just whether it happens — adoption increases by 24% (ChangingPoint, 2025). Note the word “genuine.” Asking for input and then ignoring it is worse than not asking at all. People can tell the difference between consultation and theater.

Working WITH Resistance Instead of Against It

So what do you actually do? Here’s what shifts the needle.

Stop framing resistance as opposition. It’s not you versus them. It’s a puzzle you’re solving together.

Listen for the signal in the noise. What specifically are people resisting? Dig into the real concern. In my experience, when you ask people directly — not in a way that’s defensive, but genuinely curious — they’ll tell you what’s actually driving the resistance. And often it’s not what you assumed.

Address the psychological roots. Acknowledge what’s being lost. If you’re replacing a tool people are competent with, that’s a real loss. You don’t have to make it go away, but naming it reduces the defensive response. “We know this tool is familiar and you’re proficient with it. Here’s why we’re moving” is a conversation. Pretending there’s no loss just makes people feel unheard.

Build trust before you need it. 41% of resistance is a trust problem. You can’t solve that with a single communication. Trust is built through consistent leadership behavior, transparency about decisions, and follow-through on commitments. That happens over time, not during change.

Involve employees in implementation design. Participatory approaches increase successful adoption. This isn’t about asking for input and ignoring it. It’s about genuinely shaping how change happens based on what people with expertise in the work tell you.

Ensure organizational justice. Fairness in the process reduces defensive responses. If people feel like the change was decided without them, imposed on them, or designed without understanding their reality, they’ll resist. If they feel like they had voice and like the process was fair, they’re far more willing to try.

The Real Question

The next time someone tells you “people are resistant to change,” push back. Ask them what specifically people are resisting — and whether anyone has actually listened to find out.

Because here’s what I’ve learned: resistance isn’t the enemy. It’s the immune system. It’s the organization’s way of saying “something isn’t right here.” And the leaders who treat it that way — who get curious instead of frustrated, who listen instead of lecture — are the ones whose changes actually stick.

The question isn’t how to overcome resistance. It’s whether you’re willing to hear what it’s telling you.

This article is part of gothamCulture’s Change Management & Culture series. For the cultural dynamics specific to AI adoption, see AI Adoption Resistance Is Cultural, Not Technical. For a deeper look at how organizational culture shapes change, see How to Change Organizational Culture.

Leading Organizational Change: Why Culture Eats Strategy for Breakfast

Most change initiatives come with a beautiful strategy deck. Polished slides. Clear milestones. ROI projections. Detailed timelines. And then, somewhere between the launch meeting and month three, it all falls apart.

Here’s what I’ve learned: the strategy isn’t the problem. Leadership behavior is.

I’ve watched executives unveil an 18-month digital transformation while simultaneously undermining it with their own actions. I’ve seen a VP announce a shift to “agile decision-making” while reverting to command-and-control the moment something goes wrong. I’ve observed countless leaders give a rousing town hall about a new culture and then walk back to their offices and run the old culture.

People notice. They always notice.

Culture doesn’t beat strategy because culture is harder to change. It beats strategy because culture is what actually happens. Strategy is what you say is going to happen. Those are different things.

The Data Is Brutally Clear: Leadership Is Everything

73% of change initiatives succeed when there’s active executive sponsor support. Without it? 29%. That’s not a difference. That’s a completely different world. You’re looking at a 2.5X success premium just from having leadership that actually shows up.

Even more specific: 79% success with truly effective sponsors versus 27% without. When I talk to practitioners about what moves the needle most, it’s always the same answer: sponsor behavior. Not sponsor titles. Behavior.

Only 25% of organizations say their leaders excel at managing change. Three-quarters don’t think their leadership is good at this. And yet, leadership is the lever that matters most.

Only 27% of employees agree that their organization’s leadership is trained to lead change. And from HR leaders? 69% say their managers aren’t equipped to lead change.

No wonder two-thirds fail.

The Say-Do Gap: Your People Are Watching Closer Than You Think

I’ve been studying executive presence and credibility for years. And there’s one pattern that never changes: people don’t believe what leaders say. They believe what leaders do.

Leaders who close the say-do gap get rated significantly higher in effectiveness. CCL and Harvard Business Review studied 5,400 leaders and found the same pattern. The difference between leaders people trust and leaders people doubt? It’s not eloquence. It’s consistency.

When you’re asking people to embrace new ways, their BS detector goes way up. They’re watching your behavior more carefully during change than at any other time.

Here’s the uncomfortable reality: Fewer than half of organizations hold leaders accountable for actually living the values they announce. Which means there’s no real consequence for the say-do gap.

When Alignment Breaks: What Happens in the Middle

Organizational change doesn’t fail at the top. It fails in the middle.

Organizations with shared vision and aligned leadership across all levels are 2X more likely to achieve above-median financial performance. Alignment isn’t nice to have. It’s the difference between average and strong results.

And turnover? A 25% reduction in turnover when leadership alignment is strong. People stay because they trust where the organization is going.

When middle managers undermine the direction, even subtly, the organization defaults to skepticism. People think: “If they don’t believe it, why should I?” And they’re right to think that.

The Trust Equation: Everything Comes Down to This

41% of resistance to change stems from lack of trust in leadership. Not confusion. Not inability. Not even disagreement with the change itself. Lack of trust in the people leading it. That’s the #1 reason people resist.

How do you build trust? Not in a town hall. Not with a memo. Trust is built in daily behavior. It’s built when you say you’re going to do something and you do it. It’s built when you acknowledge a mistake instead of spinning it.

Employees who trust their direct manager are 5X more likely to be engaged. And engagement? Only 31% of employees were engaged in 2024, the lowest rate in a decade.

You can’t get discretionary effort from people who don’t trust you. And real change requires discretionary effort.

What Actually Effective Change Leaders Do

1. They Model the Change Visibly

They don’t just approve it. They do it. I watched a CEO announce a shift to asynchronous-first communication. She changed her own calendar. Started declining meetings. Within three months, meeting time across the company dropped 20%. Not because she mandated it. Because she showed it was real.

2. They Close the Say-Do Gap

Effective change leaders are obsessive about the say-do gap. They audit themselves. When they notice their behavior doesn’t match their words, they acknowledge it. They adjust. Or they stop saying the thing.

3. They Invest in Middle Management

This is where most change initiatives collapse. Effective change leaders give middle managers more information, not less. They involve them early. They ask them what’s hard. They give them tools and language they can use with their teams.

4. They Build Trust Before They Need It

You build trust in calm times. You spend it in crisis times. If you wait until the change begins to build trust, you’re already behind.

5. They Create Early Wins and Tell Those Stories

Change is long. People get fatigued. You have to interrupt that fatigue with moments of “Look, this is actually working.” Early wins are psychological, not just practical. Effective leaders understand that.

The Uncomfortable Reality: Your Credibility Is Harder to Build Than You Think

Leadership credibility is built over years and spent in months.

Your team is not looking for perfection. They’re looking for consistency. They need you to do what you said you’d do. They need you to acknowledge when you don’t. They need you to be the same person in private meetings as you are in public.

Nokia Case Study: Having the Right Strategy with the Wrong Culture

Nokia had smartphones figured out. By 2006, they saw where the market was going. They had the technology. They could have owned smartphones the way they owned mobile phones in the 1990s.

But Nokia’s culture was built on a premise: We are the standard. When the iPhone arrived in 2007, it was a threat to that cultural identity. The organization punished dissent. People who raised the iPhone threat were marginalized.

Two years later, Nokia had to make a strategic partnership with Microsoft. Five years later, Microsoft bought the business for $7.2 billion, a fraction of Nokia’s former value. The strategy was right. The culture ate it anyway.

The Three Conversations Leaders Need to Have Before Change Begins

Conversation 1: Are we actually aligned? Not “Do we agree on the direction?” but “Are we each going to change our behavior?”

Conversation 2: What is this change actually threatening about our culture? Every change threatens something. Name it. Acknowledge what you’re asking people to grieve.

Conversation 3: What are we willing to change about ourselves to model this? This is the moment of truth. If your answer is vague, people will notice.

The Final Truth: Culture Beats Strategy Because Culture Is What Leaders Do

Culture change doesn’t start with a strategy deck. It starts with leaders looking in the mirror and asking: “What am I going to do differently?”

Not “What is the organization going to do?” What am I going to do?

Because the moment you change your behavior, your actual, daily, visible behavior, culture begins to shift. Not because you mandated it. Because you modeled it.

Your Closing Challenge

Pick one change initiative you’re leading right now. Ask yourself: Do my people trust me? Not “Do I think they trust me?” Ask someone. Ask your direct report. Ask honestly.

If the answer is yes, move forward confidently. You have the foundation.

If the answer is no or equivocal, stop. Not the initiative. The recruitment for it. Spend the next 30 days building trust. Keep commitments. Acknowledge mistakes. Be consistent. Close the say-do gap.

Because here’s the truth: You can have the right strategy and fail because people didn’t believe you. Or you can have an imperfect strategy and succeed because people trusted you and committed discretionary effort to make it work.

Strategy is what you say you’re going to do. Culture, real, durable, change-enabling culture, is what leaders actually do.

Make sure they’re the same thing.

Change Management Models Compared: Which Framework Actually Fits Your Culture?

When I ask senior leaders how many change initiatives they’re running simultaneously, the answer keeps growing. Last year it was three or four. Now? Eight. Ten. Some are managing a dozen concurrent transformations. And when I ask how many of those are succeeding, the silence is telling.

Here’s the uncomfortable truth: 85% of senior executives report an explosive increase in change initiatives. And yet, two-thirds of them fail. The problem isn’t change itself. It’s that most organizations are using the wrong framework for their culture.

I’ve seen this a hundred times. A Fortune 500 company adopts Kotter because they read the Harvard Business Review article. A tech startup copies ADKAR because a consultant sold them on it. A mid-market manufacturer tries McKinsey’s 7-S because they used it for strategy and assume it translates to implementation. And then they’re surprised when the model that worked beautifully for someone else lands flat in their organization.

The frameworks themselves aren’t broken. The fit is.

The Five Major Models And Which Cultures Actually Need Them

Let me walk you through the ones that matter. There are five that show up over and over in real organizations. And each one works brilliantly if you match it to your culture.

Kotter’s 8-Step Model: The Classic Hierarchy Play

What it is: John Kotter’s framework is the gold standard for large-scale transformation. Create urgency, build a coalition, craft a vision, communicate it, empower action, create short-term wins, consolidate gains, embed culture. It’s elegant, sequential, and proven at scale.

Strengths: Built for scale. Creates visible milestones. Top-down clarity. In hierarchical organizations, people want that clear direction from leadership. Combat-tested across thousands of large-scale transformations.

Weaknesses: It’s linear. Real change isn’t a straight line. Culture is often Step 8, the final step after the change happens. But culture drives everything. That’s backwards. Requires tight executive alignment.

Best cultural fit: Hierarchical organizations. Large enterprises. Manufacturing. Finance. Government. Defense.

When to avoid it: Flat organizations. Startup cultures that pride themselves on autonomy. High-trust environments where top-down mandates feel tone-deaf.

ADKAR: The People-First Lens

What it is: Prosci’s ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) flips the model on its head. Instead of asking “What are the steps of change?” it asks “What do people need to change their behavior?” It’s individual, psychological, and it’s now the dominant measurement framework in change management.

Strengths: Focuses on actual behavior change. Diagnostic precision. Built for technology adoption. Measurement clarity with over 40% of change practitioners using ADKAR as their primary measurement framework.

Weaknesses: Micro-focus misses the macro shifts. Assumes rationality. Heavy lift on sponsorship. This framework requires relentless reinforcement.

Best cultural fit: Tech companies. Learning-focused organizations. Any org managing large-scale digital adoption.

Lewin’s 3-Stage Model: The Classics for a Reason

What it is: Kurt Lewin’s model is elegantly simple. Unfreeze, Change, Refreeze. It’s the granddaddy of modern change management, and it’s still useful for discrete, bounded changes.

Strengths: Crystal clear. Useful for discrete transitions. Acknowledges inertia. Low overhead.

Weaknesses: Too simple for modern complexity. Organizations are in continuous change now. Underestimates culture. Doesn’t differentiate resistance sources.

Best cultural fit: Manufacturing. Process changes. Legacy industries where change is episodic, not continuous.

Bridges’ Transition Model: For When Emotion Matters

What it is: William Bridges distinguished between change (the external event) and transition (the internal psychological process). His model tracks Ending, Neutral Zone, Beginning, acknowledging that people need time to grieve the old before embracing the new.

Strengths: Names the emotional reality. Explains the productivity dip. Useful for high-stakes transitions like reorgs, layoffs, role changes.

Weaknesses: Descriptive, not prescriptive. Assumes slow, reflective culture. Needs pairing with another framework for structure.

Best cultural fit: Purpose-driven organizations. Nonprofits. Companies going through existential shifts.

McKinsey’s 7-S Framework: The Systems Approach

What it is: McKinsey’s classic diagnostic tool treats an organization as an integrated system. Structure, Strategy, Systems, Skills, Staff, Style, Shared Values. Change one, and you have to adjust the others. Shared Values sit at the center.

Strengths: Systems thinking. Catches hidden blockers. Shared Values at the center. Useful for complex, interconnected changes.

Weaknesses: Diagnostic, not prescriptive. Requires systems thinking sophistication. Slow.

Best cultural fit: Consulting firms, tech strategy teams, organizations doing M&A or major strategy shifts.

Here’s What Actually Happens in Real Organizations

60% of organizations now use hybrid approaches. They’re not picking one framework and running with it. They’re mixing and matching.

I watched a healthcare system use Lewin for the discrete switch to a new EHR system, but then layered ADKAR on top for the behavioral changes. They used Bridges’ language to acknowledge the grief around old workflows. And they used McKinsey’s 7-S to audit whether their staffing model, incentive systems, and training infrastructure could support the new clinical reality.

That’s the real skill: diagnosis, not dogma.

How to Choose the Right Model for Your Change

Stop asking “Which framework is best?” Start asking “Which framework fits our culture?”

Question 1: How hierarchical is your organization? Highly hierarchical? Kotter is your baseline. Flat or matrix? You’ll need Bridges and McKinsey 7-S.

Question 2: Is this change discrete or continuous? Discrete? Lewin gives you the mental model. ADKAR gives you the measurement. Continuous? You need McKinsey 7-S thinking and Bridges.

Question 3: How change-savvy is your leadership team? Very experienced? McKinsey 7-S. Newer to change leadership? Kotter.

Question 4: What’s your organization’s relationship with emotion? Values emotional intelligence? Bridges isn’t optional. Moves fast? Bridges is still there but you won’t dwell.

Question 5: What’s your change magnitude? Single system? Lewin + ADKAR. Multi-system? McKinsey 7-S plus another. Existential? All of them.

The Model Isn’t the Problem. The Fit Is.

I worked with a manufacturing plant manager who tried to run a major process redesign using pure McKinsey 7-S. Beautiful diagnosis. Useless implementation. His people wanted Kotter. Different culture, wrong model.

I worked with a fintech startup that hired a traditional change consultant who wanted to run Lewin. They were doing continuous product evolution. Lewin’s “refreeze” felt like death.

The frameworks aren’t wrong. The matching is where most organizations fail.

  1. Audit your culture. Not with surveys. With observation. How do decisions get made? Who has voice?
  2. Audit your change. Is it discrete or continuous? Strategic or operational? What’s the emotional weight?
  3. Match consciously. Pick your primary model, then ask what the other frameworks teach you.
  4. Adapt ruthlessly. The framework is your thinking tool, not your religion.
  5. Communicate the logic. Tell your team why you chose this approach. That transparency builds trust.

The Closing Challenge

Stop looking for the perfect framework. There isn’t one. What there is is a perfect framework for your culture.

Pick one change initiative you’re running right now. Walk through those five questions. Be honest about your culture. Then pick the framework or combination that actually fits.

Not because it’s trendy. Not because a consultant sold you on it. Because it fits how your people actually work.

That’s the difference between change management that looks good on a slide deck and change management that actually sticks.

What Is Organisational Culture? u2014 A Practical Guide for Leaders

Organisational culture is not soft. It’s not vague. And it’s not something you can afford to ignore.

Yet most leaders treat it like it is.

I’ve spent the better part of two decades advising senior teams on culture change, and I can tell you what I’ve seen: leaders who understand organisational culture as a strategic asset move faster, retain talent better, and adapt more effectively to change. Those who don’t? They end up fighting fires, losing good people, and scratching their heads wondering why their strategy isn’t landing.

The problem isn’t that organisational culture is hard to define. It’s that too many leaders dismiss it as “the way we do things” and call it a day. That’s like saying your computer’s operating system is just “the stuff that makes it work.” True, but useless.

So let’s be direct: organisational culture is your business operating system. It’s the invisible architecture that shapes every decision, interaction, and outcome in your organisation. Get it right, and it multiplies your strategy. Get it wrong, and it destroys it—no matter how brilliant your strategy is.

Why Organisational Culture Actually Matters

Here’s a question I ask every leadership team I work with: How much of your strategy fails because of culture, not because the strategy itself was wrong?

Most leaders pause. They’ve felt it. They’ve watched brilliant initiatives flatline. They’ve seen talented executives leave because “the culture wasn’t right.” They’ve observed teams saying yes to change while actually resisting it.

That’s culture at work.

Organisational culture is the filter through which every message, every initiative, and every decision gets interpreted. It’s what determines whether your people will innovate or protect their turf. Whether they’ll speak up or go silent. Whether they’ll see setbacks as learning opportunities or career threats.

In my experience, this is where the gap between intention and reality lives. A leader announces a new strategy on a Monday. By Friday, it’s been interpreted through the lens of existing culture, repackaged, and sometimes reversed. The same words mean entirely different things depending on what your culture says about change, trust, and accountability.

That’s not a communication problem. That’s a culture problem.

The Three Components of Organisational Culture

When we’re talking about organisational culture, we’re really talking about three overlapping systems:

Values and beliefs. These are the stated and unstated principles that guide behaviour. What does your organisation truly value? Not what the mission statement says—what does your hiring, promotion, and discipline actually reward? In my experience, that gap between espoused values and enacted values is where most culture problems hide.

Behaviour and norms. This is what people actually do, day to day. How do people communicate? Who speaks in meetings, and who stays silent? How are conflicts handled? What happens when someone challenges the status quo? The norms are the unwritten rules. And they’re powerful.

Systems and structures. These are the formal mechanisms—how you hire, how you develop people, how you measure success, who has authority, how decisions get made. Culture lives in these structures. You can’t separate them.

Most organisations try to fix culture by changing the espoused values—new mission statements, new posters on the wall. But if you don’t change the behaviour and the systems, nothing shifts. You just get a shiny new lie.

There are many examples of this that you may be familiar with. You may have experience working with or being a customer of one of these organisations. Creating values that are something people aspire to and actively work toward is one thing. Creating espoused values and throwing them up on the wall because you think that is what people expect you to do, without putting in the work to move toward them, doesn’t fool anyone.

What Shapes Organisational Culture?

Organisational culture isn’t magic. It’s built, deliberately or by default.

It starts at the top. Not because senior leaders need to be perfect, but because they set the tone. What gets rewarded? What gets called out? How do they talk about failure? How do they treat people who disagree with them? That’s the culture blueprint right there.

It gets reinforced through hiring. You can say you value collaboration, but if you hire individual contributors who hoard information, your culture will reward information hoarding. Hiring is where culture either strengthens or weakens.

It gets embedded in daily processes. How long does it take to make a decision? Who needs to sign off? What happens when someone admits a mistake? These routines become invisible. And they shape behaviour.

It persists through storytelling. Every organisation has stories about heroes and cautionary tales. What stories do people tell about your organisation? Are they stories about courage, or stories about politics? In my experience, the stories people tell about their workplace are the most honest measure of culture you’ll find.

The Cost of Getting Organisational Culture Wrong

I’ll be blunt: weak organisational culture costs you money.

It costs you in turnover. Good people leave bad cultures. They might not say that in their exit interview, but it’s the primary reason. According to SHRM research, workers in positive organisational cultures are almost four times more likely to stay with their current employer. Among employees who rate their culture poorly, 57% are actively looking for the exit. And 67% of employees cite organisational culture as a primary reason for their decision to stay or leave.

It costs you in productivity. When people are focused on office politics instead of delivering value, your organisation slows down. Gallup research shows that organisations with high numbers of disengaged employees—a direct symptom of weak culture—have 18% lower productivity and 15% lower profitability. Conversely, organisations with strong cultures see up to 72% higher employee engagement and 21% greater profitability.

It costs you in execution. Strategy without culture is just wishful thinking. In reality, even the most sound strategy is set up to struggle or fail if the culture does not support and reinforce the behaviours required to execute on it. Plain and simple—yet a mistake that business leaders make and remake all the time.

And it costs you in recruitment. In a tight talent market, word gets out. If your organisational culture is toxic, you won’t attract good people. You’ll end up hiring whoever will take the job, and that compounds the culture problem.

How to Intentionally Shape Your Organisational Culture

So what do you do if you’ve diagnosed a culture problem?

First, be honest about what your culture actually is, not what you want it to be. That means looking at your data: Who stays? Who leaves? What gets rewarded? What gets punished? What stories do people tell? Get brutally clear on the gap between your espoused culture and your actual organisational culture.

Second, start with behaviour, not values. Pick one or two specific behaviours you want to shift. Not “be more collaborative.” More specific: “Before you escalate a conflict, you’ll have a one-on-one conversation.” That’s specific. That’s measurable. That changes organisational culture because it changes what people actually do.

Third, align your systems. If you want your organisational culture to reward innovation, don’t measure people solely on short-term delivery. If you want accountability, don’t hide failures. Make sure your hiring, evaluation, and promotion systems reinforce the culture you’re building.

Fourth, model it relentlessly. You can’t ask for a culture you don’t embody. Leaders set the tone. If you want trust in your organisation, be trustworthy. If you want candour, be candid. Your team watches you more closely than any communication strategy can reach.

The Payoff

Organisations with strong, intentional organisational culture outperform those without it. They move faster. They retain talent longer. They innovate more effectively. They adapt better when conditions change. The research backs this up: Kotter and Heskett’s landmark study of over 200 companies across 22 industries found that organisations with adaptive, performance-oriented cultures dramatically outperformed those without—in revenue growth, stock price, and net income—over an 11-year period.

Why? Because everyone’s pulling in the same direction. Not because they’re forced to, but because the culture makes it clear what matters, how to behave, and how decisions get made.

The reverse is also true. Weak organisational culture is a silent tax on everything you’re trying to build.

So here’s my challenge: Stop treating organisational culture as something that happens to you. Stop waiting for a team offsite to “fix it.” Stop hoping that a new set of values will change behaviour.

Instead, ask yourself: What’s one specific behaviour I want to shift in my organisational culture? Not a value. A behaviour. And what system am I going to change to make that behaviour the easier choice?

That’s how you build organisational culture that actually works. Not through speeches or posters. Through clear intention, aligned systems, and relentless modelling.

The question isn’t whether your organisational culture exists. It does. The question is whether you’re going to shape it, or let it shape you.

New Leader Assimilation: Your Questions Answered

If you’re in HR or talent leadership, you’ve probably watched a new executive struggle through their first six months—or worse, fail outright. And you may have wondered whether there was something you could have done differently.

There was. It’s called new leader assimilation, and it’s one of the most underused, highest-leverage practices in leadership development.

Here are the questions I hear most often—and what I’ve learned from running these processes with hundreds of leaders.

What is new leader assimilation?

New leader assimilation is a structured process that accelerates the integration of a new leader into their team, their role, and the organisation’s culture. It creates a deliberate space—typically in the first 30–90 days—for the leader and their team to exchange information, surface expectations, and build working relationships before the normal pressures of the job take over.

It’s not orientation. It’s not onboarding. Those are primarily about logistics and information. Assimilation is about relationship and alignment.

For a full breakdown of the distinction, see: What Is New Leader Assimilation? — which includes a downloadable resource you can share with your HR team.

Why do new leaders fail?

The data is sobering: research from the Center for Creative Leadership found that roughly 40% of new leaders fail within 18 months. A separate Leadership IQ study tracking over 20,000 new hires put the number even higher—46% failing within 18 months.

And the reasons might surprise you. It’s rarely about competence or technical skill. The failures are almost always relational: misreading the culture, moving too fast, not building trust with the team, or making assumptions about how decisions get made.

The new leader comes in confident. The team is cautious. Neither side has a reliable way to close that gap quickly. And by the time the misalignment is obvious, it’s expensive to fix.

What’s the difference between onboarding and assimilation?

Onboarding gets the leader set up: systems access, introductions, org chart, HR paperwork. It answers the question, “What do I need to know to function?”

Assimilation answers a different question: “How do I build the trust and clarity I need to lead effectively?”

Most organisations do onboarding reasonably well. Almost none do assimilation. The result is a new leader who knows where the bathrooms are but doesn’t understand the unwritten rules of the culture, the team’s concerns, or the political landscape—and has no structured way to learn them quickly.

When should assimilation happen?

Ideally, within the first 30–60 days. Early enough that patterns haven’t hardened. Late enough that the leader has had time to observe and form initial impressions.

The most common mistake is waiting too long. Leaders feel pressure to prove themselves fast, so they start making decisions and building momentum before they’ve built trust. By the time they realise the team isn’t with them, they’re already defending their choices instead of building relationships.

A secondary window exists at 90 days—useful for leaders who weren’t introduced to the process earlier, or those navigating a significant transition (new team, new scope, merger integration).

Who facilitates a new leader assimilation session?

Not the leader. And not their manager.

The process requires a neutral third party—typically an internal OD practitioner, executive coach, or external consultant—who can create psychological safety for the team to speak candidly. The facilitator meets with the team separately before the joint session, surfacing questions and concerns in a confidential context, then helps the leader and team have the conversation that matters.

When the leader’s manager facilitates, the team filters everything. When the leader facilitates themselves, it defeats the purpose entirely. The facilitator’s independence is what makes the exchange honest.

What happens in a new leader assimilation session?

A typical session has three phases.

Before the session: The facilitator meets separately with the leader and the team. The team surfaces their questions, concerns, and what they most want the leader to know. The leader reflects on what they want to learn and what they’re willing to be transparent about.

The joint session: Usually 2–4 hours. The facilitator structures a dialogue where the team’s questions are addressed, the leader shares their working style and priorities, and both sides agree on ways of working. It’s direct in a way that almost never happens organically.

After the session: The leader sends a follow-up communication summarising what they heard and any commitments they made. This closes the loop and signals that the conversation was taken seriously.

What questions does the team typically raise?

In my experience, they fall into three categories: style, priorities, and trust.

On style: How do you prefer to communicate? How involved do you want to be in decisions? What do you do when you’re under pressure? These sound simple, but the team is really asking: “Will working with you be safe and predictable?”

On priorities: What’s most important to you right now? What does success look like in 90 days? These surface alignment—or misalignment—early.

On trust: What’s your track record with teams like ours? How do you handle mistakes? What do you expect from us? These are the questions that build or erode the foundation of the relationship.

What results should we expect?

Faster time to productivity. Research from Harvard Business Review suggests new leaders typically take 6–9 months to reach full effectiveness when left to their own devices. With structured assimilation, we see that compressed to 3–4 months. That’s a meaningful difference in project delivery, team performance, and organisational impact.

Higher retention. As noted above, external executive hires fail at 40–46% within 18 months—most because of cultural misfit or early political missteps, not incompetence. Organisations that run structured assimilation processes see that failure rate drop dramatically. People stay because they understand the organisation and feel integrated into it.

Stronger team performance. When a new leader and their team have a shared understanding of expectations, working style, and priorities from day one, the team can focus on work instead of second-guessing. That’s not a small thing.

How do we know if it worked?

A few indicators I watch for:

The leader can articulate what the team was worried about before the session—and address those concerns directly in their first 90 days. If they can’t, the session didn’t stick.

The team’s communication with the leader increases. People start flagging problems earlier and seeking input more often. That’s trust being built in real time.

The leader makes fewer unilateral course-corrections in month two. Early assimilation tends to front-load the “getting to know you” awkwardness, so the leader can move faster, not slower, once the process is complete.

And the simplest check: ask the team at 90 days whether they feel the new leader understands how to work with them. If the answer is yes, the investment paid off.


Ready to accelerate your new leader’s success?

Download our free guide to the new leader assimilation process, or learn more about our leadership transition services. Your next hire’s first 90 days matter more than you think.

Organizational Change Management: A Culture-Driven Approach for Leaders

Organizational change management process with leaders guiding teams through transition

Two-thirds of organizational change initiatives fail. Most leaders blame strategy, timelines, or bad tech. They’re wrong. The real culprit is culture.

I’ve watched this play out across industries for years. A company invests millions in a digital transformation. They hire consultants, build project timelines, and communicate the vision from the C-suite. Six months in, adoption stalls. Employees revert to old workflows. The change just… dies. And everyone ends up blaming the resistance of people instead of looking at what was actually broken.

Here’s what I’ve learned: organizational change management advice obsesses over process models and implementation timelines. But the real lever—the one that determines whether your change initiative actually sticks—is culture.

This isn’t soft philosophy. It’s backed by data. And once you understand how culture actually works in the context of change, you can stop fighting your organization and start channeling it.

Why Most Change Initiatives Actually Fail

The numbers are stark. Base-case success rate? 32%. When change management is done right? 88% (Prosci, 2023). That’s a 6.7x difference. Not an improvement. A transformation.

So what separates the winners from the 68% of failed initiatives?

When researchers dig into the failures, the culprits are almost always cultural:

33% of transformations fail due to inadequate management support. (McKinsey, 2023)
39% fail due to employee resistance. (McKinsey, 2023)

Both are cultural. Both prove that people behave based on what actually gets rewarded, not what the org chart says they should do.

One analysis across multiple industries found that 75% of popular change approaches fail because they neglect the human element entirely. (American Journal of Social and Humanitarian Research, 2022) Organizations roll out Six Sigma. They implement new software platforms. They restructure reporting lines. But they treat people as a problem to manage instead of a foundation to build on.

And here’s the kicker: only 25% of organizations report that their senior leadership excels at managing change. (Gartner, 2024) Which means the people who are supposed to champion these initiatives are often the least equipped to do it.

The Frameworks Everyone Knows (and What They’re Missing)

You’ve heard them all: Kotter, ADKAR, Lewin, Bridges, McKinsey’s 7-S. They work. But they all make the same mistake—they mention culture, then bury it.

Kotter’s model has “shaping corporate culture” as Step 8. That’s the final phase. By that point, you’ve already made most of your decisions. You’ve already designed your change, communicated it, and started the rollout. Culture becomes a checkbox, something to “consolidate and drive change home,” not the foundation everything’s built on.

This is backwards.

The best organizations I’ve worked with don’t use just one framework. They integrate multiple models, adapting them to their specific context. There’s no single change management strategy that works for every organization. But they all start with the same question: What is our culture right now, and is it aligned with where we’re trying to go?

For a deeper look at how different frameworks compare and where they’re best applied, see Change Management Models Compared.

“Culture Eats Strategy for Breakfast”—The Real Story

Everyone attributes this quote to Peter Drucker. It sounds like something he’d say. It has that Drucker gravitas.

The truth? Drucker never said it. The Drucker Institute has no record of it. It’s folklore. And the fact that it’s folklore is actually the most interesting part.

The quote actually comes from Mark Fields, Ford’s President of the Americas, speaking in 2006 about Ford’s transformation efforts. He said: “You can have the best plan in the world, and if the culture isn’t going to let it happen, it’s going to die on the vine.” (Ford, 2006)

What’s telling is that this insight resonated so powerfully across industries that executives everywhere independently recognized themselves in it. CEOs at tech companies, manufacturing firms, financial institutions—they all looked at their own strategic initiatives and thought, “Yeah, that’s exactly what happened to us.”

The data backs this up. 78% of Fortune 1000 CEOs identify culture as a top-3 performance factor. (Gartner, 2024) And research from Harvard Business Review found that cultural alignment accounts for nearly half the variance in successful strategy execution. (Harvard Business Review, 2019)

Take Nokia. Here’s a company that had the engineers, the resources, and actually invented many of the core technologies that powered the smartphone revolution. They understood where the market was going. But their culture rewarded incremental improvement and punished dissent. Risk-taking was career-limiting. Hierarchy mattered more than the quality of the idea. So when the iPhone showed up, Nokia’s brilliant engineers were trapped inside a culture that wouldn’t let them win. Culture didn’t just eat strategy. It quietly starved it.

The AI Adoption Proof Point

Here’s a live experiment happening right now in thousands of organizations.

78% of companies use AI in at least one function. (McKinsey, 2025) That’s adoption at scale. But here’s the gap: only 1% describe themselves as “mature” in their AI implementation. (McKinsey, 2025)

Why such a massive disparity?

Because only 28% of employees know how to use their company’s AI tools. (Gartner, 2024) And 74% of companies struggle to achieve and scale AI value. (McKinsey, 2025)

The technology works. The business case is clear. But the change isn’t sticking because the culture isn’t prepared for it.

Every successful AI implementation is a change management challenge, not just a technology deployment. You’re asking people to change how they work. You’re asking managers to trust that an AI tool can augment their team’s capability instead of threatening their authority. You’re asking risk-averse organizations to experiment with new tools when failure might be visible and costly.

That’s not a software problem. It’s a cultural problem.

What Culture-First Change Management Actually Looks Like

So if culture is the real lever, what does that mean in practice? How do you actually do this?

Start With Diagnosis, Not Deployment

Most organizations approach change like this: leadership makes a decision, hires a consultant, and launches a program. The culture is an afterthought.

Culture-first change management inverts this. Before you design your initiative, you need to understand your actual culture—not the one you think you have or the one you want, but the one that actually exists right now. What are the unwritten rules? Who gets rewarded, and for what? That’s your real culture. Everything else is just the org chart.

This diagnosis takes time. It requires honest conversations. But it’s the difference between designing change that works with your culture and designing change that ignores it.

Leadership Alignment Comes First

I’ve never seen a change initiative succeed when senior leadership was divided on it.

You can have the most elegant change strategy in the world, but if the COO doesn’t believe in it while the CEO is pushing it hard, everyone watches and waits to see who wins. The default behavior is inertia. Resistance becomes rational because people know the initiative might not last.

Before you communicate change to the broader organization, leadership needs to be genuinely aligned—not just aligned on the messaging, but aligned on the direction. And that alignment needs to be visible. People need to see leaders modeling the change before they’re asked to adopt it themselves.

Build Psychological Safety First

People won’t experiment if they’re afraid to fail. I’ve watched organizations with brilliant change ideas stall because the first failure cost someone their credibility.

Psychological safety isn’t abstract—it’s leaders saying “I don’t know” out loud and celebrating the failures that teach you something. If your organization punishes mistakes, you’ll get compliance. You won’t get the innovation that makes change stick. It’s uncomfortable. And it’s non-negotiable.

Involve Employees in the Design

Here’s what I’ve seen destroy change initiatives: leadership designs the change in isolation, then tries to convince people to adopt it.

Here’s what I’ve seen make change stick: leadership sets the direction, then brings employees into the design of how you get there.

The difference is ownership. Compliance is something you do because you have to. Ownership is something you do because you helped create it and you believe in it.

This doesn’t mean design by committee. It means identifying key voices across the organization—frontline employees, managers, skeptics—and genuinely incorporating their input into how the change gets implemented.

Measure Culture Alongside Business Metrics

Most organizations measure adoption: Did people take the training? Are they using the new system? Did we hit the KPI?

But adoption and impact are different things. You can hit your adoption numbers and still have a change that didn’t actually transform how the organization works.

Measure culture directly. Are people more psychologically safe after the change? Has collaboration improved? Are silos breaking down? Are people innovating more or just following the new playbook?

These metrics are harder to track than adoption rates. But they tell you whether the change actually stuck or just became another rule people follow while doing things the old way behind closed doors.

For guidance on designing metrics and tracking cultural change, see Measuring Organizational Change.

The Integration Point: Building Your Change Strategy

Kotter’s brilliant at creating urgency. ADKAR nails the individual transition. Bridges gets the emotional reality. McKinsey’s 7-S gives structural clarity. Most organizations treat them like competing models. That’s the mistake. Integrate them around a cultural foundation:

  1. Diagnose your current culture (foundation)
  2. Assess which frameworks align with your org’s needs (integration)
  3. Design change with cultural dynamics in mind (application)
  4. Communicate in ways that respect your culture (activation)
  5. Measure culture as your success indicator (accountability)

This approach respects the rigor of established frameworks while centering the human reality that makes or breaks change.

The Responsibility Is on Leadership

Here’s the hard part: none of this works if leaders don’t own it.

Culture doesn’t eat strategy for breakfast by accident. It happens when leaders hand culture off to HR or the change management office. That’s the abdication right there. Culture is a leadership responsibility.

Which means you have to look at your actual culture—not the values statement, the real one. You have to model the change yourself. You have to stay committed past the point where it’s comfortable. Change doesn’t stick in a quarter. It sticks when people see leadership is still prioritizing it two years in. And you have to tolerate the chaos of transition—things feeling slower, less efficient, more messy. That’s not failure. That’s what change looks like in the middle.

The Organizations Getting This Right

The companies I’ve seen successfully navigate significant organizational change share one thing: they looked at their culture honestly before they started.

They didn’t assume “we’ll just communicate better.” They asked what communication styles actually worked in their environment. They didn’t assume “resistance is natural.” They asked why people were resisting and what fears drove that resistance. They didn’t assume “adoption = success.” They asked what success actually meant and how they’d know when they got there.

These organizations are rarely the ones with the flashiest change management frameworks or the biggest budgets. They’re the ones willing to do the harder work of cultural diagnosis and integration before they start the more visible work of transformation.

The Challenge

Here’s my direct ask: What have you actually done to understand your organizational culture?

Not the culture you want. Not the culture your mission statement describes. The real, lived culture—the one that determines what actually gets done and why.

Because when you’re facing the next organizational change, the next transformation, the next initiative that requires people to work differently, your success won’t be determined by how well-designed your change management plan is.

It’ll be determined by how deeply you understand the culture you’re trying to evolve and how intentionally you integrate that understanding into every decision you make.

That’s organizational change management. That’s what actually works.

Dive Deeper

Explore related articles in the Change Management & Culture cluster: