Loading…
Loading…
Technology that informs without demanding attention, staying at the periphery.
stellae.design
Calm Technology (Mark Weiser, John Seely Brown, Xerox PARC) envisions technology that informs without demanding attention. It moves information between center and periphery of attention. Core principles: smallest possible attention required, create calm, use peripheral attention, amplify the best of technology and humanity, work even when failing. In an age of notification overload, respecting user attention is paramount.
Calm technology is a design philosophy originating from Mark Weiser and John Seely Brown's work at Xerox PARC, proposing that the most effective technologies inform users without demanding their attention — moving between the center and periphery of awareness as needed rather than constantly competing for focus. In an era of notification overload, attention fragmentation, and screen fatigue, calm technology principles have become essential for designing products that respect users' cognitive resources and integrate into their lives without creating stress. Products built on calm technology principles achieve higher long-term engagement precisely because they do not exhaust users — the tool that quietly works in the background gets used daily, while the one that screams for attention gets silenced or uninstalled.
The Echo device uses a colored light ring to communicate status — spinning blue for listening, pulsing yellow for waiting notifications, green for incoming calls — providing peripheral awareness without demanding visual attention or interrupting conversation. Users glance at the light when they choose to, rather than being pulled out of their current activity by an intrusive alert. The design embodies calm technology's core principle: technology should inform at the periphery and move to the center of attention only when explicitly invited.
Apple's Focus modes allow users to define context-specific notification filters — work mode suppresses social notifications, personal mode silences work email — ensuring that interruptions are relevant to the user's current activity rather than their entire digital life. Grouped and summarized notifications further reduce attention cost by batching low-priority updates into periodic digests rather than delivering each one individually. The system respects user attention as a finite resource and provides tools to manage it intentionally.
A fitness tracking app sends push notifications for every completed step milestone, water reminder, standing prompt, sleep suggestion, friend activity update, and promotional offer, averaging 23 interruptions per day across a user's phone, watch, and tablet. Users initially engage with the notifications but within two weeks either disable all notifications for the app or uninstall it entirely, losing access to the features they actually valued. The app's aggressive attention-seeking behavior destroys the long-term relationship that a calmer approach would have sustained.
• The most common mistake is equating calm technology with minimal technology — calm design is not about removing features or information, but about presenting them at the appropriate level of attention demand for their urgency and relevance. Another frequent error is designing calm defaults but allowing internal stakeholders to override them with 'urgent' marketing notifications and engagement prompts that violate the calm contract users implicitly agreed to. Teams also fail to test attention cost holistically — a single notification seems reasonable in isolation, but when multiplied across features, services, and devices, the aggregate interruption load becomes anything but calm.
Was this article helpful?