Skip to content
Same core steps: Your book and positioning already describe a journey of Simplify → Clarify → Assess → Leverage → Execute as the process you take SMEs through to untangle complexity and scale. Matches the narrative arc: The transition from “Daily Firefight” to “Scalable Engine” mirrors the core transformation of the book: from messy, complex operations to a streamlined, scalable business model. Consistent with your tools and PDCA: S.C.A.L.E. sits neatly inside your broader PDCA mindset – Simplify/Clarify/Assess is largely Plan/Do/Check, and Leverage/Execute is where you Act and lock in change.
Brand clarity: It gives you a simple, memorable label for the methodology that already underpins your ICP, offers, and the book structure. Positioning as KPI: “The S.C.A.L.E. Framework” reinforces you as the person that turns chaotic SMEs into scalable engines – it’s concrete enough to feel real, but flexible enough to apply across your toolkit of 20+ frameworks.
Make sure “Assess” explicitly nods to root cause analysis and leverage points (so readers connect it to your root-cause chapters, not just a light review). In the book, you can show how S.C.A.L.E. loops with PDCA (e.g. each S.C.A.L.E. pass is one iteration of PDCA applied to the business model), so it feels integrated rather than “yet another framework”.
Plan = understand the problem, analyse causes, choose what to try (so RCA fits here).Do = run the change / experiment.Check = look at the results vs the goal.Act = standardise what worked or adjust and loop again.
Plan = Simplify + Clarify + AssessSimplify: What are we really trying to achieve, and what obviously doesn’t belong?Clarify: How does the work actually flow to create that result (value streams)?Assess: What’s really going on in those flows; what’s the root cause, where are the leverage points?All of that is “thinking before doing”, which is classic Plan.Do = LeverageYou run experiments, try new ways of working, test tech or process tweaks.Check = (still part of Leverage / bridge into Execute)You look at what happened in those experiments: did the leverage actually move the needle?In practice, you usually design the “how we’ll check” as part of Leverage, then review results before fully executing.Act = ExecuteYou lock in what worked (SOPs, standard work, governance, training), or adjust and go again.Plan = S + C + ADo + Check = L (design → test → review)Act = E
Keep S.C.A.L.E. intact and intuitive.Honour PDCA without contorting your steps into an unnatural order.Avoid adding complexity or “framework salad” for the reader.
More
Share
Explore
SCALE - back bone of MCS
So in my Key person of influence (KPI) branding position O sort of come up with this acronym
4. Core Methodology: The S.C.A.L.E. Framework
Ash utilizes a proprietary diagnostic process to transition a business from a "Daily Firefight" to a "Scalable Engine":
Simplify: Removing friction points and "dead wood".
Clarify: Defining value streams that deliver actual profit.
Assess: Evaluating the "critical few" leverage points.
Leverage: Transitioning from manual tasks to system-driven value.
Execute: Bridging the gap between high-level strategy and practical reality.
Does this fit with what I am writing about in my book do you think?
Yes, S.C.A.L.E. is very aligned with what you’re writing about – it’s basically the same spine you already have, just packaged in a reader-friendly acronym that fits your “making the complex simple” promise.
How it fits the book
Where it’s especially strong
A couple of small tweaks you might consider
Would you like to make S.C.A.L.E. the explicit through-line of “The Process” chapter, or keep it more as your personal consulting brand and only lightly referenced in the book?
You’re right to question the order; if it feels off to you, it will feel off to readers too. The good news: your instinct (RCA as part of Plan) is solid, and we can tidy the mapping without breaking S.C.A.L.E. or PDCA.
1. How PDCA is usually grouped
In practice, most continuous improvement people treat PDCA like this:
So your suggestion to move Assess into Plan is entirely aligned with how PDCA is commonly used.
2. A cleaner mapping that respects your flow
Given how S.C.A.L.E. actually feels when you use it, I’d suggest this alignment:
So instead of trying to force a 1:1 letter-to-letter match, you can be explicit that PDCA sits at a different “zoom level”:
That’s simple to explain and honest about how you actually work.
3. Updated mapping table
Here’s a revised table that matches your thinking more closely:
Classic cycle
S.C.A.L.E. step(s)
What it means in your book
Typical “boring good” tools inside
Plan
Simplify
Decide what you’re really aiming for and what clearly doesn’t belong any more; set a simple, concrete business goal.
Goal setting, basic strategy refresh, simple prioritisation, “stop doing” list.
Plan
Clarify
Map the value streams that actually deliver that goal and make work visible.
Value chain/value stream mapping, process sketches, basic metrics definition.
Plan
Assess
Dig into what’s really happening, find root causes and the critical few leverage points before you change anything.
5 Whys, simple data checks, cause‑and‑effect diagrams, impact vs effort thinking.
Do + Check
Leverage
Design and run small changes, then look at the results against the goal: did this leverage actually help?
SSC (Stop, Start, Keep) - potential goals of this step.
Small experiments, manual‑first pilots, basic before/after measures, trialling tools or tech.
Act
Execute
Lock in what works, embed it into the business, and get ready for the next improvement loop.
SOPs, standard work, simple governance, training, feedback loops and reviews.
And you can make that explicit with one line in the text, e.g.:
“If you’ve used PDCA before, you’ll notice that Plan in S.C.A.L.E. is where we Simplify, Clarify and Assess, Leverage is where we both Do and Check what works, and Execute is where we Act to lock the change in.”
That way you:
Does this grouped mapping (Plan = S+C+A, Do+Check = L, Act = E) feel closer to how you actually think and work with clients?
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.