The task that sits untouched for a week
"Sort out the insurance" looks like one task. Inside it sit a phone call, a document you cannot find and a decision you have been putting off. Nothing starts because the first move is unclear, and the label hides that. The item gets copied to tomorrow, then to next week, and it starts to feel heavier than the work inside it.
Research on procrastination describes part of this. Piers Steel's 2007 meta-analysis found that delay grows when a task feels unpleasant and when its reward is far away. A vague task is both. It is unpleasant to look at because you cannot see where it begins, and the payoff sits at the end of several steps nobody has named yet.
Why splitting works
Albert Bandura and Dale Schunk studied children working through a long series of subtraction lessons. The children who set a small target for each session made more progress, and enjoyed the work more, than those who aimed only at the distant total. Near goals produce feedback early, and early feedback keeps the work going.
Peter Gollwitzer's work on implementation intentions approaches the same problem from another side. A plan phrased as "when this happens, I will do that" is acted on more reliably than a general intention to get something done. Naming the moment in advance hands the start to a cue in the day.
Estimation is the part most people skip. We underestimate how long our own tasks will take, a pattern Roger Buehler, Dale Griffin and Michael Ross called the planning fallacy. Justin Kruger and Matt Evans later showed that listing a task's parts before estimating it produces longer and more realistic estimates. Breaking a task down is also how you find out how big it is.
Splitting it, step by step
- Write the first physical action. "Open the renewal email and write down the renewal date" is a first action. "Research options" is a project. David Allen calls this the next action: the visible thing you would do if you started now.
- Cut until the first step takes under fifteen minutes. If you cannot picture yourself doing it, it is still too big.
- Name the step that needs someone else. A reply from a broker or a signature from a landlord waits on other people's time, so it goes first or it stalls everything behind it.
- Attach a moment to each step. "After lunch, at the desk" is enough. That is Gollwitzer's implementation intention in its plainest form.
- Give each step a duration once the list is split. A step without a duration cannot be scheduled, so it drifts.
- Keep the steps in one place, each as its own task with its own line.
How small is small enough
Splitting has a limit. Forty two-minute steps create their own overhead, and managing the list becomes the task. A better test is whether a step can be finished in one sitting without deciding anything new. "Call the insurer" passes if you know the number and what to ask. It fails if you still have to choose which policy you want, and in that case the choice is its own step.
Some steps hide waiting. Sending a form takes two minutes and the reply takes a week. Write those as two items, the send and the follow-up, and put a date on the second one.
A worked example
Take "renew the car insurance", due in ten days.
- Find the renewal letter and note the date and the current premium. Ten minutes.
- Get two comparison quotes online. Thirty minutes in one sitting.
- Call the current insurer and ask whether they will match the lower quote. Fifteen minutes, during business hours.
- Decide and pay. Ten minutes, after the call.
- Save the new policy where you will find it next year. Five minutes.
That is seventy minutes of work spread over two or three days, with the call placed early because it depends on someone else's opening hours. The original label suggested a lost afternoon. The split version fits around an ordinary week.
What Flowo does with this
Brain Dump stores the thought before you have decided what it is. When a task feels too broad, task breakdown proposes editable steps on request, and you keep, cut or rewrite them. The steps are then ordinary tasks with durations, so the scheduler places them around your fixed events and daily boundaries like anything else. Nothing runs unless you ask for it. The features page shows how the breakdown and the scheduler connect.
Questions people ask
How many steps should a task have?
As many as it takes for the first one to be obvious and short. Most admin and household tasks land somewhere between three and seven. Past ten, check whether part of the list is really a separate project.
Should I schedule every step at once?
Schedule the first step and anything that depends on other people. The rest tend to change once the work starts, so planning them in detail early is effort spent twice.
What if the first step still does not start?
Make it smaller or more concrete. "Open the laptop and find the email" is a legitimate first step. Once something is moving, the next step is usually easier to see.
Sources
- Allen, D. (2001). Getting Things Done: The Art of Stress-Free Productivity. Viking.
- Bandura, A., & Schunk, D. H. (1981). Cultivating competence, self-efficacy, and intrinsic interest through proximal self-motivation. Journal of Personality and Social Psychology, 41(3), 586-598.
- Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the "planning fallacy": Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366-381.
- Gollwitzer, P. M. (1999). Implementation intentions: Strong effects of simple plans. American Psychologist, 54(7), 493-503.
- Kruger, J., & Evans, M. (2004). If you don't want to be late, enumerate: Unpacking reduces the planning fallacy. Journal of Experimental Social Psychology, 40(5), 586-598.
- Steel, P. (2007). The nature of procrastination: A meta-analytic and theoretical review of quintessential self-regulatory failure. Psychological Bulletin, 133(1), 65-94.
Related: capturing a thought before you classify it, re-planning a day that has slipped, and how placements are decided.
Flowo is free to download on the App Store for iPhone and on Google Play for Android, with optional in-app purchases.