Concept
Process, Not Product
Process, not product is the practice of committing to a fixed block of focused effort, such as 25 minutes, instead of committing to finishing a task, so that starting stops feeling like a threat.
Procrastination is rarely laziness. It is usually a quick escape from the brief discomfort of starting. In A Mind for Numbers, Barbara Oakley cites brain-imaging work by Ian Lyons and Sian Beilock. For people anxious about maths, simply anticipating a maths problem activated regions linked to pain. The striking part is the timing: the discomfort peaked before the work, not during it. A goal like "finish the report" keeps that dread alive because the product is big, vague and about to be judged. A goal like "work on the report for 25 minutes" is small and clear, and you are already achieving it once the timer starts. The question shifts from "Will I succeed?" to "Did I show up?" Once you are inside the work, the anticipatory pain usually fades. The finished product tends to arrive as a by-product of repeated sessions. Oakley's tool for this is the Pomodoro: a timer, one task and no interruptions.
A real-life example
Maya has a grant application due in ten days. She has opened the file six times without typing a word. Her to-do list says "Write application." She changes it to "Two 25-minute sessions on the application, 9:00." At nine she sets a timer and drafts a messy budget section. Nothing is finished, but the session counts as a win. By day four, after eight sessions, she has a full rough draft.
How to use it
- 1Rewrite one dreaded task as a time commitment: replace "finish X" with "25 minutes on X" and give it a start time.
- 2Set a timer and put your phone in another room. Work on whatever part of the task is in front of you until the timer rings. Quality is not the test; staying is.
- 3Take a short break. Judge the day by sessions completed rather than tasks finished, then repeat tomorrow.
