Frequently Asked Questions About Efficiency Works 20-Minute Bottleneck Audit
21 answers covering everything from basics to advanced usage.
// Basics
What is a continuous improvement system in simple terms?
It's a structured, self-running operational framework built on three must-haves — Recognise, Educate, Implement — that surfaces and eliminates bottlenecks on an ongoing basis without needing constant leader intervention. Recognise means detecting bottlenecks daily, Educate means building staff capability in improvement tools, and Implement means running improvement projects as tracked projects. If the system stops when you step away, it isn't yet a true one.
What does Recognise, Educate, Implement actually mean?
These are the three pillars every operational excellence system rests on. Recognise is a systematised daily way to surface bottlenecks — like a daily huddle and problem register. Educate is ongoing capability-building so staff can use improvement tools such as root cause analysis and process mapping. Implement is structured project execution tracked in an improvement register. All three must be on autopilot, not ad hoc.
What's the difference between intention and a plan in this framework?
Intention is wanting to improve; a plan is a structured Recognise–Educate–Implement system with direction. Most businesses intend to improve but very few actually plan to improve. Entering a financial year motivated but without structure guarantees you'll spend it reacting and fighting fires. The framework converts vague intention into a concrete, repeatable system.
What is the Traffic Light self-audit?
It's a self-assessment where you score each of the three must-haves Red, Yellow, or Green. Red means none of the practices are in place, Yellow means some are, and Green means all are fully operational. Most organisations are Red across all three. The audit reveals which pillar to prioritise first and stops you from solving the wrong problem.
// How To
How do I set up the Recognise pillar in daily operations?
Install a systematised daily mechanism, not ad hoc firefighting. This includes a daily huddle with a fixed, pre-known agenda; a problem register or ticketing system where any team member can log an issue; and a structured feedback loop from both internal and external clients. The test: does this happen without you initiating it?
How do I build the Educate pillar without a big training budget?
Start by selecting only the lean tools relevant to your identified bottleneck types — root cause analysis and process mapping for information issues, takt time and line balancing for process issues, 5S for workspace flow. Build a competency matrix so you know who can use what. Schedule recurring leader time to review scorecards plus separate time to upskill. Make education the norm, not a one-off event.
How do I run improvement projects on a cadence?
Pick one bottleneck — never all at once. Assign it, manage it through your improvement register, and validate the fix with data, not gut feel. Celebrate completed projects visibly because recognition drives the culture. Once one project is embedded, layer in the next. Over time this compounds into ongoing improvement that no longer needs leader intervention.
How do I record findings during the audit?
Log every finding and its bottleneck type in an improvement register — even a basic spreadsheet works. Note which issues appear more than once, because frequency is a signal of systemic rather than random failure. The register becomes a living log of identified bottlenecks, in-progress projects, and completed fixes that maintains momentum without leader prompting.
// Troubleshooting
My audit didn't reveal any obvious bottleneck — what went wrong?
You likely observed the workflow only during a quiet period. Process bottlenecks are only clearly visible at peak load, when work piles up before a step while downstream staff wait idle. Re-run the observation during your busiest window, and be sure to ask frontline staff directly — they'll answer without hesitation and often name the bottleneck instantly.
I fixed a bottleneck but the delay just moved somewhere else — why?
That's normal — relieving one constraint exposes the next one downstream. It means your fix worked and revealed the true next priority. Re-run the four diagnostic questions on the new pile-up point, classify it, and log it in your improvement register. Continuous improvement is exactly this loop: recognise, educate, implement, measure, repeat.
My team says we don't have time to build this system — how do I respond?
Point out that the system generates time rather than consuming it. If a task takes 60 minutes today, the system may reduce it to 45, freeing 15 minutes every time it runs. The upfront investment in time and education pays for itself. The constraint is upfront investment, not ongoing capacity — 'no time' is the most common objection and it's backwards.
The system falls apart whenever I go on leave — how do I fix that?
Apply the 'take me out of the picture' test: if the Recognise–Educate–Implement cycle stops when you step away, you've found a single point of people-dependence. Treat the system itself as a bottleneck and apply the resolution process to it — document the huddle agenda, delegate register ownership, and cross-train facilitation so it runs without you.
// Comparisons
How does this framework compare to Six Sigma or generic lean training?
It's lighter and faster to start than a full Six Sigma deployment, using a 20-minute audit instead of lengthy DMAIC projects. Rather than teaching every tool upfront, it selects only the tools relevant to your specific bottleneck types. Generic lean training often stops at education; this framework insists on all three pillars — Recognise and Implement — so knowledge actually turns into results.
How is this different from just tracking KPIs on a dashboard?
A dashboard tells you the number is flat but not why. This framework diagnoses the underlying bottleneck causing the flat number, classifies it, and gives you a structured system to eliminate it. KPIs are the measurement; the audit and the three pillars are the mechanism that actually moves the KPI. The framework uses your KPI as the anchor, not the endpoint.
How does this compare to hiring a management consultant for a full review?
A full consultant review often audits the whole business at once and produces a heavy report. This framework deliberately targets one small focus area, produces action within 20 minutes, and hands ownership to your team rather than an external expert. The goal is a self-running system your people maintain — not a dependency on repeated outside engagements.
// Advanced
Why audit one small focus area instead of the whole business?
Auditing everything at once spreads attention thin and buries the real signal. Picking one small, specific area where work piles up, delays are frequent, or frustration is visible lets you diagnose accurately, fix decisively, and build a repeatable pattern. Once you've embedded improvement in one area, you replicate the loop elsewhere. Trying to boil the ocean is a named pitfall.
How do I spot a people bottleneck versus a process bottleneck?
A people bottleneck shows up as delays that spike when one specific person is absent or busy — the 'Bill on holidays' pattern — because that person holds all key knowledge or approvals. A process bottleneck shows up as work physically piling up before or after a step at peak load, with some people overwhelmed while others downstream sit idle. Different signatures, different fixes.
What is the McDonald's benchmark for consistency?
It's the standard of a fully process-dependent operation: the system produces consistent output regardless of which team member executes the process. Inconsistent quality — great one week, poor the next — is the signature of a people-dependent operation. The benchmark reminds you the goal isn't heroic individuals but a documented, standardised process anyone can run reliably.
How often should I re-run the audit and Traffic Light scoring?
Check the huddle scorecard daily and review the improvement register monthly against your target. At each interval, re-grade every pillar with the Traffic Light and prioritise the next Red. The loop is recognise, educate, implement, measure, repeat. This regular cadence is what keeps improvement compounding rather than stalling after the first win.
Does the specific KPI I use for my baseline matter?
No — the metric type doesn't matter as long as it's a meaningful productivity or efficiency KPI. It could be achievement to plan, billable hours, or equipment utilisation, expressed as a percentage. Record the baseline before doing anything else as your reflection anchor, then name what a 10-point improvement would mean in real terms to customers, staff, and revenue.
What is an improvement register and what goes in it?
It's a living log of identified bottlenecks, in-progress improvement projects, and completed fixes. Each entry records the finding, its bottleneck type, and whether the issue recurs. It lets the team track what's been done, celebrate wins, and maintain momentum without leader prompting. Even a basic spreadsheet works — the discipline of logging matters more than the tool.