using the output to conduct an experiment to get customer validation. The prototype is not the final product, although it might inform, inspire, or annoy the future designers of it. Here is the general framework of the solution prototype screens and their content. The order and amount of the middle screens is flexible based on how many key experiences you need to show. 1. Setup. Typically the landing page or user dashboard. 2. Key UX 1. Typically in one to three screens, shows the crucial interactions that show value innovation. 3. Key UX 2. Typically in one to three screens, shows the crucial interactions that show value innovation. 4. Value proposition. This is the final result of a successful transaction. 5. Pricing strategy (if applicable). This shows the cost of the app, monthly fees, package costs, and so on. If the revenue stream of the product is advertising, then you should consider putting examples of how ads might look on the prior screens. Let’s return to Bita and Ena, my students whom I introduced in Chapter 3, to see how to make a successful solution prototype. Step 1 Write a simple list or an outline of the screens you are going to show. It’s going to potentially include one or two key experiences. As with the storyboard, you want to really distill out the details that you need to show. Bita and Ena wanted to show the screens from their storyboard but with more details. This was the list they wrote: 1. The landing page with the user’s query entered 2. The result set with the listing and the maps and the filters exposed 3. A filtered result set with the listing and the maps and the filters closed 4. A result detailed screen 5. A photo gallery featuring images of a home, specific to the wedding 6. The package options with pricing 7. The tour setup screen 8. The confirmation screen with final pricing, including cost of service Notice how all the steps of the solution prototype refer to the experience online. That’s because this is what Bita and Ena need to test: does the digital product solve the customer’s problem?
UX Strategy: How to Devise Innovative Digital Products that People Want Page 188 Page 190