Tech Lead 30-60-90 Day Plan Template with Examples
A 30-60-90 day plan is your strategic roadmap for the first three months as a tech lead. It is not a detailed task list. It is a framework that keeps you focused on the right priorities at the right time, and gives your manager confidence that you are ramping up intentionally.
I have used this framework every time I stepped into a new tech lead role, and I teach it as a core module in the First Lead course. The pattern is consistent: Learn in the first 30 days, contribute in days 31 to 60, and lead in days 61 to 90. Rushing any of these phases creates problems that take months to fix.
The Three Phases Explained
Each phase has a distinct purpose and builds on the previous one. The biggest mistake new tech leads make is jumping to Phase 3 actions in Phase 1. You cannot effectively lead change when you do not yet understand the landscape.
- Days 1-30 (Learn): Understand the people, the technology, and the business context. Build relationships. Identify quick wins but do not overhaul anything.
- Days 31-60 (Contribute): Start making visible improvements. Establish your processes. Deliver your first meaningful results.
- Days 61-90 (Lead): Drive strategic initiatives. Set the team's technical direction. Own the roadmap alongside product.
Every phase should end with a checkpoint meeting with your manager. Share what you learned, what you accomplished, and what you plan to focus on next. This keeps expectations aligned and demonstrates structured thinking.
TECH LEAD 30-60-90 DAY PLAN TEMPLATE
Days 1-30: LEARN
Theme: Understand the landscape. Build relationships. Earn the right to lead.
People Goals:
- Complete 1:1 meetings with every team member using the 1:1 template
- Meet all key stakeholders: product manager, design lead, dependent team leads, your skip-level manager
- Understand each team member's strengths, growth areas, and career aspirations
- Identify team dynamics: who are the informal leaders, where are the friction points?
Technical Goals:
- Create a high-level architecture diagram of the systems your team owns
- Review the CI/CD pipeline, deployment process, and monitoring stack
- Read the last 20 pull requests to understand code quality and review culture
- Identify the top 3 technical risks or debt items the team talks about
- Complete the onboarding checklist
Business Goals:
- Understand the product roadmap for the next quarter
- Learn how the team's work connects to business metrics and revenue
- Identify the top 3 priorities from leadership's perspective
Quick Wins (deliver 1-2):
- Fix a long-standing minor annoyance (slow build, flaky test, missing documentation)
- Improve one team process (cleaner standups, better PR template, updated README)
30-Day Checkpoint Deliverables:
- Architecture diagram (even if rough)
- Written landscape assessment: strengths, risks, opportunities
- Manager sync: share findings, align on Phase 2 priorities
Days 31-60: CONTRIBUTE
Theme: Deliver visible results. Establish your leadership rhythm.
People Goals:
- Establish recurring 1:1 cadence with all team members
- Give specific, actionable feedback to at least 2 team members
- Identify one person ready for a stretch assignment and provide it
- Address one team dynamic issue surfaced in Phase 1
Technical Goals:
- Lead one significant technical initiative (feature, migration, or infrastructure improvement)
- Establish or improve code review standards
- Start addressing the top tech debt item identified in Phase 1
- Improve one DORA metric (deployment frequency, lead time, MTTR, or change failure rate)
Process Goals:
- Optimize sprint planning using the sprint planning template
- Run or improve team retrospectives using the retro template
- Start sending weekly reports to your manager
- Define on-call rotation improvements if needed
60-Day Checkpoint Deliverables:
- One shipped technical initiative
- Documented team processes (sprint cadence, code review standards, incident response)
- Manager sync: share results, get feedback, align on Phase 3 strategy
Days 61-90: LEAD
Theme: Set direction. Drive strategy. Own the technical vision.
People Goals:
- Create individual development plans for each team member
- Identify hiring needs and start writing job descriptions if applicable
- Mentor one team member for a leadership or senior-level growth goal
- Build a relationship with at least one peer tech lead for cross-team alignment
Technical Goals:
- Write and share a 6-month technical vision document for your team
- Propose one Architecture Decision Record for a strategic technical choice
- Create a tech debt backlog with prioritization
- Establish engineering metrics dashboard (DORA metrics, bug rates, velocity trends)
Business Goals:
- Participate actively in quarterly planning with product leadership
- Propose team OKRs for the next quarter
- Present a technical roadmap that aligns with business priorities
90-Day Checkpoint Deliverables:
- 6-month technical vision document
- Proposed team OKRs for next quarter
- Self-assessment: what worked, what to adjust, what to focus on in months 4-6
- Manager sync: formal 90-day review conversation
Customization Guidelines
Promoted internally? You can compress Phase 1 to two weeks since you already know the codebase and people. Spend extra time on the relationship shift — your former peers are now your reports, and that dynamic needs deliberate management.
Joining a struggling team? Extend Phase 1 to six weeks. Struggling teams have deeper trust issues and more complex dynamics. Rushing to Phase 3 will make things worse because you will lack the context to make the right changes.
Joining a high-growth startup? Compress everything. You might need to be in Phase 3 mode by week four. Prioritize ruthlessly: focus on the people relationships and the most critical technical risk. Everything else can wait.
Nail Your First 90 Days as Tech Lead
First Lead gives you the complete framework for transitioning into technical leadership, from day one to your first year. Three pillars: Technical Leadership, Business Acumen, People Management. Lifetime access.
Enroll in First Lead