You've built right-sized infrastructure. It's simple. It works. It disappears when you don't need it.
Now you need to keep it that way.
This is where most people fail. They build good infrastructure, then slowly let it bloat. They add features. They optimize. They maintain. And before they know it, the infrastructure has turned again.
This section teaches you how to maintain infrastructure without it becoming maintenance.
Most weekly reviews are too long, too comprehensive, and too exhausting to sustain.
A right-sized weekly review takes 15 minutes. Not 2 hours. Here's how.
Minute 1-5: What happened this week
Minute 6-10: What's next
Minute 11-15: System check
That's it. No elaborate project reviews. No comprehensive life audits. Just: what happened, what's next, are the systems working.
You don't need to track everything. Most things can be trusted to memory and intuition.
Track:
Trust:
The less you track, the less you maintain. The less you maintain, the more you create.
Not every friction requires a system adjustment.
Sometimes friction is good. It slows you down when you should slow down. It makes you think when you should think.
Adjust when:
Leave alone when:
The discipline is in not fixing every minor problem. Let things be imperfect.
Set a timer. Do your weekly review. Stop at 15 minutes no matter what.
Notice what didn't get reviewed. That's probably fine. It wasn't urgent enough to fit in 15 minutes.
Once a month, take 30 minutes for a deeper check. Not to optimize. To notice what's changed.
What stopped working?
Systems that worked last month might not work this month. Your work changes. Your needs change. Notice what's no longer serving you.
What's getting in the way?
What infrastructure are you working around instead of with? What's become an obstacle instead of an enabler?
What can you delete now that you couldn't delete last month?
You evolve. Systems that were essential become unnecessary. Give yourself permission to let go of what you've outgrown.
This is hard. You built something. It seemed important. Now it's not.
Delete it anyway.
Building infrastructure isn't a one-way process. You add. You remove. You adjust. You simplify.
The infrastructure you needed last month might not be the infrastructure you need now. That's fine. Change it.
Here's how to tell when your infrastructure is turning again:
When you notice yourself thinking about how the system works instead of just using it, something's wrong.
Good infrastructure doesn't require thought. It's automatic. Invisible.
If you're conscious of the system while using it, simplify it.
Do you have documentation for your own systems? Do you need to remind yourself how things work?
That's a sign the system is too complex.
If you can't remember how it works without documentation, it's not simple enough.
When you spend more time improving systems than using them, you've crossed the line.
Track your time for a week. How much on infrastructure? How much on actual work?
If the ratio is wrong, stop optimizing. Start deleting.
The ultimate test: Are you maintaining infrastructure or wandering toward interesting work?
If you're spending your best energy on maintenance, your infrastructure has won.
Delete ruthlessly. Simplify aggressively. Get back to wandering.
Check for warning signs:
These are your next deletion candidates.
You now know how to maintain infrastructure without it becoming maintenance:
Maintenance isn't about preserving what you built. It's about constantly simplifying toward what actually serves you.
In Part 5, you'll learn how to stay free long-term. How to resist complexity creep. How to build trust in simplicity. How to keep wandering.