PRD: Explain this change (AI)
Summary
When a metric moves, users click Explain and get a plain-language breakdown of the top drivers, grounded in their data.
Problem
Users see what changed but not why; CS leads can't act on health-score drops (INS-003· CS leads need account-level 'why' explanations to act on risk., INS-004· Opaque health scores erode AE trust in CS.).
Goals and non-goals
Goals: weekly habit for 250 accounts; explanations cite segments and events.
Non-goals: forecasting; free-form chat.
Users
PER-001· Priya, Product Manager Product managers, PER-002· Marco, CS Lead CS leads.
Requirements
| # | Requirement | Priority |
|---|---|---|
| R1 | Explain button on every time-series chart | P0 |
| R2 | Top 3 drivers with contribution % | P0 |
| R3 | Account-level explanations for health scores | P1 |
Success metrics
Weekly AI explanation users (MET-005· Weekly AI explanation users) from 180 to 250.
Open questions
- Cost per explanation at scale?
- Do we show confidence intervals?