First 90 Days Plan

A first-90-days plan is not a promise to transform a business in three months. It is a structured way to learn the situation, establish relationships, choose a small number of priorities, test assumptions, and create a credible path into the next quarter.

Research on leadership transitions emphasizes learning, stakeholder relationships, early wins, and clarity about the destination. Harvard Business Review has also highlighted the value of combining near-term action with a longer-term view rather than treating the first weeks as a race to prove yourself. Sources and methodology

Use the plan as a working document. Replace assumptions with evidence as you learn.

Write down:

• Role and scope:
• What success should look like after 90 days:
• What is already working:
• What appears broken:
• What you do not yet know:
• Decisions you are expected to make:
• Decisions you are not expected to make:
• Key customers, partners, investors, managers, and team members:
• Existing commitments:
• Known constraints:
• Metrics already used to judge performance:

Then write three versions of the situation:

Known: facts you can verify.

Assumed: beliefs that still need testing.

Unknown: questions for which you currently lack enough evidence.

Do not turn an assumption into a priority until you have a reason to believe it matters.

The first month is the diagnosis phase.

Record:

Prioritize conversations with customers, team members, managers, partners, and other stakeholders who have direct knowledge of the situation.

Ask questions that produce evidence rather than asking people to endorse your proposed solution:

• What is working better than I might expect?
• What is harder than it looks?
• What should I understand before changing anything?
• Where do customers experience friction?
• Which decision has been repeatedly delayed?
• What would you protect if resources were cut?
• What would you stop doing if you had to simplify?
• What evidence would change your mind?

The point is not to collect opinions for their own sake. It is to discover patterns, contradictions, dependencies, and missing information.

For each important stakeholder, record:

• What they need from the role
• What they know that you do not
• What they are worried about
• What decisions they influence
• What evidence you need from them
• What you need to communicate
• Next conversation

Harvard Business Review's transition guidance repeatedly emphasizes relationships and stakeholder understanding as part of the early transition period. Sources and methodology

Track learning and decisions, not just meetings completed.

At Day 30, you should be able to state:

1. What the business is trying to accomplish.
2. What is preventing it from getting there.
3. Which assumptions have been confirmed.
4. Which assumptions have been disproved.
5. Which problems deserve attention now.
6. Which problems should wait.

The second month is the prioritization phase.

For each priority, complete:

Problem: What specific problem are we solving?

Evidence: What tells us this problem is real?

Why now: What happens if we do nothing for another quarter?

Desired outcome: What should be measurably different?

Owner: Who is accountable?

Dependencies: What must happen first?

Trade-off: What will receive less attention because this is a priority?

Test: What is the smallest useful action that can increase our confidence?

A plan with ten priorities is usually a list of wishes. A useful 90-day plan makes trade-offs visible.

A quick win is useful when it addresses a real problem without creating unnecessary future complexity.

Do not choose an initiative merely because it can be completed quickly. Harvard Business Review's research on transitions distinguishes useful early progress from activity undertaken simply to demonstrate visible action. Sources and methodology

For every proposed quick win, ask:

• What problem does this solve?
• Who benefits?
• What evidence says it matters?
• What could this accidentally make worse?
• Can we reverse it if the assumption is wrong?

For each priority:

Outcome: What should change?

Metric: How will we know?

Baseline: Where are we now?

Target: Where are we trying to get?

Review date: When will we reassess?

Where team work is involved, clarity of goals, roles, responsibilities, and progress measures can be more useful than simply increasing activity. Google's research on team effectiveness, for example, identified structure and clarity as one of the important dimensions it studied and used a combination of qualitative and quantitative measures rather than relying on one metric alone. Sources and methodology

The final month is the transition from diagnosis to operating rhythm.

What did we expect?

What actually happened?

What evidence changed our view?

What should continue?

What should stop?

What needs another experiment?

What needs a larger investment?

What remains unknown?

Do not hide a failed assumption. A 90-day review is more useful when it shows what the team learned, not just what it completed.

• Role:
• Date started:
• Business stage:
• Team:
• Revenue model:
• Main customer:
• Current strategic objective:
• Biggest known constraint:

Priority 1

• Problem:
• Evidence:
• Outcome:
• Metric:
• Baseline:
• Target:
• Owner:
• First test:
• Review date:

Priority 2

• Problem:
• Evidence:
• Outcome:
• Metric:
• Baseline:
• Target:
• Owner:
• First test:
• Review date:

Priority 3

• Problem:
• Evidence:
• Outcome:
• Metric:
• Baseline:
• Target:
• Owner:
• First test:
• Review date:

For every material decision, record:

• Decision:
• Date:
• Context:
• Options considered:
• Evidence available:
• Trade-off accepted:
• Owner:
• Review date:

At the end of the period, answer:

1. What do we understand now that we did not understand on Day 1?
2. Which assumptions were wrong?
3. Which priorities produced evidence of progress?
4. Which activities should stop?
5. Which problems became more important?
6. Which risks increased?
7. What should the next 90 days focus on?
8. What should remain deliberately unfinished?

The first 90 days should leave the business with more clarity, stronger working relationships, better evidence, and a smaller number of explicit priorities.

It does not need to produce a perfect strategy.

The plan should become more accurate as evidence arrives. Treat it as a living decision document, not a presentation that must be defended.

This template draws on published work about leadership transitions and organizational effectiveness, including Harvard Business Review's work on early wins, stakeholder relationships, and future-back planning, plus Google's published research on structure, clarity, goals, and measurement in teams. Sources and methodology

Related reading: \2 · \2

Define what the person should understand, own and improve by day 30, 60 and 90. Include the evidence required at each stage, dependencies, decision rights and review dates. Treat the plan as a working agreement that can change when the role or business changes.

1. Fill it with one real situation rather than hypothetical inputs.
2. Record the evidence behind each important field.
3. Make the smallest decision the tool is designed to support.
4. Set a review date and update the tool when the evidence changes.

Good output: another person should be able to understand what was decided, why, what remains uncertain, and what happens next without needing a separate founder explanation.