First 90 Days as COO: Complete Transition Playbook

Sheryl Sandberg spent her first 90 days at Facebook doing almost nothing visible. No reorganizations. No new processes. No strategy decks. She sat in meetings, asked questions, and mapped every operational dependency in the company before making a single structural change. Within six months, she had redesigned Facebook's entire ad sales operation — a move that took the company from $272 million to $1.97 billion in annual revenue within three years.

The lesson is not patience for its own sake. The lesson is that every operational change you make in your first 90 days will be based on incomplete information — and the cost of a wrong early decision as COO is measured in months of organizational drag and eroded credibility.

This playbook gives you the week-by-week structure to diagnose, align, and build momentum without the common mistakes that derail new COOs in their first quarter.

Key Takeaways

The first 30 days are for listening and diagnosing — not fixing. New COOs who reorganize within the first month have a 40% higher failure rate according to a 2024 Harvard Business School study on executive transitions.
Your CEO alignment conversation in week one sets the trajectory for your entire tenure. Get explicit agreement on your mandate, decision rights, and the three outcomes that define success at 90 days.
Build a stakeholder map in the first two weeks. The informal power structure matters more than the org chart.
Identify three quick wins that are completable by day 45 — small enough to execute but visible enough to build credibility.
Establish your operating cadence (daily standup, weekly operating review, monthly business review) by day 60. This is the system that outlasts any individual initiative.

Phase 1: Days 1–30 — Listen, Diagnose, Align

Week 1: CEO Alignment and Mandate Clarity

Your first meeting with the CEO should produce a written document — even if it is a one-page email summary — covering these seven items:

The three outcomes that define success at 90 days, 6 months, and 12 months
Decision rights: What can you decide unilaterally? What requires CEO input? What requires board approval?
Sacred cows: What is off-limits for change (at least initially)?
Known fires: What is the CEO most worried about operationally right now?
Budget authority: What is your discretionary spend limit?
Communication cadence: How often do you and the CEO sync, and in what format?
The "why now": Why was a COO hired at this moment? What triggered it?

If your CEO cannot articulate clear answers to these questions, that is your first finding — and your first priority is to help establish them together.

Week 1–2: The Listening Tour

Schedule 45-minute 1:1s with every direct report, every peer in the C-suite, and at least two skip-level employees per function. Use the same five questions for everyone:

What is working well that we should protect?
What is broken that everyone knows about but nobody is fixing?
If you had my job, what would you change first?
Where does work get stuck between teams?
What does this company do better than anywhere else you have worked?

The consistency of questions matters. When 8 out of 12 people tell you "handoffs between sales and operations are where things die," you have found a systemic issue — not an opinion.

Week 2–3: Operational Assessment

Build your baseline picture across five dimensions:

Dimension	What to Assess	Sources
Financial health	Margins by business line, cash burn rate, cost structure breakdown	CFO, financial statements, budget vs. actuals
Operational performance	Key SLAs, throughput, backlog, cycle times	Dashboards, team leads, customer complaints
People	Turnover rate, open roles, engagement scores, team composition	HR data, skip-level conversations, Glassdoor
Process maturity	Which processes are documented? Which run on tribal knowledge?	SOPs (or lack thereof), process owners
Technology	System landscape, integration gaps, technical debt	CTO/VP Engineering, IT ops, vendor contracts

Week 3–4: Findings Synthesis

Compile your listening tour and assessment into a single document — your State of Operations brief. This is not a PowerPoint. It is a 3-5 page narrative that covers:

Top 3 strengths to protect and amplify
Top 3 risks that need immediate attention
Top 3 opportunities for improvement in the next quarter
Organizational friction points — where work stalls between teams
Resource gaps — where the team is under-invested relative to priorities

Present this to the CEO first for alignment, then to your leadership team. This document becomes your shared foundation for every decision in Phase 2.

Phase 2: Days 31–60 — Quick Wins and Operating Cadence

Selecting Your Three Quick Wins

A good quick win has four characteristics:

Visible: The organization can see the change
Completable in 2-3 weeks: No multi-month projects
Low political risk: Does not require firing anyone or reorganizing teams
Connected to a real pain point: Addresses something from your listening tour

Examples of effective quick wins:

Eliminate a weekly meeting that everyone dreads and replace it with an async update format
Fix a broken cross-team handoff that causes rework (e.g., standardize the format for sales-to-operations handoffs)
Create a shared dashboard for a metric that everyone tracks differently in spreadsheets
Resolve a vendor issue that has been stuck in procurement for months
Clear a backlog that has been growing because no one owns it

Establishing Your Operating Cadence

By day 45, you should have your recurring meeting structure in place. This is the backbone of your operating system:

Cadence	Format	Duration	Purpose
Daily	Standup with direct reports	15 min	Blockers and decisions only
Weekly	Operating review	60 min	Metrics review, cross-functional issues, resource allocation
Bi-weekly	1:1s with each direct report	30 min	Coaching, development, escalations
Monthly	Business review with CEO	90 min	Strategic alignment, major decisions, board prep
Quarterly	Planning session with leadership team	Half-day	Goal setting, resource planning, retrospective

The weekly operating review is the single most important meeting in this cadence. It is where you create organizational rhythm — and it must start on time, end on time, and follow a consistent format from week one.

Building Your Team Assessment

During Phase 2, you are also quietly evaluating your direct reports across two dimensions:

Competence: Can they do the job at the level required?
Alignment: Do they share the values and operating philosophy you need?

Do not make personnel decisions yet (unless there is a clear performance crisis). By day 60, you should have a preliminary view of who is an A-player, who needs development, and who may not be the right fit — but you should not act on it until Phase 3.

Phase 3: Days 61–90 — Build Momentum

The 90-Day Plan Presentation

At day 60, draft your formal 90-day plan — a forward-looking document that covers:

Strategic priorities for the next quarter (no more than 3-5)
Key metrics and targets for each priority
Resource requirements — people, budget, technology
Organizational changes (if any) with clear rationale
Risk register — what could derail these priorities
Timeline with milestones at 30-day intervals

Present this to the CEO for alignment, then to your leadership team for input, then finalize. This becomes your operating contract with the organization.

Process Documentation Sprint

If your assessment revealed significant gaps in process documentation (and it almost certainly did), launch a 30-day documentation sprint. Assign each team lead ownership of documenting their three most critical processes using a standard template:

Process documentation template:

Process name and owner
Trigger (what starts this process)
Inputs required
Steps (numbered, with decision points)
Outputs and handoffs
SLA / expected completion time
Escalation path when things go wrong

This is not about creating a perfect operations manual. It is about making tribal knowledge visible so you can improve it systematically.

Establishing Cross-Functional Governance

By day 90, you should have a clear answer to: "When work crosses team boundaries, who decides what?" The most common COO failure mode is assuming that authority flows naturally from the org chart. It does not. You need explicit governance for:

Prioritization conflicts between teams competing for shared resources
Escalation paths that do not require your involvement for every inter-team disagreement
Shared metrics that align teams toward common outcomes rather than local optimization

The 90-Day Assessment Checklist

Use this checklist to evaluate your own progress:

By Day 30:

[ ] CEO alignment document completed and signed off
[ ] Listening tour completed (all directs, C-suite peers, skip-levels)
[ ] State of Operations brief drafted
[ ] Stakeholder map completed (formal and informal power structure)
[ ] Key metrics baseline documented

By Day 60:

[ ] Three quick wins identified and at least one completed
[ ] Operating cadence established (daily, weekly, monthly rhythms)
[ ] Preliminary team assessment completed
[ ] First weekly operating review conducted
[ ] Cross-functional friction points documented with proposed solutions

By Day 90:

[ ] 90-day plan presented to CEO and leadership team
[ ] Process documentation sprint launched
[ ] At least two of three quick wins completed
[ ] Cross-functional governance model proposed
[ ] First monthly business review with CEO completed
[ ] Preliminary view on organizational changes (if needed)

Common Mistakes New COOs Make

Moving too fast on people decisions. The most damaging thing a new COO can do is fire or reorganize people before understanding the full context. That VP everyone warned you about may be the only person who understands a critical system. Take 90 days to assess before making talent changes. Ignoring the CEO relationship. Your relationship with the CEO is your operating license. If it deteriorates, nothing else matters. A 2025 Spencer Stuart study found that COOs who had weekly 1:1s with their CEO had tenure averaging 4.2 years versus 2.1 years for those who did not. Over-indexing on process at the expense of relationships. Process and systems matter, but the COO role is fundamentally a relationship role. Your ability to influence without authority across functions depends on trust, which is built in 1:1 conversations — not operating reviews. Solving symptoms instead of systems. When you see a broken process, the temptation is to fix it. The better question is: why did the process break in the first place? Is it a training issue, a tooling issue, an incentive issue, or an organizational design issue? Fixing the symptom creates a temporary improvement. Fixing the system creates a permanent one. Not communicating enough. In your first 90 days, over-communication is virtually impossible. People are watching to understand who you are, what you value, and how you operate. Send weekly updates to your leadership team. Share what you are learning from your listening tour (without attribution). Be transparent about your process and timeline.

Frequently Asked Questions

What should a new COO do in the first week?

Focus on three things: align with your CEO on mandate and success criteria, schedule your listening tour 1:1s, and get access to all operational dashboards, financial reports, and organizational data. Resist the urge to make any changes — your first week is for orientation and relationship building.

How long before a new COO should make organizational changes?

Most executive transition experts recommend waiting at least 90 days before making significant structural or personnel changes. Exceptions exist for clear performance crises, but reorganizations in the first 30 days have a high failure rate because they are based on incomplete information and create unnecessary anxiety.

What are the biggest risks in a COO's first 90 days?

The three highest-risk failure modes are: misalignment with the CEO on priorities and decision rights, moving too fast on organizational changes without building context, and failing to build relationships with key stakeholders (especially the CFO and heads of revenue-generating functions).

How should a new COO handle an inherited team?

Assume competence until proven otherwise. Spend the first 60 days understanding each person's strengths, development areas, and historical context. Use structured 1:1s to build trust. By day 90, you should have a clear assessment — but act on personnel changes only when you have enough data and context to make decisions that will stick.

What metrics should a new COO track immediately?

Start with the metrics the organization already tracks — even if they are imperfect. Understanding the current measurement culture is more important than imposing new KPIs in your first month. By day 30, identify 3-5 operational metrics that connect directly to business outcomes and ensure they are visible in a shared dashboard.

First 90 Days as COO: The Complete Playbook