Simplify – remove dead work and accidental complexity

First, we focus on the core vision, seek to realign and strip away anything that does not fit.

In a Drifted business, that means identifying dead work, duplicated tools, unnecessary handovers and “custom everything” offers that no longer make sense at this scale. We look for places where the founder’s early “say yes to everything” reflex has created a maze of exceptions the team now has to navigate daily.

In one client case, a €3.5 million services firm had 27 active service variants on paper and at least 10 more “special deals” in the founder’s head. Simplifying meant collapsing those into four standardised offers, retiring several legacy tools and agreeing that certain types of work were no longer worth taking – even if they had sentimental value.

Clarify – design value streams, roles and decision rights on purpose

Next, we clarify how work is meant to flow. We map one or two core value streams – from lead to cash, or from request to delivery – and define who owns which step and who has the right to make which decisions.

For a Drifted founder, this often means admitting that “everyone does everything” is not a strategy; it’s a symptom. In that same firm, Clarify meant defining a simple delivery structure: one lead operator per client, clear handover points, and a short list of decisions that still needed founder input – plus a longer list that no longer did.

Here we also challenge the Founder to assess their current metal models and question if it still serves the Enterprise in its current stage. As needed we start changing the mental models to lean towards Design founder thinking to become the Simplification champion their enterprise needs.

Assess – pick the few leverage points that matter

Then we assess and decide on the top priorities that need our attention. We do this by looking for root causes to problems and seek to understand the impact to the enterprise. When we understand the impact it becomes clearer which ones we need to fix first.

Using the UEM and Enterprise Triangle, we identify the 3–5 issues that make the powerful leverage points that will actually shift patterns over the next 12–18 months, rather than trying to fix everything at once. Often those issues sit in the mental models of key leaders, org design, knowledge transfer and cash flow – not in the shiny new tool stack. For the Drifted firm, the leverage was obvious once we looked at the iceberg:

• Fix the "Yes" to every idea to see what sticks (mental models);
• consolidate tools (structure);
• free the founder from day‑to‑day scheduling (mental model & structure); and
• create a simple weekly operating rhythm so the team could see and solve issues before they hit the founder’s desk (structure).

You will notice we addressed both mental models and structures, when planning for a different future patterns. Also each one of these can be broken down into small experiments to see the impact on the whole enterprise in the next step.

Leverage – move from founder effort to system-driven output

Leverage is where we start to design and implement the high impact improvements. They may take the form of small experiments. Leverage is where many founders stall.

It means shifting from “I fix this personally” to “the system handles this by default”. In practice, that often looks like one key hire, one key platform and one new operating rhythm that shifts the load off the founder’s shoulders.

In our Drifted case, Leverage meant elevating a trusted senior operator into a clear “delivery lead” role, giving them explicit decision rights with clear escalation rules and the why they are critical to the enterprise, then consolidating client work into a single project platform that already existed, instead of three overlapping tools. It was finalised by a weekly reporting so the founder can be kept up to date, while they start working on the next stages of growth.

Execute – install an operating rhythm that stops re-drift

Finally, we execute – not as a one‑off project, but as a new rhythm.

For many 7‑figure SMEs, that’s as simple as a weekly “systems huddle” and a monthly review of one value stream at a time. In the Drifted firm, Execute meant committing to a 90‑day “complexity sprint”:

• 12 weeks where the founder and delivery lead met weekly to review exceptions, retire one legacy element at a time and protect the new operating model.
• At the end of that period, the founder’s involvement in day‑to‑day delivery had dropped sharply, the team had a shared language for complexity, and margins improved without adding headcount.

You may recognise this is similar to a simple PDCA‑style cadence (Plan–Do–Check–Act), so the new structures don’t collapse under real‑world pressure and drift back to the old way. In fact SCALE's origins was born from the PDCA philosophy, but I chose to expand on it to enable critical focus on Simplification and enable a deeper understanding of the details in the iceberg.

SCALE doesn’t ask you to abandon your origin story; it asks you to stop letting that story run your operating system. For the Drifted, Lifestyle and Performance founders, it’s the structured path into the Designed Business mental model – and the most reliable way I’ve found to get across the €3–5 million desert without burning yourself, or your team, out.