Is All This Clicking Helping? A Calm Lens on Interactive EdTech


Most of us have sat through some version of the same demo. A module opens with an animated guide, the learner drags labels onto a diagram, a progress bar fills, a badge appears, and a short quiz pops up to confirm that the labels went to the right places. Everything moves. The vendor calls it interactive, and in a narrow sense it is, since the learner is doing something on nearly every screen. The question the demo rarely answers is whether any of that doing has much to do with learning. A learner can click through every screen of a module like that without once having to explain, decide, or revise anything.

That gap between activity and understanding is what this piece is about. “Interactive” has become one of the words EdTech uses to sell itself, and as such it gets applied to almost anything a learner can tap. I wanted a way to look at a tool and ask a more specific question: is this interaction doing the learning work, or is it simply keeping people busy? And if it is doing the work, is it doing it without crowding the learner’s attention with everything else?

Where did this framework come from?

I built the framework below during my instructional design coursework, and I have kept coming back to it since. I have used it on tools on my own and shared it with teachers as something to explore. It is not a validated instrument, and I would not want anyone to treat it as one. It is closer to what I have called thought technology elsewhere on this site, in that it is a way of looking at something from an angle you might not take on your own. Every framework carries an argument about what matters, and this one carries mine.

The framework pulls from four places. Woo and Reeves’s work on meaningful interaction argues that interaction supports learning only when it deepens understanding, which means learners have to question, justify, and build knowledge rather than perform surface tasks. Chi and Wylie’s ICAP framework sorts engagement into passive, active, constructive, and interactive modes, with learning gains rising as learners move from receiving information toward generating and co-constructing it. Calm technology, the idea Mark Weiser and John Seely Brown developed at Xerox PARC and Amber Case later turned into design principles, asks technology to inform without demanding attention and to use the edges of awareness so people can stay with the task in front of them. And cognitive load theory, from John Sweller’s work, reminds us that working memory is limited and that every bit of extraneous complexity in a design comes out of the same budget the learner needs for the content.

What are the four lenses?

The framework looks at an interaction through four lenses. The first three ask whether the interactivity is authentic to the learning. The fourth, calmness, asks whether the design keeps interactivity limited to what is authentic, so that the meaningful interactions stand out and the meaningless ones fall away. The goal is interactivity that is simple in presentation and deep in impact.

LensWhat to look forMinimalBasicStrongExemplary
1. Depth of EngagementHow deeply does the interaction invite learners to think with ideas, not just move through tasks?Learners mainly watch, read, or click through without meaningful response.Simple actions such as matching or selecting; actions relate to content but do not require reasoning.Learners generate new ideas, explanations, or connections; thinking is visible.Learners co-construct understanding with peers or the system; interaction feels conversational and idea-driven.
2. Learner Agency and Emergent PathsHow much freedom does the learner have to make choices, pursue questions, or shape how learning unfolds?Single fixed path; little choice or control; unexpected input is ignored.Some small choices (topic or difficulty), but overall structure is predetermined.Choices meaningfully change the experience; system adapts to different strategies.System and learner co-shape the path; unexpected ideas are integrated and remain coherent.
3. Feedback, Reflection, and Knowledge BuildingHow does the system respond to the learner and promote understanding and reflection?Feedback limited to right/wrong or progress; little reflection or revision.Occasional hints or explanations, but generic or optional.Feedback is specific and actionable; reflection and revision are encouraged.Feedback and reflection are central; learners articulate reasoning, compare perspectives, and iterate on ideas.
4. Calmness and Cognitive LoadHow well does the system support focus and mental clarity? Does it respect the learner’s attention and emotional state?Interaction feels noisy or confusing; many alerts or unclear steps.Interface is somewhat cluttered but usable; minor confusion or extra effort required.Design feels orderly and focused; feedback is clear and timely without distraction.Experience embodies calm design; minimal attention demands, peripheral cues used appropriately, sustained flow and focus.

The printable version lays each lens out on its own with the steps and research notes. It is shared under a CC BY 4.0 license, so you are welcome to copy, adapt, and share it, including in your own trainings, as long as you give credit.

Depth of engagement is the lens closest to ICAP. The drag-and-drop diagram from the demo sits at Basic, in that the action relates to the content but a learner can get it right by pattern-matching. Move the same activity up a level and the learner might have to explain why a label belongs where it does, or predict what happens if one piece of the diagram changes. The content is the same. What changes is whether the learner has to think with it.

Learner agency asks how much of the path belongs to the learner. A lot of tools offer what I would call cosmetic choice: pick an avatar, pick a color theme, pick which of three identical practice sets to do first. None of those change the learning. The stronger end of this lens is where a learner’s choices or unexpected answers actually change what happens next, and where the system can take an idea it did not anticipate without falling apart.

Feedback, reflection, and knowledge building is where a lot of tools that score well on the first two lenses fall back. Right and wrong with a green check or a red X is feedback in a technical sense, but it gives the learner nothing to revise with. The stronger versions ask learners to say why, compare their reasoning to someone else’s, and try again with something they did not have the first time.

Calmness and cognitive load is the lens that holds the other three in check. It is easy to read the first three lenses as a call for more: more interaction, more choice, more feedback. The fourth lens pushes back. Every prompt, alert, animation, and badge costs attention, and the question is whether each one is paying for itself in learning. A tool can score well on depth and still be exhausting to use if the meaningful interactions are buried under a layer of notifications and decorative motion. The calm version keeps the meaningful interactions and trims the rest, which is the same move I argued for in The Hidden Cost of EdTech Complexity and Better Notifications in Online Learning and EdTech, applied at the level of a single activity.

How do you use it?

The process is short: 1) choose a learning task or a short sequence within a tool; 2) work through it as a learner, or watch a learner do it; 3) describe the interaction through each lens, with a rating if that helps; 4) look across the four lenses for patterns, such as where the design supports depth and calm and where it adds noise or stays on the surface; and 5) use what you notice to propose one or two small redesigns that move the experience up a level on one lens.

The fifth step matters most to me. The point is not to give a tool a score and file it away. It is to come out the other side with a specific change you could make or ask for. Most of the tools teachers use were not built by them and cannot be rebuilt by them, but nearly every tool leaves some room in how an activity is set up, what gets turned on, and what gets turned off.

What did teachers say about it?

When I have shared the framework with teachers, the reactions have split in a way I find useful. One or two told me the table assumed a lot of background knowledge about the research behind it, or that it left too much up to interpretation. That is a fair criticism. A teacher who has never run into ICAP or cognitive load theory is being asked to apply ideas the table only gestures at, which is part of why this post explains each lens instead of only posting the table. The interpretation part I am less inclined to fix. A framework that tells you exactly what to conclude is closer to a checklist, and checklists tend to get filled out rather than thought through.

Others appreciated the choices about what went into the framework and what was left out, and the fact that it was clearly making its own argument rather than trying to cover everything. That was the reaction I had hoped for. The framework says nothing about price, data privacy, integrations, or vendor support, all of which matter when a district is deciding what to buy. It is meant to be one lens among several, not the whole evaluation.

Has anyone else been thinking about this?

Not long after I built this, a paper came out that started from nearly the same place. Maria Firdous, Muhammad Ahsan, and Saul Delabrida presented “Designing Calm Educational Technologies: A Framework for Non-Intrusive and Emotion-Aware Classrooms” at the CSEDU conference in 2026. It is a conceptual paper built from a literature synthesis of calm technology, human-computer interaction, cognitive load theory, and emotion-aware learning research, and the authors are upfront that the framework has not yet been tested in classrooms. What they propose is a layered pipeline: 1) unobtrusive multimodal sensing of the classroom environment, learner behavior, and affective signals; 2) an AI layer that estimates each learner’s engagement, cognitive load, and emotional state; 3) peripheral responses such as ambient displays, subtle cues, and simplified interfaces; and 4) human-in-the-loop control, where teachers set the system’s thresholds and learners take up the support voluntarily.

Reading it felt a bit like convergent evolution. Two frameworks, built separately, reached for calm technology and cognitive load theory as the core pairing, and both are meant to help people judge tools rather than only design them. The paper ends its discussion with three questions for technology selection and procurement: does the system operate peripherally rather than intrusively, does it preserve teacher agency, and are consent and transparency explicitly addressed. Those are good questions, and I would happily set them beside my four lenses. I think they get several other things right as well. Grounding calm in cognitive load theory gives the idea a mechanism instead of an aesthetic. Their emphasis on interaction that moves between focused and peripheral attention is closer to what Weiser and Brown actually wrote than the common reading of calm as “quiet.” And they say plainly that emotion recognition deployments have drawn criticism for privacy violations and lost teacher autonomy, which a lot of papers in this area skip past.

Where we part ways is the sensing layer, and the paper’s own examples show why. In one, a 14-year-old working on algebra is passively monitored for task completion time, error rates, posture, and pauses. The system concludes she is cognitively overloaded, simplifies her screen, and sends a quiet update to the teacher’s dashboard, and the teacher walks over and offers a private hint. In another, a language class is read for gaze aversion, long silences, heads on desks, posture, and speech prosody; the system concludes the room is bored or mildly anxious, shifts the tone of the lighting, and suggests the teacher switch to pair work. In both cases the student experiences nothing disruptive, which is the point of the design. But the student also never decided to be read. “Non-intrusive” in this framework describes the interruption, not the observation. The sensing runs continuously, and the paper notes that it is built to work even when a student’s face gives nothing away, by reading posture, gaze, and interaction speed instead.

That is the distinction I tried to draw in Calm Technology in Educational Settings, where I argued that calm in the interface and calm in the surveillance are different things, and that a system can be quiet for the student while being loud for the institution. The paper’s answer is human agency, and its version of agency is real but uneven. Teachers configure the thresholds and decide what to do with what the dashboard tells them. Students engage voluntarily with the support that results, but nothing in the framework gives them a say over the sensing that produced it. Weiser and Brown were explicit that the person, not the environment, should decide what moves from the periphery to the center. A system that reads a learner’s mood and posture and acts on that reading has made the decision for them, however gently it acts. My fourth lens asks whether a design respects the learner’s attention and emotional state. It does not ask the system to detect that state, and of everything the two frameworks disagree on, that difference matters most to me.

Who is being informed?

That question is where I keep landing with both frameworks. A calm lens can tell you whether a tool respects a learner’s attention, and the first three lenses can tell you whether the interaction is doing learning work. Neither can tell you who the tool is ultimately serving. A drag-and-drop activity that scores Basic on depth might still be the most useful thing in the room for a learner who needs low-stakes practice, and an emotion-aware system that scores well on every calm criterion might still be quietly reporting on that learner to someone else. My framework does not resolve that, and I am not sure any rubric can.

The framework also has to apply to the tools I recommend and help roll out, not only to the vendor demos I am skeptical of. That is a less comfortable exercise, and it is probably the one worth doing first.

If you try the framework on a tool you use, or you think one of the lenses is missing something, 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.


Discover more from Brady Licht

Subscribe to get the latest posts sent to your email.