ARTICLE · BUSINESS · 10 MIN READ
There Is No Such Thing As “Best Practices”
It’s become cliché to hear “just follow best practices,” as if you could solve your organization’s biggest challenges with Google search

It’s become cliché to hear “just follow best practices,” as if you could solve your organization’s biggest challenges with a quick Google search and a willingness to emulate what worked elsewhere. But were “best practices” truly universal, learning across companies would be easy and competitive advantage would disappear.
You know the scene: some consultant slides in, flips open a presentation titled “Best Practices for Growth”, and suddenly everyone’s nodding like they’ve uncovered a universal truth. But what if that’s the problem? What if the notion of “best practices” is less about excellence and more about complacency?
Recent industry research paints a sobering picture. 68% of companies encounter difficulties in aligning implementations with industry best practices, while 40% of organizations report that lack of executive buy-in is a significant factor in failures. Even more striking, 50-75% of ERP implementation projects fail to meet their objectives, with 55% failing to deliver the projected benefits. These aren't minor setbacks—they represent billions of dollars wasted and countless strategic opportunities squandered.
The logic is seductive. Why waste time and resources "reinventing the wheel" when you can simply identify what the most successful companies are doing and do that? It's easy to say that processes can't just be picked up and moved. After all, every organization is unique—with different markets, histories, and cultures. But if there weren't any universals, the sharing of best practices would be a waste of time. Think of all the companies that have benefited from Toyota’s production model.
Blindly borrowing what worked for someone else often fails spectacularly and can stunt innovation, erode adaptability, and cap your team’s ambitions. It’s time to challenge the status quo and focus on next practices—custom, forward-looking solutions designed for your unique circumstances.
This logic of “Best Practices” sounds reasonable until you examine what actually happens when organizations try to transplant someone else's success formula into their own soil.
About 19% of software projects result in complete failure, with 49% facing budget overruns, and 17% of IT projects risk collapsing the company itself. The fundamental problem isn't that these organizations lacked access to best practices—most were following them religiously. The issue is that best practices, by their very nature, strip away the contextual factors that made those practices work in the first place.
Think about Toyota's legendary production system. Companies from General Motors and Ford to Batesville Casket Company and Barnes-Jewish Hospital have adapted the Toyota Production System, with healthcare organizations finding that stroke patients receive damage-mitigating treatments 20 minutes faster. Notice the word "adapted"—not "copied." The companies that succeeded understood the underlying principles and reshaped them to fit their unique circumstances. The ones that failed treated TPS as a plug-and-play solution.
The Best Practices Trap
Best practices represent the codification of what has already worked. By definition, they are backward-looking, describing solutions to yesterday's problems using yesterday's tools and context. When we implement best practices, we're essentially agreeing to be followers rather than leaders in our market.
Consider the technology sector, where companies like Amazon, Google, and Tesla didn't achieve dominance by following retail, search engine, or automotive best practices respectively. Amazon created entirely new approaches to customer service and logistics. Google reimagined how search should work. Tesla redefined the entire automotive manufacturing and sales process. These companies succeeded precisely because they ignored conventional wisdom and created new practices that competitors then scrambled to copy.
The problem with best practices goes deeper than just being outdated. They often become rigid doctrines that stifle creativity and critical thinking. When something is labeled a "best practice," questioning it becomes almost heretical. This creates organizational blind spots where teams implement processes without understanding the underlying principles or considering whether those principles apply to their unique situation.
The 'Copy-Paste' Error (Lack of Adaptation)
The first and most common pitfall is the temptation to take a process or tool from a successful company and apply it directly, without tailoring it to the new environment.
Because companies are so different, it is exceptionally rare that a practice developed in one place can be applied elsewhere without significant customization. This is the critical failure point for so many "lean" or "agile" transformations. Companies try to copy the tools of the Toyota Production System—like kanban boards or andon cords—without truly understanding the deep-rooted principles of continuous improvement (kaizen) and respect for people that make those tools work.
Success doesn't come from just learning the tool; it comes from understanding the principles behind it. This calls for hard work, far beyond making road trips or sending a few people for training.
A masterclass in adaptation comes from GE. Years ago, their senior team visited Wal-Mart to learn about its "quick market intelligence" (QMI) approach.
-
Wal-Mart's Process: Dozens of managers from headquarters went into the field during the week, spent Friday in Bentonville analyzing what they learned, and shared findings with all store managers via a company-wide video conference on Saturday.
-
GE's Adaptation: GE's leaders loved the principle—capturing and disseminating field data quickly and systematically. But they realized the Wal-Mart process of flying managers back and forth wouldn't work for their diverse, global businesses. Instead, GE developed its own QMI process. It required business leaders to conduct regular, pre-scheduled group teleconferences between headquarters staff and managers who interfaced directly with customers.
GE didn't copy Wal-Mart. They learned from them and built a solution that worked for their culture and structure. They focused on the "why," not the "what."
The 'Empty Ritual' (Lack of Adoption)
The second pitfall is even more insidious: utilizing a borrowed process without full leadership support and commitment, as though just having the tool will generate results.
A former client at GE called this "the difference between doing it and really doing it." This is when a dynamic process becomes a "form-filling exercise."
-
Example 1: Succession Planning. An HR leader admitted that her team was driving the company's new succession planning process, not line management. For most managers, it was a bureaucratic task to fill out forms, resulting in a "nice book" that sat on a shelf. It was never actually used to make key staffing decisions.
-
Example 2: The 'Work-Out' Failure. Another company tried to adopt GE's famous "Work-Out" approach, a process designed to quickly solve problems by getting the right people in a room to make a decision on the spot. It turned out the process was just a glorified brainstorming meeting. Senior managers did not put themselves on the line to make real-time decisions—a key feature of Work-Out.
In both cases, the organization had the label of the best practice, but not the substance. Without genuine adoption and commitment from leadership, the "best practice" becomes an empty ritual, a waste of time and a source of cynicism.
When Good Ideas Become Bad Advice
This brings us to a larger problem. My experience has been consistent: whenever a common aspect of business turns into a "practice area," trouble is on the horizon.
Before you know it, a herd mentality forms. Legions of consultants and advisors use this new practice area as a platform to be evangelized. When this happens, common sense and the reality of what actually works often get thrown out the window as a trade-off for promotional gain.
This dispensing of "one-size-fits-all" advice has allowed the ranks of consultants to swell. After all, if you can apply someone else’s theory in a vacuum, it lowers the barrier to entry. But labeling something as "best practices" is not a substitute for wisdom, discernment, subject matter expertise, or creativity.
Let's use a common example: automating a manual process. What constitutes the "best practice" here?
-
Purchase an off-the-shelf solution?
-
Utilize a SaaS (Software-as-a-Service) tool?
-
Develop a custom application?
-
If custom, build it internally or outsource it?
-
If outsourced, domestic or offshore?
You can find a "best practice" evangelist who will tell you any of these is the right answer. Whenever methodologies become productized and you are being pitched a product as the solution, exercise caution. Business is fluid, dynamic,and ever-evolving. Static advice is, at best, short-lived.
Forget "Best." Start Building "Next."
This is why I am attempting to extricate the phrase "best practices" from my vocabulary. I cringe when I hear it used in an authoritarian manner to justify a position.
Instead, I advocate for focusing on "Next Practices."
It is a fundamental shift in mindset.
-
Best Practices are about maintenance. They ask, "How can we do what our successful competitors are doing?"
-
Next Practices are about creation. They ask, "How can we innovate around our competitors to create a new advantage?"
Best practices maintain the status quo. Next practices shatter it.
This doesn't mean you should operate in a vacuum. A blatant disregard for existing methodologies is foolish. One of the characteristics of great companies is that they actively learn from others. But how they learn is the key.
Instead of copying, they deconstruct. They look at a competitor's "best practice" and ask:
-
What is the core principle? (Like GE looking at Wal-Mart's QMI).
-
Why does it work for them? (What specific cultural, market, or structural elements support it?)
-
What is our equivalent need? (How does that problem manifest in our organization?)
-
How can we build a better solution? (How can we solve this in a way that is unique to our strengths, leverages our culture, and creates a competitive advantage that others will try to copy?)
This is how you unlearn legacy-based thinking. Maintenance doesn't lead you forward—creation does. Don’t fall into the trap of doing something a particular way just because others do.
The Way Forward
“Best practices” have their place—but treat them with skepticism. Don’t adopt them blindly. Instead, view them as starting points. Then adapt, deploy, and lead the change
The most dangerous thing about the "best practice" myth is that it encourages you to look backward at what has already worked. It positions your organization as a follower, perpetually playing catch-up.
Just because a professor says it’s so, a consultant recommends it, or a book has been written on it, doesn’t mean it's the right option for you.
Stop benchmarking your way to mediocrity. Learn from everyone, but be a copy of no one. Find advisors who won't cram your needs into their canned sets of rules, but who will help you create the right solution for your specific needs.
Leaders who are truly smart don't just react to events; they proactively aim to secure and maintain a leading position. Instead of merely adopting current "best practices," their focus is on innovating and establishing the "next practices."
Loading the full page…