David Schenberg’s Post

Transcript

So we need to create something new that is customer facing where the customer may be internal customers of the business or externally facing customers. To be effective, we're really going to want to understand the personas or users of this application and the must have features to be effective for an initial minimum viable product or MVP. This will be something with enough features and functionality to delight the users and create a wonderful experience that we can grow from. To get started, think about a recent ethnic restaurant menu you may have interacted with and the number of pages and items to choose from. Now imagine walking back into the kitchen to find a prep area with maybe a dozen ingredients that somehow create this massive selection of dishes. What does this analogy have to do with the delightful product development experience? Well, to satisfy different users, we first define the functional areas of our new user experience as the facets at the center. The Spider Web 6 to 10 different ingredients required to assemble a complete user experience. We use this visual web when designing an MVP so the group can decide what features must come first and how early feature adoption will teach us about our users and what they need. For example, new users need a way to enter our application for the first time. How secure? How easy do we use single sign on for an internal app or a Google or Facebook account? Or a personal experience. Once we have a secure user, they'll want to create more of a personal profile for a personalized experience. Each layer out from the middle helps us to build on the previous one. As we gain more data to customize the next layer out, we can define as many layers as we want and decide later what's included in the MVP.