The methodology
Five operating levers, three amplifiers. The pattern under everything.
Every growing business pulls the same five levers: decision, customer, operations, people, and product. Some are pulled hard and could go further. Some are stuck and quietly costing you. From inside, both look like normal.
This is the diagnostic lens we use to see it from the outside. Five operating levers that shape every scaling business. Three forces that amplify each one. It's the framework behind every engagement we run, and behind the diagnostic you can take before we've spoken.
Core lever 01
Decision Lever
The accumulated weight of decisions that were never made cleanly, or were made once and never revisited.
Every business starts with fast, informal decision-making. The founders decide. Things move. That speed is a competitive advantage in the early stages, and it creates a habit. Over time the habit calcifies: decisions require the same people, the same informal sign-off, the same implicit consensus. The business scales. The decision pattern does not.
Decision Lever accumulates at the intersection of authority and clarity. It shows up as recurring arguments that never reach resolution, escalations landing on the same desk regardless of their nature, and a culture where getting things done requires navigating informal power rather than following structure. Meetings multiply. Confidence degrades. The cost of every decision rises because the energy goes into the act of deciding rather than the quality of the decision itself.
The most damaging form is invisible drift: decisions that appear to have been made but haven't. Different parts of the team proceed under different assumptions. The rework surfaces six months later, after real cost has been committed.
Pattern observed
A business with three co-founders and twelve employees reaches thirty-five people. They've written a strategy document. Every senior hire has read it. But the same commercial decisions keep landing on the same founder, because no one else knows where the implicit boundaries are. Two years of growth, and the authority map was never externalised. The document describes what they decided. It doesn't say who gets to decide what next.
Signs it's present
- The same debates recur in different rooms
- Decisions require the founders even when they shouldn't
- Senior hires defer when they've been hired to lead
- The org chart and the real authority map don't match
Core lever 02
Customer Lever
The structural exposure created by who your customers are, how dependent you are on them, and what you've implicitly committed to in order to keep them.
Customer Lever is rarely about individual customers being bad customers. It's about what a portfolio of customer relationships has come to mean structurally. The business that wins its first big customer takes on concentration risk as a side effect of success. One that keeps a founding customer for a decade has often made ten years of informal accommodations (pricing exceptions, scope creep, escalation paths that bypass the standard model) that can't easily be unwound without the relationship breaking.
The lever compounds through product decisions. A business that builds for its loudest customers builds a product that reflects those customers' problems, which may or may not be the market's problems. The roadmap drifts. The ICP calcifies. New customer acquisition gets harder because the product that keeps existing customers renewing is not the product that wins new ones.
The exit risk is the most uncomfortable manifestation. A single customer or segment representing 40% or more of revenue isn't just a concentration risk. It's a negotiating position the customer holds whether they exercise it consciously or not. Pricing conversations, contract renewals, scope discussions: all happen in the shadow of that dependency.
Pattern observed
A SaaS business has a flagship enterprise customer who accounts for 38% of ARR. Every product quarter, roadmap items shift slightly toward that customer's needs. The product team frames it as serving the enterprise segment. Three years in, a mid-market competitor wins deals the business used to close on value. The mid-market product, built for the founding customer, no longer fits.
Signs it's present
- Any single customer over 25% of revenue
- Pricing that varies significantly by customer without a documented rationale
- Roadmap decisions driven by named customer requests rather than segment analysis
- Renewals that require founder involvement to close
Core lever 03
Operational Lever
The friction embedded in how work actually gets done: the gap between the documented process and the real one.
Operational Lever is the most visible form of operating friction, and therefore the most commonly misdiagnosed. It presents as inefficiency, and businesses respond by adding process: new tools, new workflows, new roles whose primary function is coordination. The overhead accumulates. The underlying problem stays untouched. (That problem is usually that the real process was never documented because it evolved informally.)
The real process in most growing businesses is a palimpsest. Layers of workarounds, each built to fix the failure of the last one. The original system had a gap. Someone bridged it with a spreadsheet. The spreadsheet grew. Someone built a report from it. The report required manual input from three teams, so a weekly meeting was called to collect that input. The meeting now takes ninety minutes. No one remembers the gap that started it.
Operational Lever creates rework, handoff failure, and capacity drag. It's the reason good people operate at 60% of their potential. Not because of skill or will, but because the system they work inside demands it. In high-growth phases the drag is invisible; the energy of growth obscures it. The friction surfaces in the plateau, when growth slows and the inefficiency can no longer be ignored.
Pattern observed
A professional services firm with forty-five consultants onboards new clients using a process documented three years ago. Everyone uses it as a starting point, then adapts it based on their own experience. There are now eleven meaningful variants in use. Quality of onboarding varies significantly: consultants with the most tenure have the best version; juniors use the documented one and learn from complaints. No one has counted the variants or mapped the rework they cause.
Signs it's present
- The documented process and the real process are not the same thing
- Output quality varies significantly by who does the work
- Tribal knowledge is load-bearing: if one person leaves, something breaks
- A significant share of team time is coordination, not delivery
Core lever 04
People Lever
The gap between the capability the business needs and the capability it has, often disguised by loyalty, tenure, and the difficulty of the conversation.
People Lever is not about bad people. It is almost always about good people in roles the business has grown past them into, or roles that were designed for a business that no longer exists. The first head of sales who thrived at £500k ARR is not automatically the right head of sales at £5m ARR. The operations manager who built the function from scratch may not be the person to scale it. The role changed. The person didn't, not because they couldn't, but because no one named the change clearly enough to make development an urgent priority.
The lever compounds through succession risk and single-point fragility. People who've been in the business long enough become load-bearing: they hold relationships, institutional knowledge, and informal authority that has never been documented or transferred. When they leave, voluntarily or otherwise, the departure is more disruptive than any org chart would suggest. The business discovers the gap when it's too late to address it systematically.
The most insidious form is the capability gap that looks like a motivation problem. A person struggling in a role that has exceeded their capability presents as disengaged, inconsistent, or resistant to change. The response is a performance management process rather than a conversation about the actual gap. The gap deepens. The person often leaves, taking the institutional knowledge and whatever engagement remained with them.
Pattern observed
A technology business promotes its best individual contributor into management because it's the next logical step and they've earned it. Eighteen months in, the team is frustrated and the delivery metrics have declined. The promoted manager is working harder than anyone. They're just working in the wrong way for the role. No one named the capability gap at promotion. No investment in management development followed the title change. The gap is now a retention risk for the whole team.
Signs it's present
- Key-person dependency: the business couldn't absorb the departure of specific individuals
- Roles whose scope has grown faster than the person in them
- Promotions driven by tenure or loyalty rather than assessed readiness
- Capability gaps being managed as motivation problems
Core lever 05
Product Lever
The growing gap between what you sell and what your market actually needs, often hidden by the momentum of what's already working.
Product Lever accumulates through incremental drift. The founding product was right for the founding market. Then the market shifted, gradually as markets do, and the product responded to the loudest signals: the features existing customers asked for, the capabilities that closed the last big deal, the roadmap built to retain the enterprise anchor rather than win the next growth segment. Each of those decisions was defensible. The cumulative direction was not.
The symptom is a product that's hard to sell without context. The sales team needs to explain it. Prospects need to be educated rather than convinced. The market problem exists, the product addresses it, but the framing has drifted so far from the current buyer's language that the connection takes effort to make. Win rates fall. Sales cycles lengthen. The business diagnoses a marketing problem and doubles down on positioning, when the actual issue is that the product has been built for yesterday's customer and yesterday's problem.
Product Lever also accumulates technically as feature range broadens without strategic pruning. The product does more and more, and the core value proposition becomes harder to articulate. Every capability was added for a reason. Together, they obscure the reason anyone should buy at all.
Pattern observed
A workflow automation platform started in professional services, added integrations for manufacturing at the request of a major client, then added a compliance module to retain a regulated-sector anchor. Three years on, it serves three distinct segments with one product. None of the three segments feels fully served. The sales team pitches differently to each. The roadmap is a negotiation between three segment needs. The founding segment (where the product is strongest) is losing deals to a focused competitor that does less, better.
Signs it's present
- Sales requires significant context-setting before buyers understand the value
- The product serves multiple segments whose needs are in tension
- Roadmap is driven by retention rather than new-market acquisition
- The core value proposition takes more than one sentence to state clearly
The amplifiers
Three forces that make every debt worse.
The five core levers exist independently. Amplifiers don't create debt. They intensify it, accelerate its compounding, and make it harder to see and address. Understanding them separately matters because an amplifier present in the system changes the urgency of every debt it touches.
Amplifier 01
Technology
Technology amplifies every form of operating friction it touches. A decision authority problem becomes a workflow automation problem: the system enforces the broken decision pattern at scale. Operational debt becomes architectural debt: the workaround is built into the platform, and now it's load-bearing. Customer debt gets encoded in data models that reflect the founding customer's requirements, not the market's.
The speed of technology compounds the amplification. In a manual process, a bad decision pattern creates friction slowly. In an automated one, it creates friction at the pace of the system. The debt surfaces faster, at higher cost, and is harder to unwind, because unwinding it requires unpicking the technical implementation alongside the structural problem underneath.
Technology is not the cause. It is the accelerant. This is why we diagnose the operating friction before we advise on the technology.
Amplifier 02
Culture
Culture amplifies debt by making it feel like identity. A decision-making pattern that bypasses structure becomes "how we work here." An operational workaround becomes "our approach." A people problem (a capability gap no one has named) becomes "that's just how [person] operates." The debt is protected by the culture's resistance to examination.
Culture as amplifier is particularly powerful because it makes debt invisible to insiders. The people inside the system don't experience the pattern as debt. They experience it as normal. The consultant who comes from outside sees it immediately; the leadership team that built it doesn't see it at all. This is the epistemic problem at the centre of our whole practice.
Cultural amplification is also why the conversation about operating friction is harder than the technical work of fixing it. Naming a cultural pattern as a liability is experienced as an attack on identity. The resistance to diagnosis is not obstruction. It's attachment.
Amplifier 03
Regulatory
Regulatory amplifiers operate differently from the other two. Technology and culture amplify debt by accelerating or hiding it. Regulatory exposure amplifies debt by raising the stakes of not addressing it. A customer lever problem (concentration, dependency, accommodation) has a commercial cost. In a regulated sector, it may also have a compliance cost. An operational lever problem (process inconsistency, tribal knowledge) creates rework. In a regulated sector, it creates audit exposure.
The regulatory amplifier matters most for businesses entering or expanding into regulated sectors: financial services, healthcare, legal, critical national infrastructure. The operating friction they carry into that sector does not disappear when the regulation arrives. It becomes a compliance liability with a deadline attached.
We treat regulatory exposure as an amplifier rather than a debt category in its own right, because the root cause is always one of the five core levers. The regulation doesn't create the problem. It makes the cost of leaving it unaddressed explicit.
Why this framework
Where this came from — and why these categories and not others.
The framework emerged from a simple observation: the businesses with the most room to move weren't held back by a single visible problem. They were shaped by a pattern of interacting forces, forces that masked each other, reinforced each other, and were collectively invisible to the people who had built them over time.
We looked at the recurring patterns across engagements in growing businesses, typically between twenty and two hundred people, past the initial product-market fit moment and encountering the structural problems that growth surfaces. The same categories kept appearing. Decision authority breaking down under scale. Customer portfolios concentrated in ways that constrained the business without the leadership fully recognising the constraint. Operations that had been manual and flexible hardening into processes that were manual and inflexible. People in roles their roles had grown past. Products drifting from the markets that needed them.
The taxonomy we landed on is specific because specificity is the point. "Organisational health" frameworks exist. They are useful for broad assessment but not for sequencing a move, because a general framing produces general advice, and general advice compounds rather than addresses the actual lever you need to pull. The framework names each lever precisely because precision is what enables prioritisation. You cannot decide where to act first if you cannot name what you have.
The three amplifiers emerged separately, from a different observation: that the same underlying debt had wildly different severity levels across different businesses. The differentiator was almost always one of three forces, technology, culture, or regulatory exposure, sitting on top of the debt and multiplying its impact. Treating amplifiers as a separate layer, rather than folding them into the debt categories, preserves the diagnostic clarity. The debt is the problem; the amplifier is the force multiplier. Fixing the amplifier without addressing the debt solves nothing. Addressing the debt without understanding the amplifier produces a plan that underestimates the work.
We publish this framework because the thinking should be available, not proprietary. The diagnostic, the structured process of applying it to a specific business from outside the system, is the engagement. The framework itself is open.
What this can and can't see
"This is what the diagnostic can see from your answers. Here's what it can't see — the patterns visible from outside the system. If you want help finding those, that's what we're for."