The Arboretum

Calm Technology

5 min read

Calm Technology

Technology designed to live in the periphery of human attention — informing without demanding, available without insisting.

The Idea

In 1995, Mark Weiser and John Seely Brown at Xerox PARC published “Designing Calm Technology,” and in 1996 extended the argument in “The Coming Age of Calm Technology.” They were thinking about ubiquitous computing — a future in which computation was everywhere rather than at a single desk — and asking what that future ought to feel like. Their answer was: calm. Technology that “informs but doesn’t demand our focus or attention.” Technology that could move between the center and the periphery of human attention as needed, without forcing the choice.

The periphery concept is the load-bearing idea. Weiser and Brown argued that the periphery is not emptiness — it’s where most of human awareness actually lives. You drive a car while carrying on a conversation because most of driving has moved to the periphery; only an unusual event (a dog running into the road, a light changing) pulls it to center. Calm technology works the same way. It provides information at the edge of awareness, where the mind can absorb it without interrupting whatever is actually in focus. An unusual engine noise is their example: you’re not listening for it, but you’ll notice if it changes.

The canonical demonstration of this at PARC was a piece of eight-foot string, a motor, and an Ethernet connection. The “Dangling String” twitched or whirled in proportion to network traffic. Nobody stared at it. But anyone in the room could glance at it to get a sense of load — or notice it in their peripheral vision without glancing at all. It informed. It did not demand.

Origins

Weiser died in 1999, before ubiquitous computing arrived in the form the smartphone took it. The irony is sharp: ubiquitous computing did come, and it became the opposite of calm. The smartphone moved everything from periphery to center — notifications, feeds, alerts, badges, the pull-to-refresh that mimics a slot machine lever. The attention economy that emerged is systematically built on the destruction of peripheral attention: if you’re not fully engaged, you’re not a monetizable user.

Amber Case revived the calm technology framework in her 2015 book Calm Technology: Principles and Patterns for Non-Intrusive Design, and has since formalized it into a set of eight principles and founded the Calm Tech Institute (2024). Her principles hold together: technology should require the smallest possible cognitive load, move easily between periphery and center, amplify human capacity without replacing it, fail gracefully rather than catastrophically, and use only as much technology as the problem actually requires. These are design constraints, not aspirations — ways to evaluate whether a given system is calm or merely quieter than usual.

What Designing Calm Actually Costs

The attention economy didn’t win by accident. Calm interfaces are harder to build and less immediately rewarding to use. They don’t create the feedback loops — scroll, dopamine, scroll — that make addictive products sticky. They require designers to accept that users might pay less attention to the product, which runs against every incentive structure built into how software is funded and measured.

Building a calm interface means resisting the pressure to add notifications, personalization, algorithmic ranking, infinite scroll, engagement nudges. Every one of those features looks like “adding value” from a product perspective, and every one of them degrades calm. The discipline is specifically the discipline of not doing things that would capture more attention — which is unusual to build as a positive design goal.

There’s also a technical cost. Periphery-first design requires understanding what information belongs in the periphery and what genuinely needs the center — which requires understanding human attention in context. A status light that shows “system healthy” without demanding acknowledgment is simple to describe and surprisingly hard to execute. The right ambient indicator for a given situation depends on what the person is already attending to, what would actually interrupt versus inform, and what failure modes look like.

The Tension

“Calm” can become a euphemism for passive. There are situations where demanding attention is the right interface choice — a smoke detector that doesn’t insist would be a design failure. Calm technology requires knowing when to interrupt, not just how to avoid it. The discipline is calibration, not minimalism for its own sake.

There’s also a class dimension. The most common examples of calm technology — ambient displays, smart home sensors, good industrial interfaces — tend to appear in well-resourced contexts. The attention economy, in the meantime, is most aggressively deployed on cheap smartphones used by people who can’t afford to opt out of ad-supported services. Calm technology as a design movement has mostly produced products for people who already have attention to protect. The question of how to extend calm design to everyone is not solved.

Connections

  • appropriate-technology — the shared logic of using only as much technology as the problem requires
  • convivial tools — Illich’s parallel argument about tools that enhance rather than colonize human capacity
  • local-first — infrastructure that doesn’t require constant connection, which tends toward calmer interaction patterns
  • daily-rhythm — calm technology serves rhythm rather than disrupting it

Further Reading

Graph View

Backlinks