Identify a clear product goal (step-by-step revision)
Position your product with cognitive associations (positive and negative correlations with what you know)
Give the system to users and let them dig their own gameplay
demand analysis
Three-step mining requirements: collect phenomena -> ask more questions and trace the reasons -> start from the reasons
All user behaviors can be traced back to their ultimate goals or results. It must ultimately be a goal or need that we can't- go back further, the satisfaction of which is an end in itself
There is no perfect design, just keep adjusting
Combining usage scenarios - user perspective
People like to be surrounded by unnecessary functions, filtering the truth from the clutter
Requirements design
scene
Combining usage scenarios - user perspective
emotional design
Make the product more fun
content
The core of the requirements document: those operations, user operation processes, and specific presentations that need to be implemented in development
Conceptual Design -> Functional Design -> Information Architecture and Interaction Design -> Interface Design -> Visual Design
WOW: Creating an Experience That Exceeds Expectations
Simplified products: rational deletion, transfer to reduce jumps, hierarchical organization
user
Don't make users think
Social Proof – Attention – Fear of Losing
Advanced users who are familiar with every detail of the product are not the core group. Only those users who are too lazy to learn and research your product can bring you real value.
product development strategy
User-participated product development model (Xiaomi)
Product Manager Skills
data analysis
Focus on the single key metric OMTM: Every stage of the product needs to find a clear number
Effectively record data and effectively interpret data
