Geek University Product Manager Training Camp: Lesson 14 Summary of Product Planning and Function Planning

Lecturer: Qiu Yue

1. What exactly is product planning

Insert picture description here
Insert picture description here

1.1 Implementation steps of product planning

  1. Find out the higher-level [objective-logic-strategy] and evaluation criteria.
  2. Disassemble the goals and strategies of the previous level, set your own goals and evaluation criteria at this level.
  3. List all possible strategies by brainstorming or comparing competing products, and disassemble as much as possible.
  4. Analyze the logical dependencies, costs, and priorities between strategies.
  5. Determine the priority and plan the implementation steps with other cooperative departments.

1.2 How to prioritize

  • First consider the logical relationship: the refrigerator door must be opened first.
  • Secondly, consider the effect expectation: the efficiency of helping the target;
    ☞ universality: benefit scenario or the proportion of the population;
    ☞ profitability: how much effect increase may be possible;
    ☞ harmfulness: possible negative impact;
    ☞ uniqueness: Value curve and opportunity.
    ☞ Stability: Whether it has been verified.
  • Finally, consider cost and feasibility: input-output ratio.
    Insert picture description here

1.3 What are the outputs of product planning?

  • A big picture, or a simple memo file with description;
  • A list of items with priority and description;
  • Product function roadmap (Roadmap).

1.4 The rhythm of product planning

  • Focus on phases, don't fall apart;
  • Tick-Tock
  • Front end & back end / busy & idle / confident & not confident / explicit & restrained

1.5 Some experience in product planning in reality

  • Almost no product planning for more than one quarter can guarantee [precision], but product planning is very useful;
  • The formation of product planning is mostly top-down, but it does not mean that we can only passively execute it. Even if it is a demand pool, it also requires [planning] progress.
  • Product planning must start with the end, knowing the facts, assumptions, and logic.
  • The product manager's test is not to cut the budget, but to increase the budget;
  • In the planning, it is necessary to reflect the proportions of several different modules, such as phased goals/continuous optimization goals/bugfixes;
  • Strategically cautious, tactically aggressive.

Should people in the workplace listen to themselves or their boss?

If pigs, chickens, and parrots make a sandwich together, the pigs pay for the pork and the chickens pay for the eggs. The parrot service is just casual. So you should listen to the pigs, because you pay the most.

So you can express your own opinions, but you must resolutely implement the boss's instructions.

Guess you like

Origin blog.csdn.net/zgpeace/article/details/114763062