Skip to main content

Technical

The Importance of Discovery UX in Product Development

Over the years, we watch products come and go, some products grow high, and others don’t make the cut. Why is that? Imagine for a second that you are an entrepreneur or you work for a company that needs new products to be competitive and innovative.

Maybe the first question that comes to your mind is: is the right product? Is this the right approach? Design is much easier when you ask the right questions; the heart of the matter is to discover what they are for in each case and how to organize them. Share and use the feedback obtained to see the whole picture.

Discovering may answer all your troubles because it leads you the right way. Although each project and context will indeed vary greatly in the focus of our questions, I have tried to condense in a general way some questions for different cases that will undoubtedly allow us to receive meaningful feedback and thus help avoid assumptions when making design or strategy decisions.

For that reason, let me walk you through the process:

1. Discovery

This is the stage where we focus on digging up the major information that we could have. First, we should start with interviews with our stakeholders to understand their points of view, requirements, and restrictions, monitor customer service and find the most data possible to define UX´s metrics.

2. Explore

Part of the work here is to find what others are doing. We start by doing research and benchmarking all the competitors out there, journey maps, card sorting, and developing the UX personas, to define the customer we are to center our design.

3. Testing

Now that you have all the information, it is time to get things done. We have a prototype that is crucial to testing and monitoring the results. Reach out to social media and read what the customer feels, evaluate accessibility, do the benchmarking, and redirect if you have to.

4. Hearing

If you are here now, congratulations, you made it so far, but you need to do a lot of work. You must create surveys, check for usability errors, and Q&A in talks and demos. Primarily to collect qualitative feedback, these are opportunities to complement these findings with answers and results.

Always remember design and documentation shouldn’t be a headache. It’s essential to make the best of the information and check how this could be helpful for you and your team to be on the same page and achieve great results.

Good luck on your journey!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Javier Blanco

More from this Author

Categories
Follow Us
TwitterLinkedinFacebookYoutubeInstagram