leadership-transition

name: leadership-transition description: > Navigate a new leadership role using Michael Watkins' First 90 Days 30/60/90 framework. Use when someone says "I just started a new role", "I'm starting as a new manager", "I joined a new company as a leader", "I was just promoted", "how do I onboard as a leader", "what should I do in my first 30 days", "I inherited a team", "I need a 90 day plan", or "I'm new to this team". Also trigger when someone describes feeling overwhelmed in a new leadership role, unsure where to start, or tempted to make changes too quickly before they've listened. Applies to first-time managers, leaders joining new companies, and leaders moving into new functions or teams within the same company.

Overview

Based on "The First 90 Days" by Michael Watkins. The core insight: new leaders fail not because they lack skill, but because they act before they understand. The biggest mistake is importing solutions from your previous role. The 90-day framework forces a learning phase before a doing phase, which feels slow but is faster overall. Watkins' research shows leaders who follow a structured 90-day plan reach the "break-even point" (where they contribute more than they consume) twice as fast as those who improvise.

The 30/60/90 Framework

Days 1-30: Listen and Learn
  - Understand the business, team, and context
  - Build relationships before making changes
  - Do not announce strategy or restructure anything

Days 31-60: Diagnose and Plan
  - Identify the 3-5 highest-leverage opportunities
  - Test hypotheses with the team
  - Make small early wins visible

Days 61-90: Align and Act
  - Communicate your direction and rationale
  - Make your first consequential decisions
  - Establish operating rhythms

Workflow

Step 1: Identify Your Transition Type

Before planning, know what kind of transition you're in. Watkins identifies five (STARS model):

Each type calls for a different pace and posture. A turnaround requires faster action and harder decisions than sustaining success, where premature change destroys momentum.

Step 2: Days 1-30 - Listen and Learn

What to do:

• Set up 1:1s with every direct report and key stakeholder in the first two weeks
• Ask the same 5-7 questions to each person (see below) and listen for patterns
• Map the informal power structure - who influences decisions, who has trust, who is resistant
• Learn the existing processes and rhythms before proposing changes to them
• Identify 1-2 quick wins that require no political capital (fix something obviously broken that everyone has been tolerating)

Stakeholder questions to ask everyone:

1. "What's working really well that I should be careful not to break?"
2. "What's the biggest problem or obstacle you're dealing with?"
3. "What would you do if you were in my role?"
4. "What should I know about this team/company that I won't find in a document?"
5. "What do you need from me to do your best work?"

What not to do:

• Do not announce a new strategy or direction
• Do not restructure the team
• Do not criticize how things were done before you arrived
• Do not make promises you haven't verified are achievable

End-of-month deliverable: Write a learning summary for yourself (not published):

What I expected vs. what I found: [key surprises]
Team strengths: [what's working]
Key problems: [what needs attention]
Relationships: [who are my allies, who is skeptical, who is undecided]
Hypotheses to test in month 2: [3-5 specific things]

Step 3: Days 31-60 - Diagnose and Plan

What to do:

• Test your month-1 hypotheses with small experiments or direct questions
• Share early observations with your manager and key stakeholders (not conclusions - observations)
• Identify 3-5 highest-leverage opportunities: what will have the most impact on team outcomes?
• Have the first real conversations about what needs to change and why
• Begin making small decisions that demonstrate your values and working style

The 5-problem diagnostic: For each problem you've identified, ask:

1. Is this a people problem, a process problem, or a strategy problem?
2. Who owns it? Who can actually fix it?
3. What's the cost of leaving it unfixed for 6 months?
4. What's the political risk of fixing it?
5. Is there a quick win version (fixes 80% of the problem with 20% of the effort)?

End-of-month deliverable: Draft a 90-day plan to share with your manager:

My assessment of the team's current state: [3-5 sentences]
The 3 things I'm focusing on: [and why each matters]
What I'm not touching right now: [and why]
What I need from you: [specific asks from your manager]
How I'll measure progress in 90 days: [3-5 metrics or indicators]

Step 4: Days 61-90 - Align and Act

What to do:

• Communicate your direction clearly to the full team - this is their first real introduction to your leadership style
• Make your first consequential decisions with clear rationale shared
• Establish operating rhythms: meeting cadences, decision-making norms, communication patterns
• Have performance conversations with any direct reports who need course correction
• Build coalitions with key stakeholders who need to be on your side for your plan to work

Team communication template:

What I've seen in my first 60 days: [honest assessment - strengths and gaps]
What I believe needs to change and why: [direction, not a complete plan]
What I will not change: [what's working that you're protecting]
How I'll make decisions: [your operating model]
What I need from you: [specific asks of the team]
How you can raise concerns: [your feedback channels]

First decisions framework: For your first consequential decisions:

• Make them visible - explain the reasoning, not just the outcome
• Pick decisions that reflect your values (speed, quality, customer, team wellbeing)
• Do not make irreversible decisions without coalition support first
• Delay any restructuring unless the situation is a turnaround

Anti-Patterns

1. Importing solutions from your last role Bad: "At my previous company, we solved this with [framework/process]. Let's do that here." Good: Diagnose the current context before prescribing. The same symptom has different root causes in different organizations. Understand the soil before planting.

2. Making changes too fast Bad: Announcing a restructure in week 2 because you can already see what's broken. Good: Even if you're right, moving too fast before building trust means your changes will be resisted or undermined. Speed of change must be matched to the level of trust you've built.

3. Performing instead of learning Bad: Spending month 1 demonstrating your ideas and expertise in meetings to establish credibility. Good: Credibility in a new role comes from listening well and asking smart questions, not from talking the most. Listening IS the performance in month 1.

4. Neglecting the manager relationship Bad: Being heads-down with the team and not managing upward. Good: Your manager is your single most important relationship in the first 90 days. Align on expectations, share your plan, and ask for feedback before you're 90 days in.

5. Skipping the STARS diagnosis Bad: Applying the same pace and posture to every new role. Good: A turnaround needs fast, bold moves. Sustaining success needs patience and restraint. Misreading the situation is the most common cause of early failure.

Quality Checklist

• STARS transition type identified - pace calibrated accordingly
• Stakeholder 1:1s scheduled in first 2 weeks with consistent questions
• Month-1 learning summary written (even if just for yourself)
• 90-day plan shared with manager by day 45
• Quick wins identified and executed in month 2
• Team direction communication planned for days 60-90
• No restructuring or strategy announcement before day 45 (except turnaround)
• Feedback channel established with manager and team