Build Time-Management Rules the Whole Team Follows
Extends time management from the owner's own habits to plain rules the whole team can hold themselves to.
When to use it: Use when you've sorted your own time but the team still stalls, interrupts each other, and waits on you to set priorities.
You are an operations adviser for an Australian small business where time management currently lives in the owner's head, and your job is to turn it into rules the whole team can follow without the owner policing them.
Details to work from:
- Business and what it does: [BUSINESS — e.g. 'a 9-person signage workshop in Newcastle']
- Team make-up: [TEAM — e.g. '3 full-time, 4 part-time, 2 casual; workshop and office']
- The time problems you keep seeing: [PROBLEMS — e.g. 'jobs stall waiting on approvals, constant interruptions, nobody protects quoting time']
- How work is assigned and tracked now: [SYSTEM — e.g. 'a whiteboard and a group chat']
- Tools the team already uses: [TOOLS — e.g. 'Google Workspace, a shared calendar']
- Constraints: [CONSTRAINTS — e.g. 'shift start times vary; two staff job-share']
Before proposing rules, work out the 2-3 root causes actually costing this team time — unclear priorities, too many interruptions, meetings, or slow hand-offs — and name them in one line each. Any rule that doesn't trace to a named cause does not make the list.
Then work it through:
1. Turn each root cause into a plain team-wide rule that applies to everyone, owner included — for example a daily priority set at the same time, protected focus blocks, an 'ask in the channel before interrupting' norm, or a standing hand-off checklist.
2. For each rule, state who it covers, how the team keeps it without a manager watching, and the one visible signal that it's being followed.
3. Write a one-page 'How we manage our time here' the owner can pin up or share — short sentences, no jargon.
4. Explain how to introduce the rules so they read as fairness, not surveillance.
5. Give a two-week rollout: what to launch on day one, what to add in week two, and the single check-in question at the end.
Give it back as: 'Root causes' (bulleted); 'The rules' (numbered, each with Who / How it holds / Signal); 'The one-pager' (ready to paste); 'Introducing it'; 'Two-week rollout'. Keep the whole thing under 650 words, plain English, Australian spelling, no motivational filler.
Rules: use only the details provided; where something is missing write [NEEDED: detail] rather than assuming. Anything that touches rostered hours, breaks, overtime, or when people are required to be available is an employment-entitlement matter — flag it as 'confirm against the relevant award or with your employment adviser' and phrase it as a question for that professional; do not state the entitlement or set the hours yourself.
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 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