Your first 90 days decide if the new role sticks

1

The transition trap

New leaders fail most often by applying the exact habits that made them successful last time to a context that needs different instincts.

Watkins opens with a paradox: the people most likely to stumble are often the ones who just succeeded brilliantly. Success builds a repertoire of assumptions, relationships, and reflexes fitted to one setting. Move that person and the reflexes fire anyway—at the wrong moments.

A sales leader promoted into operations may keep pushing speed and charisma when the job now demands process discipline. A turnaround specialist dropped into a stable high-performing division may start cutting things that were never broken and alienate a team that needed reassurance.

The trap is invisible from inside. Past success feels like proof the instincts are sound. Meanwhile the organization reads the behavior as tone-deaf, and support erodes before any formal failure. The first chapter’s job is to unsettle confidence enough that the reader will actually do the diagnostic work instead of skipping to action.

In practice: A turnaround specialist parachuted into a healthy division starts restructuring unbroken processes and loses the room.

2

Break from the old role

Without a deliberate psychological break from the prior job’s mindset, a leader negotiates the new role from old and often wrong assumptions.

Before any external strategy Watkins insists on an internal one. Many new leaders arrive still tethered to old success metrics, old peer groups, and old identities. A general manager who spent fifteen years as a brilliant engineer may still measure worth by technical elegance even though the job now rewards political judgment and resource allocation.

The practical device is simple and non-motivational: before day one, write explicitly what worked last time, what will not transfer, and what new skills the role demands. The point is to interrupt autopilot.

He also flags the emotional load—anxiety of not knowing enough, the temptation to prove competence through visible action, loneliness without a peer network. Left unmanaged, those feelings drive premature decisiveness: announcing changes before understanding why things are the way they are. Self-management of the urge to act is the precondition for every later technique; without it the diagnostic tools become theater.

In practice: A new plant manager reverses a safety protocol in week one to show authority, then learns it existed because of a near-fatal accident two years earlier.

3

Build a learning plan

Most new leaders underinvest in structured learning and treat first conversations as settled fact instead of ongoing discipline.

Learning in a new role is usually haphazard: pick up whatever is in the room, form impressions from the first talks, then freeze them. Watkins wants a learning plan—a short list of specific questions about the business, people, and culture, matched to sources such as financial reports, one-on-ones, meeting observation, and outside views from customers or suppliers.

The key move is triangulation. Any single source is biased. The outgoing predecessor frames history to protect their record. Direct reports frame problems to protect turf or steer toward preferred solutions.

Two opposite failure modes: arrive with a fixed plan that blinds you to disconfirming evidence, or arrive with no plan and depend on whoever talks first and loudest. The middle path is structured openness—defined questions revised as evidence arrives. The habit does not end at ninety days; strategy chosen from bad information is worse than no strategy.

In practice: A division head trusts a confident deputy’s story of a struggling product line until customer interviews show the deputy’s own pricing decisions were a major cause.

4

Match strategy to STARS

There is no single right transition style; the correct approach depends on whether you inherited a startup, turnaround, realignment, or sustaining success.

This is the book’s central sorting tool. Startup means building from nothing with no existing team or systems. Turnaround means a business in real trouble that needs rapid, sometimes painful correction. Realignment means a business that looks fine on the surface but has drifted and needs redirection before crisis. Sustaining success means a strong business that needs momentum preserved without needless disruption.

Each type demands different behavior. A turnaround tolerates fast visible action because stakeholders already know something is wrong. Apply that urgency to sustaining success and you look like you are breaking what worked. Treat a true turnaround with sustaining-success patience and the business keeps deteriorating while you build consensus there is no time for.

Realignment is trickiest: the danger is invisible inside the organization. The first job is persuasion—building shared urgency before anyone accepts change. Most real jobs are blends; one product line can be a turnaround while another is sustaining success, so the leader must run different playbooks at once. Naming the situation honestly before choosing tactics is the practical value.

In practice: A leader who brings turnaround urgency into a sustaining-success division burns trust with a team that cannot see why change is needed.

5

Negotiate the boss relationship

The boss relationship is not a fixed given; it is an outcome to negotiate in the first weeks through structured conversations most leaders skip.

Watkins treats the boss as the single highest-leverage relationship in a transition. He wants a short series of discussions covering the business situation (which STARS type the boss believes this is), expectations (success at thirty, sixty, ninety days, and one year), style (how to update, how much autonomy), resources actually available, and personal development areas the boss sees.

Expectations are rarely explicit by default. A boss may privately want turnaround urgency while saying only “get up to speed,” so the mismatch surfaces months later as disappointment.

This is not one marathon meeting. Spread conversations across early weeks so answers are not shallow. Pride often blocks the ask—new leaders fear questions signal weakness—yet the absence of clarity is what later looks like incompetence when misaligned expectations become visible failures.

In practice: A marketing director thinks she has a year for brand strategy while her boss expects visible sales impact in two quarters; neither said so, and friction nearly ended her tenure.

6

Secure early wins

Credibility is built through a few visible, meaningful early achievements, not through general competence accumulated slowly.

Organizations judge new leaders quickly, often within weeks, and those judgments stick—later evidence works harder to overturn a first impression than to confirm it. So where you score an early win is strategic.

A useful early win solves a problem the organization already recognizes, is achievable with resources you actually have, and reinforces the longer direction you intend—not a disconnected quick fix. Easy but irrelevant wins can read as proof you miss real priorities. Dramatic overreach that needs authority you lack produces a visible early failure worse than a modest success.

Watkins asserts from experience that reputation rides on a few well-chosen moves rather than gradual accumulation, aligning with how people form first judgments of others.

In practice: A new plant leader fixes one long-complained floor bottleneck instead of launching a big restructuring; workers trust him because it was their problem.

7

Align structure and systems

Talent cannot overcome architecture that rewards the wrong behavior, so new leaders must audit and sometimes redesign structure, systems, and skills.

Beyond people and personal credibility, Watkins turns to who reports to whom, how work is divided, how performance is measured and rewarded, and whether the team has the collective capability the strategy needs. A sound strategy and a skilled leader still fail when the surrounding architecture pays for the opposite of the goal.

Do this diagnostic after STARS and early wins, once you have some credibility. Ask whether current structures were built for a prior leader’s conditions or an earlier stage of the business and now need deliberate redesign.

Structural change is disruptive. Do not restructure lightly or before you understand why the current setup exists; early surgery can remove something quietly doing important work. Leadership here is partly an engineering problem, not only a motivational one.

In practice: A customer-service leader wants higher resolution quality but metrics reward call volume and speed, punishing anyone who spends time solving the real problem—only changing measurement changes behavior.

8

Evaluate and reshape the team

Inheriting a roster is not the same as having a team; evaluate people against the role as it now exists and reshape deliberately.

Deciding who stays, moves, or goes is emotionally loaded. New leaders often delay too long from fear of seeming harsh, or move too fast on superficial first impressions—favoring the personable over the quietly effective.

Evaluate along competence for the role as it exists now (not under the prior leader), judgment, energy, and trustworthiness. A highly capable person who undermines politically can do more damage than a mediocre but loyal one.

Wholesale replacement is almost always a mistake except in genuine turnarounds: it destroys institutional knowledge and signals distrust of potential allies. The staged approach is quick decisive action on clearly unfit or actively undermining members, patient observation and development of the ambiguous middle, then final calls. Fair evaluation needs the same triangulated evidence as the business diagnosis.

In practice: A leader keeps a talented disgruntled deputy for their skills; the deputy works to discredit the new strategy among peers and costs more than the skills were worth.

9

Build alliances beyond authority

Success depends on people with no formal duty to help—peers, other departments, informal influencers—and those ties need deliberate cultivation.

Formal authority rarely reaches far enough. Important initiatives need cooperation from peers who control resources, information, or approval and who owe the new leader nothing by default. Alliance-building is core work, not optional networking.

Map the informal influence structure: who shapes opinion in meetings regardless of title, who holds historical credibility that outlasts any single leader, who may nod in the room and quietly oppose later. Rely only on the formal org chart and you get blindsided by slow-walked cooperation or quiet sabotage.

This loops back to the transition trap. A leader who once succeeded through pure hierarchy may not see that a new organization runs on informal trust; failing to build alliances deliberately repeats the error of old instincts in a unfit context.

In practice: A technically sound reorganization approved by the boss stalls for months because a senior engineer with huge informal credibility was never consulted, felt disrespected, and spread quiet skepticism.