Product Discovery defines what should be built – and why. Collaboration Is Key. Your success with agile development depends on delivering the right product requirements at the right time.
During the past few years when I have been working as Lead UX or Product Owner I have come to a core process of how to do the discovery. At my latest gig on Viaplay as Chief Product Owner I had great use of some of these methods and also found it to be a great tool to have it visualised for all Product Owners in a one pager.
Within this process I see lots of different methods that may be used.As I use it I pick different methods in each level depending on organisation, product or project. Sometimes not all steps are neccesary off course. When working methodically for some time you start getting a feel for what seems like a good ide or not.
In this post I’m presenting a framework of the process as well as the methods in short formats. I will try to post more in dept posts on some of the methods going forward. Please let me know what methods you would like to know more about 🙂 Hope you find it useful in your daily work.
Download the one pager for Product Process and Tools here >
Here is my blogpost on the product development process with a continuous discovery and delivery process with one team >
Note: Due to some lazyness there are some Swedish material in this article also – sorry for that!
1. Strategy
Why are we doing this? What is the goal & desired impact?
1.1 Concept
Concepts enables people passionate about a product idea, regardless of role, to realise it all the way to happy client. Concepts is a one page specification, in A3 format that represents a product idea of feature. It is enough to enable a prepared conversation with engineers developing the product. Think of it as a “flexible minimum specification”. Mattias Skarins blog post on this http://www.crisp.se/concepts
Here you can download the Concept template I have created from Mattias Skarins examples > (more…)