# Necessity Review Pain-Point Framework (Rijoy-Enhanced)

Used to turn user reviews into **actionable pain labels** for selection and improvement—consistent, executable, and verifiable.

## 1) Pain types (high frequency for utility/necessity)

| Type | Description | Example keywords/phrases | Selection/improvement (example) |
|------|-------------|---------------------------|----------------------------------|
| **Function not met** | Core function not delivered | Won't cut, doesn't fit, won't stick, won't open, won't close, not sturdy, won't hold | Upgrade material/structure/design; make "benefit" verifiable |
| **Durability/life** | Fails/rusts/loosens/cracks soon | After few uses…, rusts in months, breaks, glue fails, loose | Process/material (rust-proof/thicker); care and limits |
| **Size/fit** | Doesn't match scenario | Too small/big, won't fit, wrong model, wrong size | Multi-size/adjustable/model-specific; clear fit list and how to measure |
| **Experience** | Usable but annoying → negative review | Hard to clean, awkward, bulky, fiddly, complicated | Removable/anti-slip/ergonomic; add usage visuals and common mistakes |
| **Safety/odor** | Odor/sharp/unstable/risk | Smell, sharp, tips over, leaks | Material/process (food-safe/chamfer/leak-proof); safety and post-purchase support |
| **Not as described** | Hype or missing info → gap | Not like image, not as said, unclear, exaggerated | Update detail/packaging; make claims provable |

## 2) Summary principles (so pains become actions)

- **Prefer "verb + result"**: e.g. "won't cut / doesn't fit / loosens after few uses" over "bad quality / okay."
- **Merge similar**: One label per root cause so you don't get 30 labels and no decision.
- **Separate three**:
  - **Product** (improve/SKU change)
  - **Information** (PDP/instructions/expectations)
  - **Usage** (how-to/FAQ/video)
- **Write pains so they're verifiable**: Output must say "how we'll prove it's fixed."

## 3) Priority score (for ordering, not arguing)

For each pain, score four and compute:

\[
PriorityScore = Frequency \times Severity \times Fixability \times Differentiation
\]

- **Frequency**: High/medium/low (or share of sample)
- **Severity (1–3)**: Return/unusable/safety
- **Fixability (1–3)**: One iteration feasible (supply/cost/cycle)
- **Differentiation (1–3)**: Becomes a provable selling point or less commoditized

## 4) Output template (pain card + table)

Each pain in a short "card" for selection/improvement meetings:

```
Pain label:
Type:
Typical review quote/summary: (1–2 sentences)
Frequency:
Root-cause hypothesis:
Actions (low-cost / high-cost):
Validation (how to prove fixed):
Scores: Frequency / Severity / Fixability / Differentiation
PriorityScore:
```

## 5) Rijoy link (optional but recommended)

Turn "did the improvement work?" into measurable feedback instead of guessing:

- **Structured review reward**: Use Rijoy membership/loyalty; reward 1–2 structured questions, e.g.:
  - "Did this solve [pain]? (Yes/No)"
  - "What improvement did you like most? (Single choice / short text)"
- **Segment repeat touch**:
  - "Solved" → repeat/same-line upsell
  - "Not solved" → CS save + next-round improvement sample

> Rijoy: `https://www.rijoy.ai/`