First 90 Days as a Tech Lead

Stepping into a tech lead role is a significant shift. You're no longer judged solely on your code—you're responsible for the team's output, technical direction, and culture. The first 90 days set the tone. A structured approach—inspired by Michael Watkins' The First 90 Days—helps you build credibility, understand the system, and avoid common mistakes.

Phase 1: Days 1–30 — Listen and Learn

Your primary job in the first month is to absorb. Resist the urge to impose solutions or "fix" things immediately. Premature changes can damage trust and miss important context.

Understand the Codebase and Architecture

Spend time reading code, tracing flows, and understanding the architecture. Where are the pain points? What works well? Set up your environment, run tests, and deploy to staging. Get hands-on so you can speak from experience, not assumption.

Map the Stakeholders

Identify who matters: your direct team, adjacent teams, product managers, and leadership. Schedule one-on-ones with each. Ask open-ended questions: What do you expect from me? What's working? What would you change? Take notes and listen more than you talk.

Learn the History and Context