[Boxue Valley learning records] Super summary, sharing with heart | Product manager basic stage learning review summary and sharing (2)

[Boxue Valley learning records] Super summary, sharing with heart | Product manager basic stage learning review summary and sharing (2)

---

foreword

After learning the video of the basic stage of the product manager of Erudite Valley, a summary of some knowledge points and personal insights.

demand analysis

The process of transforming business requirements into product requirements;
based on scenario analysis;

Prioritize needs

Kano model

Two dimensions:
functional perfection, user satisfaction;
four requirements:
necessary type; expected type; exciting type; indifferent type;

Four-quadrant rule

Two dimensions:
urgency and importance;
four types of needs:
urgent and important;
urgent and not important;
not urgent and important;
not urgent and not important;

function list

Included modules: modules, sub-modules, function points, descriptions, priorities;
difference from requirements pool:
content: function list has no stakeholders, time nodes, original requirements;
maintainer: requirements pool may be maintained by multiple departments, The function list is maintained by the product department;
the function list will only enter the development schedule;

user

user role

We abstract the typical characteristics of users (user basic information, user goals, usage scenarios) and put them together to form one or more user roles; it
can help project team members better understand users;

User portrait

Two types of tags: dynamic tags and static tags;

Difference from user portrait

The time of appearance is different. User roles are used before or at the beginning of the product launch. User portraits are used after the product has a large number of users and user data. A product with a user level of about
100,000 can consider the user portrait system;
user roles It is virtual, and user portraits are based on real data;

Three sets of classic user portraits

The first set

Core users: can feed back the platform;
secondary users: willing to participate, but have limited creative ability;
niche users: obsessed with a single function of the platform;
negative users: users who like to complain;
users can have multiple identities at the same time;

second set

Sheep: users;
head sheep: KOL, key opinion leader;
wolf: advertisers;

third set

Xiaoming: has a clear goal;
Benben: has a goal but is not clear;
Xiaoxian: just hangs out to pass the time, no consumption needs;

Structure flow chart

information architecture

The essence is the overall structure design of the product, page layout; classification of information and functions;
enabling users to use the product more efficiently;
considerations:
Correspondence: the correspondence between user needs and product goals;
functional similarity: similar functions Putting it together, large categories are used as the main frame, and small categories are used as sub-frames;
the relationship between functions and functions: inclusion and juxtaposition;
system scalability: the future development of the product needs to be considered, and the location and entrance of new functions need to be reserved;

structure diagram

Product function structure diagram

Focus on the functional modules of the product and extend them step by step;
production method: now list the main functional modules of the product according to the first-level page of the product, and then expand step by step to list its sub-functional modules;

Product Information Structure Diagram

Role: Help develop and establish a database; help product managers prevent information omission, duplication, and redundancy when redesigning products; for some products with more complex information, help product managers integrate information through information structure diagrams; Note:
Emphasis Break away from more than a dozen pages; do not need to do it according to the level;
production method: You can sort out the main information modules in the product according to the first-level page of the product, then list its sub-information modules, and finally list the information fields of each sub-information module;

Product Structure

It includes not only the function of the product, but also the information of the product, which is a simplified expression of the product;
function: it can replace the prototype as the output in any occasion;
production method: expand step by step according to the level of the page, each Just list the content from top to bottom, from left to right on the page;
Note: key functions, key production, as deep as possible;

flow chart

Function:
When designing products, let the product manager think more clearly;
during demand review, before introducing specific products to project team members, first introduce the business process;
in the flow chart, be sure to make all the abnormal states of the process and how to deal with them ;

Note: Swimlane diagrams can have multiple starts and multiple ends;

Classification: Business Flowchart, Page Flowchart, Data Flowchart;