The one idea
Starting is a separate skill from working. Once you are twenty minutes in, the task is usually fine — the resistance was almost entirely at the door.
So the whole problem is the door.
Reduce the task to a first action so small that doing it takes less effort than deciding not to.
Not "write the report". Open the document and type the four section headings. That is a two-minute action with no judgement in it, and it is very hard to argue yourself out of. Once the document is open with headings in it, you are already working, and the decision you were avoiding never had to be made.
Make the first step small enough that starting is easier than avoiding.
Define the first action as a physical, specific, two-minute step with no thinking required. Protect the first block from interruption.
Avoidance attaches to ambiguity and to anticipated difficulty, not to effort. Reducing ambiguity — making the next action concrete — removes most of the resistance without requiring any change in motivation.
Why the door is heavy
Three things make a task hard to start, and they are worth telling apart because they have different fixes.
It is not defined. "Sort out the client thing" is not a task; it is a region of worry. You cannot start it because there is nothing specific to do. The fix is not motivation, it is a decision about what the first action is.
You expect it to feel bad. Difficult, boring, or a place where you might find out you did something wrong. Avoidance here is not irrational — it is accurate short-term forecasting, and the fix is to shrink the exposure: two minutes, not an afternoon.
You do not know how. This is being stuck, not being reluctant, and it wears the same clothes. If you cannot start because you do not know how, you need the-stuck-protocol, not this lesson. Telling these apart matters: the fix for not-knowing-how is a question, and no amount of starting technique substitutes for it.
Shrinking the first action
The test: could you do it in two minutes, without deciding anything?
| The task | Not a first action | A first action |
|---|---|---|
| Write the quarterly report | "Start the report" | Open last quarter's report and copy the headings |
| Reply to a difficult email | "Deal with that email" | Open a reply and write the first sentence, do not send |
| Learn SQL | "Start learning SQL" | Open the tutorial and do exercise one |
| Fix the broken spreadsheet | "Fix the sheet" | Open it and write down the one sentence describing what's wrong |
| Chase an unpaid invoice | "Follow up on the invoice" | Find the invoice number and the contact's email |
Notice the pattern. Every good first action is physical, specific, and requires no judgement. "Think about the structure" fails all three. "Copy last quarter's headings" passes all three, and by the time you have done it you are usually thinking about the structure anyway.
Two useful variants:
Permission to do only that. Tell yourself you are doing only the two-minute thing and will then stop. Mean it. If you stop, fine — the document now has headings, and tomorrow's door is lighter. Usually you will not stop, but the technique stops working if you use it as a trick on yourself.
Start in the middle. If the beginning is the hard part — an introduction, a first email — start with the section you know how to write. Order of writing does not have to match order of reading, and the blank page is what you are avoiding, not the work.
Attention, and the cost of interruption
Once started, the second problem is staying. This is mostly not about willpower either — it is about what is within reach.
Interruptions cost more than they take. A thirty-second Slack message does not cost thirty seconds; it costs the time to get back into what you were holding in your head, which is longer. Several small interruptions can consume an hour of capacity while occupying five minutes of clock.
The practical countermeasures, in order of how much they work:
- Remove the thing rather than resisting it. Phone in a drawer or another room, notifications off, unrelated tabs closed. Resisting a visible distraction costs attention continuously; removing it costs nothing after the first ten seconds.
- Keep a capture list. When an unrelated thought arrives — an email you must send, a thing to buy — write one line on a scrap and continue. The thought returns because you are afraid of losing it; writing it down ends that.
- Work in a fixed block. Twenty-five or fifty minutes, timer running, one task. The value is not the duration. It is that a block has an end, so continuing does not feel unbounded.
- Leave a deliberate loose end. Stop mid-sentence, or with the next step written down. Tomorrow's door is much lighter when there is an obvious first action waiting, and this is the cheapest trick in this lesson.
You have to call a client to explain a delay. You have been not-calling for two days, and each hour makes it worse.
The task is not "make the call". It is a chain of avoidances: you do not know exactly what to say, you expect them to be annoyed, and you have not decided what you are offering.
First action, two minutes: write three bullet points — what happened, what the new date is, what you are doing to prevent it. Nothing else.
With those three bullets on a page, the call is now reading three lines and answering questions. That is a different activity from the one you were avoiding, and the difficult part — deciding what you were going to say — has already happened.
An assignment is due in five days and you have not opened it.
First action: open the brief and highlight the actual question. Then write, in your own words, one sentence saying what is being asked for.
That sentence is worth an hour. Half of assignment paralysis is not knowing what the deliverable is, and the brief usually contains a specific verb — compare, evaluate, describe — that tells you the shape of the whole thing. You have not started writing, and you have removed the ambiguity that was doing most of the blocking.
Try this
Pick something you have been avoiding for more than three days. Write the first action.
Then test it: could you do it in two minutes? Does it require you to decide anything?
Your challenge
Level 3 · IndependentFor one week, keep a list with two columns: the task you avoided, and the first action you eventually took that got you moving.
At the end, look at your first actions. Most people find they are all the same two or three shapes — usually "open the file", "copy the previous version", or "write one sentence describing the problem".
Success criterion: you can name your own three first-action shapes. Then use them deliberately, rather than rediscovering them each time after two days of avoidance.
What people usually get wrong
- Waiting to feel like it. The feeling arrives after starting, not before. Waiting for motivation is waiting for the consequence to precede the cause.
- Making the first action too big. "Write the introduction" is not a first action. "Open the document" is.
- Planning instead of starting. Reorganising your task list is avoidance that produces a document, which makes it harder to notice.
- Choosing the hardest task as the entry point. Starting anywhere beats starting correctly.
- Treating a not-knowing-how problem as a motivation problem. You will try harder at something no amount of trying will fix. Ask instead.
- Setting up an elaborate system. A timer and a notebook are enough. Two hours choosing an app is the most sophisticated form of not starting.
How someone experienced does it
Experienced people end a session by writing the next action, not by finishing a section. Stopping at a clean boundary feels satisfying and makes the next start hard, because tomorrow you face a blank space again. Stopping with "next: check whether the Q3 figures include refunds" written at the top means tomorrow you sit down and do that, and you are working before you have decided to be.
They also protect one block rather than trying to protect the whole day. One genuinely uninterrupted block, at whatever time of day your attention is actually good, does more than six fragmented hours — and defending one block is socially achievable in a way that defending a day is not.
The third thing is knowing their own pattern honestly. Some people work well early, some late; some need a warm-up task, some are ruined by one. This is worth observing over a few weeks rather than adopting from someone else's routine. The productivity advice that works for you is the advice that matches a pattern you actually have.
When not to use this
None of this is a substitute for a task being wrong. If you are consistently avoiding one thing, ask whether it should be done at all, whether it is yours, or whether it is unclear because nobody has defined it. Persistent avoidance is sometimes accurate information about the task rather than a fault in you.
And it is not a fix for a workload that is genuinely too large. Techniques for starting do not create hours. If everything is urgent and nothing fits, that is a conversation with your manager about priority, not a personal failing to optimise away.
Why avoidance grows the longer you leave it
An avoided task does not sit still. It accumulates.
Partly this is practical — the deadline gets closer, the email you did not answer needs an apology as well as an answer, the delay itself becomes something to explain. The task genuinely gets harder.
Partly it is that each time you decide not to start, you are practising not starting on that specific task. The association strengthens. By day three you are not avoiding the report; you are avoiding a small unpleasant feeling that now arrives when you look at the filename.
This is why the size of the first action should scale with how long you have avoided something. A task you have been avoiding for a week needs a smaller first action than one you started avoiding this morning — the reverse of what people do, which is to demand more of themselves the longer they have put something off. That demand is precisely what makes the door heavier.
Prove it
Take your current task list. Beside each item that has been sitting there more than three days, write a first action that passes the two-minute test.
Then do one of them. Not the most important one — the one with the easiest first action. The list you produce is more useful than the task list itself, because a task list tells you what to do and a first-action list tells you how to begin.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned breaking a task I am avoiding into a two-minute first action. Assume I am intelligent but relatively new to this — treat me as beginner level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood breaking a task I am avoiding into a two-minute first action. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at starting work you are avoiding — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.