The Fastest Way To Get Off The Hamster Wheel of Admin Without Quitting Your Own Org

You didn't start this to spend your days buried in admin.

You started because you had a vision - a show you wanted to produce, a program you wanted to build, a studio you wanted to open, a story you wanted to tell. You started because you believed in the work, and you wanted the freedom to do it your way.

And now?

Now you're answering emails at 10 PM.

You're writing grants instead of creating.

You're onboarding a new team member, troubleshooting a page on the website, chasing down invoices, and trying to remember where you put that one document everyone keeps asking about.

Your to-do list is longer than it was six months ago. The creative work - the reason you built this thing in the first place - keeps getting pushed to "later."

And the rest of your life? That's getting squeezed too.

You're missing dinners with friends, skipping the gym, spending less time with your family, canceling plans because you're too tired or there's too much to do.

The flexibility you wanted when you started this? It's nowhere to be found.

And if you're being honest, you've thought about how you can sustain this moving forward.

Not because you stopped caring about the work. But because this version of the work - the one where you're drowning in logistics and never quite catching up - doesn't feel sustainable. 

Here's what I want you to know: You don't have to quit. You just have to stop doing it the way you've been doing it.

The Pattern That's Keeping You Stuck

Let me tell you about a client I worked with. She's the Executive Director of a small nonprofit and is passionate about the mission and deeply committed to the work. When I came on board, she was a few months out - and very much in the lead up logistically - for the company’s big annual event.

She was wearing multiple hats. Program development, donor communications, event logistics, team management - all of it running through her. She'd delegate tasks, but then she'd end up redoing them herself. She'd ask an admin to draft a newsletter, then go through it line by line, rewrite most of it, and give so many notes that the whole process took twice as long as if she'd just written it herself from the start.

During event prep, she was constantly going. And the way she approached it - the pace, the last-minute changes, the lack of clarity on who owned what - caused stress for the people she interacted with without meaning to. It impacted how they experienced her, and how they experienced the org.

Here's what she was missing: It wasn't a personal failure. It was a structural gap.

She didn't need more discipline. She didn't need better time management. She needed systems - so the backend could actually support what she’s building without her constant involvement, and she could get back to the work she was best at.

Why Passion Turns Into Resentment

If you're reading this and thinking "That sounds like me" - you're not alone.

This is the pattern I see over and over with creatives who've stepped into leadership at a organization or started their own business:

• You got into this for the art, the mission, the creative practice, yet you end up spending most of your time managing logistics.
• You're good at the work itself. But running the business side of the work? That part was never taught. You're figuring it out as you go.
• Every time you try to delegate, it takes longer to explain than to just do it yourself. So you keep doing it yourself.
  You know you need systems, but you don't have time to build them - because you're too busy putting out fires.
  Revenue is inconsistent. Costs keep rising. The to-do list never shrinks. And the mental load of holding it all together is heavy.

The work you love starts to feel like the thing stealing your life.

And here's the part no one tells you: This isn't what "growth" is supposed to look like.

Growth isn't supposed to mean doing 10x the work for the same (or less) reward. It's not supposed to mean sacrificing your creative time, your health, your relationships, or your sanity just to keep the lights on.

But when you don't have the infrastructure to support the work - when everything runs through you, when nothing or not much is documented, when the systems are duct tape and hope - that's exactly what growth feels like. 

More chaos. More pressure. More of you doing everything.

And at some point, you hit a wall.

The Shift That Changes Everything

Here's the truth: You can't hustle your way out of a structural problem.

More hours won't fix it. More willpower won't fix it. Cutting costs, saying yes to every opportunity, or waiting for things to "slow down" won't fix it either.

What fixes it is this: Building the infrastructure that lets the backend run without you being the center of every decision, every task, and every fire.

That doesn't mean overhauling everything overnight. It doesn't mean hiring a full team or investing in expensive software or becoming a "businessperson" instead of a creative.

It means getting clear on what actually needs to happen - and building the smallest, simplest systems that let it happen consistently, without requiring your constant attention.

It means documenting the things you do over and over, so someone else can do them (or so you can do them faster next time without reinventing the wheel).

It means protecting your creative time like it's sacred - because it is. That's the work only you can do. Everything else? That's the work you can build systems around.

What It Looks Like When You Make the Shift

Back to the client I mentioned earlier.

Here's what changed for her:
We didn't add more to her plate. We took a hard look at what was already on it - and started building the infrastructure that let her stop being the bottleneck.

We started streamlining her event management process - documented the timeline, clarified who owned what, built in checkpoints so decisions didn't have to run through her at the last minute. We looked at how she was delegating (or not delegating) and adjusted the handoffs so she wasn't rewriting newsletters or second-guessing her team's work.

The result? The event ran smoother the following year. The team felt less stressed. Revenue went up. And she finally had breathing room to focus on the programmatic work she was actually best at - not just keeping the event machine running.

It wasn't a massive overhaul. It was small, intentional shifts that added up.

She didn't have to choose between doing great work and running a sustainable org. She just had to stop running it the way she'd been running it - on memory, last-minute decisions, and redoing everyone else's work.

Where to Start

If you're reading this and thinking "Okay, I get it - but where do I actually start?" - here's what I'd recommend:
 

1. Name the thing that's eating the most time
Not the thing that's most important. The thing that's draining you. The task you keep doing over and over, the decision you keep having to make, the fire you keep putting out.

Start there. That's your first candidate for a system.
 

2. Document it once
Write down the steps. Record a Loom. Build a checklist. Make it repeatable so you (or someone else) can follow it next time without having to think it through from scratch.

You don't need a 20-page Standard Operating Procedure (SOP). You need something that works.
 

3. Protect one block of time for the work you actually want to do
Not "when I have time." Not "once things slow down."

Pick a time. Put it on the calendar. Treat it like a client meeting. Don't let admin bleed into it.

Start with two hours a week if that's all you've got. But protect it.
 

4. Ask yourself: What would I do if I couldn't be the one to handle this?

That question forces clarity. If you couldn't answer that email, fix that issue, or make that decision - what would need to be in place for someone else to do it?

That's your roadmap.

You Don't Have to Quit

If you've been thinking about how to move forward - I get it.

But here's what I want you to know: The exhaustion you're feeling isn't proof that you're not cut out for this. It's proof that the way you've been doing it isn't sustainable.

And that's fixable.

You don't need to be more disciplined. You don't need to work harder. You don't need to wait until you're bigger, or have more money, or magically become "better at operations."

You just need to stop treating infrastructure like an afterthought - and start building the systems that let you get back to the work you're actually here to do.

The work that made you start this in the first place.