feedback-loop

• SKILL.mdcore · 18,377 bytes
• references/cybernetics-and-research.mddoc · 5,827 bytes

# Feedback Loop

A feedback loop is the relationship between an action and the visible response that confirms the action happened. Every system in nature is composed of interacting feedback loops; every interface is too. When users press a button, type a character, drag an item, or commit a transaction, the system must respond — promptly, visibly, and unambiguously — to close the loop. Without that response, the user doesn't know whether the action registered, whether the system is working, or whether to try again. The cumulative effect of weak feedback is a product that feels broken even when it isn't.

## Definition (in our own words)

A feedback loop in interaction design is the mechanism by which the system tells the user "I received your action and here's what's happening." Loops can be *positive* (amplifying — repeated actions create accelerating change, like clicking a "+1" button that animates and grows the count) or *negative* (dampening — bringing the system back to a stable state, like a thermostat or a Segway maintaining balance). The most important loops in product UI are usually negative: the user acts; the system confirms; equilibrium is restored. When loops are missing or delayed, users repeat actions, doubt the system, or assume failure.

## Origins and research lineage

- **Cybernetics** (Norbert Wiener, 1948 onward). The mathematical theory of feedback in systems — biological, mechanical, and social. The intellectual foundation for everything that follows in HCI feedback design.
- **Jay W. Forrester**, *Industrial Dynamics* (MIT Press, 1961) and *Urban Dynamics* (1969). Applied feedback-loop thinking to organizational and urban systems. Introduced the diagrams (causal loop diagrams, stock-and-flow diagrams) still used in systems analysis.
- **Donald Norman**, *The Design of Everyday Things* (1988). Made feedback one of the central UI principles. Norman's gulf of evaluation — the gap between the user's intent and the system's perceptible state — is essentially the absence of good feedback.
- **Lidwell, Holden & Butler** (2003) compactly distinguished positive feedback loops (amplifying — useful for change but risky if unmoderated) from negative feedback loops (stabilizing — useful for equilibrium). The book's central case: 1950s football helmets that created a positive feedback loop (more padding → more risk-taking → more injuries → more padding).