The Invisible Work of Holding a Business Together

You have support.
There’s a VA. Maybe a bookkeeper. A designer you trust. Someone helping with marketing, delivery or client admin.
There are systems, too. A project management tool. A CRM. Automations. Shared folders. Possibly several shared folders called some variation of “FINAL”, but we won’t dwell on that.
And yet... You go away for a few days and still find yourself checking in.
Someone asks a question, and you’re the only person who knows the answer.
A client reaches a certain point, and you remember there’s something that needs to happen next.
A team member completes a task, but you still need to check it because there’s a particular standard you hold that you’ve never quite managed to articulate.
You wake up at 3am remembering something that needs following up.
You have support. But somehow, everything still seems to depend on you.
I see this a lot in growing businesses. And usually, the problem isn’t that the founder needs to get better at delegating.
It’s that a significant part of how the business works is still invisible because it lives inside her head.
Your workload is bigger than your to-do list
When we talk about workload, we tend to talk about tasks.
Write the proposal.
Send the invoice.
Onboard the client.
Update the website.
Follow up with the lead.
Prepare for the workshop.
Those are visible. They can be written down, assigned, completed and ticked off.
But they’re only part of what you’re carrying. There’s another layer underneath them.
It’s remembering that this particular client needs a different follow-up.
Knowing which supplier to use and why.
Spotting that two decisions being made in completely different parts of the business are actually connected.
Remembering what happened the last time you tried something.
Knowing when “good enough” genuinely is good enough, and when it isn’t.
Holding the context behind a decision someone else only sees the final version of.
Anticipating the problem that hasn’t happened yet.
This is the invisible work of running a business.
And when most of it lives in your head, your business doesn’t just rely on your work.
It relies on your attention.
This is why getting help doesn’t always feel like help
Hiring support is often positioned as the obvious answer to founder overwhelm. And sometimes it is.
But giving someone else a list of tasks doesn’t necessarily reduce the amount of thinking you’re doing.
You might no longer send the onboarding email yourself, but if you still have to remember when it needs to go, tell someone which version to send, check that it happened, answer the question that comes back and remember the next step afterwards...
You’ve delegated the task, but you haven’t delegated the mental load around it.
That matters because you can reach a point where you have several people supporting you and still feel like the person holding the entire business together with an elaborate combination of memory, intuition and “I’ll just quickly do it myself.”
From the outside, you have a team. From inside your own brain, you’re still air traffic control.
The founder can accidentally become part of the infrastructure
Most businesses don’t start with beautifully documented ways of working. Nor should they.
You figure things out as you go. You make a decision because a client needs something. You create a workaround. You learn what works. You remember not to do that thing again. You adjust your process slightly for the next person.
Over time, you build an extraordinary amount of operational knowledge. The problem is that nobody necessarily notices you’re building it.
Including you.
Eventually, there are dozens — sometimes hundreds — of tiny decisions, standards, exceptions and bits of context underpinning how the business operates.
And if they’ve never been made visible, you become the place where that information lives.
You are the process.
You are the quality control.
You are the reminder system.
You are the search function.
You are the person who knows that when X happens, we usually do Y — except for this kind of client, when we do Z.
Which works surprisingly well. Until it doesn’t.
The answer isn’t to document every thought you’ve ever had
At this point, it would be very easy to tell you that what you need is more systems.
Document everything!
Create SOPs!
Automate the lot!
I don’t think that’s particularly helpful.
For one thing, you probably don’t have three uninterrupted weeks available to extract the entire contents of your brain into a 97-page operations manual. And secondly, not everything needs a process.
Good operational strategy isn’t about systemising your business within an inch of its life.
It’s about noticing where your brain is repeatedly doing work that something else could hold for you.
That might be information.
It might be a decision.
It might be a reminder.
It might be a standard.
It might be a sequence of steps.
It might simply be context that another person needs before they can confidently act without coming back to you.
That’s where I’d start.
Not with:
“What systems should we build?”
But with:
“What does this business currently require me to remember?”
That question tends to reveal rather a lot.
Make the invisible visible first
One of the most useful things I do with clients is simply get the moving parts out where we can see them.
It doesn't make them magically disappear. It's because complexity feels very different when it’s visible.
When everything is in your head, each thought is competing with every other thought.
Remember to follow that up.
We should probably change that process.
Did anyone send that?
I need to brief her about that client.
We need to hire before this gets busier.
Where did I put that link?
Individually, they’re tiny. Collectively, they create a business that needs your brain permanently switched on.
Once we make those things visible, we can start asking better questions.
Does this need to live with you?
Does someone else need access to this information?
Is this a decision you make repeatedly?
Could there be a default?
Does this follow-up need to rely on someone remembering it?
Is there a clearer place for this to live?
What does another person need to know to handle this without asking you every time?
That’s where streamlining becomes useful.
Not chasing efficiency for efficiency’s sake, but because every repeated decision we can clarify, every piece of context we can locate and every follow-up that no longer depends on memory gives a little bit of cognitive capacity back.
Sometimes the smallest operational changes create the most relief
I’ve seen this play out in very practical ways.
In one client’s business, part of reducing cognitive load meant creating a central place for frequently needed links and information.
It meant improving the client portal so clients knew where to go.
It meant building a more considered concierge onboarding experience.
And it meant introducing workflows and systems so the next step didn’t depend on someone — usually the founder — remembering that it needed to happen.
None of those things sounds particularly revolutionary on their own. That’s actually the point.
Operational clarity is often less about one enormous transformation and more about removing dozens of tiny dependencies.
A link that can be found without asking.
A client who knows what happens next.
A team member who has enough context to make a decision.
A follow-up that happens because the workflow prompts it, rather than because the founder remembered it while brushing her teeth.
Small changes. Significant relief.
Delegation gets easier when the thinking around the work is clearer
I saw another version of this with a founder who came to me needing clarity around her operations, delegation and future capacity.
The temptation could have been to jump straight to:
Who should we hire?
What should they do?
How many hours do we need?
But hiring into operational fog rarely fixes the fog. First, we needed to understand what was actually happening in the business.
Where was her attention going?
What was only happening because she was holding it?
Which responsibilities could move?
What needed to be clearer before someone else could take ownership?
Where was her expertise untransferable?
Once those pieces were visible, the decisions around delegation and capacity became much easier to make.
Sometimes you don’t need more support yet. You need enough clarity to make the support you bring in actually useful.
Your business needs somewhere else to put what you know
There’s a bigger shift underneath all of this.
As a business grows, the founder’s role has to change from remembering how everything works to creating ways for the business to remember.
That doesn’t mean removing yourself from it. It doesn’t mean handing over every decision or turning something deeply personal into a rigid machine.
And it certainly doesn’t mean creating a process for the sake of being able to say you have a process. It means deciding deliberately where knowledge belongs.
Some things should live in a system.
Some should live in a documented process.
Some belong with another person who has the authority and context to own them.
Some need a recurring rhythm so they’re reviewed at the right time.
And some absolutely should stay with you because they rely on your judgement, relationships or expertise.
The goal isn’t to get everything out of your head. It’s to stop using your head as the default storage location for the entire business.
What would happen if you didn't remember?
If you’ve been wondering why everything still seems to depend on you despite having support, that’s the question I’d start with.
What would stop happening if I stopped remembering it?
Which clients wouldn’t get followed up?
Which decisions would stall?
Which standards would slip?
Which information would suddenly become difficult to find?
Which next steps would nobody realise were next?
You don’t need to solve all of those things at once. Just notice them.
Because the invisible work becomes much easier to change once you can see it. And that’s often the beginning of a different kind of business that still benefits enormously from your judgement, ideas and experience, but doesn’t require your constant attention just to keep itself moving.
Your business should need you for the things only you can bring to it, not because you’re the only person who remembers where everything is.
Ready to get some of it out of your head?
If your business has reached the point where there are too many moving parts, and you’re not quite sure what needs fixing first, The Full Picture gives us space to look at the whole picture together.
We can make the invisible workload visible, identify where the pressure is actually coming from and work out the next practical steps — whether that’s streamlining, delegation, clearer systems or simply deciding what doesn’t need your attention anymore.



