Question | Evidence |
---|---|
What problems do people have? | |
What types of people have those problems? | |
How are they currently solving the problem? | |
What sucks about the solution? | |
Question | Evidence |
---|---|
How many people are facing the identified problem? | |
How interested are they in a solution to the problem? | |
How valuable is a solution? How much are they willing to pay? | |
How well does the proposed solution line up with their needs and wants? | |
Question | Evidence |
---|---|
How well do these designs hold up the promise of the proposed solution? | |
How close are we to this solution being ready? | |
What nuances come up when users interact with the proposed solution? | |
What assumptions are users making based on the proposed design? | |
Which features are most important? Most urgent? | |
Question | Evidence |
---|---|
How do practical limitations impact the experience? | |
What tradeoffs are acceptable? | |
How does the solution interact with the broader ecosystem? | |
Question | Evidence |
---|---|
Who is more interested in this solution? | |
How do they learn about new products, services, technologies, etc? | |
How easy is it to adopt our solution? Where are people falling out of our conversion funnel? | |
How flexible and scalable is the solution? Does it apply to a variety of use cases? | |
Question | Evidence |
---|---|
How are people using this solution in real life? How well does it fit into their workflow? | |
What are the most popular features? the least? | |
What are the most common feature requests? | |
Where are people getting stuck? Why is that happening, and how do we fix it? | |
Question | Evidence |
---|---|
What are the existing alternatives available for this solution? | |
What transition costs are associated with moving to a different solution? | |
What support will customers need to make the transition? | |
How much time do they need to plan and execute a migration? | |