control

• SKILL.mdcore · 13,513 bytes
• references/lineage.mddoc · 7,819 bytes

# Control

> **Definition.** Control is the degree of authority and decision-making the system delegates to the user. A high-control system exposes parameters, asks for choices, and lets the user direct outcomes; a low-control system makes decisions on the user's behalf, hiding parameters and presenting outcomes. Neither is universally better. The right level of control depends on the user's expertise, the stakes of the task, and how often the user will perform the task.

The classic illustration: a microwave. A novice user wants three buttons — popcorn, defrost, reheat. An expert wants the panel of granular options — exact wattage, time in seconds, multi-stage cooking sequences. A microwave that exposes only the three buttons frustrates the expert; a microwave that exposes only the granular panel intimidates the novice. The well-designed microwave does both: large simple presets up front, granular controls available but tucked away.

The same problem appears in software a hundred times a day. A photo editor for a casual user is "auto-enhance"; for a professional, it's curves, levels, masks, and color spaces. A code editor for a beginner is "run this script"; for an expert, it's customizable shortcuts, plugin systems, and direct shell access. The challenge is rarely "what should this product do" but "how much control over the doing should the user have."

## Why control matters

The principle named "control" in the design literature is sometimes also called "user agency" or "user autonomy" — different traditions, same problem. The effect is well-documented: users with appropriately calibrated control perform tasks faster, with fewer errors, and report higher satisfaction. Users with insufficient control feel constrained and frustrated; users with excessive control feel overwhelmed and paralyzed.

The cost of miscalibration is paid in a few specific ways. **Novices facing too much control freeze.** They can't decide which option matters and which doesn't, and either pick poorly (defaulting to whichever is most prominent) or abandon the task. **Experts facing too little control work around the system.** They open external tools, write scripts, find hacks. The work-arounds are often less reliable than the system would be if it just exposed the controls the experts need. **Mid-level users — neither novice nor expert — get the worst of both.** A simplified UI that experts work around is usually also too simplified to teach anyone how the underlying system works, leaving mid-level users perpetually stuck.