What running a software company, a care home, and a cafe at the same time taught me about systems

I spent 30 years in org development before I ever wrote a line of code for my own product. These days I run three completely unrelated businesses at once: a small software company, a care home, and a cafe.

People assume the hard part is the hours. It's not. It's the switching. Walking out of a staffing problem at the care home and into a product roadmap call twenty minutes later does more damage to your focus than any single business ever could on its own.

Three things I've learned that apply no matter which business is on fire that day.

The first is that revenue is a lagging indicator. The number I actually check every morning is how many decisions are stuck waiting on me personally versus decisions the team already made without me. When that ratio creeps up, I've become a bottleneck somewhere, and I go find it before it costs me anything.

The second is that documentation is never a later problem. In three decades of watching organizations grow past what a founder can hold in their head, the ones that scaled cleanly were the ones where someone wrote down how decisions get made before they desperately needed to.

The third is that failure is quiet before it's expensive. It's rarely the obvious stuff like cash flow. It's a shift schedule that stopped matching reality, or a support queue nobody officially owns anymore. Those things rot for weeks before they show up as a real problem.

If you're running more than one thing at once, I'd genuinely like to know: what's the part of your business that goes quiet right before it breaks, and what's the one rule you refuse to bend to keep everything from colliding?