You step into a bigger role on a Monday. Within a few weeks, before you have done anything that truly counts, the people around you have already decided what kind of leader you are. That early verdict is sticky, it is formed on thin evidence, and it shapes how much rope you get for the rest of your tenure. The work of a transition is to spend that window deliberately rather than let it spend you.

The quick version

  • A leadership transition is the move into a new role, a promotion, a new team, a new company. The first months are when you are most vulnerable and most watched, and they predict how the whole tenure goes.
  • The goal is to reach the break-even point faster: the moment you contribute as much value as you consume. A structured approach gets you there sooner than winging it.
  • Stepping up is not just doing more of what you did before. Each level asks you to value different work, and the skills that got you promoted are often the ones now holding you back.
  • The trap is rushing to prove yourself with action before you have learned enough to act well. Diagnose the situation first; match your strategy to it.

The idea in depth: the break-even point

The most useful single concept in transitions comes from Michael Watkins, whose book The First 90 Days (Harvard Business Review Press, 2003; updated 2013) is the standard text on the subject. Watkins frames every new role around a break-even point: at first you are a net consumer of value, people orient you, cover your gaps, answer your questions, and only later do you put in more than you take out. The break-even point is where those lines cross, and the purpose of a deliberate transition is to bring that crossover forward.

This matters because the cost of getting it wrong is not theoretical. IMD research summarised in Watkins' article "Hit the ground running" surveyed 1,350 HR professionals, who reported that transitions are the most difficult times in a leader's professional life, and 57% of executives said it took them six months or more to fully take charge of their last role. Separately, the Center for Creative Leadership's long-running work on derailment, leaders who were succeeding and then stalled, found a recurring culprit: an inability to adapt to the new situation (Lombardo & McCauley, "The Dynamics of Management Derailment," CCL, 1988). The pattern holds across decades and continents: the people who struggle are rarely short on talent. They are short on adaptation.

Practically, that means treating your first weeks as a learning sprint, not a doing sprint. Resist the pull to act early just to look decisive. Build a deliberate learning plan, who you will talk to, what you need to understand about the business, the team, the politics, and give it real calendar time before you start changing things. Early action on a shallow diagnosis is how confident leaders walk fast in the wrong direction.

Match your strategy to the situation (STARS)

"Hit the ground running" is bad advice if you do not yet know which ground you are on. A turnaround and a healthy team that just needs steady hands demand almost opposite behaviour, and Watkins' second contribution is a way to tell them apart. In his Harvard Business Review article "Picking the Right Transition Strategy" (January 2009), he sets out the STARS framework, five situations a new leader can inherit:

flowchart TD
  Q(["What situation
have you inherited?"]) --> S(["Start-up
build from nothing"])
  Q --> T(["Turnaround
fix what's failing, fast"])
  Q --> A(["Accelerated growth
scale what works"])
  Q --> R(["Realignment
renew before it's too late"])
  Q --> X(["Sustaining success
protect a healthy unit"])
  T --> H(["Act fast, heroic,
directive"])
  R --> D(["Act slow, build
consensus, persuade"])
The five STARS situations, and why a turnaround and a realignment call for nearly opposite styles. Leaders Loop

The two trickiest to distinguish are turnaround and realignment, and confusing them is a classic transition error. In a turnaround the unit is visibly failing, everyone knows it, and people are hungry for direction, so a fast, decisive, even heroic style fits. In a realignment the unit looks fine but is drifting toward trouble, and nobody yet agrees there is a problem, so charging in with bold moves reads as reckless. Realignments call for the patient work of building consensus that change is needed before you make it. Same energy, opposite situation, opposite move.

An honest limitation. STARS is a sorting lens, not a measurement, and real roles are rarely a clean single letter, you might inherit a thriving product line bolted onto a failing support function. Watkins' framework is widely taught and intuitively strong, but it rests on practitioner experience and case observation rather than controlled trials, so treat it as a structured way to ask "what does this situation reward?", not as a law that guarantees the right answer.

Stepping up means changing what you value

Most transition advice assumes you are doing a bigger version of the same job. Often you are not, you are doing a different job that happens to share your old title's neighbourhood. The clearest account of this is the Leadership Pipeline model from Ram Charan, Stephen Drotter and James Noel, set out in The Leadership Pipeline (Jossey-Bass, 2000; revised 2011). They describe leadership as a series of passages, and argue the hardest is often the very first: managing self to managing others.

It is hard because it is not a skills upgrade, it is a values shift. The new manager, promoted for being the best individual contributor, is now paid to get work done through others, so their old source of pride (doing the work brilliantly themselves) has to give way to a new one (developing others). Many never make that switch. They keep doing the technical work they love, treat managing as an interruption, and quietly starve their team of attention. The title changed; the values did not follow.

The skills that earned you the promotion are usually the ones you now have to stop relying on.

The fix is uncomfortable: name, out loud, what you are letting go of. Write down the two or three activities that made you successful in your last role but are no longer your job, the code you should stop writing, the deals you should stop closing yourself, the analysis you should now delegate. Then watch where your week actually goes. If you are still spending it on the old work, you have taken the new title without taking the new role, and your team will feel the gap before you do.

A worked example

Take Priya, newly promoted to lead the team she was a senior member of last week. (Illustrative figures throughout; this is a teaching example, not a real person.) Her instinct is to reassure everyone that nothing will change and to keep shipping the technical work she is known for, partly because it is what she is good at, and partly because it feels safer than the unfamiliar work of leading former peers.

Run her first 90 days through the toolkit above and a different plan appears. First, diagnosis: which STARS situation is this? The team is healthy and well-regarded, a sustaining-success or mild realignment case, not a turnaround. That alone tells Priya to slow down: no dramatic reorganisation in week two, no flag-planting. Her risk is not inaction; it is over-correcting to look like a leader.

flowchart LR
  W1(["Weeks 1–4
Learn: 1:1s, listen,
diagnose the situation"]) --> W2(["Weeks 4–8
Secure one early win
the team already wanted"])
  W2 --> W3(["Weeks 8–12
Set direction;
delegate the old craft"])
  W1 -.->|"the trap"| TR(["Act fast to look
decisive → break-even
arrives later, not sooner"])
A learning-first 90 days brings the break-even point forward; rushing to prove yourself pushes it back. Leaders Loop

Second, the pipeline shift: Priya lists the three things she must stop doing herself, owning the trickiest tickets, writing the weekly client update, being the final reviewer on every release, and hands each to a named person, framing it as their growth, not her offloading. Third, an early win without overreaching: the team has griped for a year about a clunky on-call rota, so she fixes it in week six. Small, visible, and theirs, a win that says "she listens" rather than "she's here to shake things up." By the end of 90 days Priya has spent perhaps 70% of her time learning and enabling and 30% doing, close to the inverse of her old ratio, and her team's early verdict, formed on thin evidence in those first weeks, has set in her favour. That verdict is the asset the whole tenure draws on.

Frequently asked questions

Is it really 90 days, or is that just a catchy number?

Ninety days is a useful focusing device, not a deadline with a cliff at the end. Watkins chose it because a quarter is long enough to learn and secure an early win, but short enough to create urgency. The IMD survey is a healthy corrective: most executives say genuinely taking charge took six months or more. Treat 90 days as the window to earn trust and set direction, not the moment you are expected to have everything solved.

I was promoted from within. Isn't a transition easier when I already know the place?

It is different, not easier. You skip the orientation, but you carry baggage the outsider doesn't: relationships that now have to be renegotiated, former peers adjusting to you as their boss, and an assumption (yours and theirs) that nothing fundamental has changed. The pipeline shift, from doing the work to leading it, is often harder for insiders, precisely because the old role is still right there, comfortable and within reach.

What is the single most common transition mistake?

Acting before learning. The pressure to look decisive pushes new leaders to make visible changes on a shallow understanding of the situation, the team and the politics. It is the behaviour the Center for Creative Leadership's derailment research keeps surfacing: an inability to adapt to the new context. A diagnosis you can defend beats a bold move you can't.

How do I get an early win without overreaching?

Look for the problem the team already wants fixed but no one has owned, a broken process, a tool everyone complains about, a decision stuck in limbo. Fixing something the team chose signals that you listen and can execute, without the risk of a flashy initiative that you'll have to defend before you understand it. Early wins build the credibility you'll spend later; pick ones that are visible, achievable, and theirs.

How much of my old job should I still be doing?

Less than feels comfortable. The pipeline model's whole point is that each level revalues your time toward enabling others. A useful test: if your week still looks like your predecessor-self's week, you have taken the title without taking the role. Name the two or three things you must stop doing personally, delegate them deliberately, and protect the time that frees up for leading.

Related in the Toolkit

A transition is the moment self-leadership stops being abstract, it leans hard on knowing your own strengths and development edges (so you can tell which old habits to drop), and on guarding your time, energy and attention while the demands spike.

Where to go next