VI. Technology should work even when it fails: Difference between revisions

From Cyborg Anthro Wiki
Created the page!
 
m Created the page!
 
Line 1: Line 1:
==Introduction==
==Introduction==
Machines and people are good at different things. Machines are good at precision, repetition, memory, endurance and arithmetic. People are good at judgment, context, improvisation and deciding what is worth doing. A tool that takes over the second category in order to demonstrate the first produces worse results and a less capable person.
Every system fails. The design question is what remains when it does. A system that retains its core function during a failure costs a person an inconvenience. A system that loses everything costs a person the task, and often the trust that made the system usable in the first place.
   
   
Amplification means the machine handles the part that would otherwise consume a person's attention, and hands back the part that requires a person. The test is whether the person is more capable while holding the tool and more capable after setting it down.
Failure states are part of the product, and they are the part most often left undesigned. A device that assumes power, connectivity, a working sensor and a reachable server has four ways to become useless, and each one is a decision somebody made.
   
   
* A calculator performs arithmetic so a person can hold the shape of a problem.
* A mechanical key opens a door when the battery in the lock is dead.
* A dishwasher runs a cycle so a person can leave the kitchen.
* A window opens when a ventilation system is off.
* A sewing machine produces a consistent stitch so a maker can attend to the pattern.
* A printed schedule remains readable when a display is dark.
   
   
===Autofocus Camera===
===The Escalator===
An autofocus camera performs the operations that are mechanical: measuring distance, setting focus, metering light, selecting a shutter speed that will not blur. These are calculations with correct answers, and a camera arrives at them faster and more reliably than a person can.
An escalator that loses power becomes a staircase. The treads are stair-shaped and stair-sized because they were engineered to carry standing weight, and the handrail remains at the height a hand expects. A person walking onto a stopped escalator changes their gait and continues.
   
   
Everything the camera does not do is the photograph. Where to stand, what to include, when to release the shutter, whether the moment is worth keeping. The camera has no opinion about any of it. The division holds because the camera is confident about arithmetic and silent about meaning.
Nothing about this is accidental. Tread depth, riser height and handrail placement are specified so the stopped condition is safe to walk. The comparison case is a powered door that seals shut, or a hotel lock whose dead battery leaves no mechanical path to the room.
   
   
A camera that amplifies does not need to:
An escalator that fails well does not need to:
*Choose the subject
*Announce that it has stopped
*Decide when the moment has arrived
*Be repaired before people can pass
*Judge whether the photograph is good
*Trap anyone on it
*Explain its exposure calculation
*Be operated differently while stopped
   
   
The failure mode is a tool that reverses the split. A camera that selects subjects and discards frames it scores as unsuccessful takes over the judgment and leaves the person operating the machine.
The same logic applies to software. A connected thermostat that holds its last schedule during an outage keeps a house warm. One that reverts to a default or waits for a server does not.
   
   
Just as a camera measures light so a photographer can watch a room, well-designed technology takes on the mechanical part of a task and returns the part that requires a person.
Just as a stopped escalator is still a staircase, well-designed technology retains its core function when the parts that make it convenient are gone.
   
   
==Categories==
==Categories==

Latest revision as of 18:30, 23 August 2026

Introduction

Every system fails. The design question is what remains when it does. A system that retains its core function during a failure costs a person an inconvenience. A system that loses everything costs a person the task, and often the trust that made the system usable in the first place.

Failure states are part of the product, and they are the part most often left undesigned. A device that assumes power, connectivity, a working sensor and a reachable server has four ways to become useless, and each one is a decision somebody made.

  • A mechanical key opens a door when the battery in the lock is dead.
  • A window opens when a ventilation system is off.
  • A printed schedule remains readable when a display is dark.

The Escalator

An escalator that loses power becomes a staircase. The treads are stair-shaped and stair-sized because they were engineered to carry standing weight, and the handrail remains at the height a hand expects. A person walking onto a stopped escalator changes their gait and continues.

Nothing about this is accidental. Tread depth, riser height and handrail placement are specified so the stopped condition is safe to walk. The comparison case is a powered door that seals shut, or a hotel lock whose dead battery leaves no mechanical path to the room.

An escalator that fails well does not need to:

  • Announce that it has stopped
  • Be repaired before people can pass
  • Trap anyone on it
  • Be operated differently while stopped

The same logic applies to software. A connected thermostat that holds its last schedule during an outage keeps a house warm. One that reverts to a default or waits for a server does not.

Just as a stopped escalator is still a staircase, well-designed technology retains its core function when the parts that make it convenient are gone.

Categories

Calm Technology