The longer I work in technology and leadership, the more suspicious I become of the phrase “best practices.”

Don’t get me wrong. Standards are necessary. My suspicion comes from how the term has evolved. “Best practice” has become one of the most overused phrases in professional life. It sounds incredibly smart while doing very little actual work, and it signals credibility without requiring critical judgment.

Worst of all, it is often used to shut down thinking rather than improve it.

If you are leading a team or building a product, it is time to look past the safety of the standard playbook. Here is why reliance on best practices might be holding you back and what you should trust instead.

“Best Practices” might just be someone else’s recycled success anecdotes

When we look beneath the corporate polish, most best practices are simply recycled success stories. Something worked somewhere, once, under a specific set of conditions that likely no longer exist. Yet, we copy it. By the time a methodology or framework earns the label “best,” it has usually undergone a process of dilution or oxidation:

• It is overgeneralized: The nuance is removed to make it applicable to everyone.
• It is stripped of context: The why and where are forgotten.
• It is repeated by spectators: People who have never seen it fail tend to promote it the loudest.

What is presented as industry wisdom is frequently just survivorship bias with better branding. We see the one company that succeeded using a specific method, but we ignore the hundred others that used the same method and failed.

The fantasy of the perfect environment (and the perfect team)

Context is messy, and best practices pretend it isn’t. Most standard operating procedures assume a fantasy environment that rarely exists in the real world. They assume you have:

• Adequate staffing and budget
• Pristine, clean data
• Perfectly aligned leadership
• Modern, unencumbered systems
• Unlimited time to execute

But many organizations are operating under constraints that best practices never acknowledge.

A company might be held to aggressive profit targets that leave little room for hiring, even when best practices insist on specific staffing ratios or dedicated roles. On paper, the recommendation makes sense. In reality, the math just doesn’t work.

Or the culture itself may actively discourage deadlines. That may not be ideal, but it’s real. And many best practices quietly depend on time-boxing, enforcement, and firm delivery dates. When those conditions don’t exist, the practice doesn’t fail because the team is incompetent. It fails because the environment was never compatible with the prescription.

There is often another unspoken assumption layered on top of this: that teams themselves are infinitely malleable.

Best practices tend to assume everyone is already a subject matter expert, fully aligned, highly coachable, and ready to change how they work at a moment’s notice. They also low-key assume that if someone isn’t a good fit, you can simply replace them.

In reality, teams are made up of humans. Hiring takes time. Firing carries legal, cultural, and morale consequences. You can’t endlessly swap people in and out without cost. Most leaders are working with the team they have, not the team a framework assumes they can assemble. None of this means you should keep someone in a role when it is clearly not working. That kind of avoidance can quietly undermine an entire team. But best practices often gloss over how complex and consequential those decisions are, treating people like variables that can be easily replaced, rather than humans embedded in a culture.

If you have worked anywhere real, from a scrappy startup to a mature organization trying to pivot, you know how rare ideal conditions are.

I have seen incredibly smart teams follow best practices to the letter and still fail, because those practices were never designed for their specific reality. The problem wasn’t execution, but blind obedience to a map that didn’t match the territory.

“Best Practice” is used as an insurance policy

Let’s be honest about the psychology behind the phrase. Best practices thrive in fear-based cultures. They are often a shield against blame.

The logic of the corporate ladder is simple:

• If you follow the best practice and things go wrong, you are safe. You did what you were “supposed” to do.
• If you deviate and things go right, you might not get noticed.
• If you deviate and things go wrong, it is entirely your fault.

So people cling to best practices because they are politically convenient for the individual.

Experience kills the illusion of “right answers”

Early in your career, you spend a lot of time looking for the correct solution. You want the answer key. Later, you realize there usually isn’t one. There are only tradeoffs.

Senior leadership is rarely about finding the right way to do something, but about navigating tension between opposing forces:

• Speed vs. quality
• Control vs. autonomy
• Consistency vs. relevance

Best practices pretend these tensions don’t exist. They offer binary answers to complex problems. But experienced leaders know these tensions are unavoidable, and that pretending otherwise is how systems quietly rot.

The danger of outdated standards

Technology moves fast, while organizations move slowly. Best practices tend to fossilize somewhere in between.

Once something is labeled “best,” it becomes dangerous to question, even (or especially) when it is clearly outdated.

Teams keep performing rituals that no longer serve them, calling it “maturity” instead of what it really is, namely inertia. We continue to run processes that solved problems we no longer have, simply because no one feels empowered to say, This doesn’t make sense anymore.

What to trust instead?

If we toss out the checklists and the standard playbooks, what are we left with?

I don’t trust best practices nearly as much as I trust:

• Clear principles: Guiding stars that help us make decisions, rather than rigid rules that make decisions for us.
• Contextual understanding: People who understand why something works, not just how to implement it.
• Empowered teams: Groups that have permission to adjust the plan when reality intervenes.
• Accountability: Leaders willing to own decisions instead of hiding behind “the process.”

The best outcomes I have witnessed rarely came from strict adherence to a global standard. They came from thoughtful deviation. From a team looking at a problem and saying, The book says X, but our reality requires Y.

Best practices don’t notice when conditions change, and they don’t take responsibility for outcomes. People do.

There is only what works here, now, with these people and what you are willing to own.

What about you? What’s your take on best practices?