My systems worked. I was still the problem.

Hey,

This newsletter was supposed to land on the 25th March. It's the 27th today.

Issues are normally written, proofed, and scheduled a full week in advance. That's the rule I hold myself to. But this month, an unplanned surgery pulled me out of work completely with no notice and no handover. Something scheduled for late April got moved to emergency status two weeks ago.

I'm fine. Recovery has gone well. But I wanted to write this one honestly rather than pretend the delay didn't happen.

What held. What didn't.

Here's the interesting part: the business kept running.

My automation team had everything they needed in ClickUp. Tasks were assigned, priorities were visible, nothing sat in my head waiting to be passed on. The work that could continue without me did exactly that, without anyone needing to chase anyone or ask where things lived.

That part worked exactly as it should.

What did get disrupted was the work I do by deliberate choice, not by necessity. Four potential clients had Discovery calls in the diary that had to be rescheduled. Three new clients were ready to begin onboarding in past two weeks and those had to be pushed too.

I handle Discovery calls personally. Not because no one else could technically sit on one, but because I've made a deliberate decision that the first conversation sets the tone, shapes the workflow, and matters too much to delegate at this stage. Same with onboarding. Those are intentional choices, and when I was offline, they stopped.

That's not a systems failure. That's a deliberate bottleneck, and this situation made me look at it clearly.

The difference between a deliberate bottleneck and an accidental one

Most business owners I work with have bottlenecks they never chose. They're the only one who knows where the client files actually live. The only one who remembers that a particular client needs a call before any invoice goes out. The only one who holds the unwritten rules for how things get done.

Those are accidental bottlenecks. And they only reveal themselves as a problem when something forces you offline.

My situation was different. I couldn't onboard clients because I chose to own that process. I understood the risk that came with that choice.

But if your business would struggle because your team doesn't know where things are, doesn't have documented steps to follow, or is waiting on you to make decisions that could reasonably sit elsewhere, that's a different problem. And it's one you can fix before anything goes wrong.

Three questions worth sitting with

Not as theory. Actually think about your business right now.

1. If you were unreachable for two weeks starting tomorrow, what would stop moving?

2. Is it stopped because you made a deliberate choice to own it, or because no one else has been set up to handle it?

3. What is one process that currently lives entirely in your head?

That third one is usually where the real risk sits. The undocumented thing. The workflow that only keeps moving because you're there to nudge it along.

How to start getting it out of your head

The goal isn't to document everything at once. That's overwhelming and it never actually happens.

The goal is to pick one process and make it so your team could run it without asking you a single question.

Here's a practical approach using ClickUp or Monday.com:

1. Create a task template for that process. Every repeating step becomes a subtask with a named owner and a due date rule.

2. Record a short Loom walkthrough, 5 to 10 minutes is enough. Attach it to the template. That's your training material, done.

3. Run it once with your team watching. Then run it again with them leading and you watching.

4. After that, it belongs to them.

One process, documented, handed over. You've just removed one accidental bottleneck from your business.

Do that for three or four processes over the next couple of months and the shape of your business starts to shift. Your team stops waiting on you. Important things keep moving even when you can't be there.

This month on YouTube

Two new videos went up this month. Both are worth your time if you're thinking about tightening up how your team captures and acts on information:

🤖 ClickUp AI Notetaker VS Fathom (2026): Side-by-Side Output Comparison + Pricing If you've been wondering which meeting note tool is actually worth using, this is the honest comparison. Real outputs, real pricing, no fluff.

⚡ 7 Proven ClickUp Automations To Save Time and Boost Productivity in 2026 Seven automations that remove the manual work from your week. Practical, ready to use, and directly relevant if you want your team operating without constant reminders and check-ins.

Your challenge before the April newsletter

Pick one process that currently lives in your head.

Not the most complex one. Not the most important one. The one that would cause the most friction if you weren't around for two weeks.

Document it. Build a simple template. Hand it off.

Then reply and tell me what it was. I'm genuinely curious what that process looks like for people on this list, and I read every reply.

Hina Sohrab

IT Visionists - Helping businesses run without depending on one person to hold it all together.

P.S. The clients whose onboarding got pushed have been incredibly gracious about it. Sometimes people surprise you. I'm looking forward to getting started with them properly next week.