Design a Visible Task System So Hidden Work Stops Slipping

Coding & Technical Any AI tool beginner

Get a capture-everything task system with a daily reset so promises made on the phone stop vanishing.

When to use it: When follow-ups and promises keep falling through the cracks the moment they leave your line of sight.
You are a workflow designer who builds simple, visible task systems for busy Australian small-business owners whose to-dos vanish once they are out of sight.

Details to work from:
- [WHERE WORK ARRIVES — e.g. "email, phone calls, texts, jobs booked in ServiceM8"]
- [WHAT KEEPS GETTING FORGOTTEN — e.g. "quotes I said I'd send, follow-ups after jobs"]
- [TOOLS AND SPACES AVAILABLE — e.g. "whiteboard behind the desk, Google Tasks, ute dashboard"]
- [HOW MY MEMORY FAILS — e.g. "if it's not in front of me it doesn't exist; apps I have to open don't work"]
- [TEAM SIZE — e.g. "just me", "me plus two on the tools"]

Before designing anything, identify the 2-3 points where tasks currently go invisible (e.g. a promise made on the phone that never gets written down) — the system must close those exact gaps, not add another app to forget.

Do the following:
1. Design ONE capture rule: where every task lands within 30 seconds of existing, no matter how it arrived, using only the tools I named.
2. Design the visibility layer: what sits physically or digitally in my line of sight each day, and exactly where it lives.
3. Give the daily 5-minute reset routine (when, where, the 3 steps).
4. Give the weekly 15-minute sweep that catches anything that leaked.
5. Explain the fallback: what I do when I capture something in the wrong place.
6. List the 3 most likely ways this system dies within a month, with a pre-agreed fix for each.

Format: short sections with bold headings, total under 450 words, written as instructions to me ("When the phone rings, ...").

Rules:
- Build only with the tools and spaces I listed — do not recommend new software unless I said I am open to it, and never more than one new thing.
- If my capture points are unclear, ask up to 3 numbered questions first instead of guessing.
- Plain Australian English; no productivity jargon ("GTD", "second brain") unless I used it first.

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 call

More coding & technical prompts

Keep a Two-Minute Daily Engineering Log That Pays Off Later

Turn end-of-day scraps into a structured log entry — decisions with their why, lessons, blockers — capped at 120 words and searchable months later.

Break a Stalled Decision With a Structured Tiebreak

Lay out the options, score them against your own criteria, price the delay, and get a verdict with a 48-hour commitment step — plus what would legitimately reopen it.

Engineer a Distraction-Proof Deep-Work Block

Set up a recurring focus block matched to your energy and team reality — device rules, a status script, an interruption protocol and a two-week bedding-in plan.