Which Product Methodologies Are Real Gems or Toxic Advice? A Deep Dive

1. Demand: From "What users say" to "Users don’t know what they want"

1. User Story

Definition: Describe a requirement using the three elements "role‑scenario‑value" in natural language, e.g., "As a [role], I need [function] so that [value]".

Standard template: "As a 30‑year‑old working mother, I want to complete grocery shopping in 5 minutes so that I can spend time with my child."

Avoid pitfalls

Do not use vague subjects (e.g., "users want faster" → "new users complete first order in ≤1 minute").

Do not detach from scenario (e.g., "add favorite function" → "while shopping, users can bookmark items and compare prices on weekends").

2. Maslow's Hierarchy

Definition: Split user needs into five layers—physiological, safety, social, esteem, self‑actualization.

Application scenarios:

Prioritize: first satisfy physiological needs (e.g., system stability), then self‑actualization (e.g., badge system).

High‑order needs: luxury e‑commerce emphasizes "respect" services; fitness apps highlight "self‑discipline" achievements.

Failure case: a fitness app forced a "community" feature, but users complained the calorie calculator was inaccurate.

3. KANO Model

Definition: Classify requirements into basic, expected, exciting, indifferent, and reverse types.

Application scenarios:

Requirement filtering:

Resource allocation: 80% to basic, 20% to exciting.

Avoid pitfalls: fill gaps before adding sparkle; don’t treat a skin‑change feature as core.

2. Design: From "Boss says ugly" to "Users say unusable"

4. Design Thinking

Definition: User‑centered innovation process consisting of empathize, define, ideate, prototype, test.

Application scenarios:

User research: replace a 100‑page report with a 5‑minute user journey map.

Rapid validation: sketch paper prototypes and let users critique on the spot, more efficient than a week in Axure.

Avoid pitfalls: skipping research and jumping straight to prototypes leads to "self‑satisfied solutions".

5. Nielsen's 10 Usability Heuristics

Definition: Ten golden principles for UX, such as visible system status and error‑prevention.

Application scenarios:

Show progress bar during loading (visible status).

WeChat's "recall" feature, e‑commerce "edit order" (controllability).

Confirm dialog before delete (error‑prevention).

Counter‑example: weakening the "cancel" button during installation forces users to complete the install.

6. Peak‑End Rule

Definition: Users remember experiences based on the peak moment and the ending; a pleasant peak and ending make the whole experience feel pleasant.

Application scenarios:

Peak: Alipay’s annual bill ceremony with visual data and poster generation.

End: Didi’s post‑ride coupon that leaves a "savings" impression.

Avoid pitfalls: prompting for a review after the flow can degrade the end‑value.

3. Growth: From "Burn money for volume" to "Free users"

7. AARRR Model

Definition: Five stages of user lifecycle—Acquisition, Activation, Retention, Revenue, Referral.

Application scenarios:

Acquisition: keyword ads on search engines for fashion or running shoes.

Activation: first‑order coupons for new users.

Retention: membership tiers with points, discounts, birthday gifts.

Revenue: product sales as the main income source.

Referral: invite‑friend rewards for both inviter and invitee.

Avoid pitfalls: focusing only on new users while ignoring retention turns the product into a "leaky bucket".

8. Growth Hacking

Core idea: Data‑driven, low‑cost innovation and rapid iteration to systematically optimize every stage of the user lifecycle.

Core logic:

Use data analysis to locate growth bottlenecks.

Cross‑functional teams (product, tech, ops, marketing) quickly test ideas.

Scale validated "growth levers".

Typical tactics: viral marketing, A/B testing, user segmentation, product iteration.

9. Minimum Viable Product (MVP)

Core: Focus on the core function, validate demand quickly, and iterate with low cost.

Application scenarios:

E‑commerce MVP: can place orders and pay; other features marked "coming soon".

Social MVP: can send messages and add friends; default avatar used.

Avoid pitfalls: over‑design and scope creep that prevent even the core flow from working.

4. Strategy: From "Big moves" to "Small steps"

10. Agile

Definition: Small‑step, fast‑iteration development mode.

Application scenarios:

Requirement management: break features horizontally, prioritize vertically.

Iteration planning: split tasks into "can be done in 3 days" chunks to block ad‑hoc additions.

Avoid pitfalls: daily stand‑ups without any requirement documents lead developers to guess.

11. Blue Ocean Strategy

Definition: Avoid competing in saturated markets; create new markets through innovation.

Examples:

Bilibili: merged video platform, anime community, learning, and live streaming.

Lululemon: entered with yoga pants, then defined the "athleisure" lifestyle category.

12. Porter’s Five Forces

Definition: Analyze industry competitiveness across suppliers, buyers, new entrants, substitutes, and existing rivals.

Five‑force analysis (example: JD.com):

Industry rivals: JD competes with Taobao and Pinduoduo; leverages logistics and authentic products.

Threat of new entrants: high capital for tech, logistics, marketing creates barriers.

Threat of substitutes: brick‑and‑mortar stores, live‑stream e‑commerce; JD expands to JD to home to mitigate.

Bargaining power of suppliers: large procurement volume gives JD strong negotiating power.

Bargaining power of buyers: many choices give buyers power; JD offers rich assortment, promotions, and service to retain them.

Supplement: also watch the "sixth force"—policy risk (e.g., education "double reduction", bike‑share city‑management).

5. Data: From "Fake reports" to "Insightful reports"

13. RFM Model

Core logic: Quantify user value via Recency, Frequency, Monetary to avoid one‑size‑fits‑all operations.

Definitions:

Recency (R): days since last transaction—the fewer, the higher the R.

Frequency (F): number of transactions in a period—the higher, the higher the F.

Monetary (M): total spend in a period—the higher, the higher the M.

Strategy application:

Super users (R↑F↑M↑): 3 purchases in 7 days, 5,000 CNY total → VIP support, early‑test invites, birthday gifts.

Sleeping users (R↓F↓M↑): no order for 90 days but >10,000 CNY historic spend → targeted "welcome back" coupon.

Deal‑seekers (R↑F↑M↓): weekly orders <50 CNY → limit high‑subsidy activities, steer to high‑margin items.

14. A/B Testing

Definition: Compare different variants with data to choose the optimal solution.

Golden principle: test only one variable at a time.

Button color (red vs green) → click rate +18%.

Popup copy ("Get now" vs "Miss it for a year") → click rate +23%.

Avoid pitfalls: calculate minimum sample size first; don’t experiment on just 100 users.

15. Funnel Analysis

Definition: Track the full user journey from exposure to conversion, pinpoint drop‑off points.

Application scenarios:

E‑commerce funnel: homepage UV → product page → add‑to‑cart → purchase; identify where 60% drop from add‑to‑cart to purchase and improve stock alerts.

Content product funnel: exposure → click → complete view → follow; if completion rate <30%, improve first 3 seconds of video.

Higher‑order use: compare funnel performance across user segments (new vs returning, regions, etc.).