Responsibility Should Expand Deliberately, Not by Accident

Earlier in my career, I wanted responsibility as quickly as possible. Like a lot of ambitious people, I assumed more responsibility automatically meant more opportunity. I don't think I learned otherwise from one company, or one bad week. I learned it by watching the same pattern from three different vantage points, years apart.

The first vantage point was inside other people's businesses. Moving through roles at SuperAwesome, Sojern, and later Nordic Markets, I watched people, sometimes myself, get promoted for being excellent at their current job, not because they'd actually been prepared for the next one. The role expanded faster than their capability or their support did. Some people worked it out. Often, they were left carrying the pressure of a bigger job while quietly figuring out what it actually required.

The second vantage point was running my own businesses. At Alexander Twelve, and later at Carpet & Flooring, there was nobody above me to take work back. Every new client, every new service, every operational decision landed with me by default, not by anyone's decision, including mine. The business grew because I kept saying yes. But that also meant responsibility expanded faster than the systems supporting it. In a lot of small businesses, the bottleneck isn't the market. It's the founder, carrying more than the business has actually built the capacity to support.

Building Halo has been the first time I've deliberately tried to reverse that pattern rather than repeat it.

Responsibility should be earned by growing capability first, not simply accepted because an opportunity appears.

The Commercial Diagnostic exists before broader advisory work does. The Commercial Audit sits alongside it with a clearly defined purpose, not as an upsell bolted on afterward. The Bible, the Constitution, the Operating Manual, the Framework Library, all of it was built before Halo reached the scale where any of it would have been strictly necessary. That's not caution for its own sake. It's the same lesson applied in advance instead of after the fact: I don't want Halo's capability to depend on me personally remembering everything or carrying every decision forever. This is the same instinct behind Build the Protection Before You Need It, and the same underlying belief that systems amplify capability, they don't replace it.

That's true for people. It's true for teams. And it's true for businesses. Sustainable growth isn't about taking on more as quickly as possible. It's about making sure the foundations are strong enough to support what comes next, before circumstance decides that for you.

A few honest questions worth asking before the next expansion, whether it's a new hire, a new service line, or a new piece of scope landing on your own desk:

• Is this responsibility being taken on because the capability to support it already exists, or because nobody else is available to say no?
• If a person or a business already looks stretched, does adding scope actually solve that, or does it just move the pressure somewhere less visible?
• Would this expansion still make sense if it had to be chosen deliberately, in writing, rather than simply accepted because it arrived?
• In your own business, who is currently the bottleneck, not because they're doing badly, but because too much still depends on them personally?

More on how this fits the rest of Halo's thinking is set out on How Halo Thinks. If responsibility in your own business feels like it's expanding faster than the structure supporting it, a Commercial Diagnostic is a focused way to find out where that's actually happening.

What people ask about responsibility and growth.