Best practices become expensive distractions when teams copy them without understanding their purpose or keep them after circumstances change. This guide explains the most common failure patterns, how to recognise them in everyday work and how to repair the process without adding unnecessary bureaucracy.
What Goes Wrong With Best Practice Mistakes?
The biggest mistake is treating a best practice as a universal rule rather than a context-dependent approach. Other common problems include adopting too many changes, measuring compliance instead of outcomes and leaving exceptions or ownership unclear. Fix these by connecting each practice to a specific risk or result, testing its fit and reviewing evidence from actual use.
Mistake 1: Copying a respected organisation's process wholesale
Why it hurts: A process reflects the environment in which it developed. A large software company's approval chain may depend on specialist reviewers, reliable automation and a volume of work your team does not have. Copying the visible steps without those conditions can create queues while preserving none of the original benefit.
Prestige is not evidence that an approach fits your task. Nor does a practice become appropriate simply because a competitor says it uses it. The useful question is what failure the practice prevents and whether that failure matters in your setting.
How to fix it: Separate the principle from its implementation. If the principle is independent review of consequential changes, a small team may need a named peer reviewer and a clear escalation path rather than several approval committees. Check applicable requirements before simplifying any control.
Write a fit statement: “We will use this method for these cases because it addresses this risk, provided these conditions hold.” Include what is outside scope. ISO describes quality-management principles that include a process approach and evidence-based decision-making; neither requires blindly reproducing another organisation's workflow. 1
Mistake 2: Adding steps without removing the underlying obstacle
Why it hurts: A checklist cannot compensate for missing information, broken permissions or contradictory incentives. Extra sign-offs can make a process appear controlled while the original problem continues underneath.
Imagine a delivery team repeatedly receiving incomplete handovers from sales. Management introduces a mandatory handover meeting, but nobody agrees which information must be ready or where it should be stored. Meetings happen, yet delivery still cannot start. The organisation has improved attendance at a ritual, not the handover itself.
How to fix it: Trace a real case from start to finish. Identify the point where necessary information, authority or capability was missing. Ask the people on both sides of the handover what they needed and what prevented them from supplying it.
Then change the smallest meaningful part of the workflow. In this example, define required inputs, provide one accessible record and agree who resolves missing items. Use a meeting only for cases that genuinely need discussion. Retain any required approvals, but make their purpose and evidence explicit.
Before adding a new step, state what decision it enables. If nobody can explain the decision, consider whether the step is duplication rather than protection.
Mistake 3: Measuring obedience instead of usefulness
Why it hurts: Completion rates show whether people followed a process; they do not establish whether the process improved the result. A team can complete every field while customers still receive incorrect work.
Measures also influence behaviour. If speed is the only visible target, people may rush checks or defer complicated cases. If document completeness is the only target, they may spend time polishing records without resolving the issue those records describe.
How to fix it: Pair a process measure with an outcome and a safeguard. For a review checklist, track whether reviews occurred, whether relevant errors escaped and whether turnaround became unreasonable. Interpret these signals together rather than choosing the most flattering one.
| Misleading signal on its own | What it leaves out | Better companion evidence |
|---|---|---|
| Every checklist is complete | Whether checks were meaningful | Sample review of actual decisions |
| Work finishes faster | Whether errors increased | Rework and exception patterns |
| Training attendance is high | Whether people can do the task | An observed practical exercise |
| Exceptions are rare | Whether people hide deviations | Confidential feedback and case review |
Use comparable cases and note changes in staffing or work complexity. Small samples can reveal a problem, but they rarely justify confident claims about the size of an improvement. Report uncertainty honestly.
Mistake 4: Leaving ownership and exceptions ambiguous
Why it hurts: When everyone owns a practice, nobody may maintain it. Users then improvise when a normal path fails, and managers discover conflicting interpretations only after an incident.
An exception is especially risky when approval authority is unclear. One colleague may think a deadline justifies skipping a review; another may assume that only a department head can allow any variation. Both are guessing about authority rather than following an agreed process.
How to fix it: Name the person accountable for the practice, the people who perform it and the roles that approve relevant exceptions. Atlassian's roles-and-responsibilities exercise is designed to clarify expectations and identify gaps between team members' understandings. 2
Define an exception route with a reason, approver, alternative safeguards and expiry or review point. Make clear that some requirements cannot be waived through a local exception. Escalate uncertainty to the appropriate authority rather than allowing an urgent request to silently override an obligation.
Review recurring exceptions as information. If the same legitimate case needs approval every week, the normal process may have the wrong scope. If exceptions conceal avoidable shortcuts, the remedy may be training, capacity or stronger control rather than a broader exemption.
Mistake 5: Writing documentation nobody can use
Why it hurts: Long documents often hide the decision a person needs to make. Multiple copies create uncertainty about which instructions apply, and unexplained terminology excludes new colleagues.
A document may be technically complete yet operationally weak. “Ensure appropriate validation” sounds responsible but does not identify what to check, against which record or what to do when the values differ.
How to fix it: Put one authoritative version where work starts. State the purpose, scope, prerequisites, steps and completion criteria. Link background material instead of forcing users to read a history of the process before taking the first action.
Replace vague instructions with observable actions. For example: “Compare the billing address with the approved customer record. If they differ, pause dispatch and ask the account owner to confirm the current address.” Include an example of both an ordinary case and an escalation.
Ask someone unfamiliar with the document to use it on a safe, representative task. Watch for assumptions, missing access and ambiguous terms. Do not treat their questions as a training failure; they are evidence about the document.
Keep sensitive details out of examples. Good documentation helps people do the job without unnecessarily exposing customer, employee or security information.
Mistake 6: Freezing the practice or changing everything at once
Why it hurts: A once-useful approach can become obsolete as tools, workloads and responsibilities change. The opposite reaction, replacing several workflows simultaneously, can obscure which change helped and leave users unsure what still applies.
Both patterns avoid disciplined learning. A frozen process assumes the original decision remains correct forever; uncontrolled change assumes any new approach is an improvement.
How to fix it: Give the practice review triggers as well as a calendar review. Useful triggers include a serious incident, a tool migration, repeated exceptions, a new obligation or a significant shift in work volume. At review, choose explicitly to retain, revise, retire or retest the practice.
For revisions, use a bounded trial and record the version being tested. Keep a rollback route where feasible. Explain what changes, why it changes and how existing work should transition. Do not delete old instructions before people can identify the current version.
Keep a short decision log so future owners can understand the reasons behind the design. Record evidence and constraints, not just who attended the meeting. That makes later simplification more informed and less dependent on institutional memory.
Questions About Best Practice Mistakes
Is resistance always a sign that staff dislike change?
No. Resistance may expose duplication, missing tools, unrealistic timing or a conflict with another requirement. Ask for a concrete case and investigate it. People may still need support or accountability, but dismissing feedback prevents useful diagnosis.
Can a team have too many best practices?
Yes. Even individually reasonable steps can create excessive combined overhead. Review the whole workflow, including repeated data entry and overlapping approvals, rather than evaluating each practice in isolation.
Should every mistake lead to a new checklist item?
No. First identify the cause and whether a checklist would address it. Some problems require clearer ownership, better system design or specialist judgement. An ever-growing checklist can bury the checks that matter most.
When should we retire a practice completely?
Consider retirement when the problem no longer exists, a better control replaces it or evidence shows that its cost exceeds its benefit. Confirm that no mandatory requirement depends on it, communicate the decision and update linked instructions.
How to Avoid Best Practice Mistakes
A best practice is useful only when it improves the work in its actual context. Repair the relationship between purpose, evidence, ownership and daily action before adding another layer of procedure.
Next steps: Revisit what best practices mean, use the adoption checklist and browse the best-practices hub.
Sources
- ISO — Quality management principles: The foundation for success
- Atlassian — Roles and Responsibilities
This guide is general education, not professional advice.
