Greg DeVore writing about GarageBand for iPad and how we can get caught up with features:
But feature lists don’t ensure outcomes[...]The features don’t matter. It’s all about the outcomes. What can people do with your software? How does it make them better or happier? Can it turn a 7-year old into a rock star?
I’ve seen this happen countless times. Usually it happens like this: You have a basic requirements document. As you start to socialize it, each person throws in a “what if…” or two that grow that requirements list. All of a sudden, it isn’t a requirements list but a wish list. It’s hard to say no to, because each idea is justifiable in some way.
That’s why I’m a fan of how Amazon starts their product development.