How to Turn User Feedback into Prioritized Product Requirements

Background

This year I was responsible for iterating two features—Linglong Video and Linglong GIF—both of which address e‑commerce designers' pain points but lack systematic optimization. After extensive questionnaires and user interviews, we collected a large amount of feedback and needed a method to distill real user needs and drive concrete improvements.

1 Think from a Global Perspective

Before diving into individual issues, consider the overall picture:

Who are the target users of this product/feature?

What is the goal of this iteration?

Answers to these questions guide subsequent filtering and positioning of requirements.

1.1 Target Users

Before iteration, create a target‑user persona based on the product’s positioning. Personas help summarize typical behaviors within the target user range and guide analysis. Even without extensive qualitative research, existing data and informed assumptions can be used. For Linglong Video, deep user research (online interviews and surveys) produced a target‑user persona, providing a solid foundation for optimization decisions.

1.2 Optimization Goals

Different development stages have different optimization goals. Clarifying the current most important goal is essential; the goal acts like a flag guiding direction.

For Linglong Video, the first major version focuses on generating a main‑image video from a SKU or image, targeting small‑to‑medium merchants who need efficient, low‑cost video creation. Since the product is newly launched with low user volume, the current stage is promotion, and the primary goal is to increase users, retain them, and improve adoption of design results.

2 Extracting Requirements from Feedback

After defining the optimization direction, we extract actionable requirements from feedback using three steps: Filter – Connect – Analyze.

2.1 Filter – Does it match user expectations and iteration goals?

Evaluate whether user feedback aligns with the target‑user expectations and iteration goals. This quickly discards non‑core issues.

Example: Some users request advanced video‑editor features. This does not match the primary user expectation for simplicity and is a high‑level feature not needed during the growth stage, so it is excluded.

2.2 Connect – User Experience Map to overview the whole flow

After filtering, connect issues using a user experience map to see the overall process and avoid missing important parts. For Linglong GIF, we added the product‑awareness stage and downstream usage to the map.

2.3 Analyze – Reconstruct scenarios to uncover the essence and find optimal solutions

Build a complete narrative (person, time, place, goal, action, result) to clarify usage scenarios, trigger conditions, and constraints, thereby uncovering the true need and identifying the best solution.

3 Prioritizing Requirements

After extraction, we often have many potential improvements. With limited resources, we prioritize based on three factors:

Coverage : How many users are affected?

Frequency : How often does the issue occur?

Satisfaction impact : Use the KANO model (Must‑be, One‑dimensional, Attractive, Indifferent, Reverse) to assess impact on satisfaction.

For the GIF export issue, coverage is high, frequency is high, and it is a Must‑be requirement, making it a top‑priority improvement.

Conclusion

After ranking, design output and resource coordination follow. The initial user persona and iteration goals continue to influence the entire implementation process, making early global thinking essential.

These are my reflections on requirement filtering and analysis after iterating two features this year. Thank you for reading.