Feature-oriented development leads to bad products

“Gaining a Competitive Advantage with a Solid Experience Vision”

“It’s impossible to avoid: feature-for-feature parity ultimately leads to experience rot. When we continually add new features, we make our design more complex. And when we increase complexity we reduce the quality of the user experience.”

This is what happens when, after making a solid launch product, switching to feature-oriented development makes the product worse overall and opens it up to competition.

What’s even worse are the projects that are feature-oriented from the start: instead of focusing on the overall utility and experience, you tick off desired features like items on a grocery list, leading to a sort-of-functional but hopelessly useless product at launch.

Baldur's Notes @baldur