I Stopped Optimizing My Life and Started Designing It Instead

# I Stopped Optimizing My Life and Started Designing It Instead

There was a Tuesday — I can’t tell you which one because they all looked the same — where everything was working. Calendar full, inbox under control, deals moving, automations humming. I looked at it and felt something I couldn’t name for a while.

Not tired. Not overwhelmed. Not grateful.

Wrong.

Not dramatically wrong. Just quietly, specifically, unmistakably aimed at something I’d never actually decided to aim at.

That’s the part nobody writes about. Not the burnout. The opposite of burnout. The machine running beautifully toward a destination you never chose.

**Efficient misalignment** doesn’t sound like a crisis. That’s what makes it the most expensive thing most high-functioning people carry around without ever naming it.

You’ve got the tools. The calendar. The habits. The inbox system that would make a productivity influencer weep with joy. You return texts fast, you close things, you don’t drop balls. By any external measure, you’re winning.

And the whole apparatus is pointed somewhere you accidentally inherited, or copied from someone who looked successful, or stumbled into during a season of your life that ended fifteen years ago.

Here’s the thing about efficiency: it compounds whatever you already chose. Including the choices you never made on purpose.

That’s not a mindset problem. That’s a design problem.

Most content about this goes straight for the burned-out person — the one running on fumes, barely holding it together. I get it. That person needs help.

But that’s not who I’m talking to.

I’m talking to the person who is *not* burned out. The person who is genuinely excellent, genuinely high-functioning, and quietly running their best effort through a machine that was never aimed at anything they actually decided to want.

Nobody writes about that person. That person looks fine.

Ask yourself this: if nothing changes for five years, what does a normal Tuesday look like?

Don’t skip past that question. Sit in it for a second.

If the answer makes you exhale — good. If it makes you flinch — you already know what I’m talking about.

The moment it got concrete for me wasn’t a breakdown. There was no rock bottom. It was more like looking at a week that checked every box and realizing the things I’d told myself mattered — fishing, actually being present for Hollie, the slow-burn creative work I do with AI that I actually find interesting — were getting the leftovers. Every time.

Not because I was lazy. Because the machine was optimized. And the machine had its own logic, and the machine’s logic wasn’t mine.

I was excellent at making a life work that I hadn’t designed.

That’s a grief feeling, not an inspiration feeling. And it doesn’t go away by finding a better productivity app.

You know these people. You might be one of them.

The contractor who answers client texts at 11 p.m. not because he chose that, but because that’s just the shape the business grew into, and the system he built to manage it made it easier to keep saying yes at midnight than to redesign the intake process.

The consultant whose calendar is impeccably blocked, whose work is genuinely great, and whose family gets whatever’s left after the good hours are claimed. She didn’t decide that. She just kept optimizing.

The solopreneur who automated everything — follow-ups, scheduling, invoicing — except the one thing automation can’t solve: the fact that the whole business is organized around a yes he never examined.

None of these people are failing. That’s the point. They look like they’re winning. From the outside they probably are.

But reducing friction on a bad default just makes the bad default easier to repeat at scale. That’s true in software and it’s true in your calendar and it’s true in your life.

I’m not telling you to do less or want less. I’m not writing a “slow down and notice the trees” post. If you know me at all, you know that’s not my game.

The reframe I’m offering is architectural, not spiritual.

Decide what gets protected first. Then build the machine around that.

Not “find your why.” Actual structural decisions. What goes on the calendar before the urgent stuff claims it? What gets a hard fence, not a hopeful intention? What does a Tuesday look like if you’re the one who decided it?

When I started doing the AI and automation work for FlowStateOps, the most useful thing it taught me — more than any specific tool — is that the best systems aren’t the most productive ones. They’re the ones that keep human priorities from getting swallowed by the operating system.

That’s not a productivity principle. That’s a design principle.

The machine should serve the life. Not the other way around. When you optimize first and design never, you end up with a very fast vehicle and no idea where you’re going.

Some of what I redesigned was uncomfortable. Some of it cost me. Not everything in the old machine was bad — some of it I wanted to keep, and I had to figure out which parts were mine and which parts I’d just inherited. That work is ongoing. Probably always will be.

But at least the machine is aimed at something now.

So here’s the question I’ll leave with you — and I mean it, don’t just read past it:

**What are you optimizing that you never actually decided to want?**

*If this landed somewhere real, most of what I write here is about this — real estate, AI, fishing, and what it actually takes to build a life in North Idaho that you’d choose twice. If you want more of that thinking, stick around.*

Leave a Reply

Your email address will not be published. Required fields are marked *