Explore

Flow to next chapters

This chapter: Strategy Execution (Clarify the system)

Goal: help the reader see how their current system really works — mentally and structurally.

Evidence you pull from them:

How they think about strategy vs execution.

Where their Wall to Wallet gaps are (story + questions).

Their own mindset and their team’s (e.g. control vs coach, effectual vs planned).

Where the value chain actually breaks.

How they currently use data and KPIs (measurement madness).

This is essentially “Clarify how you’re thinking and operating today.”

Simplifying and Optimizing Business Models (Clarify the shape)

Goal: use Drucker, business model stats, and your monsters to decide what to stop and simplify.

Evidence you pull:

Which offers, segments, and activities are really creating value.

Where Kraken (legacy), Hydra (compounding problems), and Minotaur (maze) are strongest.

What simplification would look like in their context.

This is “Clarify what the business should actually look like going forward.”

Problem & Impact (Clarify the battles to fight first)

Goal: focus them via Pareto and PAERTO so they don’t try to fix everything at once.

Evidence you pull:

Which problems, if solved, change the economics or stress of the business most.

Where strategy–execution gaps hurt the most.

Here you’re already starting to pivot into L (Leverage): which few problems will you lean into first.

Where to weave specific research into your columns

Using your column blocks from the screenshot:

Column 1: Strategy Execution — topic by topic

Strategy Execution just a fancy term or something else? (Topic)

Bring in:

Survival stats + planning meta‑analysis: “This matters in hard numbers.”

Clar definitions of strategy, execution, alignment (with 6Ws frame).

Wall to Wallet (Story)

Bring in:

SMU/Bridges execution failure data and uncommon practices.

Wall to Wallet as your own metaphor for the translation gap.

One or two founder‑level diagnostic questions.

Mindset (yours, the customer, the team) (Topic)

Founder:

Mintzberg potter metaphor and patterns.

Effectuation vs planning.

Burnout evidence and Cyclops (one‑eye) risk.

Customer:

How their expectations drive complexity if you’re not deliberate.

Team:

Tacit vs explicit knowledge; how much WHY they actually see.

This is where you link back to your Iceberg model.

Value Chain (Topic)

Bring in:

Porter's value chain idea simplified.

Pragmatic Value Chain as your operationalisation of alignment.

Tie to Wall to Wallet: where does strategy stop flowing?

A word on data (Topic)

Discuss:

Activity vs outcome metrics.

Founder temptation to measure what’s easy vs what matters.

How bad metrics create Chameleon and Measurement Madness.

Graph on Financial Performance Improvement / Data business focus (Data)

Bring in:

Planning meta‑analysis graph (or an adapted version).

Financial visibility findings (professionalising finance, SME scalers / NGO sustainability).

Make it concrete: “Here’s what happens when you actually measure the right things.”

We only improve what we…? (Topic)

Land the point:

“We only improve what we can see clearly and care about.”

Connect back to Clarify: this chapter was about surfacing what you really see today.

Measurement madness (Story)

Close with a story that shows:

A business drowning in KPIs and reports but blind to strategic reality.

Tie back into the next chapters: simplifying business model and choosing the right problems.

⁠

4. Mindset as the hinge between “system now” and “change later”

Your instinct that Topic: Mindset should come before the value chain is also helpful for the later C‑chapters:

Mindset you surface here (control vs coaching, hoarding vs sharing, “more is better” vs “less but sharper”) → explains why simplification is so hard in the Business Model chapter.

The same mindset shows up when they try to prioritise in Problem & Impact (e.g. “I can’t let that go”).

So in this chapter, you don’t need to fully “fix” mindset. You just:

Make it visible.

Show how it shapes Wall to Wallet gaps, tacit knowledge transfer, and burnout.

Ask questions that make the reader see themselves clearly.

Then the later chapters can say: “Remember how you reacted in that earlier chapter? That’s why this next step will feel hard — and here’s how to work with that.”

⁠

If you like this mapping, I’d suggest we next take one block from your first column (maybe “Mindset” or “Wall to Wallet”) and build a draft section: 2–3 paragraphs plus 2–3 diagnostic questions, aligned exactly with the role of this chapter in C of SCALE.

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.