I Spent 20 Years Making Other People's Systems Run. Then I Built My Own.

Let me paint you a picture.

It's 7am. I'm already on my second coffee, already three emails deep, already solving a problem that has absolutely nothing to do with my bank account. I am sharp. I am focused. I am on it. Every moving part is accounted for. Every deadline is tracked. Every potential fire has been identified, contained, and extinguished before anyone upstairs even knew there was smoke.

The machine is running smoothly.

The machine that belongs to somebody else.

I spent 20 years in manufacturing — 14 of them in aerospace — keeping complex, expensive, very-important-to-people-with-government-contracts programs from falling apart. Order management. Supply chain. Operations. The kind of work where one dropped ball doesn't just cause a problem, it causes a very expensive, very embarrassing, somebody-is-getting-on-a-plane problem. And I was good at it. Not "pretty good for someone at my level" good. I mean genuinely, structurally, intuitively gifted at making complicated things work.

I could look at a broken process and immediately see where it was breaking. I could build a workflow that ran without me standing over it like a helicopter parent. I could manage 50 moving parts, hit the deadline, keep the client happy, and still have bandwidth left over to help someone else fix their moving parts because apparently I also enjoyed that for some reason.

And what did I get for it?

A salary. Benefits. A direct deposit that hit on the 15th and the last day of the month like clockwork. A nice enough title on a business card that I definitely overpaid to have printed. A performance review that said I was "exceeding expectations" — as if that was supposed to be a surprise to anyone paying attention. And a LinkedIn endorsement from somebody named Brad who I honestly cannot picture clearly anymore but who I am choosing to believe meant well.

Thanks, Brad. Truly. It changed my life.

(It did not change my life.)

Here's the thing nobody tells you when you're good at your job — and I mean really good, not just showing-up-and-not-causing-problems good — being indispensable to someone else's operation is not the same as building something of your own. In fact, sometimes being too damn good at someone else's thing is exactly what keeps you from building yours. Because you're too busy. Because they need you. Because you've been there long enough that leaving feels complicated and you've got kids and a mortgage and the 401k is finally looking decent and now is really not a great time to do anything risky.

I know every single one of those excuses because I lived inside them, comfortably, for years.

And they're not even wrong exactly. They're just incomplete. They leave out the part where you look up one day — not dramatically, not in a movie-montage way, just quietly, over your second coffee on an unremarkable Tuesday — and think: I have been applying my absolute best thinking to someone else's problem for two decades. What the hell would happen if I pointed this at myself?

That was my moment. No breakdown. No burnout spiral. No viral resignation letter. Just a thought. A quiet, inconvenient, won't-shut-up thought that kept showing up no matter how many times I buried it under professionalism and practicality and the general busyness of having a whole life to manage.

The thought was: you know how to build things that run. So why isn't anything running for you?

And I didn't have a good answer. Which was annoying. Because I usually have answers.

Here's the inventory of what I actually knew how to do after 20 years: build systems from scratch. Identify inefficiencies and kill them. Create processes that didn't require me to babysit them 24/7. Track, measure, adjust, optimize. Take something chaotic and make it predictable. Make complicated things look easy — not because they were easy, but because I was thorough and I gave a damn and I did the work.

These are not small skills. These are the skills companies pay serious, serious money for. These are the skills that keep multi-million dollar programs on schedule. And I had been renting them out — cheerfully, professionally, at a negotiated annual rate — without ever once thinking to use them to build something that actually belonged to me.

When that fully landed, I went through a few phases. First I sat with it. Then I got kind of pissed about it. Then I got motivated. Then I started building.

Not overnight. Not dramatically. I am a mom from Inglewood with real responsibilities and real bills and real children who need real things on a real schedule, and I am not about to stand here and sell you some fantasy where I just said screw it and burned it all down and it worked out fine. That's not a plan. That's a cry for help with good lighting.

What I did was start in the margins. Before the house woke up. After it went to sleep. In the pockets of time that most people fill with mindless scrolling — and listen, I am not judging the scrolling, I have done the scrolling, the scrolling is a warm and comfortable place — but I started filling those pockets with building instead.

OneBadBreeze Media is what happens when you take 20 years of operations expertise and finally, finally, point it at yourself. It's not a pivot. It's not a brand deal or a rebrand or a midlife anything. It's me, using the same skills I always had, for the right person for once.

If you've been doing exceptional work for someone else and you're starting to feel that pull — that low-grade, persistent, won't-leave-you-alone awareness that you could be building something of your own — this is your sign. Not to blow everything up. Not to quit tomorrow. Just to start asking the question.

Whose building is your ladder leaning against?

Because you can spend a whole career being excellent at climbing someone else's. Or you can start building your own.

I did the first one for 20 years. I've been doing the second one for two.

There is absolutely no comparison.

Say hi to Brad for me.

— Des