The Job Nobody Wrote Down

Planning an ops hire means knowing what is real overflow and what is structural, so the exercise starts with a question put to everyone on the team: what do you do that nobody assigned you?

The answers come back scattered. One person says they rebuild the client handoff process every few months because the old one doesn't hold. Another catches proposals mid-flight because the template breaks down on real deals. A third runs a standing meeting that exists only to catch work that would otherwise fall through the cracks.

None of this work shows up on an org chart. None of it has a job description line. It was never named out loud, so it has never been delegated or planned around. It just happens, usually in the margins, usually by whoever noticed it first.

The work that holds things up

This is the invisible operations work. It's real. It's load-bearing. It's what keeps a firm running when systems haven't quite caught up with the size or complexity of what you're doing.

Common shapes this takes in a founder-led firm: catching gaps in a handoff sequence before a client sees it. Rebuilding a template, process, or checklist because the last version didn't survive contact with real work. Running a meeting nobody else could run, because it exists solely to surface what would otherwise stay hidden. Filling in for communication that should happen automatically but doesn't yet. Holding context nobody else has yet, because the firm grew too fast to document it.

What makes it stubborn: the work is genuinely necessary. The firm would lose something important if it stopped. But because it was never named, nobody can take it off your hands, and nobody can plan around it. You carry it until you can't anymore, and then something cracks.

Three questions to find it

If you're sitting on a hiring question and unsure whether the gap is real, start here. Ask yourself these three things:

Do I do work that nobody assigned me to do? Not work that's in my job description but not delegated yet. Work that doesn't have a description at all. Work that came into being because I noticed something broken and fixed it, and now I run it.

Would this work go undone if I stopped doing it? Not eventually handled by someone else. Just gone. Lost. The thing would fall apart or the client would catch the gap.

Have I ever described this work out loud to anyone else who works with me, in enough detail that they could take it over? The honest answer is usually no. It has not been named, it has not been written down, and it has not been handed off, because nobody has ever articulated what it is.

If you answered yes to all three, you've found invisible work. You're carrying something that should be visible before you hire.

What to do first

Once you see it, the move is simple: name it. Write it down. Give it a job title if it needs one. Describe what it actually does. Assign it or delegate it or plan for it as a real line item, not a thing that just happens.

That clarity changes everything. It changes whether you need to hire. It changes who you hire and what you ask them to do. It changes whether something that felt like overflow is actually a structural gap that needs fixing.

You can't delegate work you haven't named. And you can't plan around work you can't see. The invisible work stays invisible until you decide to look at it straight on.

Naming it is the part you can do this week. If what you find is bigger than one role and woven into how the firm runs, that is what a fit call is for.