Count it, before you fix it to save you time in the future.
Most small business owners can tell you their week was flat out. Very few can tell you what it went on.
That's not carelessness. It's that the work doesn't announce itself. Nobody books in "answered the same delivery question eleven times" or "rewrote the quote because the first version had last year's pricing". It just happens, in gaps, between the things you'd actually call your job.
So when it finally gets bad enough that you decide to fix something, you fix from memory. And memory is a terrible witness. It hands you the loudest problem, not the biggest one.
The fix is boring: count it first.
The one week tally
For five working days, keep a note open.
Phone, notebook, back of an invoice book, doesn't matter. Every time you switch to a new task, write down three things:
What you did
Roughly how long it took
Whether anyone else in the business could have done it
That's it. Round to five minutes. Don't build a spreadsheet, don't set up an app, don't make it a project. If logging takes more than ten seconds you'll stop by Wednesday.
One rule, and it's the one people break: don't fix anything during the week.
The instinct will be strong. You'll notice on day two that the same question keeps landing in your inbox and you'll want to go write the FAQ right then. Don't. You're measuring. If you start patching mid-week you'll end up with a half-fixed process and no data, which is worse than either.
Write the idea in the margin. Come back to it Friday.
What you'll actually find
Every business is different, but a few things turn up nearly every time.
Repeats. The same question, the same lookup, the same manual fix. On the day, each one is thirty seconds and not worth mentioning. Across a week it's ninety minutes. Across a year it's a fortnight of your life.
The tax on switching. You'll see how often a fifteen-minute job got cut in half by something else. The tally makes visible what a calendar never shows: not the length of the work, but how many pieces it got broken into.
Ghost tasks. Things you do because of a decision made two years ago that nobody has revisited. The double entry between two systems. The report you send weekly that one person opens quarterly. These are the cheapest wins in the business and they're invisible until you write them down.
The stuff only you can do. Column three is the uncomfortable one. Most owners find that between half and two thirds of what they touched that week could have been done by someone else — if that someone knew how. Which is a training and documentation problem wearing a workload costume.
Sorting it out on Friday
Take the list and put every line into one of four buckets.
Bin it. It doesn't need to exist. Stop doing it and see if anyone notices. Usually nobody does.
Trim it. It needs to exist but not in this shape. Fewer steps, fewer approvals, fewer places the information lives.
Give it away. Somebody else can do it once it's written down. Not delegated verbally in a rush — written down.
Guard it. It's yours, it's worth your time, leave it alone.
Do them in that order. There's no point handing over a task you were about to bin, and no point documenting a nine-step process that should be four.
Then pick one thing. Not five. One. The businesses that get out from under this are not the ones with the best plan, they're the ones that finish something before starting the next thing.
Why bother
Because "we're flat out" isn't a problem you can solve. It's a feeling. "We answer the same freight question fourteen times a week and it costs us two hours" is a problem you can solve, and you can solve it in an afternoon.
The tally isn't the work. It's what lets you stop guessing about the work.
Run it next week. It costs you nothing but the discipline to write things down while you're already annoyed.
If you hear your business from this article & want to discuss how The Creative Unload can help your business please reach out anytime at thecreativeunload@gmail.com
The Creative Unload works with small businesses across the world from North East Victoria on systems, automation and the unglamorous behind the scenes underneath them.