What teachers actually want from school technology

Every August, somewhere in every district, a well-meaning leadership team unveils new software to a room full of teachers, and every August the same silent calculation runs behind hundreds of polite faces: how many clicks is this going to cost me? Not “is this innovative,” not “is this transformative,” and certainly not “does this leverage AI.” Clicks. Minutes. Friction. Teachers judge school technology the way emergency room nurses judge equipment, by whether it works instantly under pressure, because a classroom is pressure, thirty times over, five periods a day.

I have taught for a long time, sat on more technology committees than I can count, and listened to thousands of staff room verdicts on new tools. The gap between what gets purchased and what teachers actually want is one of the most expensive misunderstandings in education. Districts buy features. Teachers want flow. The platforms that earn genuine teacher love, and in my own school that has been our district’s adoption of Edsby, win not by doing the most things but by making the daily, repeated things nearly effortless: attendance in seconds, grades entered where lessons already live, a message to a parent without switching apps. Teacher-friendly school technology is not a product category. It is a design philosophy, and most edtech does not practice it.

This piece is my attempt to write down what teachers actually want, plainly enough that anyone who buys or builds school software can act on it.

We want fewer clicks, and we are not joking

Start with the thing that sounds trivial and governs everything. A teacher’s day is a sequence of transitions with no slack between them. Attendance while greeting students. A behavior note while circulating. Grade entry in the eleven minutes between the last bell and the staff meeting. Any tool that lives in those moments gets used or abandoned based on click count, screen loads, and logins, because a teacher performs its core actions thousands of times a year.

Do the arithmetic that vendors never do on stage. A workflow that costs four extra clicks, at two seconds each, performed thirty times a day, is twenty minutes a week, which is a full instructional day per year, per teacher, incinerated by interface design. Now invert it. Reducing clicks for teachers is one of the cheapest ways a district will ever buy back teaching time. When teachers beg for “simple,” administrators sometimes hear “dumbed down.” What we mean is engineered, the way a cockpit is engineered, so that the frequent actions are the fast ones. Intuitive edtech is not the absence of power. It is power that does not charge a toll every period.

We want one place, not seventeen

The second wish is consolidation, and the staff room word for its absence is “tab fatigue.” The typical teacher today operates a gradebook in one system, attendance in another, lesson resources in a third, parent messages in a fourth, report cards in a fifth, and a district data dashboard nobody remembers the password to. Each tool was adopted by someone reasonable solving one problem. The teacher inherits the sum, along with the daily job of being the human API that re-types information between systems that refuse to speak.

What teachers actually want is embarrassingly modest: the class list, the assignments, the grades, the attendance, and the family communication in one coherent place, so that recording a mark or messaging a parent happens in the flow of teaching rather than as a separate administrative errand.

A simple LMS for teachers is not one with few capabilities. It is one with few seams. Every seam between systems is a place where a teacher’s evening goes to die, and every consolidated workflow is an evening partially returned. When our school moved to a unified platform, the single most common piece of staff feedback in year one was not about any feature. It was some version of “I stopped copying things from one screen to another.” That sentence is what adoption sounds like.

We want technology that respects how classrooms actually run

Here is the tell that separates software built with teachers from software built about them: does it match the real rhythms of a classroom, or an engineer’s imagination of one? Real classrooms are interrupted constantly. So teachers want tools that save state instantly and forgive abandonment mid-task. Real classrooms run on routines. So teachers want defaults, class lists that already know the schedule, attendance that assumes present and asks only for exceptions, gradebooks that remember how this teacher structures categories. Real teachers move around the room. So anything that chains us to the desktop in the corner will lose to anything that works from the phone in our pocket.

And real teachers differ enormously in confidence with technology. Classroom technology usability means the tool must serve the twenty-six-year-old who grew up on apps and the veteran who has perfected her craft over thirty years and rightly refuses to sacrifice teaching time to a learning curve. A study backs the intuition that the human side decides everything here. Peggy Ertmer and Anne Ottenbreit-Leftwich’s influential study of teacher beliefs and technology integration found that even when schools remove external barriers to access, training, and support, teachers’ internal beliefs, confidence, and judgment of a tool’s actual value for learning determine whether technology is used meaningfully at all.

The implication is sharper than it first sounds. You cannot procure your way to adoption. A tool earns its place by convincing each teacher, through daily experience, that it gives back more than it takes. Usability is not a nicety on top of the feature list. Usability is the argument.

We want reliability more than novelty

There is a hierarchy of needs in classroom technology, and the industry keeps decorating the penthouse while the foundation cracks. Before a teacher can care about any advanced feature, the tool has to clear a brutally simple bar: it works, every period, on the first try, on whatever aging device the cart contains, on the building’s overloaded wifi, in front of thirty watching adolescents. A teacher who gets burned by a tool during class, a login loop at 9:05 with the whole room staring, does not file a ticket and move on. She quietly rebuilds her lesson so the tool is never load-bearing again, and no feature release will ever win her back, because the cost of that failure was paid in the currency teachers guard most fiercely: credibility in front of students.

This is why teacher enthusiasm for “boring” software confuses vendors. We rave about the gradebook that has never once lost an entry and shrug at the dazzling new feature, because we price technology by its worst day, not its best demo. The most underrated specification in all of edtech is what a tool does when the network hiccups: does it hold my work and sync later, or does it eat forty minutes of grading? Ask any staff room to name its most trusted tool and its most hated one, and I promise both answers will be about reliability, not capability. Teachers are not technology pessimists. We are experienced actuaries of classroom risk, and we insure accordingly.

We want technology that assumes we are professionals

Beneath the clicks and the consolidation sits something harder to put on a requirements document: dignity. A surprising amount of school software is designed with an implicit user in mind, and that user is someone who must be constrained, monitored, and standardized rather than empowered. Teachers feel this in a hundred small design choices. Locked settings that assume we cannot be trusted with options. Workflows that generate compliance reports for someone above us before they generate anything useful for the students in front of us. Mandatory fields that exist for the database, not the child.

The tools teachers embrace share the opposite assumption. They treat the teacher as the expert operator and design for judgment: flexible where classrooms differ, structured where consistency genuinely helps students, and transparent about what data flows upward and why. When a platform lets me organize my gradebook the way my subject actually works, or lets me decide how to phrase a note home instead of forcing a dropdown menu of canned sentiments, it is making a statement about what it thinks I am. Software is an opinion about its user, rendered in buttons. Teachers can read that opinion within a week, and adoption follows the reading. If districts want to know why one purchased tool thrives while another rots unused despite identical training hours, this is very often the answer nobody puts in the post-mortem.

We want to be asked, before and after

The wound underneath most teacher cynicism about technology is not any particular product. It is process. Tools arrive in our classrooms chosen by people who will never use them, demonstrated in conditions that resemble no classroom on earth, and evaluated by renewal contracts rather than by the people clicking through them two hundred times a day. Teachers do not expect veto power over district purchasing. We expect what any profession expects: that the daily operators of a system be consulted in its selection and heard in its evaluation.

The fix is not complicated, and I have watched it work. Put practicing teachers on the selection committee with real votes. Pilot with a genuine cross-section of staff, including your skeptics, not just your enthusiasts, because a tool that only delights the tech-forward is a tool that will divide your building. Ask for a feedback channel to the vendor and proof that past feedback changed the product. And after rollout, measure teacher time saved or lost as seriously as you measure any student metric, because teacher time is the resource everything else in a school is built from.

A short checklist I hand to administrators who ask:

• Count the clicks for the five most frequent teacher tasks, live, with a stopwatch
• Watch a skeptical teacher, not the vendor, drive the demo
• Ask what the tool eliminates from teachers’ plates, not just what it adds
• Check whether it consolidates existing systems or becomes login number eight

What it feels like when it goes right

I want to end with the positive case, because teachers are not anti-technology; we are anti-friction, and the difference matters. When our school’s platform consolidation settled in, something subtle changed in the building’s mood that I did not expect. The technology became boring, in the best sense. Nobody talked about it, the way nobody talks about the electricity. Attendance took seconds. Feedback reached students and their parents in the same motion. A veteran colleague who had sworn off “one more system” told me, almost annoyed with herself, that she could no longer remember her old workflow.

That is the actual finish line for school technology, and it is the one vendors rarely put on a slide: invisibility. Teachers do not want to be technology users. We want to be teachers, with tools so aligned to our work that they disappear into it. Every hour of friction removed from a teacher’s day does not vanish; it moves into feedback that got written, into the hallway conversation with the kid who needed it, into a teacher who goes home at five with something left in the tank. Teacher-friendly technology is, in the end, a student outcome wearing a disguise.

If you make decisions about school technology, spend one full day this term shadowing a teacher through every login, click, and retyped record, and let that day rank your priorities.

If you are evaluating platforms and want to see what a teacher-first, all-in-one design looks like in practice, Edsby’s approach to gradebooks, attendance, communication, and planning was built specifically around K-12 classroom workflows, and you can request a demo at edsby.com to judge it with your own stopwatch.

And if you are a teacher, the next time a survey or committee seat about technology appears, take it, even though you are tired, especially because you are tired. The people who buy the tools genuinely cannot see the clicks from where they sit. The only way they ever learn what teachers actually want is the way anyone learns anything in a school. Somebody has to teach them. You can try Edsby and see for yourself how things are working for your school!