Efficiency Works 20-Minute Bottleneck Audit
Identify and systematically eliminate the process, people, and information bottlenecks dragging down your productivity — and build a self-running continuous improvement system so gains stick without your constant involvement.
// TL;DR
The Efficiency Works 20-Minute Bottleneck Audit is a lean framework for finding and eliminating the process, people, and information bottlenecks that quietly drag down productivity. In four fast steps, you pick one lagging focus area, ask four diagnostic questions, observe the workflow, and classify every finding into one of three bottleneck types. You then build a self-running continuous improvement system on three pillars — Recognise, Educate, Implement. Use it whenever a team faces inconsistent output, recurring fires, or a stubbornly flat efficiency number, especially at the start of a planning cycle or any time you're reacting more than leading.
// When should you run the 20-Minute Bottleneck Audit?
Use this skill whenever a business, department, or team is experiencing inconsistent productivity, recurring fires, or a stubbornly flat efficiency number. Apply it at the start of a new planning cycle or any time you are reacting more than leading.
// What do you need before starting a bottleneck audit?
- Focus Arearequired
A single department, production line, product family, or small process segment where performance is lagging — not the whole business. - Current Efficiency Numberrequired
Your baseline KPI expressed as a percentage (e.g., 70% achievement to plan, 70% billable hours, 70% equipment utilisation). The specific metric type does not matter — any meaningful productivity or efficiency KPI works. - Target Efficiency Number
Where you want that KPI to be by end of the financial year (e.g., 80%). - Business / Org Type
Brief description of the operation (e.g., NDIS provider, law firm, manufacturer, event agency) so bottleneck language can be contextualised.
// What core principles drive the Bottleneck Audit framework?
Root Cause Is Never People
When productivity is low, the instinct is to blame staff. The real problem is always bottlenecks caused by poor processes, lack of processes, or no continuous improvement system. Investigating with this lens is the prerequisite for every step that follows.
Process-Dependent vs People-Dependent
A business that relies on specific individuals for knowledge, approvals, or quality is inherently fragile and unscalable. The goal is to shift from people-dependent to process-dependent operations — so that removing any one person does not stop the system.
Recognise, Educate, Implement
Every continuous improvement system rests on three must-haves: (1) a systematised way to Recognise bottlenecks daily, (2) ongoing Education that builds staff capability in improvement tools, and (3) structured Implementation of improvement projects — on autopilot, not ad hoc.
Intention Is Not a Plan
Most businesses intend to improve but very few actually plan to improve. Entering a financial year with motivation but no structured direction guarantees you will spend it reacting and fighting fires.
The System Creates Time
The most common objection to building a continuous improvement system is 'we don't have time.' Running the system generates time — if a task takes 60 minutes today, the system may reduce it to 45 minutes, freeing 15 minutes. The upfront investment in time and education pays for itself.
Improvement on Autopilot
The benchmark for a mature system is that bottlenecks are recognised by everyone (not just the leader), education is the norm, and improvement projects happen without the leader driving every one. If the system stops when you step away, you do not yet have a true system.
// How do you run the Bottleneck Audit step by step?
- 1
Record your baseline efficiency number and set a target
Write down your current KPI percentage before doing anything else. This is your reflection anchor. Then name what a 10-point improvement would mean in real terms — to customers, staff, and revenue. Do this for the chosen Focus Area only, not the whole business.
- 2
Run the Traffic Light self-audit across all three must-haves
Score yourself Red (none), Yellow (some), or Green (all) against each of the three must-haves — Recognise, Educate, Implement. Be honest. Most organisations are Red. The audit reveals which pillar to prioritise first. Do not skip this; it stops you solving the wrong problem.
- 3
Pick one Focus Area and run the 20-Minute Business Audit
Choose a small, specific area where work piles up, delays are frequent, or frustration is visible — not a whole department. Resist the urge to audit everything at once.
- 4
Ask the four diagnostic questions of that Focus Area
Question 1: Where does the work pile up or slow down? Question 2: Who are the go-to people everything flows through? Question 3: Where do teams lose time waiting for information, parts, or approval? Question 4: What causes you the most delays in your work? Observe directly for 10 minutes (walk the floor or review the workflow) AND ask frontline staff — both methods are required. Frontline staff will answer without hesitation.
- 5
Classify every finding into one of the three bottleneck types
Process Bottleneck — work piles up before or after a step; visible at peak load; some people are overwhelmed while others wait. People Bottleneck — one person holds all key knowledge or approvals; delays spike when that person is absent or busy (the 'Bill on holidays' pattern). Information Bottleneck — rework caused by unclear, late, or incomplete instructions/specifications; constant clarification requests from frontline staff. Record each finding and its type in an Improvement Register (even a basic spreadsheet). Note which issues appear more than once — frequency is a signal of systemic, not random, failure.
- 6
Build the Recognise pillar into daily operations
Install a systematised daily mechanism — not ad hoc — to surface bottlenecks. This includes: a Daily Huddle with a fixed agenda everyone knows in advance; a Problem Register (or improvement register / ticketing system for ideas) where any team member can log an issue; a structured feedback loop from both internal and external clients. The test: does this happen without you initiating it?
- 7
Build the Educate pillar — train staff in improvement tools
Select the lean and operational excellence tools relevant to your bottleneck types (e.g., root cause analysis, process mapping, 5S, takt time, line balancing). Create a competency matrix so you know who can use which tools. Schedule recurring leader time to review scorecards and improvement projects, and separate scheduled time for leaders to upskill themselves. Education must be the norm, not a one-off event.
- 8
Build the Implement pillar — run improvement projects on a cadence
Do not try to fix every bottleneck at once. Pick one. Assign it. Manage it through your improvement register. Celebrate completed projects visibly — recognition drives the culture. Use data, not gut feel, to make decisions and validate that a fix has worked. Once one project is embedded, layer in the next. Over time this compounds into ongoing improvement without leader intervention.
- 9
Stress-test the system against the 'take me out of the picture' test
Ask: if I stepped away for two weeks, would the Recognise–Educate–Implement cycle keep running? If the answer is no, identify the single point of people-dependence and apply the bottleneck-resolution process to the system itself. A true continuous improvement system outlives any individual.
- 10
Review your efficiency number against the target and repeat
At regular intervals (daily check on the huddle scorecard, monthly review of the improvement register), compare actual KPI to target. Grade each pillar again with the Traffic Light. Prioritise the next Red. The loop is: recognise → educate → implement → measure → repeat.
// What does the Bottleneck Audit look like in real businesses?
A professional services firm (e.g., NDIS provider) billing 70% of planned hours. Leaders spend most of their day chasing approvals and clarifying incomplete client briefs.
Run the 20-Minute Business Audit on the intake-to-delivery process. Step 4 reveals: (a) one senior coordinator approves all new service plans — a People Bottleneck ('Bill on holidays' pattern); (b) incomplete referral documentation triggers constant back-and-forth — an Information Bottleneck. Build the Recognise pillar by installing a daily huddle and a problem register. Educate staff in process mapping to redesign the intake checklist. Implement a delegation matrix so two people can approve plans. Target: shift billable hours from 70% to 80% within the financial year.
A product-based business where some production stations are overwhelmed at peak periods while downstream staff stand idle.
Walk the floor during peak load — the 20-Minute Business Audit will immediately surface the Process Bottleneck (work piling up before a specific machine or step). Classify it, log it in the improvement register, then apply takt time analysis and line balancing (Educate pillar tools) to redistribute workload. Install a daily huddle scorecard tracking throughput. Implement the fix as a formal project with a before/after efficiency number. Celebrate the win publicly to embed the culture.
A service business where quality is inconsistent — great one week, poor the next — and customers are unpredictable in their loyalty.
Inconsistency is the signature of a people-dependent, not process-dependent, operation. Run the Traffic Light audit: all three pillars are likely Red. Start with the Recognise pillar — install a problem register and a daily huddle. Map the core delivery process to identify which steps rely on individual skill versus documented procedure. Begin converting undocumented knowledge into standard processes. Use the McDonald's benchmark: the system should produce consistent output regardless of which team member executes it.
// What mistakes should you avoid when auditing bottlenecks?
- Blaming people for productivity problems — root cause is never people; it is always process, information, or system failure.
- Auditing the whole business at once instead of one small, specific Focus Area first.
- Confusing intention with a plan — entering a cycle motivated but without a structured Recognise–Educate–Implement system guarantees you will spend it reacting.
- Making decisions on gut feel rather than data — the improvement register and scorecard exist to prevent this.
- Building a system that only runs when the leader drives it — if it stops when you step away, it is not a true continuous improvement system.
- Trying to implement all nine improvement projects simultaneously — pick one, embed it, then layer the next.
- Skipping the Traffic Light self-audit and jumping straight to fixes — without knowing which pillar is Red, you risk solving the wrong problem.
- Believing you do not have time to build the system — the system itself creates time by reducing task duration; the constraint is upfront investment, not ongoing capacity.
- Observing the workflow only during quiet periods — process bottlenecks are only clearly visible at peak load.
// What key terms should you know for the Bottleneck Audit?
- Continuous Improvement System
- A structured, self-running operational framework comprising the three must-haves — Recognise, Educate, Implement — that surfaces and eliminates bottlenecks on an ongoing basis without requiring constant leader intervention.
- Recognise, Educate, Implement
- The three must-haves of any operational excellence system. Recognise = systematised daily bottleneck detection. Educate = ongoing staff capability-building in improvement tools. Implement = structured project execution tracked in an improvement register.
- Process Bottleneck
- A step or station in a workflow where work piles up or slows, most visible during peak load. Clue: some people or machines are overwhelmed while others downstream are idle and waiting.
- People Bottleneck
- A situation where one person holds all key knowledge or approvals, causing delays whenever that person is absent or busy. Named internally as the 'Bill on holidays' pattern.
- Information Bottleneck
- Delays caused by unclear, late, or incomplete instructions or specifications, resulting in rework, constant clarification requests, or errors that must be redone.
- 20-Minute Business Audit
- A four-step rapid diagnostic: (1) pick a Focus Area, (2) ask the four diagnostic questions, (3) observe the workflow for 10 minutes and talk to frontline staff, (4) note patterns and classify findings by bottleneck type using an audit worksheet.
- Traffic Light (Red / Yellow / Green)
- A self-assessment scoring system applied to each of the three must-haves. Red = none of the practices in place. Yellow = some practices in place. Green = all practices fully operational.
- Improvement Register
- A living log of identified bottlenecks, in-progress improvement projects, and completed fixes. Enables the team to track what has been done, celebrate success, and maintain momentum without leader prompting.
- Daily Huddle
- A short, structured daily team communication session with a fixed, pre-known agenda used to surface bottlenecks, share scorecard data, and drive accountability within the Recognise pillar.
- Process-Dependent vs People-Dependent
- The spectrum of operational maturity. People-dependent businesses rely on specific individuals for quality and consistency — output varies when those people are unavailable. Process-dependent businesses (the McDonald's benchmark) produce consistent output regardless of which team member executes the process.
- Operational Excellence
- The target state characterised by consistency, predictability, structure, genuine staff engagement, and a process-driven (rather than people-driven) operation — achieved through a mature Recognise–Educate–Implement system.
- Process Maturity
- An organisation's current level of systematisation, ranging from constantly fire-fighting (Red) through ad hoc improvement (Yellow) to a fully embedded continuous improvement system that proactively eliminates bottlenecks (Green / top 5%).
// FREQUENTLY ASKED QUESTIONS
What is the 20-Minute Bottleneck Audit?
It's a rapid four-step lean diagnostic that finds the bottlenecks dragging down productivity in a single focus area. You pick one small area, ask four diagnostic questions, observe the workflow for 10 minutes while talking to frontline staff, then classify every finding as a process, people, or information bottleneck. It's the entry point to building a self-running continuous improvement system.
What are the three types of bottlenecks in this framework?
Process, people, and information bottlenecks. A process bottleneck is where work piles up at a step, most visible at peak load. A people bottleneck is when one person holds all knowledge or approvals — the 'Bill on holidays' pattern. An information bottleneck is rework caused by unclear, late, or incomplete instructions triggering constant clarification requests.
How do I run a bottleneck audit on my team?
Record your current efficiency number, then pick one small focus area — not the whole business. Ask four questions: where does work pile up, who is everything routed through, where do teams wait, and what causes the most delays. Observe the workflow for 10 minutes at peak load AND ask frontline staff. Log and classify each finding by bottleneck type in an improvement register.
How do I know which bottleneck to fix first?
Run the Traffic Light self-audit across the three must-haves — Recognise, Educate, Implement — scoring each Red, Yellow, or Green. Prioritise your most Red pillar first. Within that, note which bottlenecks appear more than once, because frequency signals a systemic rather than random failure. Never fix everything at once; pick one, embed it, then layer the next.
How does this compare to just hiring more staff or working harder?
Hiring or pushing harder treats the symptom while the framework targets the root cause, which is never people — it's always broken processes, missing processes, or the absence of a continuous improvement system. Adding staff to a bottlenecked process just moves the pile-up. This audit fixes the underlying flow so output improves without added headcount or overtime.
When should I use the Bottleneck Audit?
Use it whenever a business, department, or team has inconsistent productivity, recurring fires, or a stubbornly flat efficiency number. It's ideal at the start of a new planning cycle or any time you're reacting more than leading. Inconsistent quality week to week is a classic trigger — it signals a people-dependent operation that the audit is designed to systematise.
What results can I expect from building this system?
You can expect a measurable lift in your core efficiency KPI — the framework's benchmark example is moving billable hours or achievement-to-plan from 70% to 80% within a financial year. Beyond the number, you get consistent output regardless of who's working, fewer daily fires, and freed-up leader time. The system itself creates time by reducing task durations.
Why does the framework say the problem is never the people?
Because when productivity is low the instinct to blame staff misdiagnoses the cause. Bottlenecks come from poor processes, lack of processes, or no continuous improvement system — not from lazy or incapable people. A good process makes average staff productive; a bad process makes great staff look ineffective. Investigating with this lens is the prerequisite for every step that follows.
What does 'process-dependent vs people-dependent' mean?
It's the spectrum of operational maturity. People-dependent businesses rely on specific individuals for knowledge, approvals, and quality, so output varies when those people are unavailable — inherently fragile and unscalable. Process-dependent businesses (the McDonald's benchmark) produce consistent output regardless of which team member executes the work. The framework's goal is shifting your operation from people-dependent to process-dependent.
What is the 'take me out of the picture' test?
It's the stress test that proves whether you have a true continuous improvement system. Ask: if I stepped away for two weeks, would the Recognise–Educate–Implement cycle keep running? If the answer is no, you've found a single point of people-dependence — so apply the bottleneck-resolution process to the system itself. A true system outlives any individual.