What are some examples of strategies used to prevent "feature-itis" in the early stages of a product?


Are their examples I can give to those that work with me to let them know, more features is not what we want at this point.


asked Aug 18 '11 at 12:20
314 points

1 Answer


I think the best thing to do is use an example like 37signals and basecamp. They made the most simplistic 'to do' list type of app and sold it as a project management tool. Thing didn't even have due dates :] and they were wildly successful. Have them read 'rework ' by 37signals team. Their entire mantra is less, and you don't really need that feature you just think you do. They say no to pretty much every feature, it takes a lot of battling to get them to add something new.

Also, use something like pivotal tracker to track features, estimates, etc. so everyone can see what a new feature will take, what needs to be sacrificed, how it will affect timelines and you can order it's priority easily.

Good luck!

answered Aug 18 '11 at 13:43
Ryan Doom
5,472 points

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics: