The revision is not as beautiful as everyone imagines, from a very ordinary product to a very high-end product.
Most product revisions either only involve a few core email list interfaces or some business modules.
Therefore, the revision of different products at different stages will actually be limited by various conditions and the current situation.
The revision should not pursue large and complete, but consider maximizing the value of limited resources. Maybe you have made changes to the homepage and added some small modules, but the cost performance will far exceed changing the entire product.
4. Program Results
It is suggested here that you must prepare 2-3 types when designing the plan. During the revision process, you will encounter many business conflicts, so we cannot make accurate decisions at our level, so in the later review process, you can Take different situations together and let the leadership make a version.
3. Late stage of the project
1. Risk Control
The revision is a double-edged sword. Good revisions are all happy, and bad revisions are not bad, but they are also very troublesome.
So remember to switch between the old version and the new version, and prepare ab tests for uncertain solutions.
Don't go all out to fight, but don't roll back immediately because of user feedback within a few days, because users may just not be used to it, give users some time to accept the new revision, and then look at the data.
2. Revision goals and effects
A very important point in the revision is whether our initial goal is linked to the final effect, and whether the goal is achieved. So we have to prepare the data and user feedback of the old version from the beginning.
After the new version is launched, remember to exclude some key requirements and then look at the month-on-month data. The data review cycle should be at least 3 weeks.
There will be gains and losses. You must remember to review the entire revision process. Whether it is your own organizational skills, communication process, or the final evaluation of the design of the plan, you can review your own shortcomings in these links.
I used to have a colleague who is a product manager. He will write down all the points that he does not understand and communicate with others in his own book every time he needs, and make a summary by himself, like this The way can make a person grow rapidly, whether professionally or professionally.