Running a North Star Framework Workshop with Stakeholders
This skill teaches you how to facilitate a structured, collaborative workshop where cross-functional teams define or refine their North Star Metric and supporting input metrics—one of the most common product manager interview questions about strategic alignment.
Run a North Star Framework workshop by assembling cross-functional stakeholders for a structured 2-3 hour session. Start with customer value mapping, brainstorm candidate North Star Metrics, score each against criteria like measurability and customer-centricity, then converge on one metric with supporting inputs. Close by assigning ownership and establishing a review cadence. This collaborative process ensures genuine buy-in rather than top-down mandates.
Outcome: You can confidently facilitate a workshop that produces a clearly defined North Star Metric with 3-5 supporting input metrics, documented with owner assignments and a review schedule—all with genuine cross-functional buy-in.
Prerequisites
- Basic understanding of the North Star Framework and what makes a good North Star Metric
- Familiarity with your product's business model and key user segments
- Access to product analytics data (usage metrics, retention, revenue indicators)
- Workshop facilitation basics (timeboxing, managing group dynamics, diverge-converge techniques)
Overview
Defining a North Star Metric in isolation—whether by a product leader in a spreadsheet or an executive in a board deck—almost always fails. The metric either lacks buy-in from the teams who need to move it, or it misses critical context that only surfaces when engineering, design, marketing, and data sit in the same room. Running a North Star Framework workshop solves this by turning metric selection into a collaborative, structured exercise. It's also one of the most frequently asked product manager interview questions because it tests both strategic thinking and facilitation skill simultaneously.
The workshop format matters because the North Star Metric isn't just a number—it's an alignment tool. When stakeholders participate in defining it, they understand the reasoning behind the choice, they've surfaced and resolved disagreements in real-time, and they leave with shared ownership of the outcome. This is fundamentally different from presenting a metric for approval. The North Star Framework depends on organizational alignment, and the workshop is the mechanism that creates it.
A well-run workshop typically takes 2-3 hours and follows a structured arc: grounding the group in customer value, generating candidate metrics, evaluating them against clear criteria, and converging on a single metric with its supporting inputs. The output isn't just a metric—it's a shared mental model of what drives value in your product, which informs roadmap prioritization, team goals, and resource allocation for months to come.
How It Works
The workshop operates on a diverge-then-converge model borrowed from design thinking, applied specifically to metric selection. The core insight is that jumping straight to "what should our North Star Metric be?" produces superficial answers anchored to whatever metric people already track. Instead, you first build shared understanding of customer value, then generate options, then evaluate rigorously.
The conceptual flow has four phases. In the grounding phase, you align everyone on what your product does for customers—not what it does technically, but the value exchange. A collaboration tool doesn't "send messages"; it "enables teams to make decisions faster without meetings." This reframing is essential because the North Star Metric should measure delivered customer value, not product activity. In the diverge phase, participants brainstorm candidate metrics without judgment. You want quantity here—typically 8-15 candidates. The evaluate phase introduces scoring criteria: Does this metric reflect customer value? Can we measure it today? Does it lead revenue (not lag behind it)? Can every team influence it? Finally, the converge phase narrows to one metric through structured discussion and dot-voting, then maps 3-5 input metrics that drive it.
The reason this works better than top-down metric selection is cognitive: when people participate in evaluating tradeoffs, they internalize the reasoning. An engineer who helped eliminate "daily active users" in favor of "weekly projects completed" understands why and can make autonomous decisions aligned with that logic. This is the same principle tested in product manager interview questions about stakeholder alignment—your ability to create shared understanding, not just deliver conclusions.
Step-by-Step
Step 1: Define the workshop scope and invite the right stakeholders
Decide whether you're defining a North Star Metric from scratch or refining an existing one—this changes the workshop's starting point significantly. Invite 6-10 participants representing product, engineering, design, data/analytics, marketing, and at least one customer-facing role (sales or support). Send a pre-read 3-5 days in advance that explains the North Star Framework concept, includes 2-3 examples from comparable companies, and shares any relevant product data (current metrics, user research highlights, retention curves).
Tip: Cap attendance at 10 people. Larger groups slow convergence dramatically. If more stakeholders need input, run a pre-workshop survey to collect their candidate metrics and concerns, then represent those voices in the room.
Step 2: Open with the customer value mapping exercise (25 minutes)
Start by asking the group: "What is the core value our product delivers to customers?" Have each person write their answer independently on sticky notes (physical or digital via Miro/FigJam) for 5 minutes. Then cluster the responses on a whiteboard. You'll typically see 3-5 distinct value themes emerge. Discuss and force-rank them: which value is most fundamental? This grounds all subsequent metric discussion in customer outcomes rather than business vanity metrics.
Tip: If the group can't agree on the core customer value, that's a signal you need to resolve this before picking a metric. Don't skip this tension—it's the most important disagreement to surface early.
Step 3: Brainstorm candidate North Star Metrics (20 minutes)
With the top customer value theme visible, ask everyone to independently brainstorm metrics that could measure that value being delivered. Set a timer for 8 minutes of silent ideation. Each person should aim for 3-5 candidates. Then go around the room and have each person present their candidates without debate—just clarifying questions. Collect all candidates on the board. You should have 8-15 unique metrics at this point, ranging from obvious choices to creative alternatives.
Tip: Encourage wild ideas. Someone suggesting 'customer smiles per week' might lead to a useful proxy metric discussion. The diverge phase should feel generative, not judgmental.
Step 4: Evaluate candidates against scoring criteria (30 minutes)
Introduce 5 evaluation criteria and score each candidate metric on a 1-5 scale: (1) Customer value reflection—does it measure value delivered, not just activity? (2) Measurability—can we track this reliably today or within 30 days? (3) Leading indicator—does improvement in this metric predict future revenue and retention? (4) Cross-functional influence—can engineering, design, marketing, and product all impact it? (5) Simplicity—can you explain it to a new hire in one sentence? Walk through each candidate as a group, discussing scores. This structured evaluation prevents the loudest voice from dominating.
Tip: Have the data/analytics person reality-check measurability in real-time. A beautiful metric you can't actually track is useless. Keep a 'parking lot' for metrics that score well but need instrumentation work.
Step 5: Converge on the North Star Metric through structured voting (20 minutes)
After scoring, you'll typically have 2-4 strong candidates. Give each participant 3 dot-votes to place on their preferred metrics (they can stack votes). The top 2 vote-getters become the finalists. For each finalist, run a quick "pre-mortem": What could go wrong if we optimize for this metric? What perverse incentives could it create? After discussing tradeoffs openly, make the final call. If the group is split, the product leader should make the tiebreaker decision—but only after both sides have been heard.
Tip: If two metrics are truly neck-and-neck, ask: 'If this metric improved 20% next quarter but nothing else changed, would we feel good about our product direction?' The one that gets the stronger yes is your answer.
Step 6: Map 3-5 input metrics that drive the North Star (30 minutes)
With the North Star Metric selected, shift to identifying the levers that move it. Ask: "What specific, measurable behaviors or outcomes directly cause our North Star to improve?" For example, if your NSM is "weekly active projects," inputs might include "new projects created," "collaborators invited per project," "templates used," and "projects reaching 5+ tasks." For each input metric, discuss the causal relationship—not just correlation. Map these visually as a simple tree with the NSM at top and inputs below. Reference the sibling skill on mapping input metrics for deeper frameworks.
Tip: Limit to 3-5 inputs. More than 5 dilutes focus. If the group identifies 8 candidates, force-rank by impact and pick the top 4. You can always revisit the others next quarter.
Step 7: Assign ownership and set the review cadence
For each input metric, assign a clear owner—the person responsible for understanding that metric's movement and proposing actions when it stalls. The North Star Metric itself should be owned by the product leader. Agree on a review cadence: weekly check-ins on input metrics (often in existing team standups), monthly deep-dives on the North Star trend, and a quarterly reassessment of whether the framework still fits. Document everything in a shared artifact—a one-page summary with the NSM, inputs, owners, and review dates.
Tip: Ownership doesn't mean sole accountability. It means one person is responsible for watching the metric and raising the flag when something changes. Make this distinction explicit to avoid defensiveness.
Step 8: Close with commitments and distribute the artifact
In the final 10 minutes, go around the room and ask each participant to state one thing they'll do differently next week based on what was decided. This creates personal accountability and tests whether the session produced genuine clarity. Within 24 hours, distribute the workshop artifact (the one-pager with NSM, inputs, owners, and cadence) to all attendees and relevant stakeholders who weren't in the room. Include a brief narrative explaining the key decisions and tradeoffs discussed.
Tip: Record the 'tradeoffs discussed' section carefully. When someone challenges the metric choice in 3 months, you can point to the documented reasoning rather than re-litigating the entire debate.
Examples
Example: B2B Project Management SaaS Defines Its North Star
A 50-person project management tool company has been tracking monthly active users (MAU) as their primary metric, but growth has stalled despite strong acquisition. The product leader suspects they're optimizing for the wrong thing. She assembles 8 stakeholders: head of product, two senior PMs, engineering lead, head of design, data analyst, VP of marketing, and the customer success director. Product manager interview questions in their recent hiring loop revealed candidates also struggled with metric selection, confirming this is a team-wide gap.
During the customer value mapping exercise, the group identifies three value themes: 'helping teams ship projects on time,' 'reducing coordination overhead,' and 'giving managers visibility into progress.' They force-rank 'helping teams ship projects on time' as the core value. Brainstorming produces 12 candidate metrics including MAU, weekly active projects, projects completed on time, tasks completed per user, and team collaboration events. During evaluation, MAU scores poorly on customer value reflection (it measures presence, not value delivered) and 'projects completed on time' scores poorly on measurability (they don't track deadlines consistently). The group converges on 'weekly active projects with 2+ collaborators' as the NSM—it measures real value delivery and is trackable today. They map four inputs: new projects created, collaborators invited per project, task completion rate, and template adoption rate. Each input gets an owner. The customer success director's insight was pivotal: she pointed out that single-user projects rarely renew, making the '2+ collaborators' qualifier essential.
Example: Consumer Fitness App Refines an Existing North Star
A fitness app that has been using 'weekly active users' as their North Star Metric for two years notices that WAU is growing but retention at 90 days is declining and monetization is flat. The CEO wants to revisit the metric. The PM leads a workshop with 7 stakeholders across product, engineering, data, marketing, content, and customer support. Several team members recently prepped for product manager interview questions about the North Star Framework and bring fresh perspective on what makes a strong metric.
The value mapping exercise reveals a disconnect: the team says the core value is 'helping people build consistent fitness habits,' but WAU rewards opening the app (possibly just to check a notification) rather than actual habit formation. Brainstorming generates 11 candidates. The breakthrough comes when the data analyst proposes 'weekly users completing 3+ workouts'—backed by cohort analysis showing that users who hit 3 workouts in a week have 4x higher 90-day retention. During evaluation, this metric scores highest on customer value reflection and as a leading indicator of retention and revenue. The team selects it as the new NSM and identifies inputs: workout starts per user, workout completion rate, streak maintenance (consecutive weeks at 3+), and content engagement (users who watch at least one instructional video). The content team lead, initially skeptical about attending, realizes her team directly influences two input metrics and leaves with clear priorities for the first time.
Example: Two-Sided Marketplace Navigates Competing Stakeholder Priorities
An online tutoring marketplace has strong opinions from both sides: the growth team wants to optimize for 'monthly bookings' while the quality team pushes for 'student satisfaction score.' The CPO runs a workshop with 9 stakeholders including representatives from both supply (tutor) and demand (student) sides, plus data, engineering, and finance. The tension between these perspectives mirrors common product manager interview questions about balancing stakeholder priorities.
The customer value mapping exercise surfaces a critical nuance: students value 'measurable learning progress,' not just 'access to tutors.' This reframes the metric debate—neither monthly bookings (activity) nor satisfaction score (lagging, subjective) captures learning progress directly. The group brainstorms 14 candidates and converges on 'monthly students with 2+ completed sessions and a returned booking'—a metric that combines engagement frequency with a behavioral signal of value received (rebooking). During the pre-mortem, the finance lead flags that this could incentivize low-price tutors over high-quality ones. They address this by adding 'average session rating above 4.0' as a guardrail metric, not an input. Input metrics become: new student-tutor matches, first session completion rate, session-to-rebook conversion, and tutor availability hours. The growth and quality teams both see their priorities reflected, resolving what had been a months-long internal debate.
Best Practices
Send a pre-read with North Star Framework basics, 2-3 company-relevant examples, and current product data at least 3 days before the workshop. Participants who arrive uninformed slow the group down and force you to spend facilitation time on education instead of decision-making.
Use silent ideation before any group discussion. Having each person write independently for 5-8 minutes before sharing prevents anchoring bias, where the first person to speak disproportionately shapes the group's thinking. This is especially critical when senior leaders are in the room.
Timebox every exercise ruthlessly and announce time remaining at the halfway point. The biggest facilitation failure in metric workshops is spending 90 minutes on brainstorming and having 15 minutes left for the actual decision. Write the time allocation on the whiteboard so everyone can see it.
Separate 'diverge' and 'converge' phases explicitly. Tell the group 'we are now in brainstorm mode—no critiques' and later 'we are now in evaluation mode—be critical.' When these phases blur, you get cautious brainstorming and superficial evaluation.
Include at least one customer-facing person (support, sales, or customer success) in the workshop. They catch metrics that look good internally but don't reflect actual customer experience. A support lead once vetoed 'daily active users' by pointing out that their most valuable customers used the product weekly, not daily.
Document dissent, not just decisions. If the VP of Engineering strongly preferred a different metric, note that in the workshop artifact along with the reasoning for the final choice. This prevents relitigating decisions and shows you took all perspectives seriously.
Common Mistakes
Letting the HiPPO (Highest Paid Person's Opinion) dominate the metric selection
Correction
This happens because senior leaders speak first and others anchor to their suggestion. Prevent it by using silent ideation for all brainstorming, having everyone write before anyone speaks. If a senior leader insists on a specific metric before the workshop, ask them to hold their perspective until the evaluation phase and present it alongside other candidates. Frame it as 'your instinct might be right, and this process will either confirm it with group buy-in or surface something even better.'
Choosing a metric that the team can't actually measure today
Correction
Aspirational metrics feel good in workshops but create immediate post-workshop paralysis. Always include a 'Can we measure this within 30 days?' criterion in your evaluation rubric. If the best conceptual metric isn't measurable, identify a proxy metric you can track now and create a 90-day plan to instrument the ideal metric. Document both the target metric and the interim proxy so the team knows this is temporary.
Skipping the customer value grounding exercise and jumping straight to metric brainstorming
Correction
Without the grounding exercise, teams default to internal business metrics (revenue, DAU, sign-ups) rather than customer value metrics. This happens because people reach for what they already track. The value mapping exercise reframes the conversation around outcomes customers care about, which naturally leads to better North Star candidates. Even if it feels slow, the 25 minutes invested here saves 45 minutes of circular metric debates later.
Ending the workshop with a metric but no input metrics, owners, or review cadence
Correction
A North Star Metric without input metrics is a scoreboard without a playbook—you can see if you're winning but have no idea what to do about it. Always allocate at least 30 minutes at the end for input metric mapping and ownership assignment. If you run out of time, schedule a follow-up session within one week specifically for input mapping. Never let more than a week pass between selecting the NSM and defining its inputs, or momentum dies.
Inviting too many people (12+) to the workshop to be 'inclusive'
Correction
Large groups create diffusion of responsibility and make convergence nearly impossible. Cap at 10 participants and use a pre-workshop survey to collect input from others. Share the workshop output widely afterward. If a stakeholder insists on attending, ask them what unique perspective they bring that isn't already represented—often they realize another team member covers their viewpoint.
Other Skills in This Method
Identifying Your Product's North Star Metric
How to discover and define the single metric that best captures the core value your product delivers to customers.
Mapping Input Metrics That Drive Your North Star
How to identify, define, and connect the 3-5 key input metrics that directly influence your North Star Metric.
Building Dashboards to Track Your North Star and Inputs
How to set up real-time dashboards and reporting structures that visualize your North Star Metric and its supporting input metrics.
Using the North Star Metric to Prioritize Your Product Roadmap
How to evaluate and rank roadmap initiatives based on their expected impact on the North Star Metric and its input metrics.
Iterating and Evolving Your North Star Metric Over Time
When and how to revisit, validate, or change your North Star Metric as your product matures and strategy shifts.
Aligning Cross-Functional Teams Around a North Star Metric
Techniques for communicating, cascading, and embedding the North Star Metric across product, engineering, marketing, and leadership teams.
Frequently Asked Questions
How long should a North Star Framework workshop take?
Plan for 2.5-3 hours for a first-time workshop defining a North Star Metric from scratch. If you're refining an existing metric, 90 minutes to 2 hours is usually sufficient because you can skip the educational preamble and start with data on the current metric's shortcomings. Build in a 10-minute break at the midpoint—decision fatigue is real, and the convergence phase requires sharper thinking than brainstorming.
What if stakeholders can't agree on a North Star Metric during the workshop?
First, check whether the disagreement is about the metric or about the underlying customer value. If it's the latter, you need more customer research before you can resolve it—and that's a valid workshop outcome. If stakeholders agree on the value but disagree on the metric, use a structured tiebreaker: for each finalist, ask 'If this improved 20% and nothing else changed, would we feel good?' If that doesn't resolve it, the product leader should make the final call, acknowledging the dissent and committing to a 90-day review where data will settle the debate.
How do I prepare for product manager interview questions about North Star workshops?
Interviewers asking about North Star Framework workshops want to see three things: your ability to structure ambiguity (how you design the workshop flow), your facilitation skill (how you handle disagreements and HiPPOs), and your metric judgment (how you evaluate candidate metrics). Prepare a specific example where you facilitated metric alignment—describe the customer value you grounded the discussion in, the tradeoffs between finalist metrics, and how you drove convergence. If you haven't run one yet, walk through how you would structure the session using the steps above and explain your reasoning at each phase.
Should remote teams run North Star workshops differently?
The structure stays the same, but the tools and facilitation techniques change. Use Miro or FigJam for visual collaboration—create pre-built templates with sections for value mapping, metric brainstorming, and scoring grids. Silent ideation actually works better remotely because there's less social pressure. For voting, use the built-in dot-voting features in collaboration tools. The main risk is multitasking; ask participants to close other apps and turn cameras on. Consider splitting a 3-hour workshop into two 90-minute sessions with overnight reflection between brainstorming and evaluation.
How often should we re-run the North Star workshop?
A full workshop should happen when there's a significant business model change, a new product line, or evidence that the current metric no longer reflects customer value. For most teams, this means annually or when retention/revenue diverges from the North Star trend. Quarterly reviews (30-60 minutes) should assess whether the metric is still working, but these are check-ins, not full workshops. If you're re-running the full workshop more than twice a year, you may be choosing metrics that are too tactical—a good North Star Metric should be stable for 12-18 months.
Can a startup with fewer than 10 people benefit from a North Star workshop?
Absolutely—in fact, small teams often benefit more because misalignment is costlier when every person represents 10-20% of your capacity. At a small startup, the workshop can be shorter (60-90 minutes) and more informal, but the structure still matters. Even with 4-5 people, silent ideation prevents the founder from anchoring everyone, and the evaluation criteria prevent gut-feel metric selection. The output—a single metric everyone optimizes toward—is arguably more impactful at a startup where you can't afford teams pulling in different directions.