Find the obstacle instead of giving an order
How do you get yourself working when the document is open but starting keeps being postponed? First identify the obstacle: low energy, an unclear task, fear of judgment, dependence on someone else, or excessive scope. These situations need different actions. A harsher order does not make missing data available or add energy.
Choose one task that genuinely needs doing. Ask: ‘Do I understand the nearest step? Do I have the materials? Do I have enough energy for a small trial pass?’ The answer helps choose the next action rather than judge your character. Sometimes clarifying the task, agreeing on a deadline, or resting is the sensible decision.
This discussion concerns work organization. It does not diagnose persistent tiredness or replace help for a prolonged decline in well-being. A useful list can reduce uncertainty but need not solve everything preventing someone from working.
Check energy and obligations
If you slept poorly, missed food, or handled urgent issues all day, start with a realistic assessment of the remaining load. Separate what is mandatory today from what can move. Do not declare every unpleasant task optional, but do not plan a normal workload on top of an already exhausted day either.
The NHS recommends medical assessment if unexplained tiredness persists for several weeks or affects everyday life. This marks a limit to productivity advice. Do not explain persistent low energy solely as a lack of discipline or diagnose yourself from work behavior.
If energy is low right now, choose a safe small step or agree on postponement. Do not use a short trial to force yourself into work where errors could have serious consequences. Being able to draft an email and being able to make a high-quality consequential decision have different requirements.
Clarify the task at the action level
‘Prepare a report’ can conceal a dozen actions and an unknown format. First clarify who needs the result, by when, and what it must contain. If that answer is missing, the nearest action is clarification rather than guessing expectations.
In the official GTD description, clarifying an item involves identifying the next action. Use a simple starting test: do you know what physical action to take first? ‘Open the previous report and list section headings’ is much more definite than ‘pull myself together and work properly’.
A small step must advance the required result. Renaming folders, choosing a new font, and cleaning the entire desk can be convenient postponements. If the task remains just as uncertain afterward, choose an action that supplies substantive information or part of the result.
Lower the stakes of the first attempt
Sometimes the obstacle is demanding good work immediately. Separate drafting from checking. On the first pass, collect structure and known facts; on the second, correct weak points. State beforehand that the draft will not be sent without review, so acceptable errors do not become a public risk.
If you fear judgment, clarify a sufficient result criterion. ‘Three headline options for discussion’ is easier to start than ‘the one perfect headline’. If the criterion depends on the client, request an example or agree on an intermediate version. This reduces uncertainty without promising immediate relief from unpleasant feelings.
You do not have to wait until you want to work. Nor must you ignore resistance. Use it as a clue: which part is unclear, what seems too difficult, and which consequence is frightening? Sometimes the answer leads to a practical adjustment; sometimes it shows that the workload itself needs discussing.
Example: a report that cannot get started
The author’s example: Marina must send a weekly report by 12:00 tomorrow. She repeatedly opens the file but reads correspondence instead of writing. Examination reveals uncertainty about whether unfinished projects should be included. The first step is a short format question to the manager, rather than fighting the phone.
While waiting for a reply, Marina opens the previous version and lists three confirmed results. She assigns 15 minutes as an illustrative trial window. This produces a report foundation and a list of missing data. She does not promise to finish the document in those 15 minutes or consider an incomplete version a failure.
After the manager replies, Marina adds a separate section on unfinished work: state, obstacle, and next step. Then she checks numbers and the recipient. Resistance has not magically disappeared, but the task has become a sequence of specific actions, each of which can be finished and checked.
- Find the obstacle
Unclear whether to include unfinished projects
- Clarify
Ask the manager about the format
- Do what is available
List three confirmed results
- Check
After the reply, fill the remaining section and verify numbers
A short trial with a real right to stop
Choose a limited window matching today’s energy and step size. For one person it is five minutes; for another, twenty. The number has no universal power: it prevents an indefinite agreement to ‘work until everything is finished’.
Before the trial, write the result: list questions, gather three facts, or fill one section. During the window, remove only the most obvious distraction. At the end, assess whether work has started moving. Continue another pass, change the step, or stop and agree on a deadline.
Do not make the right to stop fictional. If every trial obliges you to work another hour, the small promise loses credibility. Finishing with a specific intermediate result is acceptable. Record the action from which you will return to the material in the next window.
A pre-start review template
Fill in: what is needed today; why it is needed; what blocks it; which step is available; what that step lacks; when to assess the result. Do not add dozens of causes: choose one directly affecting the nearest step. The review should take less energy than the work itself.
- Unclear result: request a format or example.
- Missing data: identify the source and send a specific request.
- Excessive scope: choose one verifiable part.
- Fear of mistakes: separate drafting from sending and define checking criteria.
- Low energy: review mandatory work and the available window; agree on postponement if needed.
- Distraction: limit one source during the trial.
Every decision has a cost. Clarification can delay starting but reduce rework. Reducing scope requires agreement. Rest takes time, but attempting difficult work without sufficient energy may also produce an unusable result. Compare real options rather than an imagined unlimited version of yourself.
What to do if the pattern repeats
Look at several similar cases. Do you always postpone one task type? Skills or clear requirements may be missing. Is starting difficult after a particular time of day? An unsuitable load may be scheduled there. Are you always waiting for others’ data? An earlier request point is needed.
A recurring failure is better addressed through work conditions than solved anew each time. Create a report example, save a required-data list, and agree on an intermediate review in advance. If conditions are systematically unrealistic, discussing scope matters more than another personal starting trick.
For today’s task, an honest decision is enough: one available step, a necessary clarification, or a specifically agreed postponement.
Sources
Frequently asked questions
Should I start with the hardest task?
Not always. If it is clear and you have energy, that is reasonable. If data or skill is missing, a preparation step is needed first rather than an obligatory attempt at any cost.
Will a strict self-imposed deadline help?
It can define a window but does not remove uncertainty or missing resources. Do not present an internal date as a real commitment, and retain the option to review scope.
What if even a small step does not work?
Stop and check the cause: energy, clarity, materials, and consequences of error. Prolonged unexplained tiredness affecting life warrants professional assessment.
Turn an idea into action
Was this helpful?
Rate the article and tell us what was missing. Your feedback goes to the Sinqly team and will not be published on the site.



