<aside> 💡 Vision Product teams will build products based on user insights gathered every week

</aside>

<aside> 💡 Mission Making it easier for product teams to do user research to Identify opportunities

</aside>

What are the problems Product teams face?

• Everyone agrees listening to users is important, but doing that on a continuous basis is quite hard
• PMs have to balance multiple Jobs - Ongoing sprint discussions, writing PRDs for Identified opportunities, User research, and collaborating with stakeholders
• Often urgent matters take precedence over what is actually important - Listening to your users
• Even if you decide to prioritize Listening to your users, It takes a lot of time. and effort - sometimes days and weeks to come up with original, fresh insights

Here’s what the process of understanding your users looks like:

• Establishing the objective of user research
• Figure out which users you need to talk to
• Specify what questions are you going to ask users
• Actually listen-listen to call recordings, do the calls yourself or with some help
• Document the user’s answers by writing them out in a document/excel/ sheet
• Summarisation of the research, to prepare data that answers the objective
• Publish the insights in a consumable format for stakeholders
• Answer follow-up questions from stakeholders - What did the users that did X say about friction in using flow Y?

<aside> 💡 Well, that was a lot. Imagine doing that every week There needs to be a way to do this important process more efficiently

</aside>

What Voice insights can help you with: