It is summer, which means educators everywhere are doing one of the most dangerous and hopeful things we do: We are looking around.
We are visiting other schools. Reading books. Attending PD. Studying systems.
All of these things are good. Necessary, even.
We should learn from other people’s brilliance. We should notice what works. We should be humble enough to admit that someone else may have already solved a problem we are still wrestling with.
But this is also where we get ourselves into trouble. When we see something working in another school, system, or organization, we are rarely just asking, “What can I learn from this?”
We are usually asking something closer to, “Can we take this thing, bring it back home, and make it work here too?”
Most organizations say they want to scale. They do not.
They want to replicate.
They want to find the thing that worked in one place, copy it, paste it somewhere else, and get the same result without having to re-learn all the messy local conditions that made it work the first time.
And that is where things get weird.
Application
Application means:
“I learned something. Now I’m trying to use it in my own context.”
This is the most basic transfer move, one that requires judgment. The learning approach here is mostly about understanding the principle rather than memorizing the move.
What is the core idea?
What problem was it designed to solve?
What parts matter most?
What will I need to adapt?
Example:
A principal learns a strategy for improving hallway transitions. She goes back to her building and tries to apply the same core idea, but she adjusts it to her building layout, student age, staff culture, and current discipline patterns.
Replication
Replication means:
“I want to recreate this as closely as possible because the conditions are similar enough that fidelity matters.”
The learning approach here is about fidelity, sequence, and clarity. Replication requires discipline.
What are the non-negotiables?
What steps must happen in order?
What language/tools/templates support consistency?
What should not be changed yet?
What evidence tells us we are doing it as intended?
Example:
A school has a strong lesson internalization protocol that consistently helps teachers understand the standard, task, exemplar, and misconceptions before teaching. Another team wants to use that same protocol.
Scaling
Scaling means:
“We want this to work across many different contexts without losing the essence of what made it powerful.”
Scaling designs for variation. Scaling does not mean every school uses the exact same tracker, calendar, script, and meeting structure. Scaling means the district identifies the underlying conditions that made the practice work.
Example:
A district sees that one school has built a strong culture of weekly teacher feedback. The district identifies the underlying conditions that made the practice work.
leaders protect time for feedback,
teachers know the focus,
feedback is narrow and actionable,
follow-up actually happens,
leaders have a system for seeing patterns.
Then each school builds a version that fits its size, schedule, leadership capacity, and current culture.
The learning approach here is about principles, adaptation, capacity-building, and feedback loops.
Application: How does this idea help me solve the problem in front of me?
Replication: What exactly made this work, and how do we preserve it?
Scaling: What must remain true for this to work in different contexts?
Why We Suck at Distinguishing These
Scaling sounds sexy. Replication feels controllable.
When something works, leaders naturally want to bottle it so we say, “Let’s scale this.”
But what we often mean is: “Can everyone please do the exact thing that worked over there so I can stop worrying?”
We blame people for “not implementing with fidelity” when we never actually figured out whether the thing needed fidelity or adaptation. We blame schools for “resisting change” when we handed them a solution built for someone else’s problem.
The Learning Difference
This is where the approach to adult learning has to change.
If the goal is application…
Teach the concept, then give people practice applying it to their own reality.
They need examples, non-examples, reflection, and coaching.
The core learning question is: Can you use this idea well in your context?
If the goal is replication…
Teach the model clearly and protect the non-negotiables.
People need modeling, rehearsal, checklists, exemplars, calibration, and feedback on fidelity.
The core learning question is: Can you do this as designed?
If the goal is scaling…
Teach the principles and build adaptive expertise.
People need to understand the why, diagnose their context, make smart adjustments, test, learn, and share evidence across sites.
The core learning question is: Can you preserve the essence while adapting the form?
You cannot scale meaningful work by eliminating judgment.
You scale meaningful work by developing judgment.
The Punchline
Application is: Use the idea.
Replication is: Preserve the model.
Scaling is: Protect the essence while adapting the form.
Most failed initiatives give people a thing to replicate, call it scaling, offer training designed for application, and then wonder why implementation is inconsistent.