When the Tool Becomes the Obstacle

If you’ve ever watched a student suddenly become very interested in their phone, their neighbor’s screen, the ceiling, or literally anything other than the task in front of them -- you might have assumed they were off task. You might have been right. But there’s another possibility worth considering. They might have been stuck, with no idea how to move forward, and no safe way to ask for help without looking lost in front of their friends. In a teenager’s brain, distraction is often a much more comfortable choice than admitting confusion. The platform gave them nowhere to go, so they went somewhere else entirely.

I saw that pattern constantly during my years as a literacy specialist. And for a long time I thought it meant something about my students. It didn’t. It meant something about the design.

Frustrated student in front of computer

* * *

The Story

The program was called Read180. The science behind it was solid -- built on legitimate literacy research, and used with fidelity, it helped a lot of kids learn to read. That’s not the problem I’m here to talk about. The problem was the interface, and the way that interface failed the exact students it was supposed to serve.

Most of my students had IEPs and many were neurodivergent, already working harder than their peers just to access grade-level content. They came to class every other day on a block schedule, meaning 48 hours passed between sessions. That’s a long time to hold onto new vocabulary words when reading is already a struggle.

Some students figured out that writing the vocabulary words down helped them remember. They thought they were cheating. They weren’t -- they were using active encoding, exactly what the research recommends. But the platform never told them that. They stumbled onto a good strategy by accident and felt sneaky about it. The students who didn’t figure it out came back after 48 hours, attempted the vocabulary section, and failed. Then failed again. The platform reset without explanation -- no guidance, no alternative pathway, no hint of what to try differently. Just the same screen, the same words, the same wall.

At some point, they stopped trying. Not because they gave up on learning. Because the tool had convinced them that effort led nowhere. And here’s what makes that different from any other frustrating software experience: a typical user who hits a wall just closes the app and moves on. These students couldn’t. The platform was still there the next session, still on the lesson plan, still expected to produce results. The only exit available to them was the one their brains invented -- distraction, disengagement, and eventually giving up quietly enough that nobody noticed right away.

Fluency completion stayed around 90%, but high numbers don’t always mean meaningful engagement. The platform couldn’t detect whether a student was actually reading or just sitting silently in front of a microphone until the timer ran out. Writing was worse -- completion dropped to roughly 10%. The section offered almost no scaffolding, and when students submitted nothing, the platform marked it complete anyway. No way for me to reassign it. So I entered zeros, over and over, for kids who hadn’t failed -- they’d been failed. Those zeros didn’t reflect my students. They reflected a design that had let them down.

* * *

Now Let’s Name It

Everything I just described has a name in UX research. Knowing the name matters, because it gives you the language to spot the same patterns in whatever tools are sitting on your students’ desks right now.

Error State Design

When a user fails at a task, a well-designed system tells them what went wrong and what to do next. Read180 had almost none of this. The silent reset -- no message, no suggestion, no alternative -- is devastating for a neurodivergent learner who already struggles with persistence. Good error state design meets the user where they are. Bad error state design leaves them stranded.

Motivation and Feedback Loops

Motivation is not a fixed trait. It’s something the experience itself builds or destroys. When a system offers no positive reinforcement, no sense of progress, and no clear path forward, motivation collapses. That’s not a character flaw in the student. It’s a failure of the feedback loop -- and it’s the designer’s responsibility, not the teacher’s.

Data vs. Intelligence

My dashboard was full of data -- time on task, scores, completion rates. What it lacked was intelligence. Data tells you what happened. Intelligence tells you what it means and what to do about it. A well-designed dashboard would have flagged a student stuck on the same section for three weeks and suggested I step in. Mine didn’t. I found those students manually, usually too late.

* * *

Three Questions to Ask About Any Tool

So the next time you sit down with a new platform -- or take a fresh look at one you've been using for years -- here are three questions worth asking.

1. What happens when a student fails?

Does the platform offer guidance and a path forward, or just reset and hope for the best? No error state guidance means the student carries the full burden of recovery alone.

2. Does the tool build motivation or drain it?

Watch how your students feel after using it -- not whether they completed the tasks, but whether they seem engaged or defeated. Motivation is a design responsibility, not just a student one.

3. Does your dashboard tell you who needs help today, or just who struggled last week?

One lets you intervene. The other lets you document. If your dashboard can’t surface which students need attention right now, it’s giving you data without intelligence.

* * *

I’m not sharing this to discourage you from using EdTech. Some tools are genuinely well designed and make a real difference. What I want is for you to be able to tell the difference -- to walk into a tool evaluation with better questions, a sharper eye, and the confidence to say “this doesn’t work for my students, and here’s why.”

You are not just a consumer of EdTech. You are its most important critic. The more fluent you become in the language of design, the louder and more effective your voice becomes.