← Back to BlogThe Implementation Gap · Part 4 of 8

The First 90 Days, Without Relying on Heroics

The Implementation Gap (Post 4 of 8)

Every services organization has one or two people who can save almost any account through sheer effort. They read the room accurately, they know which corners are safe to cut and which aren’t, they anticipate the customer’s next question before it’s asked, and accounts staffed with them tend to go well regardless of how messy the handoff was or how ambiguous the scope turned out to be. Leadership usually talks about these people with real pride, and they’ve earned it. What leadership talks about less is that this is not a system. It’s a single point of failure wearing a performance review.

The tell is what happens to an account that doesn’t get one of these people staffed on it. If the answer is that the account is meaningfully more likely to run long, frustrate the customer, or require an escalation, then the company doesn’t have an implementation process. It has a roster of individuals who are personally compensating for the absence of one. That’s an expensive way to run delivery, because it caps how many accounts the company can take on well at the number of exceptional people it happens to employ, and it means every new hire starts the job at a real disadvantage compared to the person they’re replacing or working alongside.

Why This Is a Design Problem, Not a Hiring Problem

The instinct when this pattern gets noticed is usually to hire more people like the star performers, which helps at the margin but doesn’t solve the underlying issue. The underlying issue is that the judgment those people exercise, about pacing, about which customer questions signal real risk, about when to escalate versus when to push through, has never been extracted from their heads and turned into something a newer or less experienced consultant can follow. It stays tacit, which means it doesn’t transfer, which means every account is still, in effect, a bet on who’s staffed on it.

This is fixable, but it requires treating the first 90 days of an implementation as something worth designing deliberately rather than something each consultant figures out for themselves based on instinct and prior experience. That doesn’t mean a rigid script that ignores what makes each account different. It means a defined structure for the decisions and checkpoints that matter most, built from what the best people already do intuitively, so a newer consultant is running the same underlying playbook even if they’re less polished at executing it.

What a Standardized Path Actually Contains

A well-designed first 90 days has a small number of load-bearing elements. It defines what has to happen in week one regardless of the account, typically confirming the stakeholder map from the handoff document is accurate and identifying who’s actually going to show up to working sessions versus who signed off on the project and disappeared. It defines the decision points where a less experienced consultant should escalate rather than guess, things like a customer pushing back on scope, a technical requirement that wasn’t anticipated, or a stakeholder who seems to be quietly disengaging. And it defines what “on track” actually looks like at each checkpoint, in specific terms, so a consultant isn’t relying purely on gut feel to know whether an account needs attention before it becomes visibly at risk.

None of this replaces judgment. It gives less experienced people a floor to stand on while they’re building their own judgment, and it gives the organization a way to notice when an account is going off the standard path early enough to do something about it, rather than finding out at the 60-day mark that nothing has gone according to any plan because there was never a plan to go according to.

Extracting the Judgment That Currently Lives in One Person’s Head

The most direct way to build this is to sit down with the people who are already doing it well and ask them to narrate their own decision-making on a real account, in detail, including the moments where they made a judgment call that isn’t written down anywhere. That conversation, done two or three times across a handful of accounts, usually surfaces the actual pattern faster than any amount of abstract process design. The output isn’t a rigid checklist that removes judgment from the job. It’s a shared starting point that means the next hire isn’t starting from zero, and the next account that draws a less experienced consultant isn’t quietly worse off than the one that happened to draw a star.

NextPeak Studio helps growth-stage SaaS companies turn their best delivery instincts into a repeatable onboarding path, so implementation quality stops depending on which consultant happens to be available. If your team’s outcomes vary more by who’s staffed than by what the account actually needs, that’s a design gap, not a talent gap.

#ProductStrategy#GTM#Implementation

This post is part of The Implementation Gap, a 8-part series.

View the full series