Who will use this requirement?

Are they our target users?

What proportion of these users account for our users?

What about user attributes?

The more realistic the scene, the more real the needs.

The high frequency of the scene determines to a certain extent whether the demand is high frequency, which naturally determines the performance of your product data.

It is possible that this scenario is not consistent with the scenario provided by the current product.

The scenarios used by users are indeed inconsistent with the current scenarios of their own products.

Listen more to user feedback and watch more user operations. If you can't contact users, try to simulate the user's scenario and experience and use it yourself to find the current problems.

Sort out the user's current solution, including but not limited to the user's operation process, functions used, products, and input content.

What users need to do in our product to fulfill this requirement is probably a basic operation path for users. At this time, we need to pay attention to the diversity of tasks. (Diversity means that there may be many ways to meet this demand. You should think of at least two and know their advantages and disadvantages.)

In order to meet this demand, what function/page do we need to create for users.

Why the user should do this and what benefits he can get from doing it are the driving force for users to use the product/function.

Why do we do this and what are the benefits to us? It’s best to have quantitative standards!

It is determined based on your needs and purposes and existing data, not based on imagination.