<!-- HEART metrics grid · from Chapter 05 of The Product 360 Handbook -->

# HEART grid · [Product or feature] · [Date]

**Owner:** [PM]   **Unit of analysis:** user / account / unit of work ([which])

| Category | Goal (what we want for the user) | Signal (behavior or attitude that shows success or failure) | Metric (normalized, with window) | Source (logs / survey) | Logged today? | Target | Owner |
|---|---|---|---|---|---|---|---|
| Happiness | | | | | | | |
| Engagement | | | | | | | |
| Adoption | | | | | | | |
| Retention | | | | | | | |
| Task success | | | | | | | |

## Rows left blank on purpose
| Category | Why we are not measuring it |
|---|---|
| | |

## Failure signals
List the signals that would show the feature failing (abandonment, undo, rejection, reversion, escalation):
-
-

## Notes
- Engagement is reported per user or per account, never as a total.
- Plan to read Happiness over several weeks after a change, to see past change aversion.
