Most scaleups don't decide to reset their operating model. They arrive at it reluctantly, after a period of mounting friction they've been attributing to the wrong causes.
The engineering team is slow. The roadmap keeps shifting. Launches disappoint. Talented people are leaving. Leadership is spending more time in escalation conversations than in strategic ones. Each gets treated as its own problem. The fixes are local. The friction persists.
What's usually happening is both simpler and harder to address. The company has a product and customers. But somewhere in the process of growing, it became organised around itself — around its functions, its internal hierarchies, its own operational comfort — rather than around the product it sells and the customers it serves. The operating model drifted inward. The strategy didn't follow.
The belief underneath the problem
Companies that sell products and services have a choice in how they organise. They can build around the org — functions, reporting lines, internal processes — or they can build around the product and the customer. The first is easier to construct. The second is harder to maintain but it's the one that compounds.
A product-centric strategy means the product is the primary vehicle through which the business creates and captures value. Every strategic decision — what to build, what to stop building, where to invest, where to hold — is made in reference to it. A customer-centric execution means that how the organisation operates day-to-day is oriented around delivering value to the customer, not around satisfying internal process.
When those two things are true simultaneously, the operating model is working. When they're not, you get a company that has a good strategy on paper and an organisation that is quietly working against it.
The triggers that make it visible
There are a handful of moments when the gap between the current operating model and the one the business needs becomes impossible to ignore.
The first is a growth inflection. Headcount doubles. New functions appear. The product team that was once close to every strategic conversation is now several layers removed from it — and the work they produce starts to reflect that distance. Features ship that are technically correct and strategically irrelevant. The org is optimising for itself.
The second is a strategic shift. The company moves upmarket, adds an enterprise tier, or changes what it's fundamentally selling. The strategy changes but the operating model doesn't follow. Teams continue to operate against old assumptions because nobody explicitly updated them. The new strategy exists in presentations. The old one lives in how decisions actually get made.
The third is a leadership transition. A new executive arrives and finds the organisation structurally resistant — not because people are obstructive, but because the existing model encodes a different set of priorities. Changing direction without changing the model is like updating a destination without touching the steering.
The fourth is simply time. Nothing dramatic happened. The company grew past the point where proximity and goodwill could substitute for structure, and the gap between product intent and customer outcome widened quietly until it became undeniable.
What people misdiagnose it as
Operating model problems persist because they present as something else. Teams misaligned on priorities look like a communication problem. A product function without real authority looks like a talent problem. Roadmaps disconnected from customer outcomes look like a planning problem.
Each framing leads to a reasonable-sounding fix that addresses the symptom without touching the structure underneath. Six months later the same friction has returned.
The tell is when the same problem keeps recurring despite genuine effort. That pattern is almost always structural. And at the root of most structural problems is the same misalignment: the organisation has drifted away from its product and its customers and started optimising for its own internal logic instead.
What a reset involves
A reset is not a restructure in the conventional sense. It doesn't necessarily mean new org charts or redundancies. What it means is pulling the operating model back into alignment with two fixed points: the product strategy and the customer.
That starts with decision-making. Not the official version but the real one — who has genuine authority, who has effective veto, and where decisions go to die. The question a reset asks is whether the people closest to the product and the customer have the authority to act, or whether they're producing recommendations that get diluted several layers up.
Accountability comes next. A product team held responsible for outcomes they cannot influence is not a product team — it is a reporting function with extra steps. Resetting the model means tracing the line between customer outcomes and the teams accountable for them, and being honest about whether that line is clean.
Then there's how work flows across teams. The boundaries between product, engineering, commercial and operations were drawn at a particular moment in the company's history. A reset examines whether those boundaries serve the product and the customer, or whether they exist for internal convenience and have quietly become obstacles.
Finally, there's performance. What the organisation measures shapes what it does. If the metrics are internally focused — velocity, utilisation, output — the organisation will optimise for those things. A reset asks whether the measures in use actually reflect customer value, or whether they're proxies that have become ends in themselves.
Revenue is a legitimate outcome. It is a poor north star.
Companies that set revenue as the primary organising metric tend to build organisations that are very good at extracting value and progressively worse at creating it. The product gets optimised for conversion, retention mechanics, and upsell paths rather than for the customer it's supposed to serve. Over time the organisation becomes self-referential — its decisions driven by what feeds the number rather than what builds the product. The revenue follows for a while, until it doesn't.
What it is not
It is not a transformation programme. A reset is targeted — focused on the specific mismatches between how the business operates and what its product strategy and customers require.
It is not a culture initiative. Culture follows structure. If you want a more product-centric, customer-focused organisation, changing the values on the wall is not the lever. Changing who has authority, what gets measured, and how decisions get made is.
And it is not a one-time event. The operating model needs to be revisited whenever the business changes materially. The companies that handle growth well treat the alignment between strategy, product, and customer as something to be maintained — not installed once and assumed to hold.