Owners ask me some version of the same question almost every week: if I want my business to need me less, should I be in fewer meetings? The instinct makes sense. Meetings feel like the opposite of freedom. But after building and stepping back from several companies, my honest answer surprises most of them. I am in fewer meetings than I used to be, with one exception. There is a single 30-minute meeting I have never missed, and it is the reason I can be unreachable for two weeks without anything breaking. Everything I cover in Built to Run about ownership versus operating eventually comes back to this one habit.

Why I Almost Cut This Meeting

A few years ago, in the middle of trying to strip my calendar down to the essentials, I looked at my weekly leadership review and nearly killed it. It felt like exactly the kind of standing meeting that accumulates out of habit rather than necessity. My team was capable. Reports were flowing through our project management tools. Surely I did not need to sit in a room and go over the same numbers every week.

I was wrong, and it took about six weeks without it to find out why. Small misses stopped getting caught early. A marketing channel that should have been paused after two bad weeks limped along for a month because no one had a forum where flagging it was expected, not optional. A hiring decision that needed my input got made without me, not because anyone was hiding it, but because there was no longer a moment built into the week where that kind of thing surfaced automatically. The business did not fall apart. It just quietly got worse in a dozen small ways that added up. I brought the meeting back within two months, and I have not touched it since.

What the Meeting Actually Covers

The version that works is narrower than most owners expect. It is not a status meeting where each department talks through what they did that week. That format is where most leadership meetings go to die, because it rewards activity over outcomes and it takes forever. My version is a scorecard review. Every function in the business has three to five numbers that tell you, at a glance, whether that part of the business is healthy: revenue against forecast, cash position, pipeline coverage, production capacity, customer churn, whatever is relevant to that team. Those numbers get updated before the meeting, not during it. The meeting itself is thirty minutes spent looking at the numbers together and asking exactly one question about anything that is off: what is the plan to fix it, and when will it be fixed.

That is the whole meeting. No slides. No narrative updates on projects that are on track. If a number is green, we do not discuss it, because discussing things that are working is how meetings balloon from thirty minutes to ninety. We only spend time where the business is telling us something needs attention.

The Rule That Makes It Work

The rule that makes this format function, and the one most owners skip, is that we do not solve problems in the room. When a number is red, the person who owns it states the cause and states a plan, and we move on. If the same number is still red the following week, that is when it escalates and gets real time on my calendar, one on one, outside this meeting. This keeps the weekly review fast and keeps it from turning into a working session that drags every leader's calendar down with it. It also creates a very healthy pressure: nobody wants to explain the same red number two weeks running, so problems tend to get solved before they become recurring agenda items.

What Changed When I Started Running It This Way

Once this rhythm was in place, something shifted in how I related to the day-to-day of the business. I stopped needing to check in informally, because I already knew, every single week, exactly where things stood across every function that mattered. I stopped being surprised by problems, because problems showed up as a yellow or red number weeks before they became a crisis. And critically, my team stopped needing me to be present for the actual work to happen, because the accountability structure was the meeting itself, not my ongoing attention. That is the entire premise behind Built to Run: a business that depends on the owner's constant presence is not actually a business, it is a job with better branding. A business with a real accountability rhythm can run without the owner in the room, because the rhythm is doing the work the owner used to do informally and inconsistently.

How to Build Your Own Version

If you want to try this, start smaller than you think you need to. Pick the three numbers per function that would tell you the business is in trouble if they moved in the wrong direction. Get those numbers reported before the meeting, not during it, so the meeting is a review rather than a data-gathering exercise. Cap the meeting at thirty minutes and enforce the no problem-solving rule from day one, even when it feels rude to cut someone off. And give yourself two full months before judging whether it works, because the first few weeks will feel unnecessary right up until the week it catches something that would have cost you real money or real time to discover late.

The rest of the operating system, including how to build scorecards for functions that resist easy measurement and how to structure escalation so it does not become a blame exercise, is in Built to Run. More on building businesses that run without you at drconnorrobertson.com.

---