Marcus Andrey Study
Ler em português Library

Framework · Measurement · 2 min read

HEART framework

Five UX metric categories (Happiness, Engagement, Adoption, Retention, Task success) that help you choose metrics per product; for mandatory internal tools, focus on Task success and Happiness.

TTask success

Can people finish key tasks, how fast, with how many errors?

Typically: completion rate, time, error rate
HHappiness

Satisfaction and perceived ease, measured with short standard surveys.

Typically: SUS, UMUX-Lite, SEQ
AAdoption

Uptake of new features, and old shadow tools being replaced.

Typically: % using new filter at 30 days
EEngagement

Depth of feature use. Weak signal when the tool is mandatory.

Typically: % users using bulk edit
RRetention

For mandatory tools, read it as workaround avoidance.

Typically: % tasks done in-tool, not Excel
HEART gives five dimensions to choose from; for internal tools, start with Task success and Happiness.

Use it when

  • You are setting up a metrics framework for one of your core apps and need a structure.
  • A stakeholder asks for "engagement" numbers on a tool that people are required to use.
  • You want to check that your metrics cover both behaviour (what people do) and attitude (how they feel).

How to use it

  1. Go through the five categories. For your app, ask which of Happiness, Engagement, Adoption, Retention and Task success matter for its goals. Mark the ones that don't apply. Output: 2–3 chosen categories.
  2. Adapt them for internal tools. Read Retention as "workaround avoidance" (tasks done in the tool instead of in spreadsheets). Read Adoption as uptake of new features and replacement of shadow tools. Output: categories reworded for your context.
  3. Run Goals-Signals-Metrics for each chosen category. Write a goal, the signals you would see, and a metric. See Goals-Signals-Metrics. Output: one goal, signal and metric per category.
  4. Pick standard measures where you can. For Happiness use SUS, UMUX-Lite or SEQ. For Task success use completion rate, time on task and error rate (see Task success and time on task). Output: a HEART table with sources.
  5. Baseline and review. Take a first measurement and review the table on a regular rhythm, for example every quarter. Output: a baseline per metric.

Worked example

A HEART table for an internal booking tool on an operations platform. Engagement is kept but marked as low priority because the tool is mandatory.

Dimension Internal-app adaptation Example metric
Happiness Satisfaction, perceived ease SUS / UMUX-Lite score per app; SEQ after tasks
Engagement Feature usage depth (less meaningful for mandatory tools) % users using bulk edit
Adoption New feature uptake, shadow-tool replacement % users of new filter after 30 days
Retention Workaround avoidance % tasks done in-tool vs Excel exports
Task success The most important for internal apps Completion rate, time on task, error rate

Watch out for

  • Filling in all five. Five categories with weak metrics are worse than two with strong ones. Choose.
  • Engagement as success in a mandatory tool. More time in the tool can mean it is harder to use. Read engagement carefully.
  • Metrics without goals. HEART tells you the categories, not the goals. Pair it with Goals-Signals-Metrics.
  • Ignoring the attitude side. Task metrics alone miss frustration. Add a Happiness measure such as SUS or UMUX-Lite.

Template

Copy this into your metrics doc and fill only the rows that matter for your app.

App:                        Date:

| Dimension     | Relevant? | Goal | Signal | Metric | Source | Baseline |
|---------------|-----------|------|--------|--------|--------|----------|
| Happiness     |           |      |        |        |        |          |
| Engagement    |           |      |        |        |        |          |
| Adoption      |           |      |        |        |        |          |
| Retention     |           |      |        |        |        |          |
| Task success  |           |      |        |        |        |          |
Source
Google, CHI 2010
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close