The boundary and outlet of products

Every product has a boundary, and the so-called boundary is actually its framework, and then what scale can it reach.

Borders are often established when the product is just decided. The border is very big, but it is rare to be killed by the team. However, the boundary is not big, and the team is eager to add various functions and contents, and there are many cases of forcibly expanding the boundary. These situations are all fueled by pulling out the seedlings and are basically easy to die. It is important to determine exactly where the product boundary is, which can reduce the waste of R&D and operation. Of course, it is also one of the most difficult skills for product managers to build a reasonable product framework and find out where its boundaries are.

If the boundary of your product has been discovered during your development or operation, you will begin to fall into a kind of pain, because you are trying to expand the boundary and want to introduce new users. So I began to embrace "expand the boundary, make a big revision without adding functions, and change the project without changing …".

A product can't be said to be much better, but it will definitely stabilize the daily life and the monthly fire. In fact, popular products cannot be maintained for a long time, so we need to find some other ways out. First, we should make our products distinctive and have a stable profit model. If the activity is not as high as expected, we can earn the cost of team survival. Second, try to find a stable activation scene. Your product may not be sticky, but users will think of opening this product in certain scenarios. Third, users are constantly losing, but at the same time, some users are deep users, and the data generated by some users with long timeliness will enhance the value of products in a certain period of time in the future.

A senior made a product. At the beginning, he predicted that the daily activity was low and the number of users was 60, but there were still hundreds of UGC every day, and most of them were accurately bound with POI, which became high-quality structured data. Even if the last day's work is not satisfactory, the accumulated content of this product has no commercial value.

Therefore, products have product boundaries. If we consider the product boundaries from the beginning, then you won't worry in the middle, but then again, how can we let you see all the product boundaries? Many people still go step by step, but don't panic when the boundaries of our products come to an end soon. What you have to think about is how to find a way out. It's really not good to change the product "wash your hands" and continue to play a game.

* * * That's all I want to share this time * * *

* * * Purpose: This article is mainly to share the content * * *