The First 90 Days Aren't a Plan. They're a Test.

You're the CEO. You signed a fractional CTO engagement three weeks ago because something in the engineering org wasn't working. The board wants to know by the next meeting whether this was the right call. The new leader is in a lot of meetings. A senior engineer pings you privately to ask if this person is actually going to do anything, or if they're just "gathering context."

Pushing for visible action now is how you hire someone who does the wrong thing fast. But "gathering context" can also be an excuse for a month of nothing.

The First Thing That Has to Happen

Michael Watkins wrote The First 90 Days in 2003 and it's still the sharpest thing in print on executive transitions. His core insight: the most common way new leaders fail isn't incompetence — it's arriving with answers before they have the situation. The playbook from the last company becomes the diagnosis for the new one, and it doesn't fit.

Fractional engagements fail the same way, faster. A full-time executive who prescribes before diagnosing has years to recover. A fractional leader has a few reviews.

The early weeks have to be disciplined listening — the kind where the leader is building a map they'll be accountable for. A fractional CTO doing this well is talking to your sales leader about deals lost on technical promises, to customer success about tickets that never close, to senior engineers about what they've stopped asking for. They're reading commit history before the roadmap, asking your CFO what the cloud bill looks like month over month and whether anyone has opinions about why.

If they produce a 40-page strategy document this early, you hired wrong.

What Listening Actually Surfaces

At GigSmart, scaling to operational coverage across all 50 states meant reconciling dozens of legal and labor constraints in code. The load-bearing information wasn't in the architecture diagram — it was in conversations with operations about which states kept generating tickets and why. The pattern shows up in every engagement. It showed up at ToolWatch before the acquisition that became AlignOps, and at Oxen.ai in how ML teams actually version data versus how the docs said they should. The decisive information lives below the org chart.

What's the executive looking for? Not deliverables. Signals. Can the fractional leader tell you which three problems actually matter and why the other seven are symptoms? Can they name the person carrying more than their title suggests? Can they describe the gap between what the architecture doc says and what the code does, with specifics?

You can evaluate that in a thirty-minute conversation.

The Credibility Tax

Here's where most engagements break. The leader finishes listening, develops a real point of view, and can't cash it. The team hasn't seen anything happen. The board meeting is coming. The pressure is to produce a roadmap — exactly the wrong move. A roadmap is a promise the engagement hasn't earned the credibility to make.

Call it the credibility tax. You pay it whether you want to or not. The only question is what the leader spends to pay it.

The leaders who do this well find one thing — small, specific, measurable — and ship it. A runbook that cuts incident response time. A kill switch on a forgotten API integration burning cloud budget. A PR policy that unblocks the senior engineer everyone's been waiting on. Their function is the same: they convert "why did we hire this person" into "what do they want to do next."

The ones who get stuck treat the quick win as beneath them, or announce the strategy before anyone's seen them execute. You lead from a track record, not a document — and in a fractional engagement you build that track record in the same phase you're still diagnosing.

That's the published version of the job: listen, diagnose, earn credibility, execute. Every firm sells a version of it, and the shape is right. But watching only the fractional leader misses where these engagements actually succeed or fail. The CEO who's been burned by a prior consulting relationship already knows this in their gut, even if they can't name it yet.

Where the Reframe Lives

Most CEOs don't see this clearly until they've run a few of these engagements: the first 90 days are primarily a test of the organization, not the fractional leader.

A fractional CTO can diagnose cleanly, ship a credible quick win, propose a sharp strategy, and still fail if the organization can't absorb what they're telling it. Recommendations get watered down by committee. The engineering team treats the new leader as a visiting consultant. The CEO privately wants a different answer than the data is producing. The engagement generates activity and no change — not because the leader was wrong, but because the organization wasn't ready to be led on this specific question.

What you're evaluating is a pair: the leader's judgment and the organization's absorptive capacity. Lara Hogan's writing on leadership transitions makes a version of this point about full-time executives. It compresses harder in the fractional case.

The useful question for the executive team, then, isn't "how is the fractional CTO performing?" That question looks at the wrong actor. Better diagnostic: is the organization making decisions it wouldn't have made before? Are recommendations turning into commitments with owners and dates? Is someone internal rising to carry the work, or is everything still routed through the fractional leader?

Reading Your Own Engagement

Picture the cloud bill conversation you might be having. Monthly AWS spend has crept to eighty thousand and half of it looks attributable to prototypes nobody owns. The fractional leader proposes a kill-switch policy and attribution dashboard. The proposal is obviously smart — most of them are. The real question: when they bring it to your engineering leads, does someone raise their hand to own it?

If yes, the engagement is working. The leader is a multiplier. Work happens through your people, not around them.

If nobody raises a hand and the fractional CTO ends up owning the fix themselves, you're drifting into a different relationship than the one you paid for. Dependency instead of capability. Bottleneck instead of lever. If that pattern shows up in the first review, it shows up in every one after. Have the direct conversation early.

The leaders we've placed into the hardest engagements all say some version of the same thing: the technical work is never the hard part. The hard part is building internal muscle to decide and commit on a cadence the engagement can accelerate.

The Conversation You Should Be Having

If you're three weeks into an engagement and not sure what you're seeing, stop asking "where's the plan." Ask instead: "what did you learn this week that I didn't know?" If the answer is specific, the engagement is alive. If it's generic, course-correct before the review.

And if you're evaluating whether to bring fractional leadership in at all, the honest first question isn't about their playbook — it's about your organization's readiness to act on one. That's the conversation we'd rather have first, before the engagement has to find out the hard way.