Key Take-Aways

Observation comes before intervention.
You can’t intelligently change a pattern you haven’t learned to see.

Design for the version of you who will actually have to execute.
A plan that only works when you’re motivated is fragile.

Repetition creates identity.
Reliability comes from evidence, not intention.

A good system contains a recovery protocol.
Falling off isn’t the main danger. Failing to return is.

Recovery is infrastructure, not a reward.
Rest belongs inside the system because the system depends on a functioning human.

overview

A good system shouldn’t require the best version of you.

It should help you become that person even when life gets messy.

Life is chaotic.
Work, fatigue, stress, money problems, distractions, temptation, bad moods — all of it interrupts the version of life we planned to be in our heads.

I keep making plans for a future version of myself who is focused, disciplined, motivated, and always knows what to do next.

Then I get annoyed when today’s me doesn’t follow through.

But that’s not fair.

I beat myself up for failing to follow through when I don’t even know how to succeed.

The system should be built for current me, and we grow from there.

Notice before you fix

Before changing a behavior, you have to actually see it.
You have to build awareness.

I’ve got some behaviors to work on.
I’ve been using the tools in Atomic Habits this week: Habit scorecards, time audits, using cue → craving → response → reward, along with my thought/impulse prevention notes have all helped with this.

Last week I did a weekly audit, where you track everything you do for a week in 15-minute increments. It’s a practice I’ve heard Alex Hormozi recommend, claiming it can be one of the most productive weeks you’ll have.

I concur.

After the weekly audit, I used that data to create my habit scorecard and started to understand my current biggest strengths and weaknesses.

With a list in place of what I was doing, the patterns were displayed for me to see and no way to make excuses, all I can do is continue to build awareness.

For that I’ve been using:

Feel → Want → Under → True → Choose

What am I feeling?
What do I want?
What’s underneath it?
What’s actually true?
What am I choosing next?

This has been very valuable data.
I’m noticing that the urge isn’t always the real problem.

Sometimes I want to smoke because I’m bored, anxious, hungry, confused, or don’t know what I’m doing next.

The awareness doesn’t instantly fix the behavior, but now I can actually see the loop.

You can’t solve a problem you’re unwilling—or unable—to see.

Observation comes before intervention.

Design instead of resist

I’ve also been experimenting with implementation intentions:

If this happens, I’ll do this.

They’ve helped, but they’re not enough by themselves.

When I’m tired, emotional, or distracted, that’s exactly when I’m least likely to remember or care about some rule I wrote earlier.
At least that’s the pattern I’ve been seeing.

So I’m learning that systems need more than good intentions.

Change the environment. Remove decisions. Make the better action easier.

Don’t repeatedly demand self-control where design could remove the decision.

And when you can’t remove the decision, have a response ready.

Build through repetition

A system also has to be repeatable.

I’ve spent plenty of time optimizing routines, journaling prompts, trackers, and plans instead of actually living them.

I was constantly rebuilding the starting line instead of collecting evidence.

The two-minute rule, done is better than perfect, starting small — these work because they help you accumulate repetitions.

Consistency doesn’t mean flawless performance. It means returning often enough for the behavior to become normal.

Identity comes from that evidence.
You don’t become reliable by deciding you’re reliable.
You become reliable by repeatedly doing what you said you would do.

Systems are for difficult moments

Yesterday I walked into a brake shop and came out thinking I had a $2,200 problem (on top of a $4,000 problem resolved last week).

My brain immediately started catastrophizing.

This morning I got a second opinion, called the first shop, got the actual information, and found out there had been a misunderstanding.

It was an $1100 problem.

Still annoying.
But very different from the problem I had created in my head.

Seneca said it best:

That was a pretty good example.

The problem became smaller when it became real.

Something happened.
I got upset.
I got the facts.
I decided what to do next.
I didn’t spiral.

That’s a system too.

Recovery is part of the system

I didn’t handle everything perfectly either.

I still stopped at the smoke shop on my way home that morning.
Before I might have been so thrown off I kamikaze ‘ed to the smoke shop, grocery store for snacks then home to lazily procrastinate the day away.

But instead, afterward I came home and got back to my Wednesday work instead of turning one decision into a wasted day.

That’s another thing I’m learning:

One bad decision doesn’t need a sequel.

A good system shouldn’t only tell you how to stay on track.
It should help you return when you leave it.

Conclusion

Being strong doesn’t mean never being frustrated, anxious, tempted, or thrown off.

You can still say:
This fucking sucks.

The important part is that the complaint doesn’t become the strategy.
I’m trying to become someone people can rely on when things are hard.

That doesn’t require perfection.
It requires learning how to respond.

Build the system before you need it.
Reduce the decisions.
Notice the loop.
Keep collecting repetitions.
And when you fall out of rhythm:

Return. Reflect. Adjust. Repeat.