The First 90 Days as a Tech Lead

Why the First 90 Days Matter

The first 90 days as a tech lead set the tone for your entire tenure. Your team is watching. Stakeholders are forming opinions. You're building — or losing — trust with every interaction.

Here's a practical playbook that worked for me.

Week 1–2: Listen and Learn

Resist the urge to change anything immediately. Your job is to understand: - How work actually gets done (not how the wiki says it gets done) - Who the informal leaders are - What's broken and what's working - What the team is proud of

Schedule one-on-ones with everyone. Ask open-ended questions. Take notes. Don't promise solutions yet.

Week 3–4: Identify a Quick Win

Find something you can improve that's visible and low-risk. Examples: - Fix a painful process (deploys, onboarding, incident response) - Unblock a stuck project - Improve documentation for a critical path

Ship it. Let the team see that you're here to make things better, not to add process for its own sake.

Month 2: Build Trust Through Consistency

Show up. Follow through. If you say you'll do something, do it. If you can't, say so early.

Start having harder conversations: performance, priorities, technical debt. Be direct and kind. Your team needs to know they can rely on you.

Month 3: Set Direction

By now you should have a clear picture. Share your read on the team's strengths, gaps, and opportunities. Propose 2–3 focus areas for the next quarter. Get feedback. Iterate.

You're not just a senior engineer anymore. Your job is to create clarity and remove obstacles so the team can do their best work.

The One Thing

More than anything else: be consistent. Your team will forgive a lot if they know where you stand and that you have their back.