17th
TumbleFriends
Spigolature
Webgolr
Giovy's
TAMBlr
Italian tumblers
For every new feature you need to…
* 1. Say no.
* 2. Force the feature to prove its value.
* 3. If “no” again, end here. If “yes,” continue…
* 4. Sketch the screen(s)/ui.
* 5. Design the screen(s)/ui.
* 6. Code it.
* 7-15. Test, tweak, test, tweak, test, tweak, test, tweak…
* 16. Check to see if help text needs to be modified.
* 17. Update the product tour (if necessary).
* 18. Update the marketing copy (if necessary).
* 19. Update the terms of service (if necessary).
* 20. Check to see if any promises were broken.
* 21. Check to see if pricing structure is affected.
* 22. Launch.
* 23. Hold breath.
Ship less features, but quality features.
You don’t need a big bang approach with a whole new release and bunch of features. Give the users byte-size pieces that they can digest.
If there are minor bugs, ship it as soon you have the core scenarios nailed and ship the bug fixes to web gradually after that. The faster you get the user feedback the better. Ideas can sound great on paper but in practice turn out to be suboptimal. The sooner you find out about fundamental issues that are wrong with an idea, the better.
Once you iterate quickly and react on customer feedback, you will establish a customer connection. Remember the goal is to win the customer by building what they want.