Feature Creep
Feature creep makes a product harder to use when added capabilities compete with its core job. Restraint can be an advantage: preserve the essential interaction and let the technology recede.
WhatsApp’s early strength was almost an absence: all you could do was send messages. Instead of proving its sophistication through options, it gave users a tiny surface they could understand immediately.
E1Every feature competes for attention
A feature does not arrive alone. It adds a choice to evaluate, an interface element to interpret, and another possible answer to the question, “What is this product for?” As these decisions accumulate, the core interaction becomes harder to see. WhatsApp reduced that burden by making the intended path unmistakable: arrive, choose someone, send a message. The product’s technology remained useful precisely because users did not have to confront much of it.
E1Where it shows up
A messenger that only messaged
WhatsApp’s minimal starting set made adoption easier: users could act before learning a collection of secondary capabilities. The absence of features was not unfinishedness; it protected the product’s central job.
E1Removal is not automatically clarity
A smaller product is better only when it preserves what the user actually came to do. Remove part of the core interaction and simplicity becomes incapacity; keep adding around it and simplicity becomes clutter. The test is not feature count but whether each addition strengthens or obscures the main job.
Run the one-job test
Open your product’s first screen and name the single action a new user should take. Then mark every visible control that does not help complete that action. Hide one of those controls in the next version and measure whether users reach the core outcome faster.
Episodes that teach this
-
The Hidden Power of Removing Things | Via Negativa | Future IQ
· explained at 1:43
4,039 views
WhatsApp succeeded because “all you could do was send messages” and users could start with “a very minimal set of things.”