The UX of Teaching: Why Understanding Teacher Workflows Should Shape EdTech Products
EdTech teams talk a lot about user experience, but too often they forget who the real user is. Teachers aren’t just one stakeholder among many, they are the early adopters, the primary operators, and the people who determine whether a product ever makes it into the classroom. When EdTech companies fail to map the teacher’s workflow as the core of the customer journey, the cost is enormous: low adoption, frustrated schools, and products that never reach their potential.
Human‑centered design tells us to start with the user. In education, that user is the teacher. And in a saturated market where every platform claims to “save time” or “simplify learning,” any barrier to classroom use becomes a barrier to success. If a product adds friction, teachers will quietly abandon it, and word will spread faster than any marketing campaign can keep up with.
I learned this the hard way while teaching an online class that relied on an external platform. We had planned the lesson beautifully. The content was strong. The pedagogy was sound. The only thing we didn’t anticipate was… the login screen. Students spent half the lesson trying to sign in, resetting passwords, refreshing pages, and asking, “Miss, is this the right link?” By the time everyone finally made it into the platform, the energy was gone and so was the learning time. The platform was amazing, it just didn’t account for how quickly a 30‑second delay multiplies into chaos.
This is why word of mouth is the real currency in education. No top‑down leader announcing how much the school invested in a piece of software will make teachers use it. Teachers trust other teachers. If a product works in the messy, unpredictable, time‑starved reality of a classroom, it will be successful. If it doesn’t, it dies quietly. Kahoot is the perfect example of this. Its brilliance wasn’t just the game mechanics, it was the fact that students didn’t need to log in at all. The teacher held the workflow, and the whole thing could be set up in the one spare minute they had before class started.
While we’re on the subject of time, the biggest misunderstanding EdTech teams have about teachers is assuming they have any. When I was doing my full‑time MBA after full‑time teaching, while also helping an EdTech company develop curriculum, my classmates kept saying it was the busiest they’d ever been. Meanwhile, I was thinking, “This is the most free time I’ve had in years.” That’s the gap. Teachers operate in a workflow where every minute is accounted for, and every extra click is a tax they cannot afford.
This is why EdTech product managers need to spend real time in real classrooms. Not in demos. Not in staged observations. In actual lessons, watching how teachers and students interact with software in the wild. How long it takes students to get their laptops out. How many forget their passwords. How many tabs open to YouTube. How long it takes to assign the right work. How quickly a lesson derails when a platform assumes a level of time, attention, or bandwidth that simply doesn’t exist.
If you spend more time understanding the problem, you spend far less time fixing the product later. The UX of teaching is not theoretical — it’s lived, embodied, and often chaotic. The EdTech products that succeed are the ones designed with that reality at the centre.
