Stop procrastinating
Procrastination isn’t laziness. It’s structural.
Your brain stalls when it can’t see the next brick. Here’s the brick-by-brick method that breaks the loop without needing more discipline, motivation, or willpower.
Most procrastination advice tells you to fix yourself. Build discipline. Get accountability. Do the hardest thing first. Use the Pomodoro. Set a timer. None of it works for long, because the diagnosis is wrong.
The full picture: This page covers one piece of the 5-folder OOPS Method. The complete framework lives on the homepage.
Procrastination isn’t a character flaw. It’s a structural failure. Specifically, it’s the failure to make the next brick visible. The brain stalls when it can’t see the smallest concrete action available. It doesn’t stall because you lack motivation. It stalls because the project is too vague to start.
You don’t need more willpower. You need the next brick visible.
Why willpower fails
Discipline is an unreliable ingredient. The next brick is always available.
Discipline-based productivity advice assumes you can summon willpower on demand. You can’t. Nobody can, reliably. Willpower is a finite, unpredictable resource that depletes by midday and disappears entirely under stress. Building a system on willpower is like building a house on weather.
The opposite approach is to engineer the friction out of the next action. If the next action is so small and so concrete that doing it requires almost no willpower, you’ll do it. Then the next one. Then the next.
That’s the brick. The brick is the smallest concrete action you could take in the next ten minutes that moves the project forward. Not the most important action. Not the highest-leverage action. The smallest concrete one.
The brick rule
If you can’t name the next brick, the project is too vague.
Here’s the test. Pick something you’re currently procrastinating on. Now answer: what is the smallest concrete action you could take in the next ten minutes that moves this forward?
If you can answer that question, do that thing. The procrastination breaks the moment you start. Movement creates more movement.
If you can’t answer it, the problem isn’t you. The project is too vague. Vague projects produce procrastination. Specific projects produce action.
Examples of vague: “Redesign the website.” “Get healthier.” “Fix the financial situation.”
Examples of specific (the next brick): “Email my designer the homepage copy I already have.” “Schedule a 30-minute walk for 4pm today.” “Open my bank app and write down the three highest-balance credit cards.”
The procrastination wasn’t about laziness. The project just hadn’t been broken down enough. Once it’s broken down, the brick becomes obvious. Once the brick is obvious, you place it.
The system
The OOPS Method makes the next brick visible by default.
The reason brick-finding works repeatedly (not just on a good day) is because the OOPS Method has it built into the structure. Every Launch in your LEGOS folders requires three things: a finish line, a deadline, and the next 3 moves visible.
That third part is the procrastination prevention layer. If a Launch doesn’t have its next 3 moves spelled out, it isn’t Launch-ready. It’s an Orbit waiting for definition. The act of defining the next 3 moves is what makes the project specific enough to act on.
This is why OOPS students stop procrastinating without trying. The system forces specificity into every Launch. Specificity is the cure.
If a Launch stalls (no movement for two weeks), it demotes back to Orbit. No shame. OOPS. Adjust. Continue. The point isn’t to never stall. The point is for the system to handle the stall without producing more guilt.