Frameworks name dimensions differently, but all require goals before metrics

What it is

HEART, PULSE, AARRR, and the various “experience health” models name dimensions differently: some cut on happiness and task success, some on pages and latency, some on acquisition through referral. The portable discipline is not that noun list. It is goal-first: decide the goal, then pick the metric. Switching frameworks switches classification drawers, not derivation direction. Delaying goal writing to argue which dimension set is “more standard” replaces measurement with a naming dispute.

Why it happens

Framework authors faced different product constraints, so they cut different axes. PULSE sits closer to site operations and scale, HEART closer to experience categories, AARRR closer to a growth funnel. If the difference is treated as a side that must be chosen, teams spend time translating nouns: is our “activation” your “adoption.” Goal-first pulls the argument back to a decidable sentence: what, in this stage, do we need to judge has happened. Once the sentence is written, most frameworks can file it in some drawer; drawers that cannot file it need not open this week. Picking the framework first and then hunting for goals reverses the order: the drawer exists, so it feels as if something must be put in it, and goals are invented to fill the names. That is the framework driving the question, not the question choosing the framework.

Studying it

File the same set of product decision questions into two frameworks, and compare overlap and unique items in the final metric sets. If the unique items cannot be traced to the original questions, they came from filling the framework, not from goals. Process coding also works: do framework nouns or goal sentences appear first in the planning discussion; noun-led plans more often produce columns that are never cited. A cross-team translation table (activation = adoption = first success) counts as alignment only when both sides’ goal sentences match; noun correspondence is not evidence.

Where it stops holding

Some industry reports and procurement lists specify a framework name; external delivery can keep that naming while internal work still derives from goals. Operational metrics (availability, latency) have engineering goals; they need not be forced into an experience framework’s drawers, and that is not a verdict against the experience framework. Goal-first does not make the goal correct; it only gives the metric a parent. If two frameworks offer contradictory “standard metrics” for the same goal, return to the signal layer rather than averaging or keeping both.

Applying it

• Write the goal sentences for this stage first, then decide which framework’s drawers will file them; do not pick a template first.
• On cross-framework noun clashes, align goal sentences; do not ship a noun-only correspondence table.
• Mark dimensions that cannot file a current goal as unused; do not fill placeholder metrics.
• When an external audience needs the framework brand, keep original dimension names in an appendix and narrate the body as goal–signal–metric.

Related

• Same group: Q6.07.1 HEART maps happiness, engagement, adoption, retention, and task success onto goals and signals · Q6.07.3 Applying every framework dimension without product stage dilutes measurement focus · Q6.07.4 A framework supplies a thinking structure; specific metrics still need product-level customization
• Adjacent: Q6.02 Goals–Signals–Metrics · Q6.01 Classification frameworks
• Search terms: goal-first measurement · HEART · PULSE · AARRR