Stop Asking “What’s Our Technology Plan?” (and What to Ask Instead)
Your school board is going to ask you a question about your technology plan: What did we get for it?
If your roadmap was built around tools, device ratios, and platform counts, you don't have a good answer. If it was built around learning outcomes, you do. How you answer that question comes down to which question you asked first.
Most district technology plans get this backward. They start with infrastructure, inventory, and vendor shortlists, then produce documents that are reviewed once a year and don't survive a budget cut. Just look at the post-ESSER numbers: only 6% of districts planned to continue ESSER-funded technology initiatives after the cliff, down from 27% the year before. Plans that couldn't connect spending to student outcomes didn't have a leg to stand on.
The wrong question to ask: What's our three-year technology plan?
Start here instead: What does our curriculum need that technology can enable?
The question most districts are asking (and why it produces the wrong document)
Most district technology plans start with a tool audit. What do we have? What's broken? What are other districts buying? It starts down a path that rarely leads to better learning outcomes.
When technology leads the planning process, curriculum follows. That produces a document IT owns that tracks platform licenses and infrastructure upgrades. While useful, that type of documentation doesn't answer the question a curriculum director, a principal, or a school board cares about: how are students better off because of this?
The average district used over 2,900 edtech tools in the 2024-2025 school year, and that kind of sprawl is more likely when there’s no instructional framework to evaluate specific tools or to intentionally roll them out.
A technology plan built around tools will always drift toward sprawl. Every vendor demo, every neighboring district's 1:1 rollout, every teacher who signs up for a free app becomes a purchasing decision with nothing to measure it against.
The districts that avoid this don't have better IT departments. They have a different first question.
What instructional-first planning actually looks like
Instructional-first planning starts with two questions, answered in order.
- What do students need to learn?
- What do teachers need to teach it?
Technology enters third, looking at how to support those two answers. When you know what instruction requires, you evaluate tools against something more impactful.
In practice, this means curriculum directors and CTOs work as co-equals. The curriculum team knows the desired learning outcomes. IT translates those requirements into infrastructure specs like bandwidth, device lifecycle, security posture, and interoperability standards. Neither function can do the other's job, but only one team should be setting the direction.
It also changes what an edtech audit looks like. Instead of "what tools do we own and how much are we paying?", the question becomes: does this tool have a job description tied to a learning outcome? Which student population does it serve? How does it simplify teacher workflows? Tools that can't answer those questions don't make the roadmap, regardless of how long the district has been paying for them.
This shift makes a multi-year roadmap defensible because every line item has an instructional case to make.
A quick overview of a multi-year roadmap
Once the instructional-first questions are in place, the roadmap itself has a shape to follow. Here's how that could play out over three years.
Align in year 1
Start with a needs assessment rooted in curriculum goals. What are students expected to master by the end of each grade level? What subtly slows teachers down in daily instruction? What does the current tool set actually support, and what gaps exist between what's purchased and what's used?
This is also when you build the planning committee. The right table includes curriculum directors, IT leadership, building principals, technology partners, title program coordinators, and classroom teachers.
Consolidate in year 2
With an instructional framework in place, you can cut what doesn't connect and formalize what does. It’s time to sunset the tools that failed the job-description test and build stronger vendor evaluation criteria tied to outcomes.
Districts moving toward outcomes-based contracts are getting clearer performance accountability from vendors and stronger positions at renewal. If a tool can't show impact against the outcomes it was selected for, that's a contract conversation.
Sustain in year 3 and beyond
A roadmap that started with instruction is easier to fund because it's easier to explain. E-Rate planning, Title IV allocations, and any successor funding to ESSER all become cleaner conversations when every platform investment maps to a documented learning goal. The board question (“What did we get for it?”) has a prepared answer.
Sustainable roadmaps also build professional development into the plan from the start, tied to the same outcomes the tools were selected to support. New teacher onboarding helps them become acquainted with the data-backed tools they can build on, and intentional PD sessions on the tools’ new features help your veteran teachers continue to get the most out of them.
The funding conversation is easier when the plan speaks curriculum
Budget pressure stalls out many technology roadmaps. But having a curriculum-led plan changes both budget and vendor conversations.
In 2026, 32% of district technology leaders named funding as their top unmet need—up from 25% the year before. And while outcomes can’t conjure new resources or larger budgets, funding requests become evidence-based when you can connect every platform investment to a learning goal.
You can also hold vendors accountable when you enter procurement with defined learning outcomes. That's the shift behind outcomes-based contracts: if a tool was selected because it was supposed to improve a specific student outcome, the contract can reflect that. Renewals, then, look at the impact on student learning, as well as price.
Canvas by Instructure also helps with this kind of accountability. Districts can see LTI usage alongside course activity, so they know which tools are being launched, by whom, and how often. Usage data is just one part of assessing tools, but any conversation about outcomes should include it.
Start with the question that changes everything
A multi-year technology roadmap that can't explain what students will learn differently or evidence-backed tools will help them achieve more is just an inventory with a timeline attached.
If your current roadmap started with tools, it's not too late to reorder the questions. Start with a curriculum-led edtech audit. Which tools have a job tied to a learning outcome? Which ones don't? That list is the beginning of a roadmap worth defending.
