产品开发大师 (Product Development Master)
Overview
Product development for e-commerce (especially Amazon/cross-border) requires more than
tool-driven keyword research. A product direction, if wrong, cannot be fixed by Listing
optimization, ads, or keyword tuning later. This skill provides a three-layer thinking
methodology that connects demand understanding, feasibility evaluation, and product
redefinition into one coherent workflow.
The three layers are:
- Divergent Thinking (发散性思维) — Open up the demand world. Transform a product
name into a network of user purposes and usage scenarios. Produce a demand map, not
scattered keywords. - Convergent Thinking (收敛思维) — Compress possibilities into testable plans. Pass
each opportunity through five evaluation gates: demand, competition, profit, risk, and
resource matching. Output a falsifiable hypothesis, not a conclusion. - Reverse Logic (反推逻辑) — Redefine products from the endpoint. Ask what a product
truly does for the user, then find alternative supply-chain solutions that fulfill the
same essential purpose at a different price point or emotional value.
The three layers connect: divergent thinking finds product categories, markets, audiences,
and scenarios; convergent thinking determines whether an opportunity can enter execution;
reverse logic then loops back to the supply chain to find a better product form for the
validated demand.
When to Use
Activate this skill when the user:
- Asks whether a product or category "can be done" (能不能做)
- Requests product selection analysis (选品分析)
- Wants to explore product opportunities or market gaps
- Needs to evaluate a product direction's viability
- Seeks differentiation angles for an existing product
- Wants to redefine or reposition a product
- Is researching demand for a new product line
- Asks about sourcing strategy or supply chain alternatives
The Three-Layer Framework
Layer 1: Divergent Thinking
Goal: Transform a product name into a demand map of user purposes.
Core principle: Do not ask "can this product sell?" Ask "what problem does this solve
in the user's life?" A product name is just a label; the real opportunity lives in the
network of user purposes behind it.
Process summary:
- Start with a product name (e.g., "Christmas tree"). Do not look for products yet.
- Ask: what do users actually do with it? List all user purposes (decoration, ambiance,
display, interaction, commercial use, modification, etc.). - For each purpose, break down further: decorate what? how? for whom? Each branch leads
to different audiences, keywords, image styles, and Listing language. - Follow the action chain: what does the user do step by step? Each step points to
associated products (tree topper, light strings, ribbons, ornaments, tree skirt,
storage bag, hooks, display stand). - Extend outward: if this scenario works, what adjacent scenarios share the same need?
- Source ideas from: reviews, TikTok, Quora, Instagram, X, Xiaohongshu, Taobao, 1688,
offline stores, and real-life observations of how users use, complain about, modify,
and combine products.
Stop criterion: Divergent thinking is complete when the following sentence can be
stated clearly for at least one opportunity:
> "Who, in what scenario, for what purpose, is willing to pay for what difference."
If this sentence cannot be constructed, the analysis is still circling keywords, not yet
in real demand territory.
Critical boundary: Divergence is not random brainstorming. Every idea must answer
three questions: who is the user, what is the scenario, and why would they pay. Ideas
that cannot answer these are just brainwaves, not opportunities.
For the full methodology, examples (Christmas tree case study), and the demand map
template, see references/divergent-thinking.md.
Layer 2: Convergent Thinking
Goal: Compress a validated demand opportunity into a testable, falsifiable hypothesis.
Core principle: Market demand only proves someone bought something similar. It does
not prove you can sell it, or that doing so now is worthwhile. Convergent thinking
transforms "I think this could work" into "I know why this is worth testing."
The five gates:
| Gate | Question | Key checks |
|---|---|---|
| 1. Demand | Is the market stable? | Search volume continuity, seasonal peaks, off-season baseline, trend direction |
| 2. Competition | Is it too crowded? | Top listing review counts, 1000+ review listings count, brand concentration, image/selling-point homogenization, new listing viability |
| 3. Profit | Can costs and logistics sustain margin? | Selling price, purchase cost, packaging upgrade, freight, FBA, platform commission, ad budget, return loss — all together, not just price vs. cost |
| 4. Risk | Are there legal/compliance landmines? | Patents, trademarks, copyrights, certifications, material compliance, platform sensitive keywords — especially for distinctive shapes, patterns, IP, functional structures |
| 5. Resource match | Can current capabilities support this? | Photography dependence, content capability, ad capability, inventory capacity — if the opportunity is real but current resources cannot support it, it is not for right now |
Output: A selection hypothesis (选品假设) with the following structure:
- Target audience: Who will buy
- Usage scenario: When and where they use it
- Core purpose: What problem they solve or feeling they seek
- Differentiation source: Packaging, combination, material, size, function, visual, or content
- Price logic: Why the user would pay this price for this difference
- Validation actions: Test images first, test keywords, test small batch, or do competitor teardown and profit calculation first
- Risk boundaries: At what ad cost, conversion rate, or unresolved IP risk to stop investing
For the full 5-gate evaluation framework, the Christmas scent gift set case study, and
the selection hypothesis template, see references/convergent-thinking.md.
Layer 3: Reverse Logic
Goal: Redefine products by working backwards from the user's essential purpose.
Core principle: A product is not what it is called; it is what it does for the user.
"Cat urn" is a label. Its essence is "a small, sealed, moisture-proof container with
memorial significance." Once the essence is extracted, alternative supply chains become
visible — a tea canister, with the right packaging and emotional layering, can enter the
pet memorial scenario.
Reverse logic process:
- Ask: what is this product's true purpose?
- Ask: what task is the user trying to complete by buying it?
- Ask: what functions, emotions, scenarios, and symbolic meanings are needed to fulfill
that task? - Ask: what other products can also satisfy these conditions?
- Evaluate: is the alternative supply chain more mature, cheaper, or more flexible?
Three rules for valid redefinition:
- Functional structure must match. A tea canister works for ashes because it is
already sealed, moisture-proof, and small. If a product's structure has no connection
to the new scenario, redefinition becomes forced labeling. - Emotional value must be expressible. Pet memorial products sell not just containers
but remembrance, farewell, preservation, and dignity. If images, packaging, and copy
cannot express this, users see only a jar. - User understanding cost must be low. A good redefinition lets users understand at a
glance. If it requires lengthy explanation, the definition is too far from user
cognition, and both advertising and conversion will struggle.
For the full methodology, the cat urn case study, and the redefinition checklist, see
references/reverse-logic.md.
Workflow
Apply the three layers in sequence, but allow iteration:
[User request: product idea or category]
|
v
+---------------------------+
| Layer 1: Divergent | Open up demand
| Thinking | -> Demand map
+---------------------------+
|
v
+---------------------------+
| Layer 2: Convergent | Evaluate feasibility
| Thinking | -> Selection hypothesis (5 gates)
+---------------------------+
|
Hypothesis viable?
/ \
Yes No -> Back to Layer 1, try another branch
|
v
+---------------------------+
| Layer 3: Reverse Logic | Redefine product form
| | -> Alternative supply chain
+---------------------------+
|
v
+---------------------------+
| Back to Layer 2 with | Re-evaluate the redefined product
| the redefined product | through the 5 gates
+---------------------------+
|
v
Final output: actionable test plan
Step-by-step execution:
-
Clarify the starting point. Determine whether the user has a specific product in
mind, a category, or just a vague direction. If vague, help them narrow to a starting
product name. -
Run divergent thinking. Build a demand map. List user purposes, break each into
scenarios, follow action chains, and extend to adjacent needs. Stop when at least one
opportunity can be stated as a complete demand sentence. -
Run convergent thinking. Take the most promising opportunity from the demand map
and pass it through the 5 gates. Be honest — the goal is not to confirm a bias but to
find out whether the opportunity is worth testing. Produce a selection hypothesis. -
Run reverse logic (if applicable). If the convergent thinking reveals that the
obvious product form has issues (too competitive, too expensive, IP risk), use reverse
logic to find alternative supply chain solutions that fulfill the same essential
purpose. -
Loop back. Take the redefined product back through convergent thinking to validate
the new form. -
Produce the final output. Deliver a structured document containing:
- The demand map (key branches)
- The selection hypothesis (all 7 elements)
- The redefinition logic (if applied)
- The next actions (what to test, what to verify, what to source)
- The risk boundaries (when to stop)
Output Format
When producing analysis for the user, structure the output as:
Demand Map
Product: [name]
├── Purpose 1: [description]
│ ├── Scenario A: [who, where, why]
│ │ └── Action chain: [step 1 → step 2 → ...]
│ └── Scenario B: ...
├── Purpose 2: ...
└── Adjacent needs: [related products/scenarios]
Selection Hypothesis
Target audience: [who]
Usage scenario: [when, where]
Core purpose: [what problem/feeling]
Differentiation source: [packaging/combination/material/size/function/visual/content]
Price logic: [why pay this price]
Validation actions: [test images / keywords / small batch / competitor teardown]
Risk boundaries: [stop if ad cost > X, conversion < Y, IP risk unresolved]
Redefinition (if applied)
Original product: [name]
Essential purpose: [what it does for the user]
Required capabilities: [function, emotion, scenario, symbolism]
Alternative source: [supply chain product]
Redefinition additions: [packaging, copy, visual changes]
Cost comparison: [original vs. redefined]
Important Notes
- Divergence without convergence is daydreaming. Convergence without divergence is
copying. Both must happen. - The output of convergent thinking is a hypothesis, not a conclusion. It says "this
is worth testing," not "this will sell." - Reverse logic is not relabeling. A cheap product cannot sell at a high price just by
changing its name. The redefinition must genuinely solve the user's scenario problem or
carry emotional value they are willing to pay for. - Tools validate thinking; they do not replace it. Keyword tools, market research
tools, and supply chain platforms are for verification and supplementation. The demand
map must exist in the mind first. - Surface-level opportunities are usually already taken. Real opportunities rarely
float on top. Dig deeper into the demand map to find less obvious branches.