“Just start” is rarely a useful operating plan. A delayed task may be unclear, unpleasant, dependent on someone else or genuinely too large for the available time. Identify which problem is present before choosing a fix.
Ask what is delayed, and why
Replace “Alex is a procrastinator” with an observable statement: “The draft due Tuesday has not started, and the reviewer needs it on Friday.” Then ask the owner what the next action is, what information is missing and what competing work has priority. This separates a commitment problem from a dependency or capacity problem.
A 2021 experience-sampling study followed 75 university students and 582 planned academic tasks. Task-specific expectations of success, value and aversiveness were associated with later delay. That is evidence about academic tasks, not proof that the same causes explain every workplace delay. It does support asking about the specific task rather than assuming a fixed personality trait.
Match the intervention to the blocker
- Unclear output: show one acceptable example and define the smallest reviewable deliverable.
- Missing decision: assign the decision owner and a time when the answer is needed.
- Large or unpleasant start: schedule a short first pass: outline five headings, open the source file or draft the first paragraph.
- Competing commitments: make the trade-off explicit. Move a deadline, remove work or add capacity; do not silently stack priorities.
For a personal task, a conditional plan can help: “If it is 09:30 on Tuesday, I will open the brief and draft the three unresolved questions.” A 2026 randomized study of 81 undergraduates found a mental-contrasting plus implementation-intention exercise improved willingness to begin relative to positive thinking; the sample and one-week follow-up limit generalization. Another experimental study did not find a significant reduction in academic procrastination from simple goal or implementation-intention prompts over three weeks. A plan is a trial, not a guaranteed cure.
Have a useful conversation with a colleague
Try: “The customer report is due Thursday. What is the first part you can send by noon tomorrow? What is stopping that part? Which other commitment should move if this takes priority?” Agree on a specific artifact and a short check-in. Write down any dependency you own. If the answer reveals a system problem, fix that system rather than asking for more reminders.
Avoid diagnosing someone from a missed deadline. Persistent difficulties may have health, disability, caregiving or other causes that a manager cannot infer from performance alone. Use the organization's support and accommodation processes where relevant, and keep personal information private.
Review the result, not the label
After the check-in, compare the promised artifact with what exists. If work began, ask which change helped. If it did not, revisit the actual constraint and reset the commitment explicitly. A useful record has the task, next output, owner, dependency and review time; it does not need a character judgment.
For a team-wide pattern, track late handoffs by type rather than ranking people. Our capacity guide helps make overload visible, and the five-day friction log helps identify recurring interruptions.
Sources and archive context
- Primary study — task appraisals and delay, 2021 ↗
- Randomized study — mental contrasting and implementation intentions, 2026 ↗
- Primary study — limits of simple planning interventions, 2017 ↗
- Wayback Machine — former Key Organization page ↗
This original 2026 guide revisits a topic from the former site's archive. It does not reproduce the former article or present the former service as available today.