Notes from User Story Mapping
A small, cross-functional team led by a product owner orchestrates product discovery work.
Discovery isn’t about building software
Discovery work isn’t about building shippable software. It’s about learning. It’s about building a deeper understanding of what we could build. It’s about asking and answering questions like:
- What problems are we really solving?
- What solutions could be valuable to our organization and to customers buying or adopting the product?
- What does a usable solution look like?
- What’s feasible to build given the time and tools that we have?
Prioritize specific business goals, customers, and users, and then their goals, before priortiziing features.