Example context. Preview only. Nothing is submitted.
When to sendYou have a defined product goal and can pair feedback with behavioral measurements.
- 01
Your experience with your product
Capture satisfaction before asking about success. It is an attitudinal signal, not a combined HEART score.
See the question
- How satisfied are you with the experience?
- Capture an attitudinal signal alongside behavior.
- 02
Getting things done
Ask whether the person achieved their goal. A complete outcome and a satisfaction score of 4–5 can finish here.
See the question
- Did you accomplish what you came to do?
- Separate liking the product from getting the intended result.
- 03
What could be better?
An incomplete task or a low satisfaction score opens an optional comment. Fillo chose this threshold; it is not part of the HEART framework.
See the question
- What would have made this experience better?
- An incomplete outcome or a satisfaction score of 1–3 opens an optional explanation. Finishing a task does not imply a good experience.
Using the answers
Choose a goal first, then compare the satisfaction and self-reported outcome with observed behavior. Keep sampling and timing consistent across releases.
When to choose another form
You need a standardized usability instrument. These questions have no external normative benchmark.
Before you publish
Define the product goal and record the usage or journey context. Pair these answers with relevant behavioral measures.
This is a custom pulse, not a standardized HEART instrument. Keep timing, scales, and recruitment consistent across comparisons.