Why the work does not take a day off
Recurring work does not pause when the person who does it is away. It piles up instead.
A week off does not save the work. It defers it into a worse form, done all at once by someone who is also behind on everything else.
Not every business has this problem, and some should leave it alone.
Most of these can be done better. Whether it's worth doing is a separate question. What follows is one common form of the problem, described in general terms, because your version will differ. These are possible challenges, not a description of your business, and some should be left exactly as they are. If it sounds like your week, that's worth a conversation.
Watch: Dates Somebody Has to Watch
Sound familiar?
- Somebody comes back from a week away to two days of catching up.
- The checking gets skipped first when a backlog has to be cleared fast.
- A vacation gets shortened because of what waits at the other end.
- A sick day quietly turns into working from home to keep the pile down.
The idea in short
Invoices keep arriving, forms keep coming in, messages keep landing. Only the processing stops, so the work becomes a pile waiting for one particular person, because nobody else knows how or has the access.
What the return looks like
A backlog gets cleared faster than the same work would be done day to day, because a week of entries has to fit into whatever time exists alongside everything else that is now also urgent. The double-checking, the pausing over something that doesn't quite fit, is the discretionary part, and it disappears first under time pressure. So the errors this work exists to catch are least likely to be caught in exactly the weeks the most work is passing through it.
The effect on people
When a week away reliably produces two days of catching up, the calculation about taking the week changes, quietly and without anyone saying so out loud. Vacations get shortened, sick days get worked through from home. Small businesses lose good administrative people this way, slowly, for a reason nobody names on the way out.
What changes
Work that processes as it arrives does not accumulate against one person's absence. The pile does not form, so there is nothing to come back to, and a week away costs what a week away should cost.
Questions worth asking about your own operation
- What happens to this task while the person who does it is away?
- Has anyone shortened their own time off because of what would be waiting?
- Would the errors this task exists to catch be more likely to slip through during a busy week?
If this sounds familiar
Bring me the version you actually have. I'll learn how the process really works before I suggest anything. If it isn't worth changing, or isn't a fit for me, I'll say so. Talk through a problem