Your First 90 Days as CTO: A Complete Playbook

The first 90 days as a new CTO are critical. Whether you're stepping into the role at a new company, promoted internally, or founding a startup, this playbook provides a structured approach to establishing credibility, understanding the landscape, and setting yourself up for long-term success.

Overview: The 30-60-90 Framework

Days 1-30: Listen and Learn - Understand the current state
Days 31-60: Analyze and Align - Identify priorities and build relationships
Days 61-90: Act and Accelerate - Execute quick wins and set long-term strategy

Days 1-30: Listen and Learn

Week 1: Orientation and First Impressions

Goal: Establish presence, understand organizational context, and build initial relationships.

Key Activities

Day 1-2: Meet Your Team

Hold 1-on-1s with your direct reports (30-45 min each)
Ask: "What's working well? What's frustrating? What would you change?"
Listen more than you talk - aim for 80/20 ratio
Take detailed notes in a shared doc

Day 3-4: Understand the Business

Meet with CEO to understand vision, priorities, and expectations
Review board decks and strategic plans from the last 6 months
Understand revenue model, key metrics, and growth targets
Ask: "What does success look like for me in 6 months?"

Day 5: Map the Organization

Create an org chart if one doesn't exist
Identify key stakeholders across departments
Schedule 1-on-1s with CPO, CFO, COO, Head of Sales, Head of Marketing
Request access to all relevant systems and documentation

Deliverable

Stakeholder map with scheduled 1-on-1s
Initial impressions document (for your eyes only)

Week 2: Deep Dive into Engineering

Goal: Understand technical landscape, processes, and team dynamics.

Technical Assessment Checklist

Architecture & Systems

Review system architecture diagrams
Identify major services, databases, and infrastructure
Understand deployment process and frequency
Review monitoring, alerting, and observability setup
Check disaster recovery and backup procedures
Audit security practices and compliance requirements

Development Process

Shadow engineers for a day
Review sprint planning and retrospective notes
Understand code review process
Check CI/CD pipeline health
Review test coverage and quality metrics
Attend standup, planning, and retro meetings

Team Health

Review recent 1-on-1 notes (if available)
Check turnover rate and hiring pipeline
Understand compensation structure
Identify skill gaps and training needs
Assess team morale through informal conversations

Questions to Ask Engineers

"What's the most frustrating part of your job?"
"What technical debt keeps you up at night?"
"If you could change one thing about our process, what would it be?"
"What are you most proud of building here?"

Week 3-4: Stakeholder Alignment

Goal: Build relationships across the organization and understand their needs.

Key Stakeholder Meetings

Product Leadership

Understand product roadmap and priorities
Ask: "What's blocking you from moving faster?"
Discuss eng/product collaboration and friction points
Align on how decisions get made

Sales & Customer Success

Learn about customer pain points and feature requests
Understand SLAs and customer commitments
Ask: "What technical limitations hurt sales?"
Review major customer escalations from last quarter

Finance

Understand budget constraints and approval process
Discuss infrastructure costs and optimization opportunities
Review headcount plan and hiring budget
Ask: "What financial metrics matter most to the business?"

Operations & Support

Review incident history and response times
Understand operational pain points
Discuss tooling needs and process improvements
Ask: "What breaks most often?"

Deliverable

Cross-functional priorities document
List of quick wins for each department

Days 31-60: Analyze and Align

Week 5-6: Technical Deep Dive

Goal: Form opinions on technical priorities and create a preliminary roadmap.

Conduct a Technical Audit

Architecture Review

Map out all services and dependencies
Identify single points of failure
Document scalability bottlenecks
Assess technical debt hotspots

Operational Excellence

Review incident response process
Analyze system reliability (uptime, error rates)
Audit observability and monitoring gaps
Check on-call rotation and burnout risk

Security & Compliance

Review security practices and vulnerabilities
Check compliance requirements (SOC 2, GDPR, etc.)
Assess data protection and privacy controls
Audit access controls and permissions

Developer Experience

Measure build times and deployment frequency
Assess documentation quality
Review onboarding process for new engineers
Evaluate tooling and productivity blockers

Create a Technical Health Scorecard

Rate each area 1-5 and track over time:

System Reliability
Scalability
Security & Compliance
Developer Velocity
Technical Debt
Team Morale
Documentation Quality

Week 7: Build Your Leadership Team

Goal: Establish trust with direct reports and define team operating principles.

Team Activities

Offsite or Extended Meeting

Share your leadership philosophy
Co-create team values and operating principles
Discuss communication norms and decision-making
Define roles and responsibilities clearly
Set up regular cadences (1-on-1s, staff meetings, all-hands)

Establish Rituals

Weekly staff meeting (strategy, cross-team issues)
Bi-weekly 1-on-1s with each direct report
Monthly all-hands with engineering
Quarterly planning sessions
Regular tech talks and knowledge sharing

Define Decision-Making Framework

What decisions do you make vs delegate?
How should teams escalate issues?
What requires cross-functional approval?
Document and share widely

Week 8: Strategic Alignment

Goal: Align technical strategy with business objectives.

Strategy Session with Leadership

Topics to Cover

Business objectives for next 12 months
Technical investments needed to achieve them
Risk assessment and mitigation plans
Resource requirements (headcount, tools, infrastructure)
Timeline and milestones

Create Draft Technical Roadmap

Q1: Critical infrastructure work (if needed)
Q2: Platform improvements and technical debt
Q3-Q4: Strategic initiatives aligned with business goals

Share for Feedback

Review with CEO and leadership team
Get input from engineering managers
Validate assumptions with product and business stakeholders

Deliverable

Technical Strategy Document (1-2 pages)
Draft 12-month roadmap
Resource request for upcoming quarters

Days 61-90: Act and Accelerate

Week 9-10: Execute Quick Wins

Goal: Deliver visible improvements to build credibility and momentum.

High-Impact, Low-Effort Wins

Process Improvements

Fix one major developer pain point
Improve deployment process or documentation
Streamline code review or testing bottlenecks
Set up better monitoring or alerting

Team Improvements

Address one obvious team structure issue
Improve meeting efficiency (fewer/shorter meetings)
Launch a recognition or feedback program
Improve onboarding documentation

Technical Improvements

Fix a high-impact bug or performance issue
Implement one security improvement
Reduce build times or deploy frequency
Improve test coverage for critical paths

Celebrate and Communicate

Share wins in all-hands meetings
Give credit to the team publicly
Document what changed and why
Measure impact with metrics

Week 11: Formalize Strategy

Goal: Get buy-in on technical strategy and secure resources.

Present to Leadership Team

Create Executive Presentation

Current state assessment (honest but constructive)
Strategic priorities for next 12 months
Resource requirements (people, tools, budget)
Expected outcomes and success metrics
Risk mitigation plans

Address Key Questions

What's the biggest technical risk to the business?
How will this strategy support revenue goals?
What trade-offs are we making?
How will we measure success?

Get Formal Approval

Secure budget for next quarter
Get headcount approvals
Align on quarterly OKRs or goals

Week 12: Set Up for Success

Goal: Establish systems and processes for ongoing success.

Implementation Plan

Hiring & Team Building

Finalize hiring plan and job descriptions
Start recruiting for critical roles
Identify high-potential team members for growth
Create career development plans

Communication Rhythms

Launch regular engineering all-hands
Set up monthly updates to board/leadership
Create engineering newsletter or updates
Establish regular 1-on-1 cadence

Metrics & Accountability

Define engineering KPIs and dashboards
Set up regular reviews of key metrics
Create quarterly planning process
Establish post-mortem and learning culture

Culture & Values

Reinforce engineering values
Launch initiatives for diversity, learning, innovation
Create feedback mechanisms
Celebrate wins and learn from failures

Deliverable

Q1 execution plan with owners and timelines
Engineering metrics dashboard
Communication calendar for next quarter

Key Success Factors

What Makes or Breaks the First 90 Days

Do's ✅ Listen far more than you talk ✅ Build relationships across the organization ✅ Deliver at least 2-3 visible quick wins ✅ Be honest about problems but constructive about solutions ✅ Over-communicate your intentions and reasoning ✅ Show respect for what the team has built ✅ Make data-driven decisions when possible ✅ Admit what you don't know

Don'ts ❌ Make major changes in the first 30 days ❌ Criticize previous leadership publicly ❌ Commit to timelines before understanding complexity ❌ Ignore cultural fit and people dynamics ❌ Try to fix everything at once ❌ Skip building relationships with stakeholders ❌ Assume your previous company's way is "the right way" ❌ Neglect your own team while focusing on strategy

Templates & Tools

Meeting Templates

1-on-1 Questions for Direct Reports

What's going well? What's challenging?
What's one thing I can do to help you be more effective?
What decisions are you waiting on?
What should I know that I don't know?
How's your work-life balance?

Stakeholder 1-on-1 Template

What are your top 3 priorities this quarter?
What's blocking you from achieving them?
How can engineering better support you?
What's one thing we could do differently?

Assessment Framework

Technical Debt Prioritization Matrix

Impact	Effort	Priority	Action
High	Low	P0	Do now
High	High	P1	Plan for next quarter
Low	Low	P2	Do when you have time
Low	High	P3	Defer or don't do

Common Pitfalls & How to Avoid Them

Pitfall 1: Moving Too Fast

Problem: Making big changes before understanding context Solution: Force yourself to wait 60 days before major decisions Exception: Critical security or reliability issues

Pitfall 2: Ignoring Culture

Problem: Focusing only on technical problems Solution: Spend 50% of time on people and culture Metric: Track team morale and turnover

Pitfall 3: Poor Stakeholder Management

Problem: Working in isolation from the rest of the business Solution: Over-communicate and build strong cross-functional relationships Metric: Regular check-ins with all C-level peers

Pitfall 4: No Quick Wins

Problem: Only working on long-term strategy Solution: Deliver 2-3 visible improvements by day 60 Metric: Team and stakeholder feedback

Measuring Success

30-Day Check-In

Have you met all key stakeholders?
Do you understand the business model and priorities?
Have you completed technical assessment?
Do you have a plan for quick wins?

60-Day Check-In

Have you built strong relationships with your team?
Do you have alignment with leadership on priorities?
Have you delivered at least one quick win?
Do you have a draft technical strategy?

90-Day Check-In

Have you presented and gotten buy-in on your strategy?
Have you delivered 2-3 visible improvements?
Do you have resources (budget, headcount) secured?
Is your team aligned and energized?
Do stakeholders trust your judgment?

Resources

Tools to Consider

Team health survey (e.g., Culture Amp, Officevibe)
Technical debt tracking (e.g., Linear, Jira)
Documentation platform (e.g., Notion, Confluence)
Engineering metrics (e.g., Jellyfish, Swarmia)

Conclusion

The first 90 days set the tone for your entire tenure as CTO. By following this playbook, you'll build credibility, establish strong relationships, and create momentum for long-term success.

Remember: Listen first, align second, act third. The investments you make in understanding and relationships during these first three months will pay dividends for years to come.

Good luck! 🚀