Let's talk about hippos.
Hippos are strong. Capable. They move with real force, and when one is angry and charging at you, you have basically three options: try to stop it, try to get out of the way, or accept your fate. None of those options are particularly good.
But here's the thing... that hippo bearing down on you isn't malfunctioning. It isn't out of control. It isn't broken.
It's doing exactly what it was designed to do.
Your business works the same way.
This is the thing I come back to over and over again in the work I do with business owners, because it reframes almost everything.
When your business feels chaotic, when it keeps producing outcomes you don't want, when you feel like you're pushing against it constantly and getting nowhere, the instinct is to think something is wrong. That you're doing it wrong. That the business is broken somehow.
But what if it isn't broken? What if it's working perfectly?
Businesses do what they're designed to do.
If your business is producing chaos, it was designed for chaos (even if nobody made that choice consciously). If it's keeping you maxed out and reactive, that's what it was built for. If it's growing in ways that feel unsustainable, that's the direction it was pointed. The outcomes you're getting aren't accidents. They're outputs. And outputs come from design.
Which leads to the uncomfortable question: who designed your business?
For most of us, the honest answer is: nobody, really. Not intentionally.
Most businesses don't get designed. They accumulate. You take on a client, and that shapes what services you offer. You price based on what feels competitive, which shapes your capacity. You hire when it gets overwhelming, which shapes your team structure. You add a service because someone asked for it, then another, then another. Each individual decision makes sense in the moment. But nobody ever sat down and said, "here's what I want this business to produce, here's the life I want it to support, here's what it needs to look like to make both of those things true."
Instead, the business gets built in motion. Reactively. On autopilot.
And autopilot has a direction. It doesn't go nowhere, it follows the path of least resistance, means almost always following the defaults. The industry norms. The cultural assumptions. The unexamined belief that success means growth, and growth means more → more clients, more revenue, more team, more complexity, more everything.
So even "no design" is a design. It's just not yours. It's borrowed from somewhere else, assembled from whatever was available, pointed toward outcomes you never actually chose.
That's the default business. And it produces default results.
Here's the part that tends to hit hardest: the default business isn't broken. It doesn't need to be fixed. It's doing exactly what it was built to do: generating growth, maximizing output, running at capacity. If those were the outcomes you wanted, great. You're all set.
But if you're reading this, I'm guessing they're not. Or at least, not entirely. Because growth without sustainability isn't actually success. Maximizing output isn't the same as doing your best work. Running at capacity all the time means there's no margin for anything. For thinking, for rest, for the unexpected thing that always eventually happens.
Default business = default outcomes. And the default outcomes feel like exactly what most of the owners I work with describe when they tell me something isn't working: exhausted, overwhelmed, reactive, waiting for a slower season that never comes.
That's not a malfunction. That's the system functioning exactly as designed.
Which means the solution isn't to work harder inside the same structure. It isn't better habits or more discipline or the right productivity system. None of that changes what the business is designed to produce.
If you want different outcomes, you have to intentionally design for them.
This is an engineering problem. It's not a mindset problem, not a motivation problem... an engineering problem. And engineering problems have engineering solutions.
But before you can design for something different, you have to know what you're actually designing for. And that starts with a question most business owners have never explicitly answered: what does success actually mean to you?
Not the default version, so not revenue targets and headcount and year-over-year growth. Your version. What does your ideal work week look like? What's the role you actually want to play in the business five years from now? What needs to be true about how this runs for it to feel sustainable, and not just financially, but energetically, emotionally, practically?
This matters because everything you build flows downstream from how you define success. Your metrics, your priorities, your daily decisions - all of it is pointing somewhere. If you've never examined that definition, you're probably designing toward someone else's version of success without realizing it. The tech bro's version. The industry's version. The version you absorbed without ever choosing it.
Your definition of success is the design spec. The business is what you build to support it. And when you get clear on what you're actually designing for, the whole thing looks different. The services you offer, how you price them, how you structure client relationships, how you manage your time and your team: all of those stop being defaults you inherited and start being choices you made on purpose.
That's intentional design. And it's the only way to get a business that produces something other than the default.
The Calmer Framework™ is the model I use for this - four levers that map out where your business currently sits and where the highest-leverage shifts are. But before the framework, before the levers, before any of the specific decisions: this is the foundational idea everything else rests on.
Your business isn't broken. It's doing exactly what it was designed to do.
If you want it to do something different, you have to design for something different. On purpose, from the beginning, around the life you actually want to live.
That's not a small shift. But it's a solvable one.
