Best Practices Can Make You Worse
Copying what the best companies do feels safe and smart. Imported without their context, a best practice is just someone else's answer to a question you never asked.
I lead the growth and organizational side of our agency, and I spend a lot of time being asked for "best practices." Companies want the playbook the winners use, on the reasonable theory that copying excellence produces excellence. So it may sound strange coming from someone who advises companies for a living: best practices, adopted carelessly, can make you worse. A practice that is genuinely best for one company in one context can be actively harmful in another.
A best practice is an answer. The problem is that companies import the answer without ever asking what question it solved — and an answer to the wrong question is just confident misdirection.
Why the conventional wisdom is wrong
The conventional wisdom treats best practices as universally good — distilled wisdom from the best, safe to copy. But a practice is "best" only relative to a specific context: a particular size, market, stage, culture, and set of constraints. Lift it out of that context and the thing that made it work is gone, leaving a ritual that no longer fits the situation it has been dropped into. You copied the visible practice and left behind the invisible conditions that made it wise.
The practice that fits a 10,000-person company can crush a 20-person one under process it cannot afford.
What works in a mature, stable market can be fatal in a young, fast-moving one that rewards the opposite behavior.
A practice tuned to one culture or business model produces friction, not performance, when forced onto a different one.
Copying the answer skips the thinking, so the team never builds the understanding that would let them adapt when conditions change.
What is actually true
What is actually true is that there are very few universal best practices — there are only practices that are best for a particular context, and the skill is matching the practice to the situation, not collecting practices. The companies people copy did not succeed by importing other people's playbooks. They succeeded by understanding their own situation deeply and designing practices that fit it. Copying their practices without their understanding means copying the output of their thinking while skipping the thinking — which is exactly the part that mattered.
This is why cargo-culting the habits of admired companies so often disappoints. The startup that adopts a giant's planning process, the small team that imports an enterprise's org chart, the local business that copies a national brand's playbook — each takes on a practice built for a context it does not share, and wonders why the magic did not transfer. The magic was never in the practice. It was in the fit.
How to borrow without breaking yourself
Best practices are worth learning from — you just have to extract the reasoning, not just the ritual.
Ask what problem the practice was actually solving before you adopt it; if you do not have that problem, you do not need the practice.
Check whether the conditions that made it work — scale, market, culture, resources — are conditions you genuinely share.
Adapt it to your context deliberately rather than installing it as-is, and expect the adapted version to look different from the original.
Treat every "best practice" as a hypothesis to test in your situation, not a law to obey because someone successful does it.
What we see at TTGC
Clients often come to us asking us to implement what some admired competitor or category leader is doing, and part of our job is to ask whether that practice fits them before we install it. Frequently it does not. We have watched companies adopt the marketing cadence, hiring approach, or operating ritual of a business three sizes larger and three stages ahead, then quietly suffer under process built for problems they do not yet have. So we work the other way: understand the client's actual situation first, then design or adapt practices to fit it — sometimes the opposite of what the "best practice" prescribes. We built our own agency the same way, by figuring out what worked for us rather than copying what worked for someone else. The practices that made us were never best practices. They were our practices.
The honest take
Learn from the best, but do not blindly copy them. A best practice is an answer shaped by a context, and importing it without that context can quietly make you worse — heavier, slower, or aimed at a problem you do not have. Before you adopt what a winner does, understand why it worked for them, check whether their conditions are yours, and adapt it deliberately to your own situation. The goal is not to do what the best companies do. It is to think the way they think — and then do what is best for you.
Sources
Harvard Business Review — research on the limits of transferring best practices across different organizational contexts. hbr.org
TTGC — patterns from building our own agency and advising clients across stages and sizes.
