The Educator’s Field Guide to EdTech Hype

The Educator’s Field Guide to EdTech Hype

Education technology runs on a reliable cycle: a capability appears, a wave of products wraps it in classroom language, budgets move, and three years later the storage closet gains another shelf of hardware nobody boots. The cycle is not proof that the technology was fake — it is proof that adoption outran evaluation. This guide is about never being on the wrong side of that gap again.

The five questions that deflate a demo

I have sat through hundreds of edtech pitches, and I have given some. The demos that survive these five questions are worth your pilot budget. Most do not survive.

1. “Show me this with my content.” Every demo is a best case: curated content, rehearsed path, ideal conditions. The product’s real value lives in the distance between the demo and your course materials, your student population, your LMS. A vendor who cannot run the tool on your syllabus in front of you is telling you the integration story is aspirational.

2. “What does the teacher do while this runs?” The question exposes the product’s theory of the classroom. Tools that assume the instructor disappears are describing a staffing model, not a pedagogy — and usually a fantasy about attention. The strongest products have a crisp answer about what they take off the teacher’s plate and what they hand back.

3. “What happens when it’s wrong?” Everything fails: recognition mis-hears, models hallucinate, adaptive engines mis-place students. The differentiating question is whether failure is visible and recoverable. Who notices the error — the system, the teacher, or a student who trusted it? A vendor without a fluent answer has not watched real classrooms use the product.

4. “What do you do with student data?” Ask it plainly and watch the tempo change. You want specific answers about what is collected, whether student work trains their models, retention and deletion, breach terms, and FERPA posture — in the contract, not the FAQ. Any hedge here is disqualifying, because this is the question where the institution, not the vendor, carries the downside.

5. “Who else like us uses this, and can I call them?” Not the logo slide — a phone number. A reference at an institution with your budget and your students, a year into use. The most informative reference call question: “What surprised you?” Nobody’s surprise is in the sales deck.

Total cost, honestly counted

The purchase price of educational technology is routinely a minority of its cost. The majority: integration hours, faculty training time, the support burden when it breaks during class, device management if hardware is involved, and the renewal you’re now anchored to. Before any pilot, write down the full-year cost including people time — then decide whether the same money spent on faculty development or student support would buy more learning. Sometimes the honest answer is that it wouldn’t, and the tool wins. The discipline is in doing the comparison every time.

Pilot like a scientist, not a fan

The purpose of a pilot is to be able to kill the tool. Decide the success measure before it starts — ideally an assessment you already run — and the date you’ll decide. Run it in a normal-difficulty section, not the enthusiast’s showcase. Keep a change log so you can attribute effects to the tool rather than to novelty or to the extra attention pilots attract. And announce in advance that “no measurable difference” means no purchase; that single sentence changes how everyone, vendors included, behaves for the duration.

Why skepticism is a service to the technology

None of this is anti-technology; it is the opposite. Educators who evaluate rigorously are how good tools separate from wrapped hype — they are the market signal that rewards products which actually work in classrooms. The teacher who asks hard questions in the demo is doing quality assurance the industry cannot do for itself, because only the classroom knows what the classroom needs.

Emerging technology genuinely is changing what is teachable: simulations that give every student the practice reps that used to be rationed, assistants that make feedback loops faster, tools that lower the floor for creation. Those wins are real, and they arrive faster on campuses with sharp evaluators. Hype is not the enemy of progress here. Unexamined hype is.

Keep the five questions in your pocket. They are short enough to remember in the demo, sharp enough to change its outcome, and universal enough to outlive whatever the next wave is called.

And when a tool does clear every question — demo on your content, credible teacher workflow, visible failure modes, clean data answers, a reference who’d buy it again — say yes quickly and loudly. Rigorous evaluators earn their credibility in both directions: the “no” that saves a budget and the “yes” that moves a program. Colleagues trust the second because they watched you practice the first.