Skip to content
Roof (Vision/Mission/Purpose): Plan clarifies whether a proposed change actually supports your direction, not just this month’s panic. Walls (Systems & Processes, Communication): Do and Check live here—this is where you run small trials and watch what really happens at hand‑offs. Foundation (Legal, Finance & Accounting, Cash Flow): Act is where you decide what becomes “how we do things,” with real impact on cost, risk, and cash. Inside the house (Leadership & Teams): The whole loop shapes culture; you reward people for learning and improving, not just for heroic firefighting.
PDCA as the business’s maintenance routine (keeping the house from falling apart). PDCA as a compounding habit (one small loop per week that quietly rewires the whole company over a year). Refine the “Loop: PDCA as the backbone” section to match your voice.Design your adapted PDCA (with your problem/impact narrative baked into Plan/Check).Shape the “Devil in the detail” story so it lands like a gentle slap in the face for chronic fix‑first leaders.
The loop: PDCA as the backbone
PDCA is the simple loop that turns “we should fix this” into “we actually fixed this and learned from it.”
The loop: PDCA as the backbone
Most small businesses already do parts of PDCA without calling it that. Someone notices a problem, people try something, they see if it helped, and they either keep it or quietly drop it. The issue isn’t that SMEs don’t improve; it’s that the improvement rhythm is random, undocumented, and driven by whoever is shouting loudest that week. PDCA gives that messy instinct a simple, repeatable structure, so you can change the business on purpose instead of by accident.
At its core, PDCA is just four questions you ask in order, again and again:
For SMEs, the key word is small. In big companies, PDCA often turns into a giant project with decks and templates. In a 20–200 person business, you want tiny, fast cycles that fit into the week, not into a quarter. You don’t “roll out PDCA”; you pick one nagging issue, run a quick loop with your team, and repeat. Over time, this builds a habit of testing assumptions instead of debating opinions.
You can lay this loop over your “business house” so it never becomes abstract:
A simple illustration you might use: imagine a small plumbing firm that constantly shows up late to jobs. Instead of buying another van or hiring another coordinator, they run one PDCA loop around “first job start time” for two weeks. They tighten the previous‑day scheduling (Plan), test a new 5‑minute morning check‑in call (Do), compare on‑time arrival rates before and after (Check), and then standardise the check‑in only if it clearly works (Act). No big project, no new software—just one loop, one part of the house, and one clear learning.
If you like this direction, the next sections can zoom in and “colour in” each step with your specific flavour: starting with problem/impact clarity in Plan, root cause tools inside Plan/Check, and how you lock in changes so they don’t slide back.
That sounds like a good plan – letting it simmer usually makes the chapter sharper.
One thought to park in the back of your mind as you drift off: PDCA is really just a weekly thinking habit more than a “tool.” If you picture your ideal reader having one standing ritual where they pick a bottleneck, run one tiny experiment, and then decide whether to lock it in or drop it, you’ll naturally keep your explanation concrete and de‑jargonised.
Sleep on which angle feels most “you”:
When you’re back, we can:
Rest well — this chapter’s going to be a strong pivot into the real “how.”
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.