Find and Fix Your Worst Workflow Bottleneck
Trace where work actually queues up in your operation, identify the true bottleneck, and apply focused fixes to that point only.
When to use it: When everything feels slow and everyone feels busy, and speeding up random parts hasn't sped up the whole.
You are a workflow analyst for Australian small businesses, trained on one stubborn truth: a business moves at the speed of its single tightest constraint, and improving anywhere else is invisible.
My core workflow, start to finish: [WORKFLOW — how a job/order/client moves through: e.g. enquiry → quote → approval → schedule → do the work → invoice → paid, with who handles each and typical wait at each stage]
Where work visibly piles up: [PILES — e.g. eight quotes 'in progress'; finished jobs uninvoiced for a fortnight]
What I've tried: [TRIED — e.g. hired an extra hand on the tools; new project app nobody opens]
Demand situation: [DEMAND — turning work away? / just keeping up? / hungry for more]
Work through this in order:
1. THE QUEUE MAP — restate my workflow as stages with, per stage: WORK TIME (actual doing) vs WAIT TIME (sitting in a pile), from my description. Mark [?] where I didn't say and ask. The bottleneck is where wait time dwarfs work time — name your candidate and the evidence from my own words.
2. THE CROSS-CHECK — test the candidate: if that stage doubled its speed tomorrow, would jobs finish sooner, or just queue at the next stage? Reason it through my map. Also check my TRIED list — if I added capacity somewhere that wasn't the bottleneck, gently point out why nothing changed.
3. THE FIXES — for the confirmed bottleneck only, in escalating order: DRAIN (clear the backlog with a one-off blitz — sized plan), PROTECT (stop the bottleneck stage doing anything a non-bottleneck stage could absorb — name what moves and to whom, from my described roles), SMOOTH (batch or template the stage's repetitive parts — specifics from my workflow), and only then ADD (more capacity, with what that costs in my terms).
4. THE RELIEF VALVE — what feeds the bottleneck: one rule to stop overloading it (e.g. qualify enquiries before quoting everything that moves, if quoting is my constraint and demand allows).
5. THE PROOF — one number to track weekly that shows end-to-end speed (enquiry-to-paid days, or jobs completed per week), so the fix shows up in reality, not vibes — baseline first fortnight, then compare.
6. THE NEXT ONE — when this bottleneck opens, the queue map says where the constraint moves next; note it so I'm not surprised.
Use only my described workflow and piles — invent no stages, staff or numbers. If the bottleneck turns out to be me approving everything, say it kindly but plainly.
Copy the block above straight into Any AI tool — anything in [BRACKETS] is yours to fill in.
Want it tuned to your business? Bring it to the free weekly call and we'll adapt it live.
Join the free callMore au business & compliance prompts
Plain-English Contract Summariser
Understand what you're signing before you sign it — and know what to ask a professional
Set Up Redirects and Caching on an Apache Site
Get a ready-to-paste .htaccess block with redirects, HTTPS forcing and caching, plus install, test and undo steps.
Script a Hard Conversation Before You Have It
Turn a dreaded workplace conversation into a short, direct script with openers, key lines and responses to likely reactions.