Capability Is Not Feature Count
Capability describes what a system allows a user to accomplish, not how many options are available. A single well-designed function can outperform multiple overlapping ones.
When features duplicate effort or introduce choice without consequence, they increase complexity without increasing usefulness.
Subtraction as a Design Method
Removing features is not an act of simplification for its own sake. It is a methodical process of identifying what does not contribute to outcomes.
Each removal should strengthen what remains, making behaviour more predictable and interactions easier to understand.
Reducing Decisions for the User
Excess features shift responsibility onto the user. Decisions must be made repeatedly, often without clear guidance or benefit.
Functional reduction removes unnecessary decisions, allowing attention to focus on use rather than configuration.
Reliability Through Limitation
Fewer features often result in fewer failure points. Mechanical, digital, or hybrid systems all benefit from constrained behaviour.
By limiting what a system can do, designers increase confidence in how it will behave under regular and irregular conditions.
Designing for Repeated Use
Features that seem valuable in isolation often reveal their cost through repetition. Steps accumulate, friction increases, and attention erodes.
Systems designed for repeated use favour consistency over novelty and depth over breadth.