Every industry has organizations that become shorthand for excellence. Leaders study their rituals, tools, team structures, deployment practices, design systems, meeting norms, and cultural language. The hope is understandable: if the practice worked there, perhaps it can work here.
But practices do not travel alone. They are carried by context: strategy, constraints, talent, trust, incentives, architecture, operating history, and leadership behavior. Copy the visible practice without the conditions that made it effective, and the organization may inherit the costume without the capability.
The practice transfer problem is the belief that high performance can be imported through imitation. Real transformation requires something harder: understanding why a practice works, what local problem it solves, and what must change for the organization to make it true.
Imitation Is a Human Default
Organizations copy because people copy. Benchmarking, case studies, conference talks, and executive visits all activate a basic instinct: if successful groups behave this way, we should behave this way too.
James Clear writes in Atomic Habits: “We imitate the habits of three groups in particular:” [[Atomic Habits]] The surrounding point is about social learning, but the organizational version is everywhere. Companies imitate the visible habits of admired peers, powerful competitors, and culturally prestigious firms.
Imitation is not foolish. It is one way humans learn. The risk begins when imitation outruns diagnosis. A copied practice should be treated as a hypothesis, not a prescription.
Direct Practice Beats Passive Borrowing
Capability does not transfer because a team has adopted another organization’s vocabulary. It transfers when people practice the underlying skill in the conditions where they need to use it.
Scott Young’s Ultralearning makes the distinction plainly: “if you can spend a good portion of your learning time just doing the thing you want to get better at, the problem of directness will likely go away” [[ULTRALEARNING]] Transformation fails when organizations acquire knowledge about practices without practicing the behaviors that make those practices work.
Reading about empowered teams is not the same as making real decisions closer to the work. Installing a continuous delivery tool is not the same as learning to release safely. Adopting a design sprint is not the same as developing product judgment. Practice transfer requires local reps.
Do Not Remove the Fence Before You Know Why It Exists
Many copied practices are introduced as replacements for existing process. The old way looks slow, heavy, or outdated. The new way looks modern. But some inherited practices exist because of constraints the organization has forgotten to name.
A daily note summarizes Chesterton’s warning: “Chesterton’s Fence warns against eliminating an old policy or process that seems pointless, before first learning why it exists.” [[daily note/Notes Bodies1/0091]] That does not mean old practices should be protected forever. It means removal should follow understanding.
Before importing a practice, leaders should ask what the current practice is compensating for. Is it hiding a trust problem? A regulatory constraint? A skills gap? A brittle system? A past failure no one wants to repeat? If the new practice ignores the old reason, it may remove the guardrail while leaving the hazard intact.
Preserve the Core, Change the Practice
The best organizations are not static. They adapt constantly. But they also know what should not be casually copied, diluted, or traded away. Their practices evolve around a core they understand.
Jim Collins writes in Good to Great: “Enduring great companies preserve their core values and purpose while their business strategies and operating practices endlessly adapt to a changing world.” [[Good to Great]] This is why imitation is tricky. An outside observer can see operating practices more easily than core purpose.
Transformation leaders need the same distinction internally. Which parts of the organization should adapt? Which principles should remain stable? Which copied practice reinforces the core, and which one quietly replaces it with someone else’s logic?
Mimicry Misses the Culture Beneath the Practice
The most dangerous copying happens when leaders imitate the surface behaviors of a high-performing system without understanding the beliefs, constraints, and discipline underneath them. The practice looks simple because the hard work has already been absorbed into culture.
In The Phoenix Project, Gene Kim, Kevin Behr, and George Spafford describe this failure mode in the Lean world: “merely teaching people how to mimic the behaviors observed at the Toyota plants, but missing the most important parts of the Toyota culture and values that framed their management practices” [[The Phoenix Project]] The same thing happens with agile, DevOps, design thinking, OKRs, product operating models, and every other management fashion.
Mimicry asks, “What do they do?” Transformation asks, “What conditions make that behavior effective?” That second question is slower. It is also the only one that transfers capability.
So, What Are You Actually Trying to Learn?
The practice transfer problem asks leaders to be more honest about admiration. Which organization are you copying? What do you believe their practice will solve? What local constraint might prevent it from working here? What capability must be built before the practice can produce the same result?
The goal is not originality for its own sake. Good ideas should travel. But they should travel as principles, patterns, and hypotheses, not as cargo-cult rituals.
Transformation succeeds when borrowed practices become locally understood. The organization studies the example, extracts the principle, tests it against its own constraints, practices the underlying behavior, and adapts the form until it becomes real. That is how learning transfers. The artifact is copied last.
