Some thoughts on the beta version of the product

After roughly planning a new product, by the time the previous trial versions were launched, I called the beta phase. The goal of this phase is to test the user's reflection and validation of the product planning process on the market. In general, companies need this phase to achieve positive results, will continue to invest.

Leader said this stage is very exercise PM's ability, temporarily first summarizes this time to work some ponders.

1 think more when planning.

Whether multiple terminals: pc-client, Web, mobile, different terminals because of the use of different scenarios, function and content design, and operating methods will be different. If it is a multi terminal development project, it is clear that different terminals in the overall product planning status and role is different, the first plan under the different terminal function shape, decide what the beta version to do first, and how to expand to other terminals.

Do you have multiple entrances: What access will users get to our products? It may be our own channel or other platform. What scene will users receive or see our entrance, how to design the entrance to guide users to quickly enter our products? How do I boot the installation? Do I need to log in? What portals did the first users introduce?

Functional scope: The scope of the function includes: the scope of the applicable user, the time and geographical scope of the application, the type of content and the scope of the source, etc. Will the scope of functionality be expanded in subsequent versions? What are the necessary functions?

Business Plan: How many users can be in different stages?

These remember to communicate with major development, usually experienced development will ask. Because the development plan is also to start from scratch, need to take into account future compatibility.

2 The first version to do less.

Although the beginning of a lot of thinking, but the first version, whether front-end product design, or back-end function, performance, to find a minimum feasible version, with the simplest form to achieve a core value, to a small range of target user groups. Minimizing a viable version is used to validate requirements and to avoid wasting resources in a wrong direction.

Personally think this is the beginning of 0 to do the product of a major difficulty. How to find: only to do the core functions, as far as possible do not need to login, the interface is the most simplified (not even interface!) ) and do not consider any revenue targets.

Perhaps the first version of the product, not even need to be an independent product!

There is an extreme idea, if I have to test an idea later, I will reach a small number of target users to a "closed activity", to publicize my imagined products, see the proportion of interested users. If the user is not interested in this conceptual model, why should it be developed? Really regret that the product you are doing is complicated.

3 to start by trying to figure out how to validate requirements.

What data do you use to explain this product? The reason? Is the basic assumption consistent with the old product data?

4 operation and operation.

What kind of concept to tell users? How did the first batch of users come? What can be done to promote the spontaneous spread of users? What resources need to be prepared in advance as the subsequent version of the iteration is to match the business plan?

The first version may only need to consider the first 2 questions, but soon the operational problem will become more and more important to integrate into the product design.

5) Grasping resources and time.

Although this is what the project manager would like to do, but as a qualified product dog, but also to understand whether the team under the other tasks, whether it will be suddenly transferred to do other things, some of the necessary resources are not configured well, progress has no problems.

If there are resource issues, dogs may wish to communicate with their superiors.