A familiar routine can make work easier while also making its weaknesses harder to notice. You know where to begin, move through the steps confidently and finish with little hesitation. Yet familiarity does not establish that the method is still suitable, or that repeating it is developing the skill the business now needs.
The later chapters of James Clear’s Atomic Habits examine the relationship between habits, challenge and review. Their practical value for business is the reminder that consistency needs periodic examination. Keep useful routines dependable, but create occasions to inspect their results, adjust the difficulty of learning and reconsider methods that no longer fit the work.
Distinguish reliable execution from improvement
Reliable execution means performing an agreed activity consistently enough to meet its required standard. Improvement means changing capability or the process so that the work becomes more useful, accurate, efficient or suitable. Repetition can support both, but it does not prove either.
A person may repeat the same error with increasing confidence. A team may follow a checklist consistently after the checklist has become outdated. In each case, the routine is stable while the result remains weak.
Clear’s useful distinction is between familiarity with an action and continued development beyond that familiarity. Once basic steps require less attention, you can direct attention towards a more demanding part of the work. That requires a deliberate choice about what to improve.
Not every routine needs continual expansion. Some activities are valuable because they provide a dependable baseline with little unnecessary effort. Decide where additional improvement matters to the business and where maintaining a suitable standard is sufficient.
Choose a specific capability to develop
A capability is the practical ability to perform a class of work to a useful standard. It is more specific than being good at business and broader than completing one task. Examples include clarifying a customer’s requirements, preparing a workable production plan or evaluating a prototype against agreed criteria.
Choose a capability connected to a real constraint or opportunity. If unclear requirements regularly lead to rework, improving requirements conversations may be valuable. If the main problem is unavailable equipment, more conversation practice may have limited effect on delivery.
Describe the current performance using actual work. Identify what people can already do reliably, where they need support and which situations cause difficulty. This creates a more useful starting point than a general label such as experienced or inexperienced.
Keep the development target narrow enough to examine. A person learning to prepare a better brief might initially focus on distinguishing requirements from assumptions. That focus makes feedback more precise than attempting to improve every aspect of briefing at once.
Use manageable challenge as a design guide
Clear describes the appeal of tasks that are challenging while remaining within reach. A manageable challenge requires effort beyond the current comfortable routine but provides a realistic opportunity to make progress with suitable support.
Treat this as a practical guide, not a fixed numerical formula. There is no useful universal percentage by which every business task should exceed someone’s ability. Difficulty can come from unfamiliar subject matter, time pressure, unclear information or the number of interacting decisions.
Change one important source of difficulty at a time where possible. Someone learning to conduct a requirements conversation might first work on familiar projects with support. Introducing an unfamiliar product, an urgent deadline and a difficult commercial negotiation simultaneously makes it harder to understand what they are learning.
Keep the delivery context in mind. Practice should not make a live customer commitment unreliable merely to create a challenge. Use suitable internal exercises, reviewed drafts or supported work where the consequences of errors can be managed appropriately.
Explore methods before declaring a permanent fit
Clear encourages finding activities and approaches that suit a person’s abilities and interests. In a workplace, fit means a useful match between the task, the person’s current capability and the conditions in which they work. It can change as experience and circumstances change.
Observe fit through actual tasks rather than inferring it from a fixed personality label. A person who dislikes unstructured presentations may communicate well with a clear brief and preparation time. Difficulty in one setting does not establish a permanent limitation across all settings.
Try a small number of reasonable approaches and compare the results. For example, planning a complex piece of work might begin with a visual sequence, a written outline or a conversation supported by a common template. The business can require a usable final plan while allowing some variation in how it is prepared.
Give each approach a fair trial. Early awkwardness may reflect unfamiliarity, while immediate enjoyment does not guarantee useful output. Consider quality, effort, feedback and willingness to continue before deciding which method deserves further practice.
Balance experimentation with dependable delivery
Exploration means trying alternatives to learn which approach may work better. Exploitation, in this context, means using an approach that has already shown value. A business needs both, but the appropriate balance depends on uncertainty, available time and the consequences of failure.
When a deadline is close and a proven method is adequate, using it may be sensible. When repeated problems show that the current method is weak, setting aside time to test alternatives may be necessary. There is no single allocation of time that suits every business or stage of work.
Give experiments a boundary. State which part of the method may change, what must remain stable and what evidence will guide the next decision. This avoids an experiment becoming an excuse for uncontrolled variation throughout the process.
Record enough context to reuse what you learn. If a method works only with complete inputs or an experienced reviewer, that condition matters. A successful trial is more useful when the team understands the circumstances that supported it.
Create a review based on evidence
A review is a deliberate examination of work against its purpose and standard, followed by a decision about what to maintain or change. It is different from merely reporting that the work occurred.
Bring a small sample of actual outputs. A brief, drawing, handover record or decision note gives the conversation something concrete to examine. Select examples that include ordinary work and a relevant difficulty, rather than only the strongest or weakest case.
Compare intention, method and result. What was the work meant to achieve? Which steps or assumptions shaped it? What could the recipient actually do with the output? Separating these questions helps the team avoid judging a method solely by whether one outcome happened to be favourable.
End with a focused decision: retain the method, revise one step, practise a skill or investigate missing information. Assign responsibility and an appropriate next review point. A review that produces only broad encouragement is unlikely to change how the next piece of work is done.
Review often enough to learn, with room to work
The review interval should reflect the work’s frequency and consequences. A newly introduced routine may benefit from early inspection. A stable, low-consequence routine may need less frequent attention. A significant problem can justify an immediate review regardless of the usual schedule.
Avoid constant interruption in the name of feedback. People need opportunities to complete work and try an adjustment before they can learn whether it helps. Reviewing every small variation can create uncertainty about the expected method and consume the time needed to perform it.
At the other extreme, an annual conversation may arrive too late to correct a recurring misunderstanding. Choose a cadence that provides enough examples to examine while still allowing useful course correction.
Distinguish the normal review schedule from escalation. If someone notices a consequential error or an unsuitable instruction, they need a route to raise it immediately. A scheduled review should not become a reason to leave an obvious problem unresolved.
A worked example of improving design briefs
This is an illustration. A small product team prepares design briefs using an established template. The briefs are completed consistently, but reviewers often need to ask which statements are confirmed requirements and which are assumptions. The routine produces documents reliably without consistently producing the clarity the team needs.
The team chooses a focused capability: identifying and labelling uncertainty before a brief is handed over. It reviews recent work and agrees on the distinction. A confirmed requirement has an identified basis; an assumption is something being treated as true for now and may need to be tested or confirmed.
The writer practises on a suitable internal example, then applies the approach to a limited set of live drafts with review. The template remains familiar. The new challenge is to make the status of important information explicit, rather than to redesign the entire document at the same time.
Suppose the team examines eight briefs before the change and eight afterwards. In the first group, reviewers find 16 assumptions that should have been labelled, an average of 2 per brief. In the second group, they find 8, an average of 1 per brief. These illustrative counts show a reduction in identified omissions, while leaving open whether the groups were equally difficult.
The team spends 30 minutes reviewing the examples together. With three people attending, that uses 90 minutes of combined staff time. It also records any additional drafting time. This prevents the improvement from being assessed only through the visible reduction in reviewer questions.
The next decision depends on the evidence. If labelling helps reviewers act and the added effort is proportionate, the team retains the change. If assumptions are labelled indiscriminately and the document becomes harder to use, it refines the definition and practises again. The aim is better information, not a larger number of labels.
Use feedback to direct practice
Deliberate practice is focused work on a specific aspect of performance, using feedback and adjustment to develop it. It differs from repeating the whole job and hoping that experience alone will address its weakest part.
Choose a task that exposes the skill you want to develop. If someone struggles to separate requirements from assumptions, a short exercise with mixed statements may be more useful than asking them to write several full briefs. The exercise makes the relevant decision easier to inspect.
Feedback should describe the work and the next adjustment. Explain which statement lacks a basis, why that matters to the recipient and what would clarify it. General judgements about intelligence, confidence or attitude provide little guidance about the next attempt.
For a fuller method of structuring skill development, Good at, need to practise: deliberate practice for business skills explores how to identify a practice target and use feedback. Keep the practice tied to the required business standard so it transfers into useful work.
Respond carefully when familiar work feels dull
Repetition can lose its initial interest. That does not automatically mean the routine has stopped being useful. Some necessary work remains repetitive because the same requirement continues to exist.
Before replacing a routine, examine whether the problem is boredom, avoidable effort, unclear value or a changed business need. Each calls for a different response. A new tool may briefly restore novelty while leaving the underlying burden unchanged.
Where learning is appropriate, add a focused challenge without disrupting the dependable core. A person who can prepare an adequate brief might practise making its assumptions clearer or its decisions easier to trace. The change should serve quality or capability, rather than create difficulty for its own sake.
Also recognise capacity and recovery needs. Persistent difficulty sustaining work may reflect an unrealistic load or other circumstances requiring attention. A message about professional consistency should not be used to dismiss those conditions or demand work regardless of their consequences.
Keep professional identity open to revision
A professional identity is a person’s understanding of the kind of worker, leader or practitioner they are. It can support consistent action, but it can also make a familiar method feel inseparable from personal competence.
If being experienced means never needing to reconsider an approach, feedback becomes threatening. A more workable identity connects to a purpose or standard: producing clear work, learning from evidence or helping the team make sound decisions. Those commitments can survive a change of method.
Make review conversations specific enough that people can examine the work without defending their entire history. An outdated template does not erase the value of earlier work. A missed detail identifies something to correct, rather than proving that the person lacks ability.
Leaders can support this by explaining changes in their own methods. Show which evidence prompted the adjustment and what will be tested next. This makes revision an ordinary part of competent work rather than a concession reserved for people with less experience.
Recognise when a routine should end
Some reviews should result in stopping an activity. A report may no longer inform a decision, a meeting may duplicate another process or a checklist may address a product the business no longer handles. Consistency is not a reason to preserve an obsolete obligation.
Before retiring a routine, identify who uses its output and whether another process depends on it. A step that appears unnecessary to its owner may provide information elsewhere. Consult those affected and arrange any replacement that remains necessary.
Document the decision briefly so the routine is not recreated later through uncertainty. Explain what changed, which need remains and how that need is now met. This is particularly useful when people join the business after the original discussion.
Review therefore has several legitimate outcomes: maintain, improve, simplify, replace or stop. The best outcome is the one supported by the work’s current purpose and evidence, rather than the one that demonstrates the most activity.
Questions to ask
- Which routine still meets its purpose, and which is merely familiar?
- What specific capability would make a useful difference now?
- Is the next challenge manageable with the support and time available?
- Which actual outputs will we inspect to assess progress?
- What evidence would justify changing a method we are proud of?
- Should the routine be maintained, improved, simplified, replaced or stopped?
Bringing it together
Established habits provide a useful foundation when they support work that still matters. Review that foundation periodically, using actual outputs and a clear standard. Then choose a focused challenge where further development has a worthwhile purpose.
Keep learning practical and proportionate. Experiment within sensible boundaries, use feedback to guide practice and remain willing to revise a familiar method. Dependability and adaptability can support each other when the business makes room for both execution and thoughtful review.
Source: James Clear, Atomic Habits (2018), primarily chapters 18–20. Business methods and examples are practical adaptations. Figures in this article are illustrations, not data. This article is general business information.
