The CTO's First 90 Days in a New Company
The first 90 days in a CTO role establish the foundation for everything that follows. Get them right and the credibility, relationships, and understanding you build will compound for years. Get them wrong and you spend the next year recovering from the impressions formed in the first three months.
Before Day One: The Pre-Start Intelligence Gathering
The most effective CTOs begin learning before their official start date. The pre-start period — from offer acceptance to first day — is an opportunity to gather context that will be more freely offered before the political dynamics of the organization are fully visible. Board members, investors, and outgoing technical leaders will share information in the pre-start period that they might frame more carefully once you are officially in the role. The questions to answer in this period are the same questions a private equity operating partner asks when assessing a new portfolio company: What is the technology expected to enable that it is not currently enabling? What are the loudest complaints about the technology team from the business? Where has the technology team failed to deliver against commitments, and what are the explanations? What are the technology team's most cherished beliefs about why they are doing what they are doing? This intelligence gathering is not about forming conclusions — it is about developing hypotheses that the first thirty days of direct observation will test. CTOs who arrive on day one with strongly formed views about what needs to change tend to misread the organization in ways that create early relationship damage. Those who arrive with well-formed questions tend to learn faster and make better early decisions.
Days 1-30: Listening and Diagnosis
The first thirty days should be dominated by structured listening rather than action. The new CTO who arrives with a transformation agenda and begins acting on it in the first month is making decisions with 2 percent of the information available to them — and signaling to the organization that the incoming conclusions matter more than the existing context. This is rarely the right approach and almost always creates organizational resistance that persists long after the decisions themselves have been updated. A structured listening tour includes 1:1 conversations with every member of the engineering leadership team, cross-functional conversations with the heads of product, finance, sales, and operations, and skip-level conversations with individual contributors across the engineering organization. Each conversation should follow a consistent framework: what is working well, what is not working well, what would you change if you had the authority, and what do you think I should prioritize in my first 90 days? Parallel to the listening tour, the technical assessment of the current state should be underway. Code review, architecture review, infrastructure audit, security assessment, and engineering process review are all inputs to a diagnostic picture that complements what the listening tour reveals. The technical assessment answers questions the listening tour cannot: not just what people think about the technology, but what the technology actually is and how it actually behaves.
Days 30-60: Synthesis and Direction Setting
By day thirty, a prepared CTO should have enough information to distinguish symptoms from root causes, to identify the two or three structural issues that are generating most of the problems being observed, and to develop a preliminary view of the sequenced interventions that would address them. This synthesis should be explicit — documented, debated with trusted advisors, and pressure-tested against evidence — rather than intuitive and implicit. The direction-setting conversation with the CEO and leadership team in this period is one of the most consequential of the first 90 days. It is the opportunity to share the diagnostic findings, to align on priorities, and to establish the mandate and resources required for the transformation agenda. CTOs who delay this conversation — waiting until they have a fully baked plan — miss the window when leadership is most receptive to new information and most likely to provide the organizational support required for change. Team assessments should be substantively complete by day 45. The new CTO needs to know who the indispensable performers are, who the strong performers who are underutilized are, and where there are capability gaps that will need to be addressed through hiring or development. Acting on these assessments — making personnel decisions, restructuring roles, beginning hiring — should begin in the second month once the assessment is grounded in sufficient evidence.
Days 60-90: Early Wins and Structural Changes
The second and third months should produce visible wins — not just planning and analysis, but actual changes that the organization can see and that demonstrate the direction the new CTO is taking. Early wins serve a specific organizational function: they build credibility, create momentum, and signal that the new CTO is able to translate diagnostic insight into operational improvement. The best early wins are chosen strategically: they address a problem that the organization has been aware of and frustrated by, they are achievable within the time and resource constraints of the period, and they demonstrate the kind of leadership and judgment that the new CTO wants to be known for. A CTO who chooses early wins based on what is technically interesting rather than what the organization values tends to build the wrong kind of credibility. Structural changes — team reorganizations, process redesigns, architectural commitments, hiring plans — that flow from the diagnostic findings should be communicated and begun in this period. The communication of these changes is as important as the changes themselves. People who understand the logic and evidence behind structural decisions are far more likely to support them than those who experience change as arbitrary or politically motivated.
Relationship Building: The Invisible Foundation
The technical and organizational work of the first 90 days is visible and measurable. The relationship building that makes all of it possible is less visible but no less important. A new CTO's ability to drive change is directly proportional to the quality of the relationships they have built with peers, direct reports, and the CEO — and those relationships are built or damaged in the first 90 days in ways that are difficult to fully reverse. Relationship building with the product organization is particularly important for CTOs who arrive into organizations with entrenched product-engineering tension. The new CTO who positions themselves as a defender of engineering against product pressure is making an organizational choice with lasting consequences. The far more effective approach is to invest heavily in the CPO or VP Product relationship — shared problem-solving conversations, genuine curiosity about the product perspective, and collaborative development of the shared planning processes that create structural alignment. The board relationship requires the same investment. Board members who understand the CTO's diagnosis of the technology situation and trust the CTO's judgment are powerful organizational allies when difficult decisions need to be made. CTOs who interact with the board only in formal presentations with carefully curated information tend to have weaker board relationships than those who invest in informal conversations that share both successes and challenges honestly. The first 90 days are the opportunity to establish the foundation of that trust.
Frequently Asked Questions
How quickly should a new CTO make personnel decisions?
Material personnel decisions — promotions, role changes, performance management — should wait until the listening and diagnostic phase is substantially complete, typically day 30 to 45. Decisions made before then are based on first impressions and political positioning rather than evidence. The exception is situations where an ongoing personnel issue is actively damaging the team — those situations require action regardless of how early in the tenure they arise.
What is the single most important relationship for a new CTO to invest in?
The CEO relationship is the most important. The CTO's ability to effect change depends on having a CEO who understands and supports the technology agenda — which requires that the CEO understands how technology enables business strategy, trusts the CTO's judgment on technology decisions, and has confidence that the CTO can translate technology context into business language. Building that relationship should be the new CTO's first priority.
How do you handle an inherited technical team that is not performing at the required level?
Performance issues in inherited teams require diagnosis before action. Are the performance problems caused by capability gaps, process failures, unclear expectations, or structural misalignment? Each cause requires a different response. Capability gaps may require development plans, role changes, or hiring. Process failures require new operating models. Unclear expectations require clarity setting. Structural misalignment requires reorganization. Acting on performance issues before diagnosing their causes leads to costly mistakes.
How should a new CTO communicate their findings to the engineering team?
Transparency with the engineering team about diagnostic findings builds trust that is critical for driving change. Share the honest assessment of current state — what is working and what is not — with as much specificity as possible. Accompany the diagnostic findings with a clear articulation of the direction you intend to take and why. Engineers who understand the rationale for change are dramatically more likely to support it than those who experience change as imposed from above without explanation.
Related Articles
What a Fractional CTO Actually Does
Most companies hire a fractional CTO expecting a part-time employee. What they get — when they get the right person — is an operating partner who reshapes how technology creates value across the enterprise.
Read →
Technology Due Diligence: A PE Firm's Guide
Technology due diligence has evolved from a box-checking exercise into a value-creation lever. PE firms that treat it as the former consistently overpay for assets and underperform on returns.
Read →
AI Strategy for Mid-Market Companies
Mid-market companies face a distinctive AI challenge: enough scale to benefit materially from AI adoption, but insufficient resources to build the infrastructure that makes large-enterprise AI initiatives possible. The answer is not a scaled-down enterprise strategy — it is a fundamentally different one.
Read →
The Crimson Bench · Est. 2002 · Founded in New York City
Deploy an Executive in 48 Hours
Verified corporate accounts only. Ivy League-educated. Flat-rate pricing. 14-day no-cause cancellation.
25,000+ Ivy League Executives · 150,000+ Global Consultants · 48-Hour Deployment