COO Transition Plan: A 30/60/90-Day Roadmap That Works
The fastest way to fail as a new COO is to arrive with a plan. The second fastest is to arrive with no plan at all. Your job in the first 90 days is to earn the right to change things by first proving you understand how the company actually runs, then shipping one improvement people can see and feel.
A workable transition splits into three phases. Days 1–30 are for listening and mapping: who does what, where work snags, which numbers the business watches. Days 31–60 are for judgment: pick two or three problems worth solving and deliver one visible win. Days 61–90 are for ownership: you stop describing what you found and start being accountable for what happens next.
This roadmap gives you the specific moves for each phase, what strong versus weak execution looks like day to day, and the traps that quietly derail capable operators. It assumes you are a real second-in-command with cross-functional scope, not a title with no teeth.
Before day one: the intake that decides month one
Most month-one mistakes come from walking in blind. The fix is a structured intake in the two to four weeks before you start, or in your first days if you had no runway.
Read four things before you form a single opinion: the last three board decks, the operating budget with actuals against plan, the org chart with headcount and open roles, and whatever the company treats as its scorecard. If a document does not exist, that absence is a finding — a company with no shared scorecard has no shared definition of "good," which becomes one of your first jobs to build.
Strong looks like arriving on day one able to name the top three revenue lines, the biggest cost centre, the two metrics the CEO checks every Monday, and the people everyone informally routes decisions through. Weak is spending week one asking questions the onboarding pack already answered. Settle the logistics too: system access, expense authority, and your exact decision rights — knowing whether you can approve a $50,000 spend or need sign-off changes how you operate from hour one. If you are still building the fundamentals, review the core competencies every COO needs before you start, not after your first stumble.Days 1–30: listen, map, and find the real problems
Your only deliverable for the first 30 days is understanding. Resist the urge to fix anything, because you cannot yet tell a genuine problem from a workaround that exists for a good reason nobody has told you.
Run a listening tour: 30-to-45-minute one-on-ones with every direct report, the CEO, your executive peers, and a sample of frontline staff two or three levels down. Ask the same open questions each time — What works well that I should not touch? What is broken that everyone has given up on? What would you fix first? Patterns emerge fast. When three unconnected people name the same broken handoff between sales and delivery, you have found something real, not one person's grievance.
Alongside the conversations, map the operation. Pick the two or three core processes that carry the most value or pain (order-to-cash, hire-to-productive, incident-to-resolution) and walk each one end to end. A simple maturity read helps: is this process ad hoc and heroic, repeatable but undocumented, standardised, or measured and improving? Most companies are a mix, and naming where each process sits gives you a defensible baseline. A structured operations assessment turns this from a gut feel into something you can show the CEO.
Strong in month one means you can draw the value chain from memory and point to the two places work reliably stalls. Weak means you have opinions about fixes but cannot explain the current process — so your fix breaks something downstream you did not see. Say almost nothing about changes yet; the credibility you are building is "this person listens before acting."Days 31–60: pick your battles and ship one visible win
By day 31 you have a list of everything wrong with the company. The discipline of month two is refusing to act on most of it. Choose two or three problems using two filters: does solving it matter to the outcomes the CEO cares about, and can you show progress within 30 to 60 days? A problem that scores high on both is where you start.
Then commit to one early win that is genuinely visible. It proves you can move the organisation and buys permission for the harder work ahead. The best wins are obvious once someone owns them: a weekly report assembled by hand that can be automated, an approval that bounces between four inboxes, a recurring complaint that maps to a single broken step. A well-run process optimization on one painful workflow beats a grand reorganisation nobody asked for.
Handle the win like a small project, not a decree. Name the current-state cost in plain terms ("this delay adds three days to every order"), agree the target with the team who owns the work, change it with them rather than to them, and measure before and after. When it lands, share the result and credit the people who did it. This is also where you stand up the measurement layer, because you cannot manage what nobody counts. If there is no real scorecard, start with a handful of operational metrics that actually drive decisions, not a 40-line dashboard nobody reads.
Strong in month two: one improvement is live, measured, and credited to the team, and the CEO heard about it from someone else. Weak: five initiatives open, none finished. Finishing one thing beats starting ten.The 30/60/90 view at a glance
The three phases have distinct jobs, and confusing them is the most common error. Here is what each phase asks of you and how to tell whether you are on track.
| Phase | Primary job | Strong signal | Weak signal |
|---|---|---|---|
| Days 1–30 | Understand the business | You can map the value chain and name the two real bottlenecks | You are proposing fixes before you can explain the current process |
| Days 31–60 | Prioritise and prove | One visible win is shipped and measured | Many initiatives open, none finished |
| Days 61–90 | Own the outcomes | You present a 6–12 month operating plan the CEO endorses | You are still describing problems, not accountable for results |
Days 61–90: from describing problems to owning outcomes
The shift in month three is subtle but total. In months one and two you were a careful newcomer. From day 61 you are the operator on the hook. The tangible output is a 6-to-12-month operating plan you present to the CEO, and where appropriate the board: the three to five outcomes you will be accountable for, the metrics that prove them, the resources you need, and the sequence you will run them in.
Ground the plan in what you learned, not a template you brought from your last company. If the listening tour surfaced a broken sales-to-delivery handoff, name it, quantify its cost, and set a dated commitment to fix it. This is also when you make the structural or people decisions you have been holding. If a direct report is clearly in the wrong seat, address it now — doing it earlier looks reactive, and doing it much later means you tolerated a known problem. Pair any structural change with a real change management approach so it lands as a considered move, not a surprise.
Guard against two failure modes. Over-reach: a reorganisation or system replacement so large it consumes a year and delivers nothing measurable for six months. Drift: staying in listening mode past the point the organisation expects you to lead, which reads as indecision. Strong at day 90 is a CEO who can repeat your plan back in a sentence. Weak is a polished strategy document no one else can act on.
The relationship that quietly decides everything
Everything above depends on one relationship being healthy: yours with the CEO. The COO role only works when the CEO genuinely wants a second-in-command and has ceded real operational ground, rather than hiring a title while keeping every decision. Test this early. In your first two weeks, agree which decisions are yours to make alone, which need a heads-up, and which need joint sign-off, and write it down. Ambiguity here is the single most common reason strong COOs quit within a year.
Establish a regular one-on-one and treat it as the operating system of the partnership: bring decisions and trade-offs, not a list of activities. The healthiest pairings run on a clear division of labour — the CEO facing outward (vision, investors, key customers), the COO facing inward (execution, operations, the team) — though the split varies. Getting the COO and CEO partnership right in the first 90 days matters more than any single win, because a misaligned pair undoes good work faster than you can produce it.
Common ways COO transitions go wrong
The predictable failures repeat. Moving too fast is the classic: changing things before you understand why the current setup exists, breaking a workaround that was holding something together. Ignoring culture is next: a daily-standup that suited a 20-person startup can suffocate a 2,000-person firm. The quieter, costlier traps are chasing process while the leadership team stops trusting you, and misreading your mandate — claiming authority you were never given, or not taking authority the CEO expected. Nearly all trace back to two habits: listening long enough in month one, and settling decision rights in writing.
Key takeaways
- Listen before you fix. In month one you cannot tell a real problem from a load-bearing workaround, so map the operation before you change it.
- Do the intake before day one. Read the board decks, budget, org chart, and scorecard so week one is for observing, not catching up.
- Ship one visible, measured win by day 60. Finishing a single improvement beats launching ten that never complete.
- Settle decision rights with the CEO in writing, early. Ambiguity here is the top reason capable COOs leave within a year.
- Present an outcome-owned plan around day 90. Move from describing problems to owning a few dated, measured commitments.
- Respect culture and pace. Your last company's operating model is a hypothesis, not a blueprint.