<!-- Behavioral design review · from Chapter 10 of The Product 360 Handbook -->

# Behavioral design review · [Feature or flow] · [Date]

**Reviewers:** [PM, designer, engineer, legal or compliance where billing, consent or data is involved]
**Spec:** [link]   **Markets:** [US / EU / other]

## 1. Choice architecture inventory
| Element | Type (default, framing, ordering, prominence, choice set, prompt, AI suggestion) | Current design | Intended effect on behavior | Rationale |
|---|---|---|---|---|
| | | | | |

## 2. Persuasion or manipulation: four tests (per element)
| Element | Serves user's own goal? | Survives disclosure? | Symmetric (out as easy as in)? | True information? | Verdict |
|---|---|---|---|---|---|
| | | | | | Keep / Change / Escalate |

## 3. Dark-pattern check
Mark any that apply and name the screen and element.
- [ ] Sneaking (items, renewals or changes added without clear notice)
- [ ] Hard to cancel or downgrade (exit harder than entry)
- [ ] Preselection that favors us over the user
- [ ] Obstruction (data export, account closure or opt-out made laborious)
- [ ] Hidden costs or hidden subscription terms
- [ ] Trick wording or confirmshaming
- [ ] Visual interference (the option we prefer is dominant, the other hidden)
- [ ] Nagging (asking again for a choice already made)
- [ ] Fake urgency, scarcity or social proof
- [ ] Comparison prevention (plans or prices hard to compare)
- [ ] Privacy choices obscured or subverted
- [ ] AI-specific: agent that flatters, pressures or exploits the user's situation

Regulatory lenses to note (confirm applicability with counsel): FTC Act Section 5 and ROSCA (US); DSA Article 25 for online platforms, UCPD and GDPR (EU); AI Act Article 5 for AI systems (EU).

## 4. AI trust check (AI features only)
- Is evidence shown where the decision is made?
- Is confidence shown honestly, including uncertainty?
- Can the user adjust the output, not only accept or reject?
- Are acceptance and wrong acceptance both measured?
- Does the design guard against automation bias at approval points?

## 5. Defaults register
| Default | Value | Owner | Rationale | Share of customers who change it | Review date |
|---|---|---|---|---|---|
| | | | | | |

## Outcome
Approved / Approved with changes / Escalated to [name]. Changes required: [list]. Signed off by [names] on [date].
