Many people begin a week with a long list: finish the report, prepare the meeting, read the material, call the client, and clear the backlog. The list may be accurate, but it does not answer the decisive question: when the computer opens on the first morning, what step will be taken, for how long, and how will we know that the work has actually started? If that answer remains vague, the plan is easily replaced by faster-response activities such as checking email, replying to messages, or rearranging documents.
This problem is often understood as a lack of willpower or personal discipline. In many cases, the nearer cause is that important work has not been designed with a sufficiently clear entry point. A goal such as “write the proposal” contains too many small decisions: which section to start with, which materials to use, what the first-draft standard is, and what needs to be discussed with someone else. When those decisions are left until the moment of work, start-up cost increases and the mind tends to choose easier activity.
Distinguish a goal from an entry point
A goal states direction and the desired result. An entry point states the concrete action that opens a work session. “Complete the quarterly plan” is a goal. “Open the draft, write three sentences describing the customer problem, and list the missing evidence in 25 minutes” is an entry point. The latter wording does not make the task smaller; it removes ambiguity from the first step.
A good entry point has four parts: a small visible output, identified inputs, a time limit, and a stopping condition. The stopping condition is particularly important. It prevents a 25-minute session from becoming a promise to complete the entire large task, while creating a specific piece of material for the next session.
| How work is often written | A usable entry point | Evidence that the first session is complete |
|---|---|---|
| Prepare a presentation | Choose one primary audience member, then write the title and three points they must remember. | There is an opening page to challenge or develop. |
| Analyse data | Open the dataset, inspect the first five rows, and record three questions about data quality. | There is a list of errors or assumptions to address. |
| Write a proposal | Describe the client problem in five sentences from the existing brief. | There is a paragraph sufficient to discuss with the responsible colleague. |
Design the first work session before leaving the work
The best time to design tomorrow’s entry point is at the end of today’s session, while the context is still present. Before closing a document, leave a short note: which file to open, where to start, which source is needed, and which question must be answered first. Where possible, place the links, reference material, or data table in one place. This is not an isolated productivity tip; it shifts some cognitive load from the morning to the time when we understand the work more clearly.
For work involving several parties, the entry point should also name the person to ask and the purpose of the question. Instead of writing “discuss with operations,” write “send three assumptions about delivery capacity to colleague A; confirm which assumption can be included in the quotation.” A specific question makes the exchange shorter and helps the work return to its main path after feedback arrives.
Example: beginning a delayed report
A manager needs to produce a campaign-review report but has postponed it for several days because data must be assembled from advertising, sales, and customer feedback. Rather than set the goal of “writing the report,” he spends the first 30-minute session creating a page with three headings: campaign objective, observed results, and data gaps. Under each heading he places links to the available source and marks the name of the person who owns the missing figure. At the end of the session, the report is still unfinished, but the work has moved from an ambiguous block to a structure that can be continued and assigned.
Do not mistake preparation for avoidance
Preparation is useful when it reduces a decision needed for the next action. It becomes avoidance when it continues without producing a new output, question, or choice. For example, rereading all reference material before drafting a single paragraph may feel diligent, but it often does not identify the argument that needs clarification. A simple rule is that after each period of preparation there should be a work trace: a draft paragraph, a question table, a provisional decision, or an information request sent.
The same applies to digital tools. A task-management application helps only when it makes the next task and its status visible. If we continuously change labels, colours, or folder systems without creating a starting step, the tool is occupying the place of the work rather than serving it.
Use a short review rhythm to adjust
At the end of each day or week, there is no need to judge yourself by busy hours. Look instead at practical questions: which work started quickly, where did work become stuck, what information was missing, and how should the next entry point change? A stopped task is not automatically a failure. It may show that the first-session output was too large, a dependency was unclear, or the decision-maker was not involved at the right time.
A plan supports action only when it connects a long-term priority with a specific work session. Rather than asking yourself for more motivation, design the first session clearly enough to begin even on a day with many interruptions. When small entry steps are repeated and adjusted, difficult work gradually becomes a sequence of manageable actions.
