On why scale often kills the actual learning
There’s a question that haunts my conversations with district superintendents and state leaders.
What are we talking about?
I don’t mean what are you doing. Teams are rarely vague there. They know their timelines. Their goals. Their milestones. The issue isn’t the plan. It’s the language. Specifically, the gap between where the work feels like it is and where it actually sits.
One of the costliest errors in educational redesign? Not picking the wrong strategy.
It’s calling the work something it isn’t.
When we slap the label implementation on something that hasn’t earned it yet, the consequences cascade. We dispatch coaches to support rollouts instead of helping teachers figure things out. We measure adoption rates. We chase fidelity. We scale the initiative before we’ve scaled the understanding.
Why? Pressure. Boards want quarterly updates. Grant deadlines don’t care about nuance. Communities demand visible change. It is agonizingly difficult to stand in front of stakeholders and say, “We’re still learning,” when the clock is ticking for results. But the name dictates the next move. And names carry weight.
The Trap of “Implementation”
Consider a Portrait of a Graduate.
It hangs in every hallway. It opens every staff meeting slide deck. But does it shape daily assessments? Hiring decisions? Budget lines?
If the answer is no, that isn’t implementation.
It is Research and Development (R&D).
That’s not a failing. It’s a fact. Calling it implementation lies to yourself. It shifts your attention from inquiry to consistency.
Think about it.
- Implementation asks: Is everyone doing it right?
- R&D asks: Is this even working, and for whom?
They require entirely different postures. One is narrow. The other must be wide open. Mislabeling the former as the latter narrows the lens exactly when you need it to be curious. You stop looking for insights. You start looking for compliance.
Same with “real-world learning” initiatives that generate hype. Great stories. Cool partnerships. But can the team articulate what the student learned? How do we know? Which conditions mattered?
If not, it’s not implemented. It’s in design.
This is where promises fracture. A pilot succeeds in one school. Leadership gets excited. They expand it.
Sometimes this works.
Often, it breaks. Why? Because the initial success relied on invisible scaffolding. In the early days of personalized learning, the best models emerged in tiny systems. Leaders and teachers who fit around a single conference table shared tacit knowledge. They course-corrected verbally in real-time. They had a unique chemistry.
Nobody wrote it down. It was obvious in that room.
But the technical components travel well. The chemistry? No. When that small unit grows beyond the table, the model frays. People start doubting the pedagogy. They don’t realize they’re doubting a hollow shell. The expansion outran the learning.
The Container
We need a better metaphor. Think about the container.
The container isn’t the idea. It’s the structural boundary holding the experiment while you extract lessons from it.
A container that’s too large crushes you. It creates management pressure before you have clarity. A container too small might lack the complexity to reveal meaningful patterns.
The goal isn’t to stay small forever. It’s to match the container size to the volume of knowledge you currently hold.
Finding out you aren’t ready for scale isn’t a failure. It’s data. Realizing a pilot needs a smaller footprint is evidence you learned something vital.
A container mismatched with your knowledge is a liability, not a milestone.
Start Here
Don’t rethink your entire district today.
Pick three initiatives. Just three. Ask these questions for each:
- What is the actual learning question? Not the goal. Not the output. What are we trying to figure out?
- Does the container fit the knowledge?
The second question does the heavy lifting.
Imagine a Portrait of a Graduate rollout across twelve schools. One school gets it. The other eleven are still guessing at what it means. That is a cohort-sized pilot living in a pathway-sized container.
Naming that honestly changes your trajectory. You stop demanding compliance from the eleven. You study the one. You document the specific conditions that make it work. Then you expand.
Redesign isn’t about making things bigger.
It’s about making the learning visible enough to support whatever size comes next. The container doesn’t have to hold everything. It just has to hold the truth for now.
