When a task keeps slipping to tomorrow, start by identifying what prevents the next concrete action. Is the brief unclear? Is the first step too large? Are you waiting for information? A useful plan addresses that obstacle instead of adding another ambitious promise to your to-do list.
This guide offers a small experiment you can run on one real task this week. The examples and worksheet are illustrative, not reports of personal testing or guaranteed results.
1. Check whether the delay is actually a problem
Postponing work can be sensible when priorities change or you need a decision from someone else. Write down the deadline, the consequence of waiting, and any missing input. If you cannot proceed without approval, sending a precise question may be the right next action.
For a task you can start, finish this sentence: “I am avoiding this because ___.” Use a specific answer such as “I do not know what the client expects” or “I keep rewriting the opening.” That answer helps you choose an intervention. It does not need to become a judgment about your character.
2. Turn the project into a visible first action
“Finish the report” describes an outcome. “Open the report and list the three decisions it needs to support” describes an action you can take now. Aim for a first step that leaves something visible behind: a question, an outline, a calculation or a rough paragraph.
Example: You owe a five-slide project update on Thursday. Start with five slide headings: goal, work completed, evidence, obstacles and next decision. Put one rough bullet beneath each. Leave formatting until you have the information. These steps are examples of a workflow, not a prescribed sequence for every project.
If even that feels too large, set a two-minute timer and create only the headings. Two minutes is a convenient starting limit, not a scientifically optimal duration. You can stop when the timer ends; the point is to define and attempt a manageable action.
3. Attach the action to a specific cue
An if–then plan connects a recognizable situation with an action. For example: “If I finish my morning meeting, then I will open the project update and draft the evidence slide before checking messages.”
Gollwitzer and Sheeran describe this approach as implementation intentions. Their research overview finds that such plans can help translate intentions into action. That supports trying a clear cue and response; it does not establish that any particular timer length will work for everyone.
Choose a cue that is likely to happen and an action you can realistically perform. Add a fallback: “If the meeting runs into my work block, then I will use the first ten minutes after lunch.” Avoid filling every available minute with fallback plans.
4. Match the adjustment to the obstacle
Unclear requirements: Ask one focused question before doing more planning. For example, “Should this update explain the delay or request a revised deadline?”
Repeated rewriting: Separate drafting from editing. Write the facts in plain bullets first, then schedule a second pass for wording. Define what the draft must contain before you start.
Frequent interruptions: Choose a short period when you can reasonably be unavailable, close unrelated tabs and tell collaborators when you will respond. If your job requires constant availability, use smaller blocks instead of an unrealistic hour-long blackout.
Too much work: List what fits into the available time and renegotiate the rest. A better timer cannot make an impossible workload fit.
5. Use a work block with a stopping rule
Try a 15- or 25-minute block for one clearly defined output, followed by a short break. Adjust the duration to the task and your circumstances. There is no need to force a particular schedule if it makes starting harder.
Before starting, write “done for this block means ___.” For the project update, that could mean five headings with one bullet each. When the block ends, record what you produced and the next action. A stopping rule helps prevent a small task from expanding into an entire evening.
Copy this one-task worksheet
Task and deadline: ___
Why it matters: ___
What is blocking me: ___
First visible action: ___
If–then plan: If ___, then I will ___.
Done for this work block means: ___
Fallback if interrupted: ___
What I completed: ___
Next action: ___
Filled example: Project update due Thursday; the manager needs a decision on a delay. Blocker: too much background material. First action: write the five slide headings. Plan: after Tuesday’s morning meeting, draft one bullet per slide for 15 minutes. Done means five rough bullets. If interrupted, finish the remaining bullets after lunch. Next action: verify the dates against the project notes.
Review the experiment after one week
Keep a short record for three attempts: what you planned to start, whether you started at the cue, what you produced, and what interrupted you. Judge the method by completed work and whether the schedule was sustainable, not by how busy you felt.
If you did not start, shrink the first action or choose a more reliable cue. If you started but kept switching tasks, adjust the environment. If the task no longer matters, remove it deliberately. Change one element at a time so you can see which adjustment helps.
For a weekly reset, allow a few minutes to review unfinished work, choose one important outcome and prepare its first action. Leave room for breaks and unexpected demands. The goal is a repeatable way to begin useful work, not a perfect record of uninterrupted productivity.
Source and scope
Peter M. Gollwitzer and Paschal Sheeran: Implementation Intentions (PDF) explains the research behind if–then planning. The worksheet, slide example and suggested work blocks above are practical applications offered by this guide; they are not a validated treatment or a claim of measured productivity gains.
