A management consultant arrives at a struggling manufacturing company. The consultant's diagnosis: the company isn't using "industry best practices."

The consultant has a playbook. Lean manufacturing. Six Sigma. KPI dashboards. Supply chain optimization. These practices have worked at Toyota, at Amazon, at Dell. They're in management textbooks. They're called "best practices."

The consultant implements them. The company pays six figures for the engagement.

Things get worse.

What happened? The consultant applied a Platonic form — a clean abstraction extracted from successful companies — without understanding what context made it work.

Best Practices Are Extracted Context

A "best practice" is a technique that worked somewhere. The technique is extracted, generalized, cleaned up, and packaged as universal. The contextual details are removed because they're messy. The universal form is what remains.

The form is clean. It's teachable. It fits into a playbook.

But the form, stripped of context, is Platonic. It's no longer describing the world. It's describing an abstraction.

Here's a specific example: a manufacturing company implements "lean manufacturing" based on Toyota's success. Lean worked at Toyota because:

Remove these contextual factors and implement only the mechanics (just-in-time delivery, minimal inventory, continuous improvement cycles), and lean manufacturing becomes fragile.

When demand becomes volatile, minimal inventory becomes a liability. When labor costs shift, the economic assumptions break. When a supplier fails, the system breaks.

The Consulting Playbook

A management consultant is selling solutions. The consultant needs to be able to apply the same solution to multiple clients. This requires abstraction. The consultant abstracts the successful practice into a repeatable playbook.

The playbook is what the consultant earns fees for. It's not customized to each client. It's not built from understanding the client's specific situation. It's the packaged form.

The consulting engagement works if the client's problem is one that the playbook solves. If the client's actual problem is different, the playbook will make things worse — but by then, the consultant has been paid and moved on.

A manufacturer's real problem might be: - A specific supplier's cash crisis that's about to cause delivery failures - A key engineer's lack of engagement that's killing innovation - An unmotivated customer relationship on the edge of termination - A quality issue in one production line that's killing margins - An unnoticed market shift

The lean manufacturing playbook doesn't address any of these. It solves an imaginary problem: "the company isn't efficient enough." In reality, efficiency isn't the constraint. The constraint is whatever unique issue is destroying value.

But the consultant can't see the unique issue. The consultant can only apply the playbook. So the consultant applies lean manufacturing. Costs go down slightly (the playbook works), but the real problem remains (the engineer quits, the customer leaves, the supplier fails).

The Physician and the Textbook

A patient presents with a cluster of symptoms that maps cleanly onto a textbook diagnosis. The physician is trained to recognize patterns. The patient's symptoms match the pattern for Condition X.

The physician confidently diagnoses Condition X. The patient is treated for Condition X. The treatment follows the standard protocol.

The patient deteriorates. A more experienced physician later identifies the real condition: a rarer disease that mimics Condition X in early presentation. The treatment for Condition X was wrong. The patient's condition worsened because the wrong model was applied.

The textbook diagnosis is Platonic. It's a clean form that describes most cases where those symptoms appear. But this case is the exception. The textbook form didn't capture the particularity of the patient.

A physician who knows the textbook well but also knows where the textbook breaks down will survive. A physician who treats the textbook as gospel will eventually kill someone by applying the wrong model with confidence.

The Template Trap

Here's what happens when best practices are applied without understanding context:

  1. You adopt the best practice
  2. You implement it correctly, following the template
  3. It solves some problems (because the template was extracted from a real success)
  4. It creates new problems (because it ignores your context)
  5. You blame yourself for not implementing it well enough
  6. You double down on the template
  7. Things get worse

The consultant or vendor can always claim you didn't implement it correctly. The failure is attributed to execution, not to the fact that the template was wrong for your situation.

How to Evaluate Best Practices

Before adopting a best practice, ask:

In what context did this work? Not the generic description. The specific situation. What was true about that company, that market, that industry?

How is my context different? What's unique about my situation? What variables are different?

What's the mechanism that makes this practice work? Is it the mechanics? Or is it the context that makes the mechanics work?

If I adopt this practice, what could go wrong? Every practice has tradeoffs. What am I optimizing for? What am I sacrificing?

What is this practice not measuring? The practice probably makes some things better (efficiency, standardization, speed). What does it make worse? What does it ignore?

Do I actually have the problem this practice solves? The manufacturer might not have an efficiency problem. It might have a demand forecasting problem. Lean manufacturing solves the wrong problem.

The Anti-Pattern

The worst pattern: adopting a best practice from a famous company without understanding why that company uses it.

Amazon uses a two-pizza team rule for organizational structure. The rule is copied by companies that have completely different scales, completely different problems, and completely different constraints.

Google implements OKRs (objectives and key results). The OKR system makes sense for Google's scale and culture. It's copied by startups and organizations that don't have Google's structure, resources, or problem space.

Toyota uses lean manufacturing. It's copied by manufacturers who don't have Toyota's supply chain relationships, labor situation, or quality culture.

Each best practice was extracted from context. Each works in that context. Copied without context, each becomes Platonic — a clean form that no longer describes the reality it's supposed to improve.

The Practical Rule

Before implementing any best practice, ask what context was stripped away when it was abstracted into a "best practice."

Then ask: do I have that context, or do I need to build it?

If you're missing key contextual factors, adapting the practice to your situation matters more than implementing it correctly. The template is less important than understanding what made it work.

Most failures in adopting best practices come from treating the practice as gospel instead of treating it as a solution to a specific context. Your context is unique. The best practice isn't.

The template works until it doesn't. Your job is to notice where the fold is.