Starting a task
Version 1, draft. Tried on 1 case (in progress).
How to get from "this is mine to do" to the first minute of doing it. For a person starting their own task, and for an agent or teammate helping them start.
When to use it
A task is chosen and nothing blocks it, yet it hasn't begun. Choosing which task comes first is a different SOP. If the task turns out to be blocked, say what it waits on and stop here.
Read the state first
Starting looks different depending on where attention is. Name the state before suggesting anything. The person's own word for it wins over any guess.
| State | What it looks like | What helps the start |
|---|---|---|
| Drawn | The task is interesting or new. | Get out of the way. Do step 3 and go. |
| Reluctant | The task is dull, fiddly or unpleasant, or it means switching place or frame of mind. | Shrink the first step and borrow structure (step 4). |
| Out of reach | The task needs a place or a tool you aren't at. | Tag it with the place and let it wait there (see Queue by place). Wanting to start and not being able to is not a failed start. |
| Deep elsewhere | Absorbed in something else. | Don't interrupt. Park the task with its first step written down. |
| Returning | Coming back after a break or an interruption. | Restate where things stand in one line, then step 3. |
| Resting | Not working, by choice. | Nothing. Rest is not a state to fix. |
Steps
- Say what done looks like, in one line. "Three checks run and their results written down." A task with no visible end is hard to begin.
- Check the place, then gather what the first step needs. Where do you have to be: anywhere, at a desk, in a particular room? Then devices, logins, files. A missing place or tool is the most common silent blocker. If you aren't there, the task is Out of reach, not late.
- Name the first physical action. Small enough to finish in about two minutes and concrete enough to picture: "open the app and load two tracks", not "test the feature". Concrete framing reduces delay (Some: McCrea et al., 2008).
- Tie it to a cue. "When I sit down after lunch, I open the app." An if-then plan with a specific moment makes follow-through more likely (Strong: Gollwitzer & Sheeran, 2006). For a reluctant start, borrow structure as well: tell someone when you will begin, or have a helper hand over one step at a time.
- Do only that first action. Then decide freely whether to continue. Stopping after one step counts as a start.
- Leave a line when you stop. One sentence on what is done and what the next action is, so the next start is a Returning start.
Queue by place
Sitting down somewhere is itself a cue. When you arrive at a place, begin with the tasks that only that place allows, one at a time, before anything that could be done elsewhere. Keep each of those tasks tagged with its place so the queue is ready on arrival. The trip to the place is where attention is most easily pulled away, so the first item should be visible the moment you sit down.
For helpers and agents
Show, then tell. Lead each hand-over with a picture of the task: a screenshot, a marked-up photo or a simple diagram that can be recognised at a glance. Words come second and stay short. Having to work out from a paragraph what is being asked is itself a barrier to starting.
Tag every task you hand over with the place it needs.
Hand over one step at a time. Say what the person should see before they act, and wait for their word before giving the next step.
Offer at most three options. One is better.
Never frame a start that hasn't happened as a failure. The task is "still open".
Don't break into deep focus to prompt a start. Hold the task and offer it at the next natural pause.
When the first step is done, say so plainly and ask whether to continue. Don't assume.
Evidence
- Strong. If-then plans ("when X, I will do Y") improve goal attainment: a meta-analysis of 94 tests found a medium-to-large effect (Gollwitzer & Sheeran, 2006).
- Strong. Delay tracks how unpleasant a task feels and how far off its payoff is, more than it tracks traits such as rebelliousness (Steel, 2007). This is why the Reluctant state gets extra structure and the Drawn state gets none.
- Some. Thinking about a task in concrete terms reduced procrastination in three experiments (McCrea et al., 2008).
- Some. If-then plans helped children with ADHD reach the response-inhibition level of children without it on a lab task (Gawrilow & Gollwitzer, 2008). Whether this carries over to adults starting everyday tasks is unknown.
- Practice. Working alongside another person ("body doubling") is widely reported to help starting. It has not been tested in controlled studies.
- Practice. Sorting tasks by the place or tool they need ("contexts") is long-standing personal-productivity practice. It has not been tested in trials.
- Field (2026-11-21). On the first trial, a task that needed a particular desk felt daunting from elsewhere, the walk there was where other things pulled attention away, and a picture of the task was asked for in place of written steps. This led to the Out of reach state, Queue by place and Show, then tell.
- Practice. The two-minute first action and the written "next action" come from personal-productivity practice, not from trials.
- Unknown. Whether naming the attention state first improves starting. This SOP's own trials are the first test.
Changelog
- 2026-11-21: Version 1 drafted.
- 2026-11-21: Draft revised after the first trial began: added the Out of reach state, the place check in step 2, Queue by place, and Show, then tell.