Product managers must have the consciousness of "decoupling"

For product managers, structured thinking is one of the indispensable qualities. This article focuses on the structured thinking in the work, combined with the case to explain the importance and criticality of the combination of business knowledge reconciliation and coupling ability in the process of product design. Recommend product partners to read and learn ~

Decifferent, essentially a structured thinking.

Students who have passed the civil servant should know the meaning of structural interviews. Mirror students believe that structural thinking is particularly important for product managers, because this is the bottom cognitive basis of product thinking.

Maybe you will find a phenomenon in your daily work:

There are so many people, no matter when you communicate with him, his answer is always very layered.

For example, when you ask him a question, he will tell you that he has three views about this problem: first of all, you may describe the reason for the problem itself and the problem; secondly talk about the solution of the problem; harm.

This is a very simple problem decision model, but it is enough to explain that through structured expression and continuous practice, it will make it easier for you to see the essence of the problem and make the understanding cost of target users lower.

Structuralization is easier to get close to essential needs, and the key to structured itself needs to clear the boundaries between different structures. There must be a clear structure level, which often means that the differences and boundaries between different structures need to be identified.

This is the true meaning of decoupling: divide different fields.

And this is very helpful for product managers in the full life cycle of demand surveys and product design. It is no exaggeration to say that if you want to be an excellent product manager, you should consciously improve your decoupling ability.

In order to facilitate your understanding, I will give a small product case:

Because a certain business department of our group proposed a new business demand, then the business services of the online course, which requires us to design the product design of the online course. Requirement research and competing product analysis.

Let's briefly introduce our product planning. In fact, the business logic and product design of the 1.0 version are also very simple. Users are divided into the operating side of the student, the teacher side, and the platform. The basic business scenario is:

The teacher applies for the platform, the platform is settled for review. After the review and passing, the teacher can post videos, trainees can place an order to buy courses and perform online payment. After completion, you can watch video learning online.

Last Friday, we reviewed and discussed the investigation of product managers and the analysis of competition.

Among them, in the analysis of the competitive product of the operating platform, she talked about a product design about orders. She found that there are two first -level menus in the "curriculum order" and "payment order". You need to add the payment information in the course list list or details.

She thinks that there is no need to do separately, a menu function can be solved. Isn't it a waste of development resources?

If you are doing this product analysis, how would you understand?

In fact, if you have enough business knowledge, you will understand that these are two business areas. You know that product design should be separated. Different field events should be decoupled. This is not redundant Refined.

We briefly analyze:

First, we must have basic business knowledge:

Everyone must know that for e -commerce venues, orders are the carrier of transactions, and transactions are generally three -streams. For example, business flow, also known as business flow or cargo flow, capital flow and invoice flow.

Obviously, the course order here is the business flow, the data processing of the user's order, and the payment order is the capital flow, the processing of funding information, or you can simply understand it as a financial account for financial accounting. Essence

Therefore, the two are facing different business scenarios, of course, they should be decoupled, and the products should also focus on.

In terms of 10,000 steps, you can reduce the payment information in the course order, but it must be two areas, which must be decoupled. The order order must be the order status. Pay orders should be called payment flow.

We should still keep two in mind:

The product is the carrier of business and business. When designing the product, you must consider business scenarios. Different business scenarios are bounded, and decoupling should be decoupled in different fields, so that technical liabilities can be avoided in the future. So you see, on the basis of sufficient business field knowledge, you must learn to decide the business field. This is the key to designing products.

In fact, for software development, product managers are the key source of the source. We should have awe. In fact, only when we have enough knowledge, we can avoid technology from the source after we have a lot of knowledge and the thinking of the field and boundary. Liabilities.

All this may require us to have excellent product thinking when designing the specific product design, and to have the awareness and structured ability of decoupling. Of course, the most important thing is to have boundary concepts and the courage to break the world.

The so -called broken boundary is not the border of the external reality, but the boundary of the internal cognition.

As the ancients said: small knowledge is not as good as the big knowledge, and the cognition is endless.

#Columnist#

Product Grand Canyon, public account: Product Grand Canyon, everyone is a product manager columnist.Seven -year B -side product manager, supply chain logistics and financial fields, good at demand design, business guidance, business observation, etc.This article was originally published by@本 本 本. Everyone is a product manager. Reprinting is prohibited without permission.

The question map is from UNSPLASH, based on the CC0 protocol.

- END -