One of the few ways I go about uncovering user needs is PRODUCT DISCOVERY.
A good chunk of our time should be spent in the problem space. The stage we are in dictates the amount of time we dedicate to discovery versus delivery. 1/5
Most times, we find that product teams gloss over the problem space (Research, Problem Immersion & Definition) and directly into the solution space without adequate exploration and validation(Build/Prototype, Measure, Learn). 2/5
Product Discovery is a great method to solve for what customers really want, and what exactly to build. It is a bunch of research and activities both qualitative and quantitative. 3/5
.
#ProductManagement #ProductDiscovery #ProductManager
Qualitative measure sentiments and intents; helps to develop empathy and know the customer’s perspective. Quantitative, of course numerical, comes from user data and testing - behavior and engagement analytics best measured with a product analytics tool. 4/5
Product discovery artifacts(Journey Map, Empathy Map and Personas) enables continuous discovery keeping user data top of mind.
More on these artifacts in another post. 5/5

#ProductManagement #ProductDiscovery #ProductManager
You can follow @DiVaBeaW.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.