A prototype is a working, hands-on implementation for evaluating a product or technology. It reveals qualities that feature lists may miss, including how an editing experience feels and how quickly a team can make a working change. section 4.2.3
Make the prototype answer a decision, rather than treating a successful run as proof that a technology is suitable.
- Decide in advance what the prototype should demonstrate, then build it to stress the specific concerns being evaluated. section 4.2.3
- A simple greenfield “Hello world” may prove little if it exercises none of the relevant concerns. section 4.2.3
- Rapid prototyping can make it practical to test multiple candidates earlier; rebuilding the same use case with another technology supports a more comparable evaluation. section 4.2.3 section 1.3.2
Compare the experience
For a visual editor, spend time using the actual product: direct experience can reveal more about its feel and learning curve than vendor materials or a feature list. section 4.2.3
