Districts Aren't Done With Edtech. They're Done With Friction.
Why the market is starting to reward the shortest path instead of the longest feature list — and what that means for publishers.
If you've spent time in K-12 edtech lately, you've felt the temperature change. The expo halls are quieter. Districts that used to pilot anything now want evidence first.1 Purchasing committees that once said "yes, and" are saying "which one, and what does it replace?"2 The exuberant buy-everything years are over.
It's easy to read that as schools cooling on technology. It isn't. What's cooling is their patience for friction.
The numbers behind the shift aren't subtle. The average district now keeps access to around 3,000 distinct digital tools, a figure that's climbed steadily for years. Yet in its 2026 EdTech Top 40 report, LearnPlatform found that students and teachers engage with only about four of them on average.1 Thousands of tools bought, licensed, and privacy-reviewed; a handful in real use. Somewhere along the way, "digital transformation" became a sprawl no one designed and no one can quite manage.
Now the bill is coming due, literally. With the wave of federal pandemic-relief funding wound down, districts are auditing what they bought.2 Denver Public Schools cut its tool list from more than a thousand down to 346 and saved roughly a million dollars doing it; its edtech lead described the old setup as a collection of tools that never cohered into a system.2 Oklahoma City trimmed to about 250 approved apps, each one now screened for whether it works with everything else.3 The message from district leaders keeps coming back the same way: impact over volume.1 Prove it belongs, or it goes.
And it isn't only districts saying it. The platform vendors have picked up the same language. LearnPlatform reads its own 2026 data as schools moving away from accumulating tools and toward deliberately built, interoperable ecosystems connected through a common infrastructure.1 Instructure, the company behind Canvas, now names simplification as what districts want and pitches "frictionless" integration as the answer.4 When even the platform vendors reorganize their pitch around simplification, you know the ground has moved.
The real issue
The tempting explanation is money. Budgets are tight, relief funding is gone, of course districts are cutting. That's true, but it's the least useful part of the story — because budget explains why a district is cutting something. It doesn't explain what survives.
What survives is what teachers keep using. And what teachers keep using is what doesn't fight them.
That's the real issue underneath all of it, the one the budget numbers point at without naming: friction. Not whether a tool is powerful, but how much work it takes to reach the power. How many logins. How many tabs. How many places to look for the one thing you need in the middle of a lesson. How much a teacher has to learn, and relearn every August, before the thing helps a single student.
Seen that way, the pullback isn't a rejection of technology at all. Teachers stepping back from tech aren't Luddites — they're tired. They will gladly use anything that disappears into the teaching and gets out of the way. What they're done with is assembly: the sense that every "solution" shows up in pieces they're expected to put together themselves, in real time, with thirty kids watching.
Two kinds of friction
Friction lives in two places, and it's worth keeping them apart, because different people feel each one.
There's implementation friction — setup, rostering, training, the thicket of settings someone has to configure before launch. An administrator or curriculum coordinator feels this one, and it quietly kills a program before a single student logs in.
Then there's daily-use friction — the extra clicks, the second login, the hunt for the answer key, the teacher working in one window while the students work in another. The teacher feels this one, every period, and it kills usage after launch. A program can clear the first bar and still die at the second.
What this means if you publish curriculum
Here's why this matters for anyone publishing curriculum. When a district runs its tool audit — increasingly a standing review rather than a one-time cleanup23 — the program that survives isn't the one with the longest feature list. It's the one that's easiest to use. Low friction shows up, in the data a district looks at, as high adoption and steady usage. High friction shows up as licenses no one opened and "too many logins" in the teacher survey. One gets renewed. The other becomes a line item someone crosses out.
For most of the last decade, the market rewarded the longest feature list. That era is closing. What's replacing it rewards the shortest path — and that's the harder thing to build, because subtraction is harder than addition. Anyone can add a feature. Making a program feel like one thing instead of twelve is real work.
What low friction looks like
So what does low friction look like in practice? It looks like context. It looks like everything a teacher and a student need to do the lesson living inside the lesson — the content, the activity, the check for understanding, the feedback, the data — instead of scattered across a content platform here, an assessment tool there, and a reporting dashboard somewhere else.
The unit that matters isn't the platform. It's the lesson. When the lesson holds everything in one place, the teacher stops managing tools and starts doing the thing they came to do — teaching the same material their students are looking at, at the same moment.
That isn't a feature. It's a design decision: a choice to consolidate context rather than expand capability. And it's the decision that's beginning to separate the programs that make it through the audit from the ones that don't.
The part that's easy to miss
None of this asks you to abandon what you've built. The content is still the thing you do best. The only open question is whether it reaches teachers in a form that clears the friction bar — whether a teacher meeting your program in September experiences a single, coherent lesson, or a scavenger hunt.
That's a hard thing to judge from a feature sheet. It's a much easier thing to see.
See it for yourself
We'll take one of your lessons — whichever you'd most like to see — and rebuild it in C2C at no cost: one self-contained lesson, with the content, the activity, the assessment, and the data all in one place. Then we'll walk you through it, the teacher view and the student experience side by side, so you can see what one lesson instead of twelve tools looks like with your own material.
Two weeks, no commitment. If it's what you pictured, we'll talk about the rest — including how much of it you can do yourselves. If it isn't, you'll still have seen your content in a new light.
Send us a lesson
Footnotes
LearnPlatform by Instructure, 2026 EdTech Top 40 report (ninth edition, released June 29, 2026). Districts maintain access to an average of ~3,001 unique digital tools, while students and educators interact with only about four on average; the report frames this as the cost of tool sprawl and describes districts moving away from tool accumulation toward deliberately built, interoperable ecosystems, demanding evidence over access. Methodology note: beginning with this edition, the report measures Learning Tools Interoperability (LTI) app launches within Canvas rather than general web traffic, so its usage figures are not strictly comparable to prior years; the ~3,000 access figure is, however, continuous with earlier reports (~2,739 in 2023–24, ~2,982 in 2024–25). Report and release: https://www.instructure.com/edtech-top40 ; https://www.prnewswire.com/news-releases/new-instructure-data-shows-k-12-districts-are-demanding-evidence-not-just-access-to-edtech-tools-302812840.html↩↩2↩3↩4
"How This District Cut Hundreds of Ed-Tech Tools and Saved $1M," Education Week, July 8, 2025 — Denver Public Schools' reduction from more than 1,000 tools to 346 and ~$1M in savings; the district's plan to review its apps on a recurring basis; and the budget pressure created by the wind-down of federal pandemic-relief (ESSER) funding. https://www.edweek.org/technology/how-this-district-cut-hundreds-of-ed-tech-tools-and-saved-1m/2025/07↩↩2↩3↩4
"Trimming the Edtech Fat: How Districts Are Streamlining Their Digital Ecosystems," EdSurge, May 16, 2025 — Oklahoma City's reduction to ~250 approved apps screened for interoperability, privacy, and instructional alignment, alongside multi-year evaluation practices in other districts. https://www.edsurge.com/news/2025-05-16-trimming-the-edtech-fat-how-districts-are-streamlining-their-digital-ecosystems↩↩2
"New LearnPlatform by Instructure Report Shows K-12 Districts Are More Selective About Edtech Tools as They Face Budget Crisis," Instructure press release, June 30, 2025 — noting that simplification is at the forefront of districts' priorities and positioning Canvas Apps for "frictionless" app integration. https://www.instructure.com/press-release/new-learnplatform-instructure-report-shows-k-12-districts-are-more-selective-about↩
