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: