
writing-north-star-metrics
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.
- Installs
- 1.6K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/refoundai/lenny-skills --skill writing-north-star-metrics- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads writing-north-star-metrics automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
- Understand the value - Ask what specific value the product delivers to users (not revenue or internal activity)
- Test for simplicity - Ensure the metric can be understood and discussed by anyone in the company
- Check for actionability - Confirm teams can actually influence this metric through their work
- 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
FAQ
What does the writing-north-star-metrics skill do?
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.
How do I install writing-north-star-metrics?
Run npx skills add https://github.com/refoundai/lenny-skills --skill writing-north-star-metrics in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/writing-north-star-metrics/ (personal) or .claude/skills/writing-north-star-metrics/ (project).
Which AI agents can use writing-north-star-metrics?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is writing-north-star-metrics safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains writing-north-star-metrics?
It is published by refoundai in refoundai/lenny-skills. It has 1,642 recorded installs.
More from refoundai/lenny-skills
personal-productivity
refoundai/lenny-skills
Help users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done.
writing-prds
refoundai/lenny-skills
Help users transform abstract ideas into actionable project specs that align engineering and design teams on the problem and success metrics.
ai-product-strategy
refoundai/lenny-skills
Help users decide where to apply AI effectively, manage the transition from deterministic to probabilistic software, and build long-term defensibility through verticalization and proprietary data.
competitive-analysis
refoundai/lenny-skills
Help users understand and respond to competition. Use when someone is positioning against competitors, evaluating market threats, running competitive war games, or deciding how much to focus on competitors versus customers.
founder-sales
refoundai/lenny-skills
Help users master the transition from product development to active selling by leveraging their unique status as founders to bridge the trust gap and define a scalable sales motion.
analyzing-user-feedback
refoundai/lenny-skills
Help users convert massive volumes of qualitative and quantitative feedback into high-confidence product decisions through rigorous synthesis and internal immersion.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.