# Mode USP and Value Proposition Testing Checklist
Purpose: track USP/value-prop variants separately from the strategic wedges.
A wedge is the strategic angle. A USP/value prop is the specific promise we put in front of users. Each value prop should be tested against a wedge, title, and proof asset.
## How to use this checklist
Each item is a test candidate, not an approved message. For each candidate, fill in the test context before using it externally, then record observed signal after the test.
Suggested fields:
- **Channels tested:**
- **Audience/user titles tested:**
- **Asset or message used:**
- **Observed signal:**
- **Objections / proof requests:**
- **Decision:** keep / refine / pause / reject
- **Notes:**
## USP / value-prop candidates
### [ ] U1 — Design directly in your real product
Associated wedges: W1, W2.
Promise: designers can work against the actual product rather than only creating mockups or handoff artifacts.
Test notes:
- User titles tested:
- Channel/asset:
- Proof shown:
- Signal:
- Objections:
- Decision:
### [ ] U2 — Real product, not mockups
Associated wedges: W1, W4.
Promise: Mode helps teams evaluate and improve working product experiences instead of staying detached in prototype/mockup space.
Test notes:
- User titles tested:
- Channel/asset:
- Proof shown:
- Signal:
- Objections:
- Decision:
### [ ] U3 — Designers fix production UI without opening an IDE
Associated wedges: W2, W3, W6.
Promise: designers get more production leverage without local setup, terminal, file tree, or code literacy.
Test notes:
- User titles tested:
- Channel/asset:
- Proof shown:
- Signal:
- Objections:
- Decision:
### [ ] U4 — Design QA / visual polish acceleration
Associated wedges: W3.
Promise: Mode can reduce the back-and-forth of last-mile UI polish and design QA loops.
Proof caution: avoid hard quantified time-savings unless supported by a named proof asset.
Test notes:
- User titles tested:
- Channel/asset:
- Proof shown:
- Signal:
- Objections:
- Decision:
### [ ] U5 — Product changes that respect your design system
Associated wedges: W5.
Promise: Mode helps produce changes that respect components, tokens, patterns, and shared UI standards.
Proof caution: proof-gated until component/token evidence exists.
Test notes:
- User titles tested:
- Channel/asset:
- Proof shown:
- Signal:
- Objections:
- Decision:
### [ ] U6 — Designers propose, engineers review
Associated wedges: W6.
Promise: Mode increases designer leverage while keeping engineering control and review intact.
Test notes:
- User titles tested:
- Channel/asset:
- Proof shown:
- Signal:
- Objections:
- Decision:
### [ ] U7 — Existing-product UI changes, not blank-canvas app generation
Associated wedges: W4.
Promise: Mode is for improving real existing products/codebases, not generating greenfield prototype apps.
Test notes:
- User titles tested:
- Channel/asset:
- Proof shown:
- Signal:
- Objections:
- Decision:
### [ ] U8 — Visual fidelity designers trust; code fidelity engineers can review
Associated wedges: W5, W6.
Promise: Mode bridges designer taste and engineering review quality.
Test notes:
- User titles tested:
- Channel/asset:
- Proof shown:
- Signal:
- Objections:
- Decision: