Your work should empower and inspire. Thatâ€s how important it is.

 State of your prototype must reflect the state of completion of your system. This simple guideline is also very profound. The degree of certainty in your design should be reflected in the level of completion of your prototype. The project starts with a rough storyboard which is highly uncertain and full of assumptions: no one knows if the audience will find the product useful, if they will pay for it, or even if the product can (or should) be built. As the design and development progress, the prototype becomes the pack of sticky notes with specific workflows, layouts and on-screen controls. As the confidence in the design grows still further and more questions are answered, the product coding begins. Both Alpha and Beta releases become the prototype until finally the confidence level reaches a local maximum and the product is released. At this point the cycle of improvement starts again.