Turning Customer Complaints into Design Requirements: A Practical Guide

Demand Analysis

Design work fundamentally solves a business's commercial needs; before starting a project, identify its core KPI. For example, adding a timeline feature in an app aims to boost overall user activity, not just to create a timeline.

User Persona

After understanding business goals, interview existing and potential users to learn why they use the product. From these insights, create a User Persona that describes the target users, their motivations, and concerns.

User Scenarios

Consider real usage contexts, such as commuting by subway, where network stability, one‑hand operation, privacy, and audio vs. text communication matter.

Is mobile network smooth during the subway ride?

Can gestures be performed with one hand during peak hours?

Is screen privacy a concern in crowded spaces?

Is voice or text messaging more effective in noisy environments?

Understanding these scenarios helps address assumptions, such as adding cache for poor network, optimizing one‑hand gestures, and providing voice‑to‑text conversion.

User Journey Map

Use a timeline to visualize the entire user experience, identify pain points, and extract optimization opportunities.

Example: European rail user experience map clearly shows user pain points and product opportunities.

Define the Problem

Summarize research insights into a single sentence that clearly states the user need, serving as the focal point for design thinking. Do not propose solutions at this stage.

Example (food delivery): Clearly describe the user problem without offering a solution.

Summary

By understanding user backgrounds and needs, we can help them achieve their goals in the app, thereby fulfilling the product’s commercial objectives. This process converts product requirements into true design requirements and provides a guiding principle for design direction and proposal justification.