How to Become a Product Manager by Running HEART Framework Workshops

Overview

How It Works

Step-by-Step

1. Step 1: Scope the Workshop Before You Schedule It

   Before sending any calendar invites, determine which HEART dimensions are relevant to your product or feature. Not every product needs all five. A mature product might focus on Retention and Happiness, while a newly launched feature might prioritize Adoption and Task Success. Review your product's current state, recent user research, and strategic objectives to narrow scope.

   Prepare a pre-read document (1 page max) that includes: a brief HEART Framework overview, which dimensions you propose covering and why, any existing metrics or data the team should be aware of, and the expected workshop output. Send this at least 48 hours before the session.

   Decide on your participant list carefully. You need at minimum: one PM, one designer, one engineer, and ideally a data analyst. Cap the group at 8-10 people. Larger groups slow down convergence without meaningfully improving output quality.

   Tip: If participants are unfamiliar with HEART, consider a 15-minute 'HEART 101' lightning talk a few days before the workshop so the actual session isn't spent on education.

2. Step 2: Set Up the Workshop Space and Grid Template

   Create a visual grid—either on a physical whiteboard or in a collaborative digital tool like Miro or FigJam. The columns represent HEART dimensions you've scoped (e.g., Engagement, Retention, Task Success). The rows represent the three GSM levels: Goals, Signals, and Metrics.

   Prepopulate each cell with a brief prompt. For example, under the 'Goals' row for 'Engagement,' write: 'What does meaningful engagement look like for our users?' These prompts prevent blank-page paralysis and keep the team anchored in user-centered thinking rather than business-centered thinking.

   Also prepare a parking lot area for ideas that don't fit the current scope, and a 'questions' section for unresolved debates the team needs to take offline.

   Tip: Color-code sticky notes by discipline (e.g., blue for engineering, yellow for design, green for PM) so you can visually spot if one perspective is underrepresented in any dimension.

3. Step 3: Open the Workshop with Context and Ground Rules

   Start the session by restating the purpose: 'We're here to align on how we'll measure user experience for [product/feature], using the HEART Framework's Goals-Signals-Metrics process.' Share 2-3 sentences of strategic context—what's the product's current challenge or opportunity that makes this workshop timely.

   Establish ground rules: (1) Goals come before metrics—resist the urge to jump to numbers. (2) Every perspective is equally valid at the goal level. (3) We'll use silent brainstorming before group discussion. (4) The parking lot exists for a reason—use it. (5) We're optimizing for alignment, not perfection.

   Allocate your time budget explicitly. For a 2-hour workshop covering 3 HEART dimensions, plan roughly 25 minutes per dimension (split into 8 minutes silent brainstorming, 12 minutes group discussion, 5 minutes prioritization) plus 15 minutes for opening and 20 minutes for wrap-up and next steps.

   Tip: Nominate a dedicated note-taker who isn't the facilitator. Facilitating and documenting simultaneously degrades both activities.

4. Step 4: Diverge on Goals — Silent Brainstorming

   For each HEART dimension, start with silent individual brainstorming on goals. Give participants 3-5 minutes to write goals on sticky notes (one goal per note). The prompt should be: 'What does success look like for [dimension] from the user's perspective?'

   Emphasize that goals should be qualitative and user-centered, not metric-shaped. 'Users find what they need quickly' is a good goal. 'Reduce time-on-task by 20%' is a metric masquerading as a goal—redirect these to the metrics row later.

   Have each person place their sticky notes on the grid silently. Once all notes are placed, read them aloud and cluster similar themes. This is where your facilitation matters most: help the team see that three different-sounding goals might actually be the same underlying intent, or that one goal might actually contain two distinct objectives that need separating.

   Tip: If someone says 'increase DAU,' ask 'Why? What user behavior does that represent?' Usually it unpacks into a richer goal about habitual value delivery.

5. Step 5: Converge on Signals — Cross-Functional Translation

   Once goals are prioritized (aim for 1-2 goals per HEART dimension), shift to signals. The prompt: 'What user actions or attitudes would tell us this goal is being achieved?' This is where cross-functional composition becomes critical.

   Designers often suggest qualitative signals: user sentiment, usability observations, support ticket themes. Engineers surface system-level signals: event logs, error rates, load times. PMs connect signals to business proxies: conversion events, feature adoption sequences. All three types are valid and usually complementary.

   Facilitate the discussion by explicitly asking each discipline for input: 'Engineering, what would you expect to see in the data if this goal were being met?' and 'Design, what would you observe in user behavior or feedback?' Document each signal on the grid beneath its parent goal. Don't filter yet—capture everything, then prioritize based on two criteria: signal strength (how directly does this indicate the goal?) and measurability (can we actually capture this data?).

   Tip: Signals that require new instrumentation aren't automatically lower priority. Flag them as 'needs engineering investment' and let the team make an informed tradeoff.

6. Step 6: Define Metrics — Make Signals Quantifiable

   For each prioritized signal, the team now defines a concrete metric: what exactly will you measure, how will you calculate it, and what's the data source? This is where the data analyst or engineer earns their seat at the table.

   For each metric, document: the metric name, its formula or calculation method, the data source, the current baseline (if known), and any segmentation needs (e.g., new users vs. returning users). If baselines are unknown, that's fine—mark them as 'TBD, needs baseline measurement' and assign an owner.

   This step naturally connects to sibling skills like measuring user happiness through surveys, tracking engagement and retention metrics at scale, and measuring adoption and task success. Reference these as 'deep dives' the team can pursue after the workshop for specific metric categories.

   Tip: Avoid ratio metrics without clear numerators and denominators. '7-day retention rate' is vague—'percentage of users who performed core action X at least once in the 7 days following signup' is actionable.

7. Step 7: Prioritize and Assign Ownership

   With the grid populated, step back and do a final prioritization pass. Not every metric will make it into the first iteration of your dashboard. Use dot-voting or a simple 2x2 matrix (impact vs. effort) to select the 3-5 metrics the team will commit to tracking immediately.

   For each selected metric, assign a clear owner—this is the person responsible for ensuring the metric gets instrumented, baselined, and reviewed regularly. Ownership doesn't mean they do all the work; it means they're accountable for progress.

   Document the 'not now' metrics in a backlog with a review date. These aren't rejected—they're deferred. This prevents the team from feeling their contributions were wasted and ensures good ideas aren't lost.

   Tip: The owner of a metric should attend whatever regular review cadence you establish. If a metric has no willing owner, that's a strong signal it's not actually important to the team.

8. Step 8: Document, Share, and Schedule the Follow-Up

   Within 24 hours of the workshop, distribute a clean summary document containing: the completed GSM grid, prioritized metrics with owners, parking lot items with proposed resolution paths, and next steps with deadlines. Share it broadly—not just with attendees but with stakeholders who need to understand the measurement plan.

   Schedule a 30-minute follow-up session 2-3 weeks later to review instrumentation progress and resolve any open questions. This follow-up is essential; without it, workshop outputs decay rapidly. The follow-up naturally leads into building HEART dashboards, where the team moves from documented metrics to live monitoring.

   For anyone studying how to become a product manager, the ability to turn a workshop's energy into lasting artifacts and ongoing rituals is what separates facilitation theater from actual organizational impact.

   Tip: Take a photo or screenshot of the completed grid before anyone leaves the room. Whiteboards get erased and Miro boards get reorganized—capture the raw state.

Examples

Best Practices

• Always start with goals before signals, and signals before metrics. The sequential GSM process is the workshop's structural backbone—skipping levels produces metrics that lack strategic grounding.

• Use silent brainstorming before group discussion for every phase. Research consistently shows that groups generate more diverse ideas when individuals think independently first, preventing anchoring on the loudest voice.

• Explicitly invite input from each discipline by name or role. Engineers in particular may stay quiet during goal-setting if they feel it's 'not their domain'—but their constraints and data knowledge are essential even at the goal level.

• Timebox ruthlessly. Allocate specific minutes to each activity and use a visible timer. HEART workshops that run overtime typically do so because the team got stuck debating a single metric—park it and move on.

• Limit scope to 2-4 HEART dimensions per session. Attempting all five in one workshop leads to fatigue and shallow coverage. It's better to do three dimensions deeply than five superficially.

• End every workshop with a 'confidence check'—ask each participant to rate 1-5 how confident they are that the team is measuring the right things. Low scores surface misalignment that the discussion missed.

Common Mistakes

Frequently Asked Questions