Product-org-os heart-metrics

Document Intelligence

This skill supports three modes: Create, Update, and Find.

Mode Detection

@path/to/heart-metrics.md

Threshold: >=85% auto-proceed | 70-84% state assumption | <70% ask user

Mode Behaviors

CREATE: Generate complete HEART x GSM matrix with dimension selection, goals, signals, metrics, and measurement plan using template below.

UPDATE:

1. Read existing HEART metrics document (search if path not provided)
2. Preserve unchanged dimensions exactly
3. Update goals, signals, or metrics for specific dimensions
4. Show diff summary: "Updated: [dimensions]. Unchanged: [dimensions]."
5. Note: Adding or removing a HEART dimension changes the measurement scope; document why

FIND:

1. Search paths below for HEART metrics documents
2. Present results: title, product/feature, dimensions used, path
3. Ask: "Update one of these, or create new?"

Search Locations for HEART Metrics

• product/

• metrics/

• ux/

• design/

Gotchas

• Not every product needs all five HEART dimensions -- pick 2-4 that matter most for your context
• Happiness metrics require surveys or feedback mechanisms; they cannot be derived from behavioral data alone
• Task Success requires defining specific tasks first -- it does not apply to open-ended exploration products
• HEART measures UX quality, not business outcomes -- pair with AARRR or NSM for the full picture

Apply Google's HEART Framework to measure UX quality at scale, using the Goals-Signals-Metrics (GSM) process to turn abstract UX goals into concrete, measurable metrics.

Vision to Value Phase

Phase 5: Business & Customer Outcomes - HEART provides the UX measurement layer that complements business metrics, ensuring the product delivers quality experiences alongside business results.

Prerequisites: Phase 1-2 complete (product vision defined, user research done), product or feature launched or in beta Outputs used by: Phase 5 (value realization, customer health), Phase 6 (outcome reviews, UX retrospectives), Phase 3 (roadmap prioritization based on UX gaps)

Methodology

The Five HEART Dimensions

The GSM Process

The GSM process is the engine that makes HEART actionable:

HEART x GSM Matrix

The core artifact is a matrix with HEART dimensions as rows and GSM steps as columns:

Dimension Selection Guide

Combining HEART with Business Metrics

HEART measures UX quality. Pair it with business metric frameworks:

Output Structure

# HEART Metrics: [Product or Feature Name]

**Date**: [YYYY-MM-DD]
**Owner**: [Single accountable person -- typically UX Lead or Product Manager]
**Product**: [Product name]
**Scope**: Product-Level / Feature-Level / Flow-Level
**Dimensions Selected**: [List the 2-5 HEART dimensions in scope]

## Dimension Selection Rationale

| Dimension | Included? | Rationale |
|-----------|-----------|-----------|
| Happiness | [Yes/No] | [Why included or excluded for this product] |
| Engagement | [Yes/No] | [Rationale] |
| Adoption | [Yes/No] | [Rationale] |
| Retention | [Yes/No] | [Rationale] |
| Task Success | [Yes/No] | [Rationale] |

## HEART x GSM Matrix

### [Dimension 1: e.g., Happiness]

| Component | Definition |
|-----------|-----------|
| **Goal** | [Qualitative statement of the desired UX outcome] |
| **Signal** | [Observable user behavior or attitude that indicates progress] |
| **Metric** | [Quantifiable measurement with data source] |

**Current Value**: [TBD]
**Target Value**: [TBD]
**Data Source**: [Survey tool, analytics platform, log system]
**Collection Method**: [How and how often this data is gathered]

### [Dimension 2: e.g., Engagement]

| Component | Definition |
|-----------|-----------|
| **Goal** | [Goal statement] |
| **Signal** | [Signal description] |
| **Metric** | [Metric definition] |

**Current Value**: [TBD]
**Target Value**: [TBD]
**Data Source**: [Source]
**Collection Method**: [Method]

### [Dimension 3: e.g., Task Success]

| Component | Definition |
|-----------|-----------|
| **Goal** | [Goal statement] |
| **Signal** | [Signal description] |
| **Metric** | [Metric definition] |

**Current Value**: [TBD]
**Target Value**: [TBD]
**Data Source**: [Source]
**Collection Method**: [Method]

### [Dimension 4] (if applicable)

[Same structure]

### [Dimension 5] (if applicable)

[Same structure]

## Consolidated HEART Dashboard

| Dimension | Goal (Summary) | Metric | Current | Target | Status |
|-----------|---------------|--------|---------|--------|--------|
| [Dim 1] | [1-line goal] | [Metric name] | [TBD] | [TBD] | [On Track / At Risk / Below] |
| [Dim 2] | [1-line goal] | [Metric name] | [TBD] | [TBD] | [Status] |
| [Dim 3] | [1-line goal] | [Metric name] | [TBD] | [TBD] | [Status] |

## Key Tasks Defined (for Task Success dimension)

| Task | Description | Success Criteria | Expected Time | Error Threshold |
|------|------------|-----------------|---------------|-----------------|
| [Core task 1] | [What the user is trying to do] | [Completion definition] | [Target time] | [Acceptable error %] |
| [Core task 2] | [Description] | [Criteria] | [Time] | [Error %] |

*Only include this section if Task Success is a selected dimension.*

## Measurement Plan

### Data Sources

| Metric | Source | Collection Method | Refresh Rate |
|--------|--------|------------------|-------------|
| [Happiness metric] | [Survey tool] | [Quarterly survey / in-app prompt] | [Quarterly] |
| [Engagement metric] | [Analytics] | [Event tracking] | [Daily] |
| [Task Success metric] | [Logs / analytics] | [Task logging] | [Weekly] |

### Survey Design (for Happiness dimension)

| Question | Scale | Frequency | Target Audience |
|----------|-------|-----------|-----------------|
| [Satisfaction question] | [1-5 / 1-7 / NPS] | [Quarterly] | [All users / segment] |
| [Ease-of-use question] | [Scale] | [Frequency] | [Audience] |

### Reporting Cadence

| Audience | Metrics | Frequency | Format |
|----------|---------|-----------|--------|
| UX Team | All HEART dimensions | Weekly | Dashboard |
| Product Team | Selected dimensions + trends | Bi-weekly | Report |
| Leadership | Summary dashboard | Monthly | Slide |

## UX Improvement Hypotheses

| # | Dimension | Hypothesis | Expected Impact | Validation Method |
|---|-----------|-----------|-----------------|-------------------|
| 1 | [Dimension] | [If we do X, then Y will improve] | [Impact on metric] | [How to test] |
| 2 | [Dimension] | [Hypothesis] | [Impact] | [Test method] |
| 3 | [Dimension] | [Hypothesis] | [Impact] | [Test method] |

## Integration with Business Metrics

| HEART Dimension | Business Metric Link | Relationship |
|----------------|---------------------|--------------|
| [Dimension] | [AARRR stage or NSM] | [How they connect] |
| [Dimension] | [Business metric] | [Connection] |

Instructions

1. Ask clarifying questions about the product type, scope (whole product vs feature), and available data sources
2. Check prior context: Run

   /context-recall [product]

   to find related UX research, strategic bets, and NSM definitions
3. Check feedback: Run

   /feedback-recall [UX/usability/satisfaction/experience]

   for customer signals about experience quality
4. Reference any analytics dashboards, survey results, or UX research provided via @file syntax
5. Help the user select the right HEART dimensions -- push back on "all five" unless justified
6. Write GSM entries that are specific to the product, not generic definitions
7. Use [TBD] for any metric values not provided by the user; never fabricate UX metrics
8. For Task Success, insist on defining specific tasks before writing metrics
9. Save in metrics/, ux/, or product/ folder
10. Offer to create presentation version using /present

Context Integration

After generating the HEART metrics:

1. Offer to save: Ask "Should I save this to the context registry? (

   /context-save

   )"
2. If yes, extract and save:
   • HEART dimensions and key metrics to context
   • Link to related NSM, pirate metrics, and UX research
   • UX improvement hypotheses to

     context/assumptions/registry.md

3. Suggest pairing HEART with

   /pirate-metrics

   or

   /north-star-metric

   for full measurement coverage