Invisible Workload: The Work Nobody Sees (Until It Stops)

When I worked in Employee Engagement at Amazon, one of the harder things to explain to leaders was why someone with a completely reasonable workload on paper could still be burning out. Their task list looked fine. Their hours looked fine. But talk to them for ten minutes and you’d find out they were also the person everyone went to when something went wrong, the one who remembered which process had changed last month, the one holding a dozen small threads that never showed up on any report. None of it was in their job description. All of it was real.

What it actually means

Invisible workload is the work that keeps a system running but was never assigned, measured, or counted — noticing, remembering, anticipating, chasing. It doesn’t show up as a task because nobody thought to write it down as one. It just becomes something a person does automatically, and the automatic part is exactly why it stays invisible.

Where it hides

I saw a version of this running events, before I ever set foot in an Amazon office. The caterer who wouldn’t confirm numbers without a chase two days before. The venue detail nobody wrote down because “everyone knows.” The run sheet that existed only in my head until the morning of, when I’d finally type it out because I couldn’t trust my own memory that day. Nothing about that work was on the contract. All of it decided whether the day went smoothly.

Why “just write it down” undersells it

The instinct once you notice invisible workload is to write it all down and consider the problem solved. That helps, but it’s not the whole fix, because a lot of invisible workload isn’t a task waiting to be listed — it’s ongoing noticing. A checklist can tell you to check the rota. It can’t replace the judgement that told you to check today because something felt off. Writing things down externalises the parts that are genuinely just information. It doesn’t remove the parts that are judgement, and most invisible workload is a mix of both.

What actually helps

Not a full overhaul. Name it first — genuinely list what you’re carrying that nobody assigned you, even if it takes a week of paying attention to catch it all. Then sort it. The parts that are pure information — a preference, a deadline pattern, a contact — can move out of your head entirely, into a note, a template, a system. The parts that are genuinely judgement can’t be delegated the same way, but they can at least be seen, by you and by anyone who might need to step in one day.

It’s worth distinguishing this from just having a lot on. A heavy workload is visible — you can point to the tasks. Invisible workload is defined by not being counted anywhere, which is exactly why it’s so easy for someone else — a manager, a client, even you — to look at your week and think you have more room than you do.

Your turn: what’s the invisible work in your business that’s never been written down anywhere — not because it’s small, but because you never thought to count it?

Similar Posts

  • The Handover Looked Fine on Paper

    Someone on my team was going on leave. We did what you’re supposed to do — sat down, went through the handover. Programs assigned. Files shared. A neat little document listing who was covering what. Everyone nodded. Everyone felt covered. Two weeks later I found out a customer had been waiting on an answer that…

  • Stop Booking Meetings Like an Operator.

    Your calendar is one of the most powerful leadership tools you own. Are you using it like one? Here’s a quick test. Open your calendar from last week. Look at it honestly. Is that a reflection of your priorities — or a patchwork of other people’s needs, last-minute requests, and things that felt urgent in…

  • One Process. This Week. That’s It.

    The first process I ever wrote down properly wasn’t for a client. It was for myself, in the first few months of running YVO, after I caught myself doing the same client onboarding steps slightly differently every single time and hoping I’d remember what worked. I sat down one afternoon and just wrote out what…

  • Make One Waiting Decision — Properly, This Week.

    The simplest antidote to Decision Latency: find the decision that’s been waiting longest, own it, and make it. By the end of this week, you should have made one decision that has been waiting longer than it should. Not the most complex decision in your business. Not the most strategic. The one that’s been waiting…

  • The Decision Your Team Is Waiting for Is Already Costing You.

    An unmade decision is not a neutral state — it’s an active operational cost that compounds with every hour it remains unmade. There’s a decision in most businesses that’s been waiting longer than it should. Not because the information isn’t available, not because the stakes are particularly high, not because it’s genuinely complex — but…

  • Pick One Task. Write Three Lines. Hand It Over.

    There was one task at Amazon I never handed over, not once, in years of managing a team. Told myself it was too important, too sensitive, too easy to get wrong. Looking back, that wasn’t true. I just hadn’t taken the twenty minutes to write down what I actually wanted, and it felt safer to…

Leave a Reply

Your email address will not be published. Required fields are marked *