The One-Task Rule in Practice
What the One-Task Rule Actually Means in the 120 Code
One task means one specific output. Not one project. Not one topic. One thing that will be done when the flame dies. This article explains the rule so you can actually apply it.
How to Apply the One-Task Rule When Working on a Long Project
The project continues for months. The session needs one task. This article explains how to identify session-sized pieces of long projects — and how to chain them into continuous progress.
What to Do When You Finish the Task Before the Flame Dies
Task done. Flame still burning. 40 minutes left. This article explains exactly what to do with remaining session time when the primary task is completed before the session ends.
Why Adding a Second Task Mid-Session Weakens Both Tasks
The second task feels harmless. It is not. This article explains what happens to the first task when a second is introduced mid-session — and why the cost is larger than it appears.
How to Break Large Tasks Into Pieces That Fit One Session
A task that takes weeks needs 120-minute pieces. This article explains how to break large work into session-sized units and chain them into a coherent project arc over time.
When the Right Task Still Feels Like Too Much to Hold for 120 Minutes
The task is correct. But it still feels overwhelming inside the session. This article explains how to work with an overwhelming task without switching to a different one.