First 90 Days as Tech Lead

The Critical First Three Months

The first 90 days in a new Tech Lead role set the trajectory for everything that follows. Whether you have been promoted from within the team or hired externally, this period is your opportunity to build trust, understand the landscape, and establish your leadership style. Rushing to make sweeping changes is the most common mistake. Instead, invest heavily in listening, learning, and building relationships first.

Days 1-30: Listen and Learn

Your primary job in the first month is to gather information and build trust. Resist the urge to propose changes, no matter how obvious problems seem. Every system and every team has context you do not yet understand.

Meet Everyone 1-on-1

Schedule a 30-45 minute introductory 1-on-1 with every person on your team, your engineering manager, your product manager, and key stakeholders. In these conversations, ask questions like:

• What are you most proud of about this team's work?
• What is the biggest challenge the team is facing right now?
• If you could change one thing about how the team operates, what would it be?
• What should I know about the codebase or system that is not documented?
• How do you prefer to receive feedback?
• What are your career goals for the next year?

Study the Codebase and Architecture

Dedicate significant time to reading code, understanding the system architecture, and running the application locally. Pay attention to:

• Where technical debt has accumulated and why
• Which services or components are most fragile
• How the CI/CD pipeline works
• What monitoring and alerting exists
• How deployments are handled and what the rollback process looks like

Understand the Product and Business Context

Read product roadmaps, attend product meetings, and understand the business metrics your team influences. A tech lead who does not understand the product cannot make good technical decisions because all technical decisions are ultimately in service of business outcomes.

Days 31-60: Assess and Propose

By the second month, you should have a solid understanding of the team, the system, and the organizational context. Now it is time to synthesize what you have learned and start proposing changes.

Write Your Assessment

Create a written document (shared with your manager) that captures your observations. Include:

## 30-Day Assessment

### Team Strengths
- Strong frontend expertise across the team
- Good testing culture with >80% coverage
- Healthy team dynamics and collaboration

### Key Challenges
1. Deployment pipeline takes 45 minutes (should be <15)
2. No formal design review process leads to inconsistent APIs
3. Technical debt in the payment service is slowing feature work
4. On-call rotation has no runbooks, creating anxiety

### Proposed Quick Wins (Next 30 Days)
1. Introduce design review meetings for features >2 days of work
2. Add parallel test execution to cut CI time by 50%
3. Create on-call runbooks for the top 5 most common alerts

### Longer-Term Initiatives (60-90 Days)
1. RFC process for architectural changes
2. Payment service refactoring plan
3. Observability improvement (structured logging, dashboards)

Deliver a Quick Win

Identify and execute one improvement that is visible, uncontroversial, and immediately beneficial. This builds credibility and shows the team you are action-oriented. Good quick wins are things that everyone knows need fixing but nobody has prioritized: fixing a flaky test, improving CI speed, updating stale documentation, or automating a manual process.

Days 61-90: Establish Your Leadership

In the third month, shift from observation mode to active leadership. You should now have the context, trust, and credibility to drive meaningful change.

Establish Ongoing Practices

• Regular 1-on-1s: Set a cadence (biweekly or monthly) with each team member focused on growth and feedback
• Design Reviews: Formalize the process for reviewing technical designs before implementation begins
• Tech Debt Tracking: Create a visible backlog of technical debt items that the team reviews regularly
• Architecture Decision Records: Start documenting significant technical decisions so future engineers understand the context

Communicate Your Technical Vision

By day 90, you should be able to articulate a clear technical vision for the team. This does not need to be a 50-page document. A one-page summary covering where the system is today, where it needs to be in 6-12 months, and the key initiatives to get there is sufficient. Share it with your team and manager for feedback.

Building Trust as a New Leader

Trust is the foundation of effective leadership, and it is earned through consistent behavior over time. The specific trust-building actions that matter most in the first 90 days are:

• Follow through: Do what you say you will do, even on small things
• Be vulnerable: Admit when you do not know something and ask for help
• Give credit: Publicly attribute good ideas and work to team members
• Take responsibility: Own failures and mistakes without deflecting blame
• Be consistent: Apply the same standards and expectations to everyone, including yourself