Since himself after the first APP development, has been has become an independent developers and then to the entrepreneurial path, so has been on the products, design with extremely high enthusiasm, so this time to attend meeting to share the products for myself, obviously is the place where you can learn a lot, also very happy, a meeting can face, oh, according to the relational database, This should be a one-to-many relationship, but unfortunately for the participation of the little sister will speak, after the two sharer on stage, became the relationship of many to one…

In fact, before attending this sharing meeting, I always thought that today’s product world can be divided into two types, one is innovative products, the other is copycat products. A truly innovative product is one that can start from scratch, go from zero to one, and take up a significant share of the market, that is, the leading product in its industry. Why do I think so myself? As far as I am concerned, it is meaningless to innovate any other product that is at the bottom of the market, because it cannot withstand the test of the market, so its innovation is of no value.

What is the innovative product in my mind? Such as Luo Zhenyu’s Get APP, Zhou Yuan’s Zhihu, Zuckerberg’s Facebook, snapchat and so on…

So what’s the second product? Is making the products, according to the law of the market follow a catch doll machine APP fire, followed by countless catch doll machine production of APP, that is to say, to do the product manager of this product does not necessarily need more good product awareness, don’t need more than a good user experience, only one thing to consider, what is the market that make money, I will do what product, But such a product is never do small, but can ensure that the company will not be eliminated by the market. Therefore, I have always been respectful of the first type of product, hoping to learn something from the first type of product manager, and this nuggets sharing meeting can indeed let me learn a lot of things in this respect, I will organize the following things I learned.

36K Product Manager – Share with Teacher Shen

  • process

Mr. Shen’s explanation process is mainly about his own revision process in the new version 36 krypton. Although Mr. Shen is a product manager born in technology, he shares the whole revision process from the perspective of products.

The whole process of sharing can be roughly divided into three parts: asking questions -> understanding questions -> solving problems

Questions: When the CEO puts forward the demand from the company’s strategy, different departments will decompose it into the demand that each department needs to meet according to the CEO’s strategy. The content department needs more explicit content display and richer display effect. Operations need more interaction; The sales department needs more advertising space, higher KPIs…

Understanding the problem: What is understanding the problem? In fact, the first thing to do to understand the problem is to decompose the problem (understand the goal, sort out the requirements), here we need to use different ways to understand the problem, what is the difference? Different Angle! Understand what the requirements are from the company’s point of view, understand what the requirements are from the product’s point of view, and understand what the requirements are from the user’s point of view. When you can understand what the problem is from different points of view, you can combine these requirements and you can understand the requirements!



Understanding the requirements is only the first step to understanding the problem. Then you have to choose the requirements! Because not all ideas are correct, there may be a part of the demand from the beginning is just fake demand, or the cost of implementation is very high, but the benefit is very small demand, this demand has no value of existence, can be cut! This was the first time I knew that there were requirements that could be cut, which reminded me of a well-known saying in the industry: “Average product managers add, good product managers subtract.” So understanding requirements can be divided into two steps: first add, then subtract.

Solve a problem: “Teacher is the way to solve the problem, I’m a little surprised, his approach was first longitudinal comparison, look at 36 kr this product many times the difference between different iteration, and the horizontal comparison, the difference between different products compared with other types, the decomposition products, from them, find out the commonness, and the distinctive differences between different products, and then according to modular combinations. The advantage of this approach is that it focuses on the market, and if it can integrate the strengths of many people, it is also possible. Just like Ruby language, it will also be liked by many people, but the disadvantages are obvious, others’ products will inevitably limit our thinking, which is not conducive to innovation.

If IT were me, I would make a preliminary version in my mind before analyzing other products. In this version, I would release my imagination and creativity, and then add the analysis and comparison of other products to make the final plan. Of course, a thousand Hamlets for a thousand people, there is no right or wrong, but everyone’s way of dealing with it.

  • feeling

In the whole 36Kr iteration process of Teacher Shen, I was deeply impressed by several points:

First: No matter what product, no matter what product manager to solve it, it is always difficult at the beginning, there are not so many overnight, are to step by step analysis, step by step to solve

Second: don’t always think about the addition of the product, to understand that subtraction is sometimes more important, is that why there are so many white space in Chinese master landscape paintings?

Third: in the process of product solving problems, the analysis of competitive products is always crucial, and it is absolutely not desirable not to pay attention to competitive products!

Mr. Gao, product manager of Ele. me

process

In the process of more products from 0 to 1 mentioned by Teacher Gao, the relationship between business, product and technology is more shared and the technology is how to meet the needs of business, which I am also more interested in.

At the beginning of the introduction of the product process: validation mode – build system – improve the system

In the 0-1 process, there will be a lot of questions (validation mode – build system)



So what’s the most important thing in all of this?

First is the core appeal of the product!

According to the detailed background investigation, understand what the core appeal of the product is, according to the core requirements can determine the rhythm of the development of the entire product, as well as the function points built on the core requirements. What is rhythm? You know what to do at a certain stage, rather than having your rhythm taken by others, which is also what I mentioned before about all products that imitate the market, will be taken by rhythm.



The second is the structure of the product!

The product structure is divided into two aspects: business extensibility and business satisfaction

There are many points of business satisfaction:



One of the most impressive points in my speech is the extensibility of business! That is, the expansibility of the business needs to be considered in the code framework from the very beginning. In the early stage of code design, the overall structure of the code needs to be based on the expansibility of the business. It is rumored that one of Tencent’s architectures has been used for ten years! It can be imagined that at the beginning, its logic is considered how comprehensive! Its business expansion is excellent!

feeling

In cocoa expanding business, there is a need to pay attention to the problem, that is often alternative = = plan for a long time, that is to say, on the structure of the code, fluky psychology should not be there from the start, need to look at problems from the Angle of architecture, want to start the deployment of a scalable software architecture of high, remember!!!!!!

Front little brother – Miss Liao share

Perception: It is a very satisfying and interesting thing to realize an Idea by yourself!

Rare earth product designer — Mr. Li

Insight: Build a set of my own models to realize my unique understanding of product requirements.


Listen to the whole thing, I learned a lot, but the activity was held in the afternoon, it was asleep in the middle of the way, and there was no water to drink, it was a big failure ah ~ flaws not overshadowed, I hope to do better and better!

Finally, I conclude by myself:

1. Product subtraction!

2. Analysis of competitive products!

3. Business extensibility == code architecture extensibility!

4. The Design!

5. You can build your own model for many things!