Walk into most classrooms that have gone through a recent technology initiative, and you will notice something familiar. There are interactive whiteboards requesting firmware updates, tablets pinging with notifications, an LMS that takes six clicks to find today’s assignment, and a teacher splitting their attention between the lesson and the technology that was supposed to support it. The tools were purchased with good intentions, but somewhere along the way, the technology became the thing everyone is paying attention to instead of the learning.
This is the problem calm technology was meant to address, and I think it is one of the more useful frameworks we have for rethinking how digital tools show up in schools.
A note added September 2026: I wrote this piece in 2024, and my view of ambient data collection in classrooms has changed since. The original version treated continuous background assessment and an engagement display as examples of calm design. I no longer think they are, for reasons I lay out in Behavioral Surveillance Refusal. I have revised those sections rather than leaving them, and the rest stands. The PDF below is the original 2024 version.
Where does calm technology come from?
The idea comes from Mark Weiser and John Seely Brown at Xerox PARC in the 1990s. Their argument was that the best technology sits at the edge of our attention and moves to the center only when it is needed, helping us take in information without asking us to manage the technology itself. In a school, that becomes a plain question: is this tool supporting the learning, or competing with it?
The framework is useful in that it gives us words for something educators already feel. When a teacher says “I spend more time managing the tech than teaching,” they are describing the opposite of calm design, and the principles give us a way to evaluate that situation rather than accept it as the cost of going digital.
What does it look like in practice?
Applying calm technology to educational tools means rethinking how those tools interact with the people using them. The goal is to keep the technology in the room but let it stay in the background, coming forward only when it has something useful to offer.
Learning management systems are an obvious place to start. Most LMS platforms ask for a lot of attention and can be hard to navigate, especially for educators juggling dozens of other responsibilities. A calm approach would favor simple interfaces that need little training, notifications that inform without interrupting, and information presented according to the user’s role and what they are doing. An LMS could put the most relevant content in front of a teacher based on upcoming deadlines and the time of day, without anyone digging through nested menus to find it. Nothing about that needs new technology; it is a design choice.
Classroom devices benefit from the same thinking. Interactive whiteboards, tablets, and other student-facing hardware can be configured to fit into existing classroom routines rather than demanding a set of procedures of their own. The device should adapt to the classroom, and the room should not have to be rearranged around it.
Assessment tools are where I have to be most careful with this framework, because it is easy to slide from calm to covert. The stop-everything-and-take-a-test model is disruptive, and there is real room for assessment that fits inside the work: a check for understanding built into the activity, feedback that arrives without a pop-up, adaptive practice that adjusts without announcing itself. What I would not call calm any longer is assessment that happens without the student knowing it is happening. Background data collection that feeds a dashboard the student never sees is quiet for the student and loud for the institution, and it is the institution’s attention that has been served. Calm in the interface and calm in the surveillance are different things, and the first does not license the second.
What stands in the way?
Calm technology is not a simple fix, and a few real obstacles sit between the idea and practice. Part of the problem is cultural. Schools are often under pressure to show off visible technology, and budget decisions, board presentations, and grant applications tend to reward tools that look impressive in a demonstration. Calm technology is meant to be hard to notice, which makes it a hard sell to stakeholders who want to see their investment at work. That does not make calm design less innovative, but it does mean we need better ways to explain its value than a demo.
There is also a technical problem. Context-aware systems that stay out of the way take careful engineering and design work, and most educational technology is not built with calm principles in mind. In practice that means a lot of configuration, workarounds, and pushing vendors for better design.
Equity and privacy are where the original framework runs out. Weiser and Brown’s 1996 essay is about attention. It does not address what happens when the ambient system is also a recording system, beyond the observation that the person, not the environment, should control what comes forward. Amber Case’s 2015 book, which turned their essay into design principles, gets closer: it asks designers to respect social norms and includes a section on designing for privacy, but it is written for consumer products, where the user chose the device. A student in a classroom did not choose the platform. So the questions the framework leaves open are the ones that matter most in education: who benefits from these tools, whose data is collected in the process, and whether “calm” is describing the student’s experience or the institution’s. James Scott uses the word legibility for what states do to the places they govern, and I am borrowing it here because a dashboard does something similar to a classroom. A system that makes learning visible to the institution without interrupting the student is calm and legible at the same time. That is less a contradiction in the framework than a gap in it, and naming the gap is part of using the framework honestly.
Teacher training matters too. Even well-designed calm technology needs educators who understand how to fit it into their teaching, which means professional development has to go past “here is how the tool works” and into “here is how to think about technology’s role in your classroom.” That is a longer and harder conversation.
What could a calmer classroom look like?
One of the more useful things about the framework is that it asks what classrooms could feel like rather than only what they could do. Two thought experiments help here.
Consider Natalie Jeremijenko’s “Dangling String” at Xerox PARC, the example Weiser and Brown themselves reach for. A plastic cord hung from the ceiling, connected to a motor driven by network traffic, twitched when the network was busy and hung still when it was quiet. Nobody had to look at it. Anyone could. It made a shared, invisible condition of the building present in the periphery without measuring any person. A classroom version of that would show something about the environment rather than the people in it: whether the shared device cart is charged, whether the network is struggling, whether the room is louder than it was an hour ago. I originally sketched a version of this that displayed the room’s collective engagement level, and I have taken it out, because engagement is a judgment about people and the sensors that produce it are watching students, however gently the output is rendered.
The same test applies to progress displays. A shared visualization where each student’s advancement is a growing plant reads as calm, and it may be, if the students planted their own trees. If the display is updated from analytics the students did not choose to share, it is a leaderboard with softer edges. The design decision that matters is not whether the information sits in the periphery but who put it there. Weiser and Brown were explicit that the individual, not the environment, must be the one who moves things between center and periphery. A display the student controls is calm technology, and a display that watches the student is the opposite, however quiet it is.
None of this is futuristic. These are design decisions, and the line between them comes down to who is being informed and who is being observed.
What should we be asking?
Taking a calm technology lens does not mean rejecting digital tools or settling for less capable ones. It means holding our tools to a higher standard: asking whether a tool is improving the learning or just adding complexity, whether it works for all learners, and what happens when technology becomes more ambient and harder to see. That last question is getting more pressing as machine learning makes it easier to build systems that anticipate needs. Anticipating a need from the calendar and the time of day is one thing, inferring it by watching the student is another, and only the first belongs under this heading.
A useful shift is to ask how a tool feels to use over time rather than what it can do. The first question leads to feature lists and demos, and the second leads to design that serves students and teachers in their daily work. I do not think that question has an easy answer for most of the tools in our classrooms, including some I have helped put there.
If you are thinking about how calm design applies in your own context, or you have examples of technology that gets this right or badly wrong, I would like to hear about it. You can reach me at licht.education@gmail.com, and there are more tools, articles, and resources at bradylicht.com.
