The COO's First 90 Days: A Practical Playbook

A day-by-day framework for newly appointed COOs to diagnose the operation, build trust with the team, and establish credibility with the CEO and board in the first 90 days.

2026-01-1214 min read

Days 1–30: Listen, Learn, and Resist the Urge to Fix

The most common mistake a new COO makes in the first 30 days is attempting to demonstrate competence through action. The instinct is understandable: you were hired to improve the operation, you have relevant experience, and you can see problems that need to be fixed. The problem with early action is that it is based on incomplete information. Organizations are complex systems with histories, relationships, and informal dynamics that are invisible to the newcomer. Actions taken before that context is understood often address symptoms rather than root causes, damage relationships that would have been useful, and create defensiveness in the team at exactly the moment when trust-building is the priority. The first 30 days should be structured as an intensive listening and learning period. The objective is to develop a complete and honest picture of the current state of the operation: what is working, what is broken, why it is broken, and what the team's theory of the case is about the highest priorities. This requires structured conversations with every member of the operations leadership team, cross-functional peers, and—critically—frontline employees who can provide a perspective on operational reality that differs systematically from what leadership sees. The listening tour should include a specific question: "What would you prioritize if you were in my position, and what is the biggest thing holding this organization back?" Asked with genuine curiosity rather than as a ritual, this question surfaces priorities and blockers that would never appear in a formal report, and it begins building the trust that effective leadership requires. People who believe their perspective has been genuinely heard are more likely to engage constructively with the changes that will follow.

The Operational Diagnostic: What to Assess and How

Concurrent with the listening tour, the new COO should be conducting a structured diagnostic of the operation's current state. This diagnostic should cover five domains: financial performance (are costs tracking to plan, and are the right cost categories being managed?), process quality (what is the defect and error rate in core operational processes?), team capability (do you have the right people in the right roles?), systems and data (are the tools and information infrastructure adequate for the business's current and near-term requirements?), and strategic alignment (is the operations organization focused on the right priorities given the company's strategic direction?). The financial diagnostic should include a detailed review of the operations P&L, unit economics for key activities (cost per order, cost per customer interaction, cost per unit produced), and comparison of cost structure against relevant industry benchmarks. This analysis frequently reveals cost categories that are materially out of line with peers—either because of efficiency gaps that represent improvement opportunities or because of conscious investments in capabilities that the operation believes differentiate it. Understanding which category a given cost position represents is essential for making informed decisions about where to invest and where to reduce. Process quality diagnosis is best conducted through direct observation—spending time in the warehouse, the service center, the production floor, or wherever the operational work is done—combined with a review of available performance data. Direct observation surfaces the gap between documented process and actual practice, and it invariably reveals informal adaptations that the team has made to work around inefficiencies in the formal process. These adaptations are both a source of intelligence about process failure modes and a target for formalization if they represent genuine improvements.

Days 31–60: Establish Trust and Prioritize

The second month transitions from passive listening to active engagement. By day 30, you should have a clear enough picture of the operation to form a preliminary hypothesis about the highest-priority improvement opportunities and the most significant organizational risks. The discipline of the second month is testing those hypotheses with the people who have the most relevant knowledge, refining them based on that engagement, and beginning to communicate your emerging perspective to the team. Building trust with the operations team during this period requires demonstrating two things simultaneously: competence (that you understand the work and have relevant expertise) and character (that you are honest, fair, and genuinely committed to the team's success rather than to your own agenda). Competence is demonstrated through the quality of your questions and the sharpness of your insights in early conversations; character is demonstrated through how you handle the first situations where you have the opportunity to be fair or unfair, honest or diplomatic. Prioritization is the most consequential early decision. The diagnostic will have surfaced more problems than can be addressed simultaneously. A new COO who launches 15 improvement initiatives in the first 60 days will overwhelm the organization and produce a culture of initiative fatigue rather than improvement momentum. The discipline is to identify the three to five highest-priority opportunities—those where improvement would produce the most meaningful impact on business performance and where success is achievable within 90–120 days—and to focus the organization's improvement energy on those priorities while explicitly deferring the others.

Days 61–90: Deliver Early Wins and Set the Long-Term Agenda

The third month should produce visible evidence that the COO's arrival is changing outcomes, not just activities. Early wins—improvement results that are meaningful enough to be noticed but achievable within the 90-day window—serve multiple organizational functions. They build credibility with the CEO and board, who are assessing whether the appointment of a new COO is generating returns. They build momentum with the operations team, who need evidence that the improvement agenda is real rather than another cycle of management initiatives that will fade. And they provide the new COO with the organizational credibility to take on the harder, longer-cycle improvements that will define the role. The selection of early wins is a strategic choice, not simply a function of what is easiest to fix. The best early wins are those that address problems the team has been frustrated by for some time, that demonstrate the COO's understanding of the operation's priorities, and that require cross-functional collaboration to achieve—signaling that the COO can navigate the organizational dynamics that have previously prevented progress. Alongside early win delivery, the third month is the time to establish the COO's long-term agenda: the 12–18 month operational improvement roadmap that will guide investment and priority decisions going forward. This agenda should be developed collaboratively with the operations leadership team—incorporating their priorities and building their ownership—while being clearly owned and sponsored by the COO. The agenda, once socialized with the CEO and board, becomes the operational plan against which the COO's performance will be evaluated.

Managing the CEO Relationship in the First 90 Days

The COO-CEO relationship is the most important organizational relationship the new COO must navigate in the first 90 days. The nature of this relationship varies enormously: in some organizations, the COO is a strategic partner to the CEO with broad authority and independent decision-making latitude; in others, the COO is an operational executor of the CEO's strategy with a narrowly defined mandate. Understanding the operating model that the CEO expects before assuming a broader mandate is among the most important early learning investments a new COO can make. The most productive first-90-days COO-CEO dynamic is one characterized by structured communication: regular check-ins (weekly at minimum in the first 90 days) where the COO shares observations, preliminary conclusions, and emerging priorities, and where the CEO provides context on the organization's history and strategic direction that the COO could not have learned from the diagnostic process alone. These conversations should be explicitly structured as two-way information exchange, not reporting sessions—the COO learning from the CEO's context as much as the CEO learning from the COO's observations. Disagreement with the CEO about operational priorities is inevitable in the first 90 days and must be navigated carefully. The most effective approach is to surface disagreements early, in private, and with the analytical backing that elevates the conversation from opinion difference to evidence-based discussion. A new COO who either suppresses disagreement (deferring to the CEO's view to avoid conflict) or surfaces it publicly before the relationship has sufficient trust will struggle to build the influence needed to drive meaningful operational improvement.

Frequently Asked Questions

How quickly should a new COO make personnel changes?

Personnel decisions made in the first 30 days are almost always premature—based on insufficient information about performance, context, and organizational relationships. The exception is situations where a clear performance failure or ethical issue is evident before the 30-day window. Most experienced operators recommend making personnel decisions no earlier than day 60 and ideally after day 90, when the diagnostic is complete, the team has been observed in their actual roles, and the COO has enough organizational credibility to make changes without triggering defensive dynamics that undermine the broader improvement agenda.

What is the single most important thing a new COO should accomplish in the first 90 days?

Establish a clear theory of the case—a well-evidenced, clearly articulated view of where the operation currently stands, why it is where it is, and what the most important priorities are for the next 12–18 months. A COO who completes the first 90 days with this theory of the case developed, tested with the leadership team, and aligned with the CEO has the foundation for effective operational leadership. Everything else—early wins, process improvements, organizational changes—is tactical execution against that strategic foundation.

How should a new COO handle the team left behind by the previous COO?

The team inherited from a predecessor is an asset until proven otherwise. The assumption that the previous leadership team was misaligned with the operation's needs is both presumptuous and typically incorrect—most operational teams contain talented people who have adapted, for better or worse, to the management context in which they have operated. The new COO's job in the first 90 days is to assess individuals on the basis of observed performance and capability in the current context, not on the basis of assumptions carried forward from the previous leadership regime.

What should a new COO avoid doing in the first 90 days?

Five common failure modes in the first 90 days: announcing a major reorganization before completing the diagnostic; making public commitments to specific outcomes before fully understanding the levers; undermining the previous COO's decisions without understanding the context behind them; spending most of the first 90 days in executive meetings rather than on the front lines where the work is done; and building an agenda based on replicating what worked in the previous role rather than understanding what the specific organization needs. The last failure mode is particularly common among experienced COOs who have a strong operational playbook from prior experience.

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.

Deploy Now →Start with a $1,500 Diagnostic

25,000+ Ivy League Executives · 150,000+ Global Consultants · 48-Hour Deployment