Making important work easier to start

Some important work is difficult before it even begins. You need to find the current file, decide which part to tackle, clear a bench or ask where the information is stored. Each obstacle may look minor in isolation. Together, they make postponement an attractive option, especially when easier tasks are waiting nearby.

James Clear’s Atomic Habits suggests making useful actions easier to repeat and reducing a new habit to a manageable starting point. For a small business, the practical opportunity is to separate the difficulty of doing good work from the unnecessary difficulty of beginning it. A simpler start can support demanding work, provided the business keeps a clear standard for completion.

Separate preparation from progress

Clear distinguishes between preparing to act and taking action that directly advances a result. In a business, preparation includes researching tools, discussing possible approaches and arranging information. Direct progress might mean testing a prototype, drafting a proposal or resolving a customer’s unanswered question.

Preparation has a legitimate place. An unfamiliar task may need careful investigation before anyone proceeds. The problem arises when repeated preparation produces no clearer decision, usable output or testable assumption. A team can become very organised around work it rarely performs.

Define the next observable change in the work itself. For a proposal, that might be a completed scope paragraph. For a process improvement, it might be a trial of the revised handover on one suitable job. The action should leave evidence that something moved forward, even if the result remains incomplete.

This distinction also helps you stop preparing. Before another planning session, identify the uncertainty it must resolve and the action that will follow. If the same uncertainty has already been discussed several times, a bounded practical test may now be more informative than another conversation.

Identify the friction around the task

Friction is the effort, delay or uncertainty involved in performing an action. Some friction is necessary: checking a measurement takes time because the measurement matters. Other friction contributes little, such as searching several folders for a template that should have an agreed location.

Observe a real attempt from the moment someone intends to begin. Record where they pause, switch systems, ask for clarification or repeat information. Avoid assuming that the most visible delay is the largest obstacle. A missing decision about the task’s purpose can cause more disruption than several extra clicks.

Consider physical, informational and decision friction separately. Physical friction includes an unavailable tool or unsuitable workspace. Informational friction includes incomplete instructions or conflicting records. Decision friction appears when someone must repeatedly choose an approach that could reasonably have been settled beforehand.

Ask the person doing the work which obstacles are avoidable. A manager may see a short form, while the employee sees several unanswered questions hidden inside its fields. Improving the visible form without resolving those questions can make the process look simpler while leaving the real work unchanged.

Find the moment when the work changes direction

Some small choices influence what happens next. After a customer call, opening the job record may lead naturally into writing an accurate note. Opening the inbox may lead into unrelated messages, after which the call details are harder to reconstruct.

A starting point is the specific action that brings the intended work into reach. It needs to be concrete enough to observe. A general intention to be more organised does not identify one. Opening the active job record before leaving the call workspace does.

Choose a starting point within the person’s control. If beginning depends on another department sending complete information, the first action may be checking whether the required inputs are present. The routine then needs a clear response when they are missing, rather than an expectation to proceed anyway.

For help locating an appropriate trigger, Designing clear cues for better work habits examines the events and environments that can prompt an action. A cue makes the work noticeable; reducing friction makes the next step practical once it is noticed.

Use a small first action honestly

Clear’s two-minute rule proposes beginning a new habit with a version that takes roughly two minutes or less. The useful principle is to make the entry action modest enough to repeat. Two minutes is a practical design constraint, rather than a universal threshold established for every person or task.

For a business writing task, the starting action might be opening the current brief and drafting its first useful sentence. For a review, it might be selecting one completed item and identifying the standard against which it will be checked. These actions bring you into contact with the actual work.

Choose an entry action that can lead somewhere. Opening a blank document and immediately closing it may establish a ritual, but it provides little business value if the next step remains undefined. Include enough information in the starting arrangement to make continuing possible when the scheduled work period allows it.

Be honest about the larger commitment. A manager should not describe a substantial assignment as a tiny task to obtain agreement. Explain that the small action is a way to begin a larger piece of work, and provide enough time and resources for that larger piece to be completed.

Keep the completion standard separate

A completion standard states what must be true before work can be treated as finished. It might require a checked drawing, an agreed scope or an accurate customer record. Making the first action easier does not alter that standard.

This separation is essential where partial work could mislead another person. A draft quote must remain clearly identified as a draft. Starting a check does not mean the item has passed. Opening a job record does not mean the required information has been captured.

Use different signals for started, in progress and complete if the distinction affects a handover. Otherwise, a team may celebrate reliable starts while the amount of unfinished work increases. The routine then improves one measure while making delivery less predictable.

Some activities must be performed as a complete sequence once begun. Do not divide a safety procedure or critical operating process simply to fit a habit technique. Make the preparation easier, ensure sufficient time is available and follow the applicable procedure in full.

Prepare the next use of the workspace

Clear describes arranging an environment so the next useful action requires less effort. A business can apply this by leaving a shared workspace ready for its next intended use. The preparation should serve a defined task rather than an abstract preference for tidiness.

At a desk, readiness may mean saving the current file in its agreed location and leaving a brief next-action note. At a workbench, it may mean returning equipment to its designated storage and recording anything unavailable. In a shared system, it may mean making the current status and responsible person clear.

Build this reset into the work that creates the disorder. If every person postpones the reset, the next person inherits the delay. The cost becomes harder to see because it appears at the beginning of a different job, possibly in another person’s time.

Keep the reset proportionate. Elaborate arrangements can become another form of preparation that takes longer than the problem it solves. Start with the few items that repeatedly prevent work from beginning, and review whether the arrangement actually reduces searching, waiting or rework.

Remove waste while retaining useful checks

An easier process is not automatically a better process. A confirmation step may protect against a costly misunderstanding. A second review may be necessary because a decision affects someone beyond the person making it. Removing those steps requires more reasoning than observing that they take time.

Classify an obstacle by its purpose before changing it. Does it prevent an error, provide required information, protect access or simply reflect an old arrangement? If its purpose remains valid, improve how it works rather than assuming it should disappear.

Test changes with the people who receive the output. A shortcut for the sender can create extra interpretation for the receiver. The relevant question is whether the whole piece of work becomes more dependable, not whether one person’s part becomes faster.

A worked example of starting a weekly review

This is an illustration. A small product business wants to review recent customer questions each week. The founder has repeatedly postponed the task because the questions sit across several records, the review has no defined starting point and the expected output is vague.

The business defines the purpose: identify one recurring uncertainty that should be addressed in the product information. It sets aside a review period and makes the first action opening the agreed question log and selecting the most recent unresolved entry. The first action is deliberately small, while the full review still has scheduled time.

The founder also changes the preceding work. When a relevant customer conversation finishes, its question is recorded in the shared log. This moves information capture closer to the event and reduces later reconstruction. The team checks that the log contains enough context to interpret the question accurately.

For this hypothetical example, the old review took 15 minutes to gather material and 25 minutes to analyse it, giving a total of 40 minutes. Preparing the log reduces gathering to 5 minutes. Analysis still takes 25 minutes, so the revised review takes 30 minutes: a saving of 10 minutes per review.

Over four reviews, that is 40 minutes less gathering time. It is not yet the net saving, because capturing questions also takes time. If maintaining the log adds 6 minutes each week, the four-week maintenance cost is 24 minutes. The net time reduction is therefore 16 minutes over the four reviews.

The business also evaluates usefulness. Did the reviews lead to clearer product information, and can the team identify which questions informed the changes? If the log is maintained but no decision follows, the routine has become a well-organised collection exercise rather than a useful review.

Build repetition around real opportunities

Clear emphasises repeated action rather than waiting for a set number of days to pass. Applied at work, this means identifying how often the relevant situation actually occurs. A monthly review has a different rhythm from a note written after every customer conversation.

Do not promise that a behaviour will become automatic after a universal number of days. The task, context, frequency and individual all matter. Even a familiar routine may need renewed attention when the system, workload or people involved change.

Count genuine opportunities and what happened at each one. If a task occurs only when a suitable job arrives, days without such a job are not missed attempts. This distinction helps you see whether the routine fails when needed or simply has fewer occasions to occur than expected.

Use an early review to identify persistent barriers. Repeatedly failing at the same starting step may indicate that the step is still too ambiguous, the cue is unreliable or the scheduled time is unavailable. More insistence on repetition will not resolve an input that never arrives.

Increase the work without making the start harder

Once a starting routine is dependable, you can increase the amount or complexity of the work that follows. Retain the familiar entry action while adding a manageable next stage. This preserves a clear beginning without treating the smallest version as the permanent business objective.

For example, a founder might move from identifying one unclear assumption in a brief to drafting the clarification and then completing a focused review of the brief. Progression should reflect the task’s needs and available capacity, rather than an arbitrary requirement to do more every week.

Assess both consistency and quality before expanding. A routine that happens frequently but produces inaccurate records needs correction, not additional volume. A routine that works well in quiet periods may need a different arrangement when interruptions are common.

If expansion causes the routine to collapse, inspect the added demand. Perhaps the next stage requires information, training or protected time that the original stage did not. Return to a workable arrangement while addressing that constraint, rather than interpreting the difficulty as a failure of character.

Common mistakes when simplifying work

One mistake is choosing an easy activity because it is easy, even though it barely contributes to the intended result. Rearranging a task list can feel productive while the customer response remains unwritten. The first action should connect directly to work that matters.

Another is shifting effort out of sight. A simpler form may create additional clarification calls. A faster handover may omit context that the receiving person must reconstruct. Check the total workflow before declaring that the change has saved time.

A third mistake is treating the small start as a substitute for capacity. A two-minute beginning cannot make a full day’s work fit into an already full schedule. If the required output has no realistic place in the week, priorities or commitments need to change.

Finally, avoid turning a personal experiment into a universal rule. People may need different arrangements because their roles, access requirements and working conditions differ. Agree on the required outcome and essential controls, then allow reasonable variation in how people prepare to deliver it.

Questions to ask

• What useful change in the work should the next action produce?
• Which obstacles add protection or quality, and which merely add effort?
• What small starting action brings the real task within reach?
• Is there enough time to complete the work after it begins?
• Who pays the preparation and maintenance cost of the simpler process?
• What evidence will show that starting more reliably improves delivery?

Bringing it together

Making important work easier to start is a practical design problem. Clarify the next action, remove avoidable obstacles and prepare the environment for its intended use. Keep the finished result’s standard visible throughout the change.

A small beginning is useful when it leads into worthwhile work. Repeat it at genuine opportunities, inspect the result and expand only when the necessary time, information and capability are available. The aim is dependable progress, supported by a starting routine that people can realistically use.

---

Source: James Clear, Atomic Habits (2018), primarily chapters 11–13. Business methods and examples are practical adaptations. Figures in this article are illustrations, not data. This article is general business information.