VOCABULARY / ENTRY
Calm Technology
calm-technology
Let technology move into the center of attention when needed, while usually supporting the main activity through appropriate peripheral information.
Keep writing your note
Notes synced
Routine updates stay in the background; failures provide a clear action.
Recognizing it
- Signal intensity matches urgency
- Peripheral status can be inspected at any time
- Respect for the task currently in progress
Concept boundary
Calm does not mean silence or hiding problems. Events requiring timely action may still need prominent alerts.
When to consider it
- Background updates and routine status need no immediate response
- The product frequently competes for attention
When to be cautious
- Hiding failures requiring timely action in the name of non-interruption
- Muting every notification indiscriminately
Tradeoff
Reducing interruption and keeping information discoverable require a deliberate tradeoff.
Conditional rules · Editorial advice
Related entries
Quiet signals still need to be perceptible to people with different abilities.
Inspectable progress can provide information without interrupting.
Sources and what they support
Discusses technology connecting the center and periphery of attention. The notification rules here are editorial applications.
Retrieved: 2026-09-15Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.
Type extensions and implementation notes
Capability tags describe this specimen only; verify the implementation again in a real product.
{
"values": [
"Respect attention",
"Appropriate awareness"
],
"tension": "Quietness versus discoverability",
"questions": [
"Does the person need to respond now?",
"Can the status still be perceived with different senses or in different environments?"
]
}Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.