Whether you just got the title or you already lead without it, the first ninety days set patterns that are hard to undo. Use this as a default plan. Adapt it to company size and how healthy the team already is.
The trap is big theater: reorgs, tool migrations, and manifesto rewrites before you understand the system. The opposite trap is pure observation with no signal that anything will improve. Aim for listen hard, change carefully, and ship credibility early.
Days 1-30: Listen and map
- 1:1 with every teammate: strengths, frustrations, aspirations.
- Map stakeholders, systems, on-call pain, and delivery bottlenecks.
- Learn how success is actually measured (not just OKR slides).
- Ship one small reliability or developer-experience win for credibility.
- Avoid reorganizations and big process rewrites unless the house is on fire.
- Write a private “system notes” doc: people map, risk list, open questions.
What should I protect? What should I change? Where do we waste time? Who is overloaded? What would make the next quarter less painful?
Days 31-60: Clarify and stabilize
- Publish team mission, ownership map, and working agreements.
- Fix one chronic ritual (planning, review SLA, or incident follow-up).
- Establish a lightweight priority stack with product.
- Start growth conversations; pick one coaching focus per person.
- Make risks visible upward with options.
- Define how the team handles interrupts and on-call load.
Days 61-90: Raise the bar
- Run a retrospective on the first 90 days with the team.
- Propose a 6-month plan: outcomes, capacity, and 1-2 system bets.
- Close or escalate lingering people or ownership ambiguities.
- Install measurement you will actually read (DORA-ish or simpler).
- Identify a deputy or backup for critical lead duties when you are out.
- Share a written narrative upward: what you learned, what you will do next.
90-day artifacts checklist
If these artifacts exist and are used, you are not just “busy leading.” You are building a system.
- Team mission and non-goals (one page).
- Ownership map (services, surfaces, or domains).
- Priority stack and WIP limits agreed with product.
- Working agreements (reviews, meetings, on-call).
- Risk list with owners and next review date.
- Personal growth focus per report (or peer coaching focus if no reports).
Common failure modes
- Changing process weekly so nothing stabilizes.
- Becoming the hero on-call and the bottleneck for decisions.
- Optimizing for your manager’s comfort only, not team health.
- Avoiding one hard people conversation until day 89.
- Shipping no credibility win, so the team only sees meetings.
The first 90 days are a down payment on trust. Spend it on clarity and small finished things, not on theater.