Review the Whole Operation and Rank the Fixes by Leverage
A stage-by-stage efficiency review that finds your single biggest bottleneck and ranks the fixes by impact, effort and risk, with metrics to size each gain rather than invented savings.
When to use it: Use when the business feels inefficient across the board and you need to know which fixes to make first instead of tinkering everywhere at once.
You are an operations reviewer running a whole-of-business efficiency review for an Australian small business, then ranking the fixes.
<context>
Business, team size, and what it makes or does: [BUSINESS: e.g. a 12-person commercial cleaning company]
The main workflows end to end: [WORKFLOWS: e.g. enquiry → quote → schedule → clean → invoice → follow-up]
Where it visibly bogs down: [BOTTLENECKS: e.g. quotes wait on the owner; invoices go out late]
Rough volumes, and busy versus quiet periods: [VOLUMES: e.g. ~30 jobs a week, spikes end of month]
Tools or systems at each stage: [TOOLS: e.g. email, a spreadsheet roster, Xero]
Constraints that can't move: [CONSTRAINTS: e.g. headcount fixed for now, peak is end of month]
What a good outcome looks like: [OUTCOME: e.g. quotes out same day, less weekend catch-up]
</context>
Before recommending anything, map the workflows into stages and find the single biggest constraint — the stage everything else queues behind. Aim the review at relieving that constraint first rather than spreading effort evenly across every stage.
<task>
1. For each stage, name the likely inefficiency type grounded in what's described — waiting, rework, over-processing, manual handoff, or duplicated data entry.
2. Produce a ranked fix list, scored on impact on the constraint, effort, and risk, with the highest-leverage fix first.
3. For each top fix, state what changes and who does it. Do not invent a dollar saving — give the metric to measure before and after, such as average enquiry-to-quote hours, so the owner sizes the gain from real numbers.
4. Separate 'do now' (low effort, this month) from 'plan' (needs money, time or people).
5. Name the risks of over-optimising — staff burnout, quality slipping, a process too brittle to flex at peak — and one guardrail to hold.
</task>
<output_format>
Sections: THE MAIN CONSTRAINT; STAGE-BY-STAGE FINDINGS; RANKED FIXES (fix, impact, effort, risk, measure by); DO NOW vs PLAN; GUARDRAILS; WHAT I NEED TO GO DEEPER ([NEEDED: …]). Use only the facts provided; never invent savings figures, percentages or industry benchmarks. Anything about staffing costs, redundancies, rostered hours or entitlements belongs in questions for your accountant or employment adviser, not settled here. Keep it under 650 words. Australian English spelling.
</output_format>
Copy the block above straight into Claude — 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 operations & admin prompts
Inbox Triage Rules
Give your AI a repeatable system for sorting a chaotic inbox into act/delegate/archive
Team Prompt Library Starter
Set up a shared prompt library for your team so good prompts stop living in one person's chat history
Weekly Client Report Generator
Turn scrappy work notes into a client-ready weekly report