10 things you should know about prototypes

We've been working on a client project recently that involved creating a portal/social network prototype. Here are a couple of learnings I'd like to share.

• Set expectations upfront, i.e. make sure everyone understands it is a prototype. It is meant to be thrown away. You should keep the ideas and learnings. Any code you save is a bonus.
  
• The goal of the prototype is not to create the product, it is to learn what the product should be. It is a 'learning' exercise, not a 'building' one.
  
• Expect the client to change his mind every day. If he isn't then maybe he is not as engaged as you thought he was.
  
• It's not a software prototype, it is a business prototype. The prototype helps not only to mold the product but the entire team and the business vision.
  
• Fail fast. This is the time where forgiveness is easily given.
  
• Don't develop prototypes in isolation, work with the client every day. The prototype is a journey, not an end point.
  
• If you going to ship your prototype, it is only to a select group of beta testers that will help you define and refine your thinking.
  
• Make sure you have beta testers that try the prototype.
  
• Play. Take the wackiest ideas and test it. Flex the system to see what it can or cannot do, and should or shouldn't do.
  
• Refine the goals often but make sure you have goals, otherwise, life will become one unending prototype.
  
• Stay loose.
  

Love to hear about your learning curve...

BTW: Seems like my assertion that Guy Kawasaki's Truemors wasn't a well-orchestrated marketing campaign to boost his brand after all. (Too bad, I kinda liked that story better, smacked of marketing genius. Guy is a genius, he just doesn't know it or too humble to admit it!) But Guy came by yesterday and put the record straight. Thanks Guy and good luck! You continue to help make the blogosphere interesting.