CTO First 90 Days: The 2026 Playbook

Week 1-2: Listen and Map the Terrain

Your only job in the first two weeks is to absorb context. You're building a mental model of the organization, the technology, the people, and the politics. Everything you do for the next 76 days depends on the accuracy of this model. Michael Watkins' work on executive transitions in HBR makes the same case: diagnose before you act.

The 1:1 blitz. Schedule 30-minute 1:1s with every engineering manager, tech lead, and senior IC. Also schedule conversations with the heads of product, design, sales, and customer success. Ask every person the same three questions: What is working that I should protect? What is broken that nobody is fixing? What decision has been stuck waiting for someone with authority to make it?

Take handwritten notes. Not because handwriting is magical, but because laptop notes during a 1:1 create a power dynamic where you look like you're documenting testimony. Handwritten notes signal you're genuinely listening.

The production reality check. Get access to monitoring dashboards, incident reports from the last 6 months, and the on-call rotation schedule. Read every post-mortem from the last quarter. These documents tell you more about the engineering culture than any interview. How blame is assigned in post-mortems reveals whether the culture is learning-oriented or fear-driven. The incident frequency tells you whether the team is building on stable ground or firefighting constantly.

The shadow day. Spend one full day sitting with a product engineering team. Watch their standup. Watch their code review process. Watch how they deploy. Watch what happens when something breaks. Don't offer suggestions. Don't fix problems. Just watch. You'll learn more in one shadow day than in ten 1:1s because you're seeing the system in motion, not hearing curated descriptions of it.

Map who actually holds power. Every organization has informal power structures that differ from the org chart. Who does the CEO actually listen to on technology questions? Who has veto power over technical decisions through informal influence? Which engineer is so critical that the team would destabilize if they left? Who has been angling for the CTO role you just got? These dynamics will shape every decision you make for the next year. Identify them now.

Week 3-4: Tech Stack Audit and Relationship Foundation

With two weeks of context, you can now do a structured audit. This isn't about judging the previous CTO's decisions. It's about understanding the current state well enough to make future decisions.

The infrastructure audit. Map every production service. For each one, document: who owns it, when it was last significantly updated, what its monitoring coverage looks like, how it deploys, and what would happen if its primary maintainer left tomorrow. Services with a single maintainer and no documentation are your highest-risk assets. Not because they'll break today, but because they'll break at the worst possible time and nobody will know how to fix them.

The velocity audit. Measure time from commit to production for each team. Not as a performance evaluation, but as a diagnostic. The four DORA metrics (deployment frequency, lead time, change failure rate, time to restore) are the standard frame here. Teams that take two weeks to deploy have process problems or testing gaps. Teams that deploy multiple times daily have built the right infrastructure. The variance between teams tells you where to invest in developer experience.

The AI readiness assessment. This is the 2026-specific addition. Every board will ask about your AI strategy within the first 60 days. You need to understand: what AI capabilities already exist (even informal ones), what data infrastructure is available for AI workloads, what the team's AI literacy level is, and what competitors are shipping with AI. Don't build an AI strategy yet. Build the assessment that the strategy will sit on.

The cost audit. Get the full infrastructure cost breakdown. Cloud spend by service, SaaS vendor costs, and licensing fees. You'll almost certainly find at least one significant waste: unused reserved instances, overprovisioned clusters, SaaS tools that nobody uses but auto-renewed, or test environments that run 24/7 when they should run 8 hours a day. Fixing one of these becomes your first visible cost win.

Establish the CEO cadence. By end of week four, you need a standing weekly 1:1 with the CEO. Not a status update. A strategic alignment conversation. Thirty minutes, same time each week. Use the first few sessions to understand what the CEO actually cares about regarding technology. It's rarely what the job description said. Some CEOs care about velocity. Some care about reliability. Some care about AI narrative for investors. Some care about cost. Find out which, and orient your early wins accordingly.

Week 5-8: Quick Wins and Strategy Formation

You have spent a month listening. Your team is watching to see whether the new CTO is all talk or whether things actually change. This is when you deliver your first tangible results.

Pick two quick wins. One for the engineering team. One for the business. The engineering win should fix a pain point that came up repeatedly in your 1:1s. The business win should address something the CEO mentioned in your first few conversations. Both should be deliverable within 2-3 weeks.

Good engineering quick wins: Kill a pointless approval process that adds two days to every deployment. Fix the CI pipeline that fails 15% of the time on unrelated tests. Cancel the weekly status meeting that could be an async update. Upgrade the development environment that takes new engineers three days to set up. Renegotiate the vendor contract everyone knows is overpriced. Each of these is small, visible, and signals that you are paying attention to the team's actual problems.

Good business quick wins: Provide the cost reduction analysis from your audit. Deliver a preliminary AI readiness assessment that gives the CEO something concrete to share with the board. Fix a customer-facing performance issue that has been on the backlog for months. Set up the monitoring dashboard that shows system reliability metrics in business terms. Each of these builds credibility with the CEO and demonstrates that the CTO function produces business value, not just technical improvements.

Begin strategy formation. By week six, start drafting your technology strategy. Not for publication. For your own clarity. The strategy should answer five questions: Where is the technology today? Where does it need to be in 18 months to support the business plan? What are the three biggest gaps? What's the sequence for closing them? What will it cost in people, time, and money?

The AI strategy component. Your overall technology strategy needs an explicit AI section. By week eight, you should have a position on: build vs. buy for AI capabilities, which foundation model provider to start with (and why it's a reversible bet), where AI can improve engineering productivity, and what data infrastructure investment is needed. You don't need all the answers. You need a framework for making the decisions and a timeline for when each decision gets made.

Build your leadership team's trust. If you have VPs or senior engineering managers reporting to you, this is the window where they decide whether to bet on you or start looking. Have explicit conversations about their career goals, their frustrations with the current state, and what they need from you to be effective. Ask them what decisions they want to make that the previous CTO held too tightly. Delegation starts here.

Week 9-12: Strategy Presentation and Organizational Alignment

The final month of your first 90 days is where listening turns into leading. You present your technology strategy, make your first structural decisions, and establish the operating rhythm that will carry through the first year.

Present the strategy to your leadership team first. Not the CEO. Not the board. Your engineering leaders. They need to see it, challenge it, and feel ownership before it goes up. If your strategy surprises your direct reports, you did the listening phase wrong. The strategy should articulate what they already know but couldn't formalize without executive authority. Their feedback will also catch blind spots: you've been here 90 days; they've been here years.

The CEO strategy conversation. This is a 60-minute working session, not a presentation. Walk through the five-question framework: here is where we are, here is where we need to be, here are the gaps, here is the sequence, here is the cost. The CEO's job is to pressure-test the business alignment. Your job is to hold firm on technical reality while adapting the sequence to business priorities. Read the CTO-CEO relationship guide for how to run this conversation.

The most important sentence in this conversation: "Here's what I recommend we don't do." Every strategy is defined as much by what it excludes as what it includes. If the CEO has a pet AI project that doesn't fit the strategy, this is the moment to redirect it. Doing it at day 90 with data and context is leadership. Doing it at day 30 without context is arrogance.

Establish the operating rhythm. By end of day 90, the following cadences should be running: weekly CEO 1:1, weekly engineering leadership meeting, bi-weekly architecture review, monthly tech strategy review, quarterly board preparation cycle. If any of these didn't exist before you arrived, introduce them now. If any existed but were ineffective, redesign them. The rhythm is how you scale your attention. Without it, you become reactive to whoever shouts loudest.

The team-wide communication. At or near day 90, do an engineering all-hands. Share your observations from the listening phase (what is strong, what needs work), your strategic direction (high level, not detailed roadmap), and your commitments (what the team can expect from you as a leader). Be specific about what will change and what will stay the same. Teams handle change well when it is explained. They handle uncertainty poorly when it is unexplained.

Set your 180-day goals. Now that you have a strategy, define what "success at 6 months" looks like. Three to five measurable goals that you will be held accountable for. Share them with the CEO. Write them down where your leadership team can see them. Public accountability creates urgency and signals that you are serious about execution, not just strategy.

The AI Strategy Assessment Framework

In 2026, no CTO first-90-days playbook is complete without addressing AI. The board will ask. The CEO will ask. Your engineers are already using AI coding tools whether you have a policy or not. Here's the assessment framework I use with new CTOs.

Common First-90-Days Mistakes

I have seen these enough times to catalog them. If you recognize yourself in any of these, course-correct now.