The Constraint Audit: What Your Biggest Problem Is Actually Building

The newsletter version of this was one question: *what is your constraint conspiring to build in you?*

This is the longer answer.

For a long stretch of school, I had no car. One job, a class forty miles away, and a schedule that looked like a logic puzzle. Bus to light rail to commuter train to work. For sixteen years, much of that time was spent doing technical support calls to keep income coming in. Variable call lengths meant I never knew exactly when I'd be free. Miss the train that got you there on time and it was "guess we aren't going to class today."

Most people would call that a problem. I called it Tuesday.

Here's what I didn't realize at the time: I was learning to route.

Not just physically — mentally. I was building a kind of systems thinking that most people only develop when they're managing teams or running operations. I was doing it because I had to. The constraint didn't leave me a choice.

That skill — routing, sequencing, finding the most efficient path through a complex set of variables — is the exact skill I use now to build AI automation workflows.

The constraint didn't hold me back. It trained me. It was conspiring for me the entire time.

But I didn't know that then.

What I knew was that I felt like butter scraped over too much bread — stretched across every obligation, every shift, every connection, until there was nothing left that felt like me. All I wanted was time with my family. That's it. That was the whole dream. And every single day, the world looked me in the eye and said: *not today.*

I hated every day of it. I want to be honest about that. It wasn't a grind I was proud of. It wasn't hustle culture content. It was a man who wanted to be somewhere else, forced to be somewhere else, watching time pass that he wasn't getting back.

But I also knew something: tech support wasn't going to give me the life I wanted. The income had a ceiling. The future had a ceiling. The degree wasn't optional — it was the only door I could see. So I kept going. Not because it felt good. Not because I had momentum. Because stopping meant the ceiling won.

Years later, I heard Alex Hormozi say something that stopped me cold. He said that if he'd had kids and had to do it all over again, it would have been much harder. That was it. That was the whole thing. Not a framework. Not a tactic. Just someone who'd built something real, admitting out loud that what I was carrying was actually heavy — that it wasn't a character flaw that it felt impossible. It was impossible. And I'd done it anyway.

I didn't know I needed to hear that until I heard it.

The Four-Step Audit

I didn't build this framework from a book. I built it because I spent years resenting my situation, and one day I got tired enough of the resentment to get curious about it instead.

That shift — from *why is this happening to me* to *what is this making me* — is the whole thing. The audit is just a way to force that shift on purpose, instead of waiting until you're exhausted enough to stumble into it.

It works for any constraint. Time. Money. Geography. Skills. Access. Whatever yours is.

Step 1: Name it honestly.

Not "I'm busy" — that's a symptom. Not "I'm tired" — that's a result. What is the actual wall?

For me it was: *I don't have the hours other people have. I never have.*

That's the constraint. Not a mood. Not an excuse. A real, concrete ceiling on what was available to me.

*I don't have three hours a day to build something new.*

*I don't have startup capital.*

*I don't have a network in the industry I want to enter.*

*I don't have a degree that opens the doors I want opened.*

Be specific. A vague constraint produces a vague audit — and a vague audit produces nothing.

Step 2: What have you had to figure out because of it?

This is where most people stop too early. They see the wall and they either quit or they spend their energy hating the wall. But every wall forces a detour — and detours teach you roads the main highway never would.

I had to figure out how to do everything in smaller windows than seemed reasonable. I had to figure out how to make a half hour count. I had to get ruthless about what actually moved the needle versus what just felt productive. I didn't learn that in a course. I learned it because I had no other choice.

No time → You've had to learn to compress. You've learned to say no faster than people who have slack in their schedule ever will.

No money → You've had to be creative. You've had to negotiate, trade, find leverage where others just paid their way through.

No network → You've had to build in public. You've had to earn attention through quality instead of buying it through connections.

Write down three to five real things you figured out because of your constraint. Actual things — not abstract virtues. Things you can point to.

Step 3: What skill did that build without you knowing?

This is the reframe — and it's the hardest step, because it requires you to look at something you've been cursing and say: *this made me better.*

The things you figured out in Step 2 are the surface. Underneath them is a transferable skill — something you built in the dark that has value in the light.

Compressing work into small windows = focus and prioritization under pressure. That's not a coping mechanism. That's a skill executives pay coaches to develop.

Getting creative with zero budget = resourcefulness. That's the thing every early-stage founder needs and most can't manufacture.

Building without a network = earned trust. You learned to let the work speak because nothing else would. That's rare.

Name the skill. Give it a real name — not "I'm good under pressure." Say: *I build systems for constrained environments.* Say: *I find efficient paths through complex variables.* Say it like you'd describe it to someone you respect.

Step 4: Where is that skill showing up now — and where could it go?

This is the point of the whole exercise. The constraint wasn't the problem. The constraint was the curriculum.

I spent sixteen years doing technical support while trying to build a life. The thing I built — routing, sequencing, finding the most efficient path through too many variables with too little time — is the exact thing I use now to design AI systems that give people their hours back.

I didn't plan that. But it wasn't an accident either. The constraint knew what it was doing, even when I didn't.

Where is the thing you built already showing up? In your work, your relationships, the decisions you make under pressure?

And more importantly — where could it go if you aimed it?

Why This Matters More Than Another Productivity System

Most content about "getting more done" assumes the problem is your system. Get a better calendar. Use this app. Wake up earlier.

That's not wrong. But it misses something.

The people who build something real out of constrained circumstances don't do it because they found the perfect system. They do it because they stopped fighting the constraint and started listening to it.

Your constraint is telling you something about who you're becoming.

The audit is how you hear it.

Do the Audit

Four questions. Write the answers down — not in your head.

1. What is my actual constraint right now?

2. What have I had to figure out because of it?

3. What skill did that quietly build in me?

4. Where is that skill showing up — and where could it go?

You can also use the [interactive tool](/audit) — it walks you through it and generates a Constraint Card you can keep.

The newsletter gives you one idea each morning. This is what's underneath it.

If you want to go deeper — past the daily read, past the tools, into the actual work of building something — that's what the community is for. More on that soon.

— Michael

The newsletter is the short version — one idea every morning. The community is where we go deeper.