There's a difference between making something work and designing something that works.
For most of my career, I've been the person who makes it work. Timelines adjusted. Budgets balanced. Personalities managed. Details held. And I'm good at that. I built a reputation on that.
That ability built trust. And trust built my business. But success can still feel repetitive, even when you respect what you built.
Listen: Substack · Spotify · Apple Podcasts · YouTube
In this episode
The difference between operator energy and architect thinking
Why being capable can quietly lead to depletion
What burnout actually revealed about my business model
The structural lessons I learned building Camp Rover
Why consulting and advisory work make sense now
How architecture creates sustainability
The hidden work behind events that look effortless
The planners who are truly excellent are the ones who make it look effortless. That's the tell. If it looks seamless, someone is carrying an enormous amount behind the scenes.
Emotional labour. Logistical foresight. Risk mitigation. Micro-decisions constantly. You're holding the energy of a room while managing a hundred invisible threads. That is skill.
But at some point, I realized I was solving the same categories of problems over and over. Different clients. Different venues. Different budgets. But the same structural flaws. And I could fix them. But fixing them started to feel… small. Not unimportant. Just small relative to what my brain wanted to do.
Operator vs architect: what's the difference?
When I walk into a room, my brain doesn't just look for what needs to be managed. It looks for what should have been designed differently.
Why was this timeline unrealistic?
Why does this team structure create bottlenecks?
Why are approvals reactive instead of intentional?
Why are we constantly firefighting instead of designing flow?
That's architect thinking. But I was still operating as the fixer.
When I started my business, there weren't polished systems you could buy. So I built my own. Every intake form. Every budget sheet. Every workflow. Every internal structure. Not in a glamorous way. In a late-night, "there has to be a better way" way.
Looking back now, that wasn't just hustle. That was architecture. I've been architecting for years. I just didn't call it that.
What building Camp Rover taught me about structure
Then there was a season that accelerated everything. I was building Camp Rover, a new inclusive business and space for creative entrepreneurs, while still running my existing company.
That required brand architecture. Programming design. Community building. Revenue modelling. Partnership structure.
It was the first time I was building something without a proven blueprint. And when you build without a blueprint, you learn how you think. And how I think is structural.
What burnout revealed about my business model
I still delivered the event. I showed up. I led. I held the room. From the outside, it looked successful.
That's the thing about operator energy. It performs under pressure. It knows how to compartmentalize. It knows how to carry what isn't visible.
But afterward, I crashed. In a way that forced me to admit that I had built a structure that relied too heavily on my ability to hold everything. Emotionally. Logistically. Energetically.
That's when the structural questions became unavoidable. My business model. My role inside it. The sustainability of how I was operating. Because if I was going to rebuild anything, I wasn't going to rebuild the same structure.
Why consulting and advisory work make sense now
Not because I'm done with events. But because I want to be at the design table before the event exists.
I want to influence decision-making structures. Budget flow. Approval processes. Team dynamics. Upstream. Because when structure is clear, execution becomes lighter.
Architect doesn't mean distant. It means upstream. Clarity before chaos. Structure before stress. Design before scale.
This doesn't mean I disappear from execution overnight. It means I narrow where I sit. I train my team to lead fully. I strengthen standards internally, so excellence doesn't depend on my physical presence. That's leadership evolution. Not withdrawal.
Operator energy builds things. Architect energy builds systems that outlast you.
Key line
Burnout isn't always about doing too much. Sometimes it's about operating below your intellectual edge.
Reflection question
Are you still operating in a seat you've outgrown? Are you being celebrated for execution when you're craving architecture?
FAQ
What's the difference between an operator and an architect in business?
An operator makes something work. An architect designs something that works. Operator energy builds things. Architect energy builds systems that outlast you.
Can burnout come from something other than doing too much?
Yes. Sometimes it's about operating below your intellectual edge. Sometimes it's about being praised for resilience when what you really want is influence. Sometimes it's about solving the same structural problems again and again instead of redesigning them at the root.
Does moving into consulting mean leaving event execution?
No. It means narrowing where I sit, training my team to lead fully, and strengthening standards so excellence doesn't depend on my physical presence.
What does working upstream mean?
It means being at the design table before the event exists, influencing decision-making structures, budget flow, approval processes and team dynamics, so execution becomes lighter.
This post is based on Season 1, Episode 3 of Work, By Design, a podcast by Amanda Douglas & Co. about redesigning how you work.
Want help with your own version of this? Start a conversation
Read next: Value-Based Pricing: Price Your Expertise, Not Time
