The first ten minutes of a task often feel harder than the next hour. Opening the document, finding the right place, and deciding what counts as a beginning can create a small maze before any meaningful work starts. It is tempting to treat that hesitation as a motivation problem. I think it is often a setup problem: the task has not yet been reduced to a visible first action.
Why the beginning gets inflated
“Work on the report” is an outcome, not an action. It leaves several decisions unresolved: which section, what source, what question, and how polished the first attempt should be. Each decision is reasonable on its own, but together they make the doorway feel heavier than the work. A student opening a dense chapter faces the same thing: reading the whole chapter is daunting; marking the first paragraph and writing one question is concrete.
There is a counterpoint worth taking seriously. Too much preparation can become another form of procrastination. A person can spend twenty minutes arranging a perfect workspace instead of starting. So the aim is not elaborate planning; it is to remove just enough ambiguity that the next physical action is obvious.
Make the first action observable
Before a session, translate the task into something you could see happening: write three rough bullets, inspect one example, or solve the first line. Then give that action a bounded stretch of attention. A countdown can make the boundary tangible, while a stopwatch can simply record how long you choose to stay. Neither tool supplies the task or guarantees concentration; they make time easier to notice while you do the work.
This distinction matters because “start small” can sound like lowering standards. It is better understood as separating entry from achievement. The first few minutes are for crossing the threshold, not proving the whole project is easy. Once underway, you can judge the real scope with more information.
Leave room for the other view
Some work genuinely needs a careful plan before action: a complex handoff, a safety-sensitive procedure, or research with multiple dependencies. In those cases, defining the sequence is part of doing the work, not avoidance. But for ordinary writing, study, and desk tasks, waiting for complete clarity often makes the first step unnecessarily expensive.
My practical position: make the opening move small and specific, then let the session reveal what deserves planning. When you are stuck, does a shorter first action help you begin, or do you need the map before you move?
iOS: https://apps.apple.com/se/app/focus-timer-desk-clock/id6762793543?l=en-GB Android: https://play.google.com/store/apps/details?id=com.focus.timer.desk.clock
Top comments (0)