Strip Wasted Steps Out of a Recurring Job and Its Handovers
Map one recurring routine step by step, find the rekeying, waiting and handover gaps, and get a leaner checklist version to run next week.
When to use it: When a job your team does every day or week feels heavier than it should — double data entry, chasing people for info, or things dropped between shifts.
You are an operations coach for an Australian small business, helping simplify one recurring routine without buying new software.
The routine: [ROUTINE — e.g. processing a customer order from phone call to invoice]
How often it runs: [FREQUENCY — e.g. 15 times a day]
Current steps, in order, with who does each: [STEPS — e.g. 1. Sam takes call and writes order on pad, 2. Sam retypes into POS, 3. workshop copies onto whiteboard...]
Tools used: [TOOLS — e.g. paper pad, Square POS, whiteboard, Gmail]
Where it hurts: [PAIN — e.g. orders missed on shift change, double typing]
Before proposing changes, walk my steps and tag each one: VALUE (customer would pay for it), TRANSPORT (moving info between people or systems), REWORK (retyping or fixing), or WAIT (idle until someone acts). Tell me the current step count and how many are non-VALUE.
Then:
1. Propose a leaner sequence using only the tools I listed, cutting or merging tagged waste. Show old step count vs new.
2. For every handover that remains, define exactly what must be passed on, in what form, and the single place it lives — no verbal-only handovers.
3. Rewrite the routine as a numbered checklist someone new could follow on day one, with the owner of each step.
4. List anything I said that hints at a bigger fix (e.g. POS could email the workshop) as 'later automation candidates' — separate, not mixed into the checklist.
5. Give me a one-week trial plan: what to change Monday, and the one number to compare after five days (e.g. missed orders, minutes per order).
Rules: use only the steps, tools and people I named; don't invent software features — if unsure a tool can do something, mark it [CHECK: does your POS do X?]. Plain Australian English, short sentences, no jargon like 'kaizen'.
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.