The model that worked for one team rarely survives being copied across the next.
Expansion is where a working commercial motion gets multiplied across new territories, segments, or teams, and the operating model that carried the first one quietly stops travelling to the next. Operation is often the right service shape here because it includes the Diagnosis, identifies where the model changes as it travels, and carries the resulting correction across the new teams or markets.
Where the strain concentrates while one working model becomes several.
The model, not just the motion, has to travel
A new region or team gets the people and the target, but not the RevOps infrastructure and definitions that made the first team's motion repeatable, so the copy starts drifting from day one.
Enablement turns reactive
New hires get trained by whoever is nearest instead of a defined path, so quality quietly diverges team by team long before anyone notices it in the numbers.
The numbers stop meaning one thing
Each new team builds its own version of a pipeline stage or a territory boundary, and the shared dashboard keeps reporting a single number that no longer describes a single thing.
Compare the model across teams before local drift becomes normal.
The diagnostic tests all six dysfunction families without assuming which one carries the expansion loss. It compares definitions, handoffs, reporting, and enablement across the original team and the teams that followed, then checks whether the model was ever written down or only appeared consistent while it lived in one person's head.
Interviews typically cover RevOps or sales operations, enablement, and a manager from each team the motion has been copied into, alongside the manager from the original team it was copied from. Pipeline definitions, territory rules, and onboarding materials are compared team to team rather than assumed to match.
Before you assume the second team just needs more time.
Our first team is already profitable, shouldn't we just copy exactly what they do?
We are just opening one new region, is that really worth a diagnostic?
How disruptive is this while we are actively hiring into the new team?
Should we start with Diagnosis or go straight to Operation?
Three ways to keep going.
See how Operation works
How a known-good model gets carried into a new team or region without drifting on the way in.
See what gets measured
The six families, the signals that reveal them, and how each one turns into cost.
Find out where you sit
Ten questions, two minutes. A first read on which part of your system is carrying the most strain.
One team's model, repeated across the company. A number shows where the copy leaks.
One call, 30 minutes. We will review what is working, what is stalling, and where the cost is actually sitting. You will leave with a concrete next step, whether that is Kihon Labs or not.
Book a diagnostic call