What I Actually Do in My First 90 Days

Most executives spend their first 90 days listening. I spend mine fixing.

That’s not a brag. It’s a structural reality. When a founder brings in a fractional COO or Chief of Staff, they’re not hiring someone to observe. They’re hiring someone because something — often several things — has quietly broken, and the company is scaling faster than its operating system can handle.

The “listen first” advice exists for a reason: premature action based on incomplete information is a real failure mode. But there’s another failure mode nobody talks about. It’s the executive who spends 90 days in discovery while the team keeps bleeding, the process debt keeps compounding, and the founder keeps wondering when they’re going to see a return on the hire.

Here’s what I actually do.

Days 1–30: Diagnose before you prescribe

The first month is diagnostic, not passive. There’s a difference.

Passive listening is attending meetings, absorbing culture, waiting for someone to hand you a problem. Diagnostic listening is structured. You’re running an audit while appearing to do nothing dramatic.

In the first 30 days, I’m mapping four things:

→  Where decisions are actually being made. The org chart tells you the official story. Shadow it for a week and you’ll find the real one. Who does the CEO call when something breaks? Which team lead is the de facto decision-maker in their space, with or without the title? These people are your leverage points, and they’re almost never labeled on a slide.

→  Where work is disappearing. Every organization has a set of tasks that exist in theory and vanish in practice. Projects that get greenlit and stall. Requests that hit someone’s inbox and die. I map the disappearances because they reveal where accountability is unclear and where process is absent.

→  What the team is afraid to say. This takes trust, which takes time — but it doesn’t take 90 days. By week two or three, if you’ve shown people that you’re not a political threat and you’re not reporting everything back to the CEO, someone will tell you the real thing. The thing nobody put in the deck. That’s usually where the problem actually lives.

→  What the data says that nobody’s reading. Most companies at the scaling stage have more data than they think and less insight than they need. I spend time in whatever systems are running — HRIS, project management, financial reporting — not to build a dashboard, but to find the number that explains what’s happening. Usually there is one. Usually nobody’s looked at it lately.

The goal of month one is a clear diagnostic. Not a presentation. Not a strategy deck. A clear-eyed answer to: what are the three things most likely to break this company in the next 12 months, and in what order?

Days 31–60: Stabilize the highest-risk thing first

Month two is about stopping the bleeding before you try to grow new tissue.

Most founders want to skip to growth. That’s natural — they hired an ops leader to scale. But you cannot scale a broken system. You just break it faster at higher cost.

The highest-risk item is usually one of three things: a people problem, a process gap, or a compliance exposure. In my experience, it’s rarely the thing the founder thought it was when they brought me in.

In one engagement, I came in thinking the priority was efficiency. What I found was a retention problem masquerading as a recruitment problem. We weren’t losing candidates — we were losing people six to twelve months in. The fix wasn’t a better hiring funnel. It was a talent management and development framework that gave people a reason to stay.

Result: 40% increase in engagement and retention. 20% reduction in unnecessary costs.

The move in month two is to pick the highest-risk item and fix one thing well, not five things partially. A single visible win in month two does more for your credibility — and for the team’s confidence — than a comprehensive plan that’s still in progress at month six.

Days 61–90: Build the operating infrastructure for what comes next

By month three, you should have a diagnostic in hand and at least one stabilized risk. Now you can build.

This is the part that varies most by company, because it depends entirely on what the founder is trying to do in the next 12 to 18 months. Raise a round? Expand to a new market? Double headcount? Each of those has a different operational requirement, and the infrastructure you build in month three should be directly in service of the next move — not a generic best-practices exercise.

What doesn’t vary is the principle: you’re building systems that work without you. The measure of a good operations function isn’t whether things run smoothly when the COO is in the room. It’s whether they run smoothly when they’re not.

This means documentation that people actually use. Meeting rhythms that produce decisions, not just updates. Accountability structures clear enough that everyone knows what they own and what happens when something slips. And increasingly, AI-powered workflows in the places where automation is appropriate — the mechanical, repeatable tasks that eat human hours without requiring human judgment.

I’ve built AI-augmented workflows into operations functions that scaled team capacity without adding headcount. That’s not about cutting people. It’s about making sure your people are doing the work that actually requires them.

What founders should know before making this hire

A few things I’ve learned from the receiving end of this conversation:

The first 90 days will surface things you didn’t know were broken. That’s the point. It’s not bad news — it’s what you hired for. The founders I work with best are the ones who can hear a hard finding without shooting the messenger.

Speed of trust matters more than speed of action. The fastest I’ve ever moved in a new engagement was when the founder signaled early that I had real authority and real information access. The slowest was when I had to spend the first month navigating political permission to see basic operational data.

The ROI isn’t always where you expect it. My highest-value interventions have often been the quietest ones — the process that got cleaned up before it became a compliance issue, the retention problem solved before it became a leadership crisis. Operations, like the goalkeeper position in soccer, is most visible when it fails.

The 90-day clock starts the moment I walk in. I’m not there to listen. I’m there to fix.