writing-north-star-metrics

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill writing-north-star-metrics
0 commentsdiscussion
summary

Framework for defining a single, customer-centric metric that aligns teams and drives product decisions.

  • Measure value delivered to users, not revenue or internal activity; use proxy metrics like messages sent or nights booked that correlate with long-term outcomes
  • Ensure simplicity and universal understanding across the company; avoid composite scores and technical jargon that obscure meaning
  • Verify actionability by confirming teams can influence the metric through their work, and a
skill.md

Writing North Star Metrics

Help the user define their North Star metric using frameworks and insights from 27 product leaders.

How to Help

When the user asks for help with North Star metrics:

  1. Understand the value - Ask what specific value the product delivers to users (not revenue or internal activity)
  2. Test for simplicity - Ensure the metric can be understood and discussed by anyone in the company
  3. Check for actionability - Confirm teams can actually influence this metric through their work
  4. Add guardrails - Help them identify countervailing metrics that prevent gaming

Core Principles

Measure value delivered, not captured

Itamar Gilad: "The North Star metric measures how much value we create for the market. WhatsApp measured messages sent because every message is incremental value. Airbnb used nights booked." Select a metric that tracks core utility provided to the customer, not business extraction.

Avoid lagging indicators

Jess Lachs: "Retention is a terrible thing to goal on. It's almost impossible to drive in a meaningful way in a short term. Find a short-term metric you can measure that drives a long-term output." Identify proxy metrics that are sensitive to experimentation and correlate with long-term goals.

Simple beats sophisticated

Jess Lachs: "If people understand it, if they have an intuition around it, if it's something people can talk about across the company, it's going to be a much better metric than your made up composite score that nobody understands." Avoid composite metrics with complex coefficients.

Measure from the customer's perspective

Jeff Weinstein: "What was the value we're trying to produce for the customer, and can we measure it from their perspective? We suggested 'companies with zero support tickets.'" Define metrics based on the absence of friction or the presence of success moments.

A high-level mission simplifies decisions

Hari Srinivasan: "Everything at LinkedIn is a very connected ecosystem, but decisions aren't difficult because we're all here to help people connect to economic opportunity." A clear company-wide mission serves as the ultimate tie-breaker for product decisions.

Name metrics evocatively

Jeff Weinstein: "Picking metric titles that make you feel something. 'Companies with zero support' - the brevity and customer mindset built into the chart name can become currency inside the company." Use simple, evocative names instead of technical database field names.

Codify definitions precisely

Manik Gupta: "Everyone will talk about the same metric but have different nuances. What is a daily active user? Pick a definition, instrument it, codify it. No confusion." Metrics only drive alignment when backed by precise definitions and accurate instrumentation.

Select a hard activation metric

Lauryn Isford: "An activation rate that falls in a lower percentage range, maybe 5-15%, is better than a high percentage because it means there's likely much higher correlation with long-term retention." High-bar activation metrics that few users reach are often more valuable.

Revisit periodically

Lauryn Isford: "A North Star metric should be a measure of what you plan to do. Revisit North Star metrics every 6-12 months to ensure they still align with business goals." Be willing to shift metrics if the strategy requires it.

Avoid revenue as North Star

Sean Ellis: "I think monthly purchases is great because it maps to value people are getting. Units of value from the customer perspective is more important than overall revenue." Revenue should be a product of doing things right, not the day-to-day guiding metric.

Questions to Help Users

  • "What specific moment represents a user getting value from your product?"
  • "Could a non-technical person in your company understand and discuss this metric?"
  • "Can teams actually influence this metric through their work in a quarter?"
  • "What would happen if you gamed this metric - what would break?"
  • "Does this metric measure value delivered to users or value extracted from them?"
  • "Is this a leading indicator or a lagging one that's hard to move?"

Common Mistakes to Flag

  • Revenue as North Star - Revenue is an outcome; focus on the customer value that drives it
  • Complex composite metrics - If you can't explain it simply, teams can't rally around it
  • Lagging indicators like retention - Find the leading metrics that predict retention
  • Gaming vulnerability - Add countervailing metrics to prevent optimization that hurts users
  • Undefined terms - 'Active user' means nothing until you codify exactly what counts

Deep Dive

For all 35 insights from 27 guests, see references/guest-insights.md

Related Skills

  • Setting OKRs & Goals
  • Defining Product Vision
  • Prioritizing Roadmap
  • Designing Growth Loops
how to use writing-north-star-metrics

How to use writing-north-star-metrics on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add writing-north-star-metrics
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill writing-north-star-metrics

The skills CLI fetches writing-north-star-metrics from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/writing-north-star-metrics

Reload or restart Cursor to activate writing-north-star-metrics. Access the skill through slash commands (e.g., /writing-north-star-metrics) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.835 reviews
  • Ama Gupta· Dec 20, 2024

    writing-north-star-metrics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Noor Ndlovu· Dec 16, 2024

    Registry listing for writing-north-star-metrics matched our evaluation — installs cleanly and behaves as described in the markdown.

  • William Garcia· Dec 4, 2024

    Useful defaults in writing-north-star-metrics — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Sakshi Patil· Nov 19, 2024

    Solid pick for teams standardizing on skills: writing-north-star-metrics is focused, and the summary matches what you get after install.

  • Alexander Agarwal· Nov 11, 2024

    Keeps context tight: writing-north-star-metrics is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Chaitanya Patil· Oct 10, 2024

    writing-north-star-metrics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Benjamin Zhang· Oct 2, 2024

    I recommend writing-north-star-metrics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aditi Kapoor· Sep 21, 2024

    writing-north-star-metrics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Sep 17, 2024

    writing-north-star-metrics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ava Verma· Sep 9, 2024

    writing-north-star-metrics reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 35

1 / 4