1
3 Comments

The three-business rule that keeps me from losing my mind

I run a software company, a care home, and a cafe at the same time. For the first year of doing all three, I thought the fix was better time management. It wasn't. The fix was a rule.

The rule is simple: nothing from one business gets discussed in a meeting meant for another, even when the same three people are sitting in the room for both. It sounds almost too basic to matter, but before I enforced it, conversations would drift, decisions would get made half informed, and everyone walked out slightly confused about which hat they were wearing.

Since I started treating that boundary as non-negotiable, meetings got shorter and decisions got sharper. If you are running more than one thing, I would be curious whether you have a similar hard rule, or whether you have found the opposite works better for you, blending context on purpose instead of separating it.

on July 9, 2026
  1. 1

    Great perspective. Founder stress often comes less from the amount of work and more from carrying too many unresolved decisions at the same time. Clear rules and constraints are powerful because they reduce decision fatigue and protect focus.

    The best systems I’ve seen usually come down to a few principles: prioritize what truly moves the business forward, automate or eliminate repetitive work, and create boundaries around time and energy.

    Building a company is a long game, and sustainable execution beats short bursts of chaos. Great reminder that simplicity is often the biggest productivity advantage.

    1. 1

      Agreed, decision fatigue is the real cost. What changed things for me was writing down a short list of rules in advance, like which decisions I make and which ones my team owns without asking, so the same question does not eat up energy every single week.

      1. 1

        Exactly. Writing down decision rules is a great way to reduce cognitive load and keep the team moving without unnecessary bottlenecks.

        I think clear ownership and boundaries create the same kind of leverage as good architecture in software — fewer dependencies, fewer repeated discussions, and more confident execution.

        Thanks for sharing this perspective. It’s a great reminder that simple operating rules can have a huge impact when managing multiple priorities.

        Feel free to connect with me on Teams: https://teams.live.com/l/invite/FBAk3iOSJkDyS11JQ?v=g1