Who this is for
Owners and office people who feel “always behind” but can't point at one task. If you already know the stuck job by name, you can skim to the log template — but don't skip the logging itself.
Pick a task with a clear finish
About 5 min
Choose something you can say in one sentence. It must have an observable finish — a moment you can point at and say “done.”
- Write the task in one sentence, ending with the finish. Three shapes that work:
- Put each new inquiry into the job list with an owner and next step
- Find a job's status and draft a customer update
- Gather the details needed to prepare an estimate
- Test the sentence: point at the exact moment you'd say “done.” If you can't point, narrow it.
Pick “fix the office” or “answer the phone better.” Those aren't tasks — they're wishes. One job, one finish line.
Set up the log
About 5 min
Seven columns. Notebook, Notes app, or spreadsheet — the tool doesn't matter. Use job references, not full customer details, in anything shared.
Mon 9:40a · Missed call → voicemail · 12 min hands-on, 35 min waiting on tech ETA · Exception: customer called twice · Finish: text-back sent with window.
Notice the split: 12 minutes of work, 35 of waiting. That split is the whole lesson — yours below.
| Date / time | Trigger | Inputs | Hands-on min | Waiting min | Exception | Finish |
|---|---|---|---|---|---|---|
| Mon 9:40a | Missed call → voicemail | Voicemail + job board | 12 | 35 — waited on tech ETA | Customer called twice | Text-back sent w/ window |
| (tap to edit) | ||||||
The table above is an editable preview — tap any cell and type. The canonical copy is the print-ready PDF:
↓ Download the 7-day log (PDF)
Example row — your PDF has 8 blank runs
- Date / time
- Mon 9:40a
- Trigger
- Missed call → voicemail
- Hands-on
- 12 min
- Waiting
- 35 min — tech ETA
- Exception
- Customer called twice
- Finish
- Text-back sent w/ window
Do this week
Log every run of that task for seven days. The discipline that matters: keep hands-on and waiting in separate columns. Waiting is where the week actually goes, and it's the part people never measure.
Try this
Tonight, log one run from memory — yesterday's counts. Date, trigger, hands-on minutes, waiting minutes.
You should see: one filled row where waiting has its own number. If waiting is blank, that's the finding — keep watching it.
Log only the easy runs. Keep going until an exception shows up — the messy case is where the fix hides.
Read the week
About 10 min, day 7
Answer three questions, then write one sentence:
- Find which step repeats.
- Find which step creates delay.
- Mark which cases need human judgment.
Your one sentence
“The smallest useful change is ___.”
A form field, a checklist, a template — or “not sure, I need a brief,” which sends you to Module 03 with something real in hand.
Success check
- ≥5 logged runs (or an honest note that it only happened N times)
- Hands-on vs waiting separated at least once
- One written “smallest change” candidate
Common failure modes
| Failure | Fix |
|---|---|
| Task too broad | Narrow to one finish line |
| Only logging easy cases | Keep going until an exception shows up |
| Counting waiting as hands-on | Split the columns |
| Jumping to “buy a bot” | Stay on the log until day 7 |
When to stop / don't buy yet
Do not buy automation, a chatbot, or a custom build from this module alone. If the log shows missing inputs, fix collection first. If volume is tiny, a checklist may beat software — permanently.
Adapted from the field note “Before you automate, track one task.”
Bring it to a free 30-minute consult. Fixed price after scoping — and an honest “don't spend it” if that's the answer.