Six Principles of Demand Analysis

 

Six Requirements Analysis principles (1) Never look smarter than customers

1. First Principle of Demand Analysis: Never be smarter than customers.
Smart people are more intelligent than smart people.
2. Principle 1: understand the needs, rather than criticize the customer.
Product managers are not critics. They must focus on customers psychologically, respect customers in action, and treat each customer equally.
3. Principle 2: customers are more familiar with the business environment than you.
The product manager is only familiar with the product itself, but the product manager is not only familiar with the product itself.
4. Principle 3: The real problem is only known to the customer. What we need to do is to make the customer willing to speak out.
The customer will give you feedback, but some of these feedback are true and some are perfunctory. If you want to be truthful or perfunctory, please refer to the first principle.

Six Requirements Analysis principles (2) Respect users' practical choices

1. Demand Analysis Principle 2: respect users' practical choices.
Products are objective, users are objective, users are objective, and needs are objective. Everything is realistic.
2. Principle 1: the customer is always right.
Customers are not our enemies, and customers will not harm us. The customer's demands seem to embarrass us, but they are essentially trying to make customers better use their products. Therefore, customers will not embarrass themselves.
3. Principle 2: provide the most appropriate solution, not the best or most expensive solution.
What we can do is not necessarily the best. What we don't want to do is sometimes what the customer needs most. Find the most suitable customer, not the most suitable one.
4. Principle 3: Do not treat customers as fools.
There are no dummies in this world. The talents who think they are dummies are really dummies. Don't fool customers, don't cheat customers. If you have to add a deadline before this, I hope it will be "forever ".

Six Requirements Analysis principles (3) The person who expresses the requirements is also the customer

1Third principle of Requirement Analysis: third parties are also our customers.

As long as we demand our products and services, our customers should be treated equally.

2Principle 1: third parties generally think of themselves as designers.

They may be familiar with products, but may be unfamiliar with the entire business. Therefore, they cannot become designers.

3Principle 2: third parties may omit or supplement some additional requirements.

Everyone expects the product to be well-prepared. This strong success mentality will easily cause people to feel dizzy, thus affecting our screening of needs.

4Principle 3: Do not complain or get angry with a third party's free play, but treat it as a customer.

Customers are the first, and they are our customers. Therefore, we should treat them calmly, whether out of public or private opinions.

Six Requirements Analysis principles (4) differentiated treatment between customers and users

1The fourth principle of Requirement Analysis: customers and users should treat each other differently.

The customer is the customer, the user is the user, sometimes consistent, sometimes separated, this is the first thing we need to understand.

2Principle 1: The product is designed for end users, and the required functions are converted to the requirements of end users.

The user decides the product, and our requirement work is based on the user. It begins with the user and is attributed to the user.

3Principle 2: Find value-oriented demands for customers.

Customers are diverse, and value orientation is also diverse. Whether our products can carry diversified customer values determines whether the products can achieve the final exchange.

4Principle 3: the interests of users are higher than anything else.

The final value of the product is embodied by the user, and is separated from the user's product, that is, "No skin is saved, nothing will be attached ".

Six Requirements Analysis principles (5) use the simplest text tool to record requirements

1Requirement Analysis Principle 5: Use the simplest text tool to record requirements.

The customer is not in trouble, and the demand is not complicated. The trouble is that we make everything too complicated.

2Principle 1: What everyone can understand is the least error-prone.

No one prefers complicated things, and the demand is no exception.

3Principle 2: things that do not need to be learned are at least prone to errors.

A product is a manifestation of a requirement. No one prefers a complex product. To do this, start with the requirement.

4Principle 3: do not want the customer to spend more time understanding the prototype after the requirement is converted.

If I pay for something, the customer can save some trouble and the customer can save trouble, and we will eventually save trouble.

5Principle 4: smooth communication is a guarantee for understanding the needs

To achieve clear requirements, we need to reverse communication.

Six Principles of Demand Analysis (6) no free lunch in the world

1The sixth principle of Demand Analysis: there is no free lunch in the world.

To get it, you must pay for it. The amount you pay is not necessarily equal to the amount you get. As a product manager, you must make the customer pay as little as possible and get as much as possible, but it will never be free.

2. Principle 1: customers have never had unreasonable demands.

The customer's requirements are both realistic and reasonable, because these requirements are objective, but we are usually used to subjective view.

3Principle 2: customers' requirements can be fulfilled.

There are no insurmountable requirements, but we do not know enough about them.

4Principle 3:We can do this-this is the cost.

Cost first and demand first. Once the customer gives us the problem, we use our wisdom to solve the problem.