The first 90 days as a fractional operator.

Most fractionals walk into a new engagement and immediately try to prove they were worth hiring. That instinct destroys more engagements than any skill gap. The first 90 days have a sequence. Violate it and the whole thing unravels by month four.

The instinct that kills engagements.

When you are brought in as a fractional operator, you are operating under a particular kind of pressure that a full-time hire does not face in the same way. A full-time executive has the luxury of a longer clock. People expect them to take six months to find their footing. The organization extends a form of patience that is partly professional courtesy and partly institutional inertia — they hired this person, they have to make it work.

A fractional has no such runway. You are being paid from month one. The CEO signed a contract with a defined scope and is expecting visible progress. The team knows you are not a permanent hire, which means they are watching to see whether you are worth integrating into the real operating rhythm or whether you are a temporary imposition they can wait out. The pressure to demonstrate value immediately is real.

The problem is that almost every way of demonstrating value in the first 30 days is counterproductive. You do not have enough context to make good decisions. You have not built enough trust to have the conversations that would give you that context. The people most likely to brief you extensively in week two are not necessarily the people with the most accurate picture of the situation — they are the people with the most to gain from your early attention.

The fractionals who succeed understand that the first 90 days are not three identical months of value delivery. They are three distinct phases that have to be executed in sequence. Getting the sequence wrong is not a recoverable error. You do not get a second first impression with an embedded team, and you do not get your credibility back once you have spent it on a recommendation that turned out to be premature.

Days 1 to 30: understand before you diagnose.

The first thirty days have one job: build an accurate picture of the operating reality. Not the version the CEO shared in the sales conversation, not the version that exists in the board deck, and not the version the most vocal team member presents in week one. The actual operating reality, which is usually messier and more interesting than any of those.

This means spending a disproportionate amount of time listening. Sit in on meetings you would not normally attend if you were a full-time leader. The weekly sales team standup. The engineering retrospective. The ad hoc conversation between the head of finance and the ops manager that happens in the kitchen. These informal interactions carry more diagnostic signal than any structured onboarding session because they have not been curated for your benefit.

The questions you ask in month one should be almost entirely diagnostic rather than prescriptive. "Help me understand how that decision got made." "What does success look like for your team six months from now?" "What would you change if you had the authority?" You are not asking these questions to have something to react to — you are asking because the answers reveal organizational assumptions that the team has stopped questioning and that you, as an outsider, can still see clearly.

The deliverable for month one is not external. It is a written diagnostic that you share only with the CEO: a clear-eyed account of what you have found, what the three or four most important problems are, what is causing them, and what you plan to do about it in the next 60 days. This document is valuable not because the CEO does not know these things — they usually know most of them — but because it demonstrates that you understand the business well enough to be trusted with decisions. It also creates a shared frame that prevents the engagement from drifting.

One other thing happens in month one that is not in any methodology document: you find out which people on the team are worth building a relationship with. Not politically — operationally. Who gives you unvarnished feedback. Who knows where the problems actually live. Who has tried to solve these problems before and learned something from failing. These people become your operating network inside the company, and they are worth more than any formal authority the org chart gives you.

Days 31 to 60: earn the right to be heard.

The second thirty days have a different job: establish enough credibility that when you start making recommendations, people act on them rather than managing around them. This is mostly done through a series of small wins rather than one large intervention.

The mechanism matters. A small win in this context is not something you did alone — it is something you helped the team accomplish that they could not accomplish without you, and that they know they could not have accomplished without you. This distinction is load-bearing. If you solve a problem by yourself and present the solution, you have added value but you have not built the kind of trust that makes future influence possible. If you pull together the right people, ask the right questions, and facilitate the outcome — and the team leaves the room feeling like they solved it — you have done something more durable.

Month two is also when you start selectively sharing opinions. Not on every topic — on the two or three areas where you have the clearest picture and the most direct mandate. The art is choosing the right moment. You want to share a view before the decision has been made, not after. You want to frame it as a perspective rather than a directive. And you want to be right more often than not, because each correct call adds to the credibility account you will need to draw on in month three.

What you are not doing in month two: restructuring teams, redesigning processes, or making commitments on behalf of the company to external parties. These actions require a level of trust that takes longer than 60 days to build with most organizations. The fractionals who make these moves in month two are usually reacting to pressure — from the CEO, from their own impatience, or from a genuine belief that the situation is urgent enough to warrant it. Occasionally they are right. More often they are spending credibility they have not yet earned, and the team's quiet resistance to what comes next is the cost.

Days 61 to 90: make decisions that stick.

The third month is when the engagement starts to look like what the CEO thought they were buying from day one. You have enough context to make good decisions. You have enough credibility for those decisions to land without extended negotiation. You know which team members will implement and which will resist, and you have the relationships to work with both.

Month three is when you run the first real initiative. Not a pilot or a proof of concept — an actual operational change with a clear before state, a defined output, and a person accountable for each moving part. The change should be in the area you have the clearest mandate for, which you should have established in the month one diagnostic. It should be completable within the third month, not because 30 days is always the right time horizon but because completing something concrete sets the tone for the rest of the engagement.

The decisions you make in month three also establish the standard for how decisions will be made going forward. Are you making them collaboratively or unilaterally? Are they documented or verbal? Are they communicated to the team or left for the CEO to relay? These patterns will calcify. Set them intentionally.

There is a specific mistake that happens at the end of month three that is worth naming. Some fractionals arrive at the 90-day mark, look at the list of things they have not yet changed, and dramatically increase their tempo — trying to make up for what feels like a slow start. This is almost always wrong. Month three is not the end of the first phase. It is the beginning of the real engagement. The 90-day sequence is not the whole job. It is the foundation. The decisions you make in month four and beyond will be built on whether you got the first 90 days right.

The calibration that separates good fractionals from bad ones.

Everything in the 90-day sequence depends on one underlying calibration: accurately reading what the organization can absorb and what it cannot, at each point in time. This is a skill that is genuinely hard to teach because it requires integrating a large number of weak signals simultaneously — how the CEO responds to pushback, how quickly the team moves on new information, how much organizational memory there is around previous change efforts that failed.

The fractionals who consistently get this calibration right have usually been embedded operators before. They have a felt sense of what resistance looks like before it becomes explicit. They know the difference between a team that is slow to move and one that is actively obstructing. They have seen enough different operating environments that they can pattern-match the current one quickly.

The fractionals who get it wrong are usually the ones who are applying a framework they developed in a different context — a company where urgency was the dominant cultural value, or where the CEO deferred to operators by default, or where the team had already done the cultural work that made change easy. Those contexts exist. They are not universal. The first 90 days is partly about figuring out which context you are actually in.

• 01
  Spend the first month listening, not diagnosing out loud. Your mouth-to-ear ratio in month one should be heavily weighted toward listening. Ask diagnostic questions. Sit in meetings that are outside your formal scope. Read whatever documentation exists. The picture you build in month one will determine the quality of everything that follows.
• 02
  Write the month-one diagnostic for the CEO, not for the team. A shared frame with the CEO is more valuable at this stage than any team-facing communication. Get aligned with the person you are accountable to before you start trying to move the organization.
• 03
  Earn credibility through facilitation, not individual contribution. Small wins that the team feels ownership over build more durable trust than brilliant solutions delivered from the outside. Your job is to make the team better, not to demonstrate how good you are.
• 04
  Choose your first opinions carefully. In month two, you will start sharing views. The ones you share first set the frame for how your judgment is perceived. Pick areas where you have the clearest picture, the most direct mandate, and the highest probability of being right.
• 05
  Run something to completion in month three. The first real initiative should be scoped to close within the 90-day window. Not because speed is the point, but because completing something concrete establishes that you can deliver — not just advise.
• 06
  Treat the 90 days as a foundation, not a sprint. The rhythm you establish in the first three months is what the rest of the engagement runs on. Set it for the long game — clear decision rights, clean communication channels, a team that trusts you enough to tell you when something is not working.

Frequently asked questions.