# The EM 30-60-90 Day Plan: How to Answer “What Will You Do First?”

Source: https://www.techinterview.org/post/3233475012/em-30-60-90-day-plan-interview/
Updated: 2026-05-05 · techinterview.org

"What would you do in your first 90 days as our EM?" is a near-guaranteed question in any senior EM or director-level interview. Strong answers demonstrate humility, a structured framework, and the discipline to listen before acting. Weak answers are either a hero narrative ("I will rally the team and ship the roadmap by week 4") or pure passivity ("I will spend the first 90 days listening").

## The structure interviewers want to hear

A great answer has three phases:

- **Days 1–30: Listen and understand** — read the room before you change it

- **Days 31–60: Diagnose and propose** — surface what you saw, propose a small set of changes

- **Days 61–90: Execute and adjust** — start changing things, measure, course-correct

## Days 1–30: Listen and understand

Concrete actions:

- 1:1s with every direct report — twice in the first 4 weeks. Open-ended questions: what is going well, what is broken, what has held you back.

- 1:1s with peer EMs and your manager. Understand their priorities and how they see your team.

- Skip-levels with senior ICs and key adjacent partners (PM, design lead, support, legal, etc.).

- Read every recent design doc, OKR, post-mortem, and customer feedback artifact.

- Sit in on team rituals — standup, planning, retro — without changing them.

- Shadow on-call if applicable.

Critical: do not ship process changes in this window. The team is watching for whether you respect what already exists.

## Days 31–60: Diagnose and propose

By day 30 you should have a hypothesis about:

- The team's top 3 strengths

- The team's top 3 risks or gaps

- The team's biggest morale levers

- The biggest cross-functional friction

Communicate findings:

- Write up a "first 30 days" memo for your manager

- Share a digestible version with the team — what you heard, what you noticed

- Propose 1–2 specific changes, scoped to be achievable

## Days 61–90: Execute and adjust

Now you can start to act:

- Implement the small changes you proposed in days 31–60

- Set up the operating cadence you want — 1:1 frequency, planning rhythm, on-call rotation

- Deliver one visible, fast win — a project shipped, a friction unblocked, a hire made

- Establish your performance review pipeline if review cycle is approaching

## What to avoid in your answer

- Promising big organizational changes by day 30

- Hiring as the first action — wait until you understand the team's gaps

- Reorganizing the team within the first 90 days — it is rarely the right call without deeper context

- Being purely passive ("I will not change anything for 90 days")

## Customizing the answer to the role

If the team is in crisis, accelerate. If the team is high-performing, slow down. If the prior manager left abruptly, prioritize stability. If the team is brand new, prioritize hiring and norm-setting.

Show in your answer that you can read the situation and adapt — generic 30-60-90 plans are uninspiring.

## Frequently Asked Questions

### How long should this answer be?

4–6 minutes when delivered verbally. Practice trimming.

### Should I mention specific frameworks (like Watkins' First 90 Days)?

Optional. If you reference a book, do it briefly. The interviewer cares more about your judgment than your reading list.

### What if I have not been a new EM recently?

Frame your answer prospectively — "based on past experience joining new teams, here is what I would do." Mention adjacent transitions (joining a new project, taking over a struggling team) for credibility.