5 UX questions to start redesigning a digital product
Before redesigning an existing digital product, it is an essential to get a solid understanding of the brief. Therefore, you will need to be a good listener and ask relevant questions of your client.
If you don’t ask questions, you will end up wasting a lot of time to redesign the prototype because it won’t match the user and business needs.
In order to create a valuable and meaningful user experience for a product, these questions are a good starting place to get an understanding of the client’s background, its target audiences, its expectations and its business goals.
1. Basic brief of company/business/product/service(s)
- What is your business/company/product/service(s)?
- Can you describe your business in few sentences?
- Why do people buy your product or service?
- Who are your competitors?
- What differentiates you from your competition?
2. What problems they are solving
- What fundamental business problems/issues/challenges do you want to address with this website? (E.g. the traffic is decreasing, users don’t know how to use your product, etc.)
3. What their profit model is
- How does your business make money?
- Describe the typical touchpoint–to–sale process for your company.
4. Who their users are
- Basic demographic: Gender, location, income, roles, background, etc.
- How many users do you have now?
- Who is your typical customer?
- What type of person do you want to visit your site?
- Where/how do people learn about your company/product/service? (E.g. events, advertisements, social media, universities, etc.)
5. What you want them to do
- What action(s) do you want a visitor to your site to complete? (E.g. Sign up to a newsletter, buy a product, follow your Twitter account, etc.)
Establishing some basic user experience guidelines and objectives helps us to get started efficiently.
In your experience, what questions have you found helpful to ask your clients? Please share with us in the comments.
1. Design Is a Process, Not a Methodology http://www.uxmatters.com/mt/archives/2010/07/design-is-a-process-not-a-methodology.php