This is that system. All five stages. Built on the H.A.R.D. Framework.
Procrastination doesn't just show up at the moment of starting. It has five specific entry points — and if any one is unaddressed, it can bring the whole system down.
Planning — the important thing never gets protected time.
Prioritizing — the hard thing keeps losing to the easier thing.
Starting — the hard thing gets deferred indefinitely.
Sustaining — the practice breaks and doesn't recover.
Finishing — the project stops at 80% and joins the collection.
The complete anti-procrastination operating system addresses all five — not as a list of tips, but as an interconnected system where each stage supports the next.
Most people plan reactively. The hard thing — important work with no external deadline — gets whatever time is left over. Which is rarely enough. The important work always gets bumped.
Once per week — Sunday — thirty minutes to build the week before its demands take over. Name the one hard thing that makes the week meaningful. Schedule it first. Block focused work sessions before the calendar fills. Identify danger zones and schedule light work there. Leave 20% unscheduled as buffer. The over-planned week collapses at the first interruption. The buffered week absorbs it.
The urgent keeps winning over the important — not because you don't know the difference, but because the system defaults to urgency. The email with immediate consequence wins over the project with long-term consequence. Every time. Until you build a rule that overrides the default.
One rule. No exceptions. The most important, most avoided, most consequential thing gets the first available energy every day — before email, before messages, before anything generated by someone else's need. The night before: name the one hard thing for tomorrow. The morning: begin it before anything reactive enters the day. Procrastination has no opening — the first action is already decided.
Starting is the highest-friction moment. Most people wait until they feel ready — but motivation is the wrong tool. It requires a feeling that isn't reliably available. Starting doesn't require motivation. It requires a sequence.
Write the specific action for tomorrow before sleep — not decided in the morning when resistance is highest.
Workspace set the night before. Document open. Every step between waking and working eliminated in advance.
When work time arrives, move within five seconds — before resistance builds its case.
The first minutes don't have to be good. They have to exist. Perfectionism removed as a starting block.
Set the timer. After two minutes, you can stop. You almost never do.
The practice breaks. A bad day, a busy week — and the hard thing misses a session. The gap opens. The guilt accumulates. The restart feels so elaborate it never happens. Most practices don't fail at the start. They fail in the gap after the first miss.
Whatever caused the miss — the practice returns within 24 hours. Not the full version. The minimum. But within 24 hours. An open-ended gap is where practices go to die.
The return happens without self-criticism, without a reset ritual. "I missed yesterday. Today I do the minimum. Tomorrow I'm back to normal." No elaborate accounting.
Define the minimum version of the practice — the thing so small it can be done sick, tired, or overwhelmed. The floor prevents the gap from becoming permanent.
Projects stop at 80%. Finishing is hardest because it's most exposed — the finished thing can be evaluated. The perfectionism managed at the start resurfaces at the end as fear of insufficiency.
Before the project begins, define what done looks like — specifically. The word count. The launch date. The sent message. Done is named before the work starts.
Nothing new starts until the current project reaches the defined done. New ideas get written down and held.
The last 20% gets a dedicated, bounded sprint — not open-ended. Bounded final pushes produce finished things. Open-ended final pushes produce almost-finished things.
When done is reached, acknowledge it. The evidence file grows. The identity of someone who finishes solidifies.
Each stage connected to the next. Procrastination addressed at every entry point.
Weekly Architecture — built Sunday, hard thing protected first.
Hard Thing First Rule — most important thing gets first energy, every day, no exceptions.
Launch Protocol — five steps executed in sequence that produce a start without requiring motivation.
Recovery Protocol — 24-hour return, no-judgment restart, floor standard that survives the worst days.
Completion Protocol — defined done, one-project rule, bounded final push, acknowledged completion.
Which stage is where procrastination wins most often for you? Not all five equally — one specific stage. Name it. That's where the system needs the most work first.
Build one element of the fix for that stage this week. Not the whole system at once. The weekly architecture. The Hard Thing First rule. The two-minute launch. One piece.
Run it every day this week without exception. Seven days. The same element. Repeated until it stops feeling like effort and starts feeling like how things work.
Don't add a second stage until the first one is running. Build it in order. One stage. Running. Then the next.
Five modules. One per stage. Each module includes the framework, specific exercises, implementation tools, and structures that convert the map into a working operating system running in your actual life. By the end, the system is built. The delay is done.
The catatonic years weren't a discipline problem — they were a systems problem. Do the Hard Things First is the philosophy underneath the operating system. Destroy Your Weak Mind is the identity work that makes the system stick.
- Hard Things First Newsletter — every Saturday, free
- Do the Hard Things First — order on Amazon
- Destroy Your Weak Mind — the companion book
- Download the Action Vault — 9 free action guides
- 30-Day Hard Things Challenge — use code PROC10 for 10% off
Build one stage this week. The rest follows.
Three alarms. Three missed starts. The same broken system running every day, producing the same result. What changed everything wasn't discipline or willpower — it was redesigning the system at every stage so that procrastination had no entry point.