Skip to content
Starts with your anecdote and clearly exposes the old/new mental models.Uses just enough evidence on quick fixes, firefighting, and hidden costs to feel undeniable.[1]Lands on “visible, testable operating model” as the practical alternative, setting up the rest of the chapter.[2]
Your boss’s line → planning for the known, adapting to the unknown.Buffett’s line → long‑term vision and persistence.Then: “Neither tells you who does what, when, or how the business will actually run on Monday morning.”
Direction and intent, goals, strategy, resources, assumptions, feedback loops.[3][4]Then immediately translate: “In an SME, those elements live in how work flows from customer request to cash in the bank – not just in a slide deck.”[1]
Last century: plan–make–sell, long research and big launches, heavy upfront cost and risk, slow learning, hard‑to‑change complexity.[6][5]MVP era: coined and popularised from early 2000s and Lean Startup, focusing on build–measure–learn, MVPs and rapid tests.[2][7][8]“Old school planned the product and froze the system. New school tests the product and forgets the system. In both cases, complexity wins.”[1]
Mental model: “get it right before launch” → culture of long cycles, fear of visible learning.Mental model: “speed above all” → culture of quick fixes, constant pivots, partial fixes.[1]Up to about 80% of organisations operate mainly in reactive, quick‑fix mode.[1]Common quick fixes: adding people, tools, rules; each feels rational but increases complexity and recurring problems.[1]Hidden costs: process/technical debt, time lost to navigating internal complexity, burnout, missed innovation.[1]
Time spent firefighting vs improving.Problems that keep coming back.Processes full of workarounds and checks.People leaving from burnout.Opportunities missed because of constant crisis.[1]
Not a business plan for the bank.Not a detailed Gantt chart.But a visible, testable operating model:What are we trying to achieve?How does work actually flow end‑to‑end?Where do we decide, measure, and learn?
“If you’re exhausted, it’s not you. You’ve been trying to change a system you never had on paper.”Next: “But my business is different” – where you show the shared building blocks.Then: PDCA and your detailed process – how to run that operating model like a governed, learning system rather than a permanent experiment.
Use external web citations mainly for:The planning elements and traditional planning model.[4][3][5]The history and intent of MVP / Lean Startup.[8][2][7]Use the attached research citation when you:Describe firefighting and quick‑fix culture.Talk about hidden costs (complexity, debt, burnout, missed opportunities).[1]Justify your audit questions as grounded in evidence, not just opinion.[1]
Updated structure plan of this chapter
Based on further research and deeper thinking
The Middle Ground I am seeking
That middle‑ground you’re aiming for is exactly where this chapter can be most powerful. When you’re ready with a revised draft, paste it in and it can be shaped so it:
Start by deciding which single message this sub‑chapter must prove, then hang research off that spine. A good core message for you is:
“Whether you grew up in the ‘plan–make–sell’ world or the ‘test–pivot–repeat’ world, if you don’t have a visible, testable operating plan, you will drift into firefighting and complexity.”[1][2]
Below is a tightened structure plus where research can back you up.
1. Hook: two quotes, one problem
Job: use your anecdote and Buffett quote to show that everyone likes the idea of planning, but few have a real, working plan.
You can keep your opening but sharpen the pivot:
No citation needed here; this is lived experience.
2. What most people think a “plan” is
Job: contrast big‑company and founder images of a plan with what SMEs actually need.
Here you bring in the generic planning elements and ground them:
Use 1–2 citations to show these elements are standard planning practice, not just your invention.[5][6]
3. Two eras, same blind spot
Job: show that both last‑century and MVP cultures miss the system.
You can use 2–3 sentences for each era:
Then your key twist:
Citations: one for MVP/Lean Startup history; one from your quick‑fix research on accumulating complexity under constant change.[7][2][1]
4. Mental models → culture → quick fixes
Job: connect mental models to everyday behaviour and to your research.
A short explanation:
Then drop in 2–3 lines from your research, in narrative form:
This section is where you lean hardest on the attached research; it directly supports your description of firefighting culture.
5. The personal audit (your questions)
Job: move from “this is the pattern” to “this is your business.”
Introduce your questions as a simple self‑diagnostic box:
One sentence framing it: “If any of these land uncomfortably close to home, your real problem isn’t effort or talent; it’s the mental model and culture your current ‘plan’ has created.”[1]
6. Redefine “plan” for this book
Job: pivot from critique to promise.
Define the kind of plan you care about:
You can nod to PDCA / structured problem‑solving here without going into detail yet: “Later in the chapter we’ll use a simple Plan–Do–Check–Act loop as the engine for changing this operating model on purpose, instead of through quick fixes.”[9][1]
7. Bridge to the rest of the chapter
Job: set up the next sub‑chapters and the emotional payoff.
You already have the line; place it here:
Then signpost:
How to use citations overall
Given your aims:
If you like, next step can be: you paste a revised draft following this spine, and it can be tightened line‑by‑line while keeping citations aligned.
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.