Inheriting a Transformation Is Not the Same as Owning It

Most onboarding plans for a new executive assume the organization was waiting for them to arrive. It wasn’t. A transformation was already moving: its own priorities, its own momentum, its own history of what happened the last time leadership changed. The new executive isn’t stepping into a blank page. They’re stepping into a sentence that’s already halfway written.

Onboarding advice usually gets the first layer right: build relationships, learn the culture, earn trust. That groundwork has to happen. What often gets skipped is the layer underneath it, an explicit call about what happens to the transformation that was already running when the new leader walked in. A new executive who never makes that call hasn’t inherited the transformation. They’ve inherited the paperwork. That’s not the same as owning it. 

A few patterns repeat across transitions like this, and they apply as much to the team preparing the transition as to the executive stepping into it. 

The Org Wasn’t Standing Still

A transformation already in motion carries its own facts: projects that are half-funded, teams that already committed to a roadmap, a prior leader’s promises people are still measuring the new one against. None of that pauses for a transition. It keeps moving, with or without an explicit decision about what to do with it.

Most new executives find this out by accident, weeks in, when someone references a commitment nobody briefed them on. By then the organization has already drawn its own conclusions about how much the new leader knows and how much they’re pretending to.

Continuity Doesn’t Happen by Default

New leaders, and the teams preparing their transition, tend to handle an existing transformation one of two ways without ever saying so out loud. They defer to it, treating the prior plan as untouchable because touching it this early feels disrespectful. Or they quietly rewrite it, treating a fresh start as proof the new leader is in charge. Both are avoidance dressed up as instinct, and both cost the organization the same thing: nobody ever heard the new leader actually decide what carries forward and what doesn’t.

We saw the alternative work at a Fortune 500 utility company, where a newly appointed executive inherited a customer experience effort with no enterprise-wide view of what was already in flight. Before changing a single project, the team built the first enterprise-wide inventory of the 200-plus initiatives already underway, giving the new leader something specific to decide against instead of a guess.

Silence Reads as a Signal

A new executive who says nothing about the existing transformation is still communicating something. Teams read silence as one of two things: the plan is safe, or the plan is already dead. Neither is usually true, and both spread faster than any actual announcement would.

The same read happens with culture, which already carries a verdict on how the last change effort landed long before a new leader says a word about it. Walking in without asking what that verdict is means inheriting it anyway, just without knowing what it is.

The Sequence Is the Safeguard

A 30-60-90 day plan works when it’s the second decision, not the first. Draft the plan before deciding what carries forward from the existing transformation, and the plan just gives the deferred decision a calendar to hide behind.

The good version of this gets the order right on purpose: the transformation vision gets revisited before the 30-60-90 plan gets drafted, not after. That sequence is doing real work. It’s the difference between a plan that reflects a decision already made and one that’s substituting activity for a decision nobody wanted to make.

The same dynamic shows up on a smaller scale, in Lexico’s data readiness work with a $3B convenience store chain, done in direct partnership with the company’s newly arrived CIO.

What the First 30 Days Are Actually For

The first 30 days were never really about winning trust or learning the org chart, useful as both are. They’re the window where a new executive either makes an explicit call about what the transformation keeps and what it drops, or lets that call get made by default: through silence, through a plan drafted too early, through inaction. Whichever way it goes, the organization notices. It always does. Only one of those paths ends with the executive actually owning what they inherited.

The Structure Comes After the Decision

The Playbook for Onboarding an Executive is built around that same order. It lays out the day-by-day shape of a 30-day onboarding window: the early handoff, a full situational assessment, then a vision draft. The plan itself doesn’t get built until after that vision is set, not before. It also walks through five supporting tools, a readiness checklist, a stakeholder mapping approach, a SWOT assessment, a 30-60-90 day framework, and a short pulse survey.                                   

None of it replaces the call about what carries forward and what doesn’t. It’s built, in the order it’s built, for the leader who’s already made that call and needs the structure to execute it well.