<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/aed44678-a66d-4f30-b3c9-cf696038f4f9/Kentico-logo.svg" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/aed44678-a66d-4f30-b3c9-cf696038f4f9/Kentico-logo.svg" width="40px" /> Hello UX community, we're happy to share our knowledge and resources with you, but also, we're super keen to know how those resources helped you and how you improved them. So please keep in touch with us at [email protected]. Cheers!
</aside>
A discovery is a preliminary phase in the UX-design process that involves researching the problem space, framing the problem(s) to be solved, and gathering enough evidence and initial direction on what to do next. https://www.nngroup.com/articles/discovery-phase/
Five common misconceptions about Product Discoveries.
Five common misconceptions about Product Discoveries.
Design and development projects are highly multidisciplinary with team members with a variety of skills and vocabulary use, sometimes with conflicting definitions of terms. A kickoff meeting can make sure everybody is on the proverbial same page regarding all the team members' skills and responsibilities. https://www.nngroup.com/videos/kickoff-meetings/
<aside> 📌 The kick-off workshop is the first activity during the Product Discovery.
</aside>
https://www.youtube.com/watch?v=5ij0Vb7EXIk
Roles | Responsibilities |
---|---|
Product Manager | • sharing product and business perspective |
• sharing assumptions about the target group | |
Technical Leader | • active listening |
• Devil’s advocate (asking anything) | |
UX Researcher | • catching potential research questions |
• Devil’s advocate (asking anything) | |
UX Designer | • facilitator of the workshop |
• taking notes |