Today’s product development efforts focus on testing, experimenting, and getting feedback on features and functions before developing them. These new techniques and schools of thought are exciting and (if the posits guiding the features are good) should improve the abysmal success rate projects experience in delivering stuff people actually use. All too often, though, user stories that are skillfully refined, defined, decomposed and successfully delivered are ultimately deemed “bad” because people don’t see any value in the finished product. That’s where the product assumption map comes in. This map helps product owners and their stakeholders better align their assumptions about what their product is expected to do and the people they believe will use their product. This creates a repository of assumptions that can be explored and validated before committing time and money to experimenting, designing and building the functionality.
The product assumption map improves the quality of user stories by creating a visual representation of the things the product is expected to do (supported roles) for the intended users (actors). The first contribution the map makes are the conversations regarding the things people will be able to do using the product, which define the roles the product supports. Everyone who has been engaged in this (stakeholders, product management, designers, etc.) should be involved in these conversations. At this stage, the map focuses on helping the product definers recognize that they could have very different people with different perspectives wanting to do the same type of thing in a product for potentially different reasons.
One reviewer, an experienced agile coach, believes this map could fill “a hole in the thought process and design that I have seen in almost all clients that I have worked with.”
Product Assumption Map: The Approach
The approach is straightforward: [Read more...]