Design by Subtraction, Not Addition

3. Design by Subtraction, Not Addition

Teams didn't ask "what feature should we add next?" They asked "what's the minimum needed for the verb to work?" Then they cut anything that didn't serve it.

Rule of thumb: A feature earns its place only if removing it makes the core loop noticeably worse. If removing it doesn't hurt, it was never load-bearing — cut it before it costs you memory, time, or clarity.

This is the opposite of modern feature-creep pitching, where more systems = more perceived value.