First 90 Days as COO: Operational Priorities and Quick Wins

What new COOs actually walk into

The first week as a new COO reveals a gap that almost no interview process prepares you for: the distance between how leadership described the business and what's actually happening on the ground.

Sometimes that gap is small. More often, it looks like this: obligations tracked in six different systems with no single owner, a weekly cadence built around status meetings that produce no decisions, critical processes that exist only in the heads of two or three people, and a team that's simultaneously overworked and unclear on what "done" means for their function.

This isn't dysfunction — it's the ordinary state of a company that has grown faster than its operations infrastructure. It's also exactly what a COO is hired to fix. But the instinct to fix everything immediately is the most common mistake new COOs make. The first 90 days aren't about change. They're about understanding the terrain clearly enough to change the right things in the right order.

What you do in these first three months sets your credibility, your team's trust, and the trajectory of every initiative that follows. Getting the sequence right matters as much as getting the substance right.

The first 30 days: map before you move

Your primary goal in the first month is a clear operational picture — not to fix anything, not to impress anyone, but to understand what's actually happening well enough to act on it with confidence.

This means asking a specific set of questions and building answers that don't depend on any single person's memory or interpretation:

• Where does the work live? What systems, tools, and informal channels does each team use to track obligations, deadlines, and documents? Map all of them — the official ones and the shadow ones.
• Who owns what? For every significant ongoing obligation, identify the named owner. Where ownership is ambiguous or shared, note it — these are your highest-risk gaps.
• What's the cadence? How do teams currently surface status to each other and to leadership? What works, what produces noise, and what's missing entirely?
• Where are the real bottlenecks? Not where leadership thinks they are — where the people doing the work say they are. Ask individually, not in group settings where political dynamics mute honest answers.
• What does "done" mean? For each major obligation type, is completion defined clearly? Is there a consistent standard for what documentation "done" requires?

The output of this month isn't a presentation. It's a working map: an honest picture of the operational landscape you've inherited, including the gaps you'll need to close and the strengths you should protect. Don't let the pressure to show momentum short-circuit this phase — decisions made before you have an accurate map tend to solve the wrong problems.

Days 31–60: establish visibility and claim your quick wins

By day 30, you should know where the operational data lives and where it doesn't. The second month is about making that data visible — to you and to the leadership team — and using what you've learned to close a small number of specific gaps quickly.

Establish the visibility layer first. Before you can manage operations, you need to see operations. This means getting task completion rates, upcoming deadlines with current status, and ownership coverage into a format that doesn't require calling a meeting to check. It doesn't have to be perfect — a functional view of who owns what and what's due when, visible at the team level and rolled up to leadership, is worth more than a sophisticated system that takes six months to build. See our guide on building real operational visibility for your C-suite for the metrics that matter most.

Then target quick wins that reinforce the right culture. The best early COO wins share a common trait: they make the team's existing work more visible and more valued, rather than replacing it. Examples:

• Clear ownership on the top five previously-ambiguous obligations
• One recurring process that was undocumented, now with a clear owner and completion criteria
• A weekly operations review — even a 30-minute version — that gives leadership a standing view of what's on track and what's at risk, without requiring anyone to compile a status report beforehand

The goal is to demonstrate the value of operational structure through a specific example, not to announce that everything is changing. Early credibility comes from solving a visible problem that the team already feels — not from rebranding existing work with a new framework.

For the cadence piece, the weekly operations review framework offers a practical agenda for running a useful review without turning it into a status theater exercise.

Days 61–90: build the foundation that compounds

The third month is where you shift from quick wins to foundation building — the structural changes that will still be paying off two years from now. This is also where COOs most commonly over-rotate: trying to implement too much, too fast, before the team has the bandwidth or the trust to absorb it.

The three investments that compound most reliably:

1. A single operational source of truth. If your first 60 days revealed that operational data is scattered across six tools, the long-term fix is consolidation — not perfect from the start, but a clear direction. Work toward a single system where tasks, documents, owners, and deadlines live together. The ROI on this is not just efficiency; it's the ability to answer operational questions quickly, retain institutional knowledge through team changes, and generate the leadership-level roll-up that eliminates status meetings as an information-gathering mechanism.

2. Named owners for every significant obligation. By day 90, every active obligation that matters to the business should have exactly one named owner. Not a team, not a committee — one person who is responsible for ensuring completion and escalating when it's at risk. This is the most mechanical improvement you can make with the highest operational leverage.

3. A forward-looking view for the CEO or board. The COO's primary interface with the CEO in year one is operational status. Build a monthly or quarterly summary that answers three questions: what's on track, what's at risk, and what requires a decision? When you can produce this from live operational data rather than compiling it manually each time, the quality improves and the cost drops. Executives who get consistent, reliable operational reporting from their COO grant that COO more autonomy — because they can trust that problems won't be hidden.

Common traps in the first 90 days

Most first-90-days failures follow predictable patterns. Knowing them in advance is the easiest way to avoid them.

Moving too fast on the wrong problems. The problems that were most visible in the hiring conversation — the ones the CEO or board called out explicitly — are rarely the ones that need to be fixed first. They're usually the symptoms. Use your first 30 days to find the root cause before acting.

Building systems instead of changing behaviors. A new tool or framework is only useful if the underlying behaviors change. COOs who spend their first 90 days implementing software without changing how the team works around it end up with an expensive system that nobody trusts. Start with behavior and expectations; layer in tooling once the behaviors are established.

Prioritizing breadth over depth. The instinct to have opinions on everything signals energy but rarely builds credibility. Pick two or three areas where you'll go deep in the first 90 days, and let others run their functions without heavy interference until you have the context to add value there.

Conflating busy-ness with progress. The first 90 days are genuinely hectic, and it's easy to mistake activity for momentum. Track your outputs against explicit goals — the ownership gaps you've closed, the visibility layer you've built, the processes you've documented — not the number of meetings you've attended.

Skipping the team. COOs who build relationships with their direct reports and a few key individual contributors in month one are consistently more effective by month three than those who stay in leadership-level conversations. The operational picture you need is almost always held by the people closest to the work.

What good looks like at day 90

The COO who exits the 90-day window in a strong position typically has six things in place:

1. An accurate operational map. You know where every significant obligation lives, who owns it, what "done" means, and what the current status is. You didn't have to ask three people to compile this — it's visible.
2. Named owners across the board. Every active obligation has one person responsible for its completion. Ambiguous ownership has been resolved or is actively being resolved.
3. A standing review cadence. There's a recurring forum — weekly or biweekly — where operational status is reviewed proactively. The agenda doesn't change based on who's in the room. Problems surface there, not in ad hoc escalations.
4. Two or three tangible wins the team can see. Not announcements about what you're going to do — actual improvements that the people doing the work feel as easier or clearer than before you arrived.
5. A forward-looking view for leadership. The CEO and board can see what's on track, what's at risk, and what requires a decision — from operational data, not a manual report.
6. A clear 90-to-180-day plan. Based on what you've learned, you know the next three months' priorities. These aren't surface-level process fixes — they're the structural changes that will compound over the following year.

The 90-day window doesn't produce a finished operation. It produces the foundation and the credibility to build one. COOs who come out of it with all six of these in place are in position to move significantly faster in months four through twelve — because their team trusts them, their leadership team trusts their data, and they have an honest picture of the terrain they're working with.

If you're stepping into a COO role and looking for a system to support this foundation — operational data that centralizes tasks, owners, documents, and deadlines in a format that's visible at both the team and leadership level — Sintris is built for exactly this use case. You can start a free trial and have a working operational view in your first week.

If you're a founder still deciding whether to make the COO hire, the COO readiness framework covers the signals that indicate it's time and what to prepare before the hire.