florianbonnet14/ThePowerOfAnalytics_ClaudeSkills / north-star-metric-agent
north-star-metric-advisor
VerifiedStrategic framing and KPI setting specialist that helps identify and validate the single most important metric capturing customer value delivery and predicting business success. Use when starting a new team or product, when existing product lacks clear success metric, when team seeks to define what success means, or when metrics don't align with customer value and/or business goals.
| File | Kind | Size |
|---|---|---|
| North Star Metric Tutorial.md | markdown | 4.4 KB |
| README.md | markdown | 2.3 KB |
| SKILL.md | skill md | 3.6 KB |
| references/advanced-faq.md | markdown | 12.1 KB |
| references/evaluation-framework.md | markdown | 6.5 KB |
| references/examples.md | markdown | 3.8 KB |
| references/output-template.md | markdown | 4.5 KB |
references/advanced-faq.md
View on GitHub# Advanced Considerations & FAQs
## Common Pitfalls in Detail
### Pitfall 1: Choosing Vanity Metrics
**Problem:** Metrics that look impressive but don't reflect real value delivered.
**Examples:**
- Page views without engagement depth
- Sign-ups without activation
- App downloads without opens
- Social media followers without interaction
- Email list size without open rates
**Why It's Problematic:**
- Can grow while customer satisfaction declines
- Easy to game without improving product
- Doesn't predict business success
- Misleads stakeholders about health
**How to Fix:**
Ensure the metric measures completion of value delivery, not just initiation.
**Better Alternatives:**
- Page views → Time on page or pages per session
- Sign-ups → Activated users (completed key action)
- Downloads → Weekly active users
- Followers → Engagement rate
- Email list → Email open/click rate
---
### Pitfall 2: Multiple North Stars
**Problem:** Team tries to track 3-4 "equally important" North Stars.
**Impact:**
- Diffused focus and resources
- Conflicting priorities in decision-making
- Team confusion about what matters most
- Inability to make clear trade-offs
**Real Example:**
A team tracking "# sign-ups," "# active users," AND "revenue" as North Stars struggled when features that increased sign-ups decreased activation rates.
**How to Fix:**
- Choose ONE North Star metric
- Other important metrics become Level 1 KPIs in the tree
- These supporting metrics help explain and drive the North Star
**Framework:**
```
North Star: # Weekly Active Users
├─ Level 1: # New Sign-ups (acquisition)
├─ Level 1: % Activation Rate (activation)
└─ Level 1: % Weekly Retention (retention)
```
---
### Pitfall 3: Choosing Lagging Indicators for Teams
**Problem:** Team North Star takes months to show impact of changes.
**Examples:**
- Annual retention as North Star for growth team
- Lifetime value for product team
- Revenue for feature team
**Why It's Problematic:**
- Can't run fast experiments
- Slow feedback loop discourages iteration
- Hard to attribute impact
- Team loses motivation when metric doesn't move
**When Lagging Is OK:**
- Company-level North Star
- Executive/board metrics
- Long-term strategic goals
**How to Fix:**
Choose leading indicators that predict the lagging outcome.
**Examples:**
- Annual retention → Weekly engagement score
- LTV → # purchases in first 30 days
- Revenue → # active users converting features
---
### Pitfall 4: Metrics You Can't Control
**Problem:** North Star heavily depends on factors outside team's influence.
**Examples:**
- Overall company revenue (when you own one feature)
- Total user base (when you only influence onboarding)
- Market share (depends on competitors' actions)
**Why It's Problematic:**
- Team can execute well but metric doesn't move
- Demotivates team
- Can't experiment effectively
- Unclear ownership
**Rule of Thumb:**
Team should control ≥70% of the metric's drivers.
**How to Fix:**
Narrow scope to what you directly influence.
**Examples:**
- Company revenue → Revenue from your feature
- Total users → Users who adopt your feature
- Market share → Conversion rate in your funnel
---
### Pitfall 5: Financial Metrics as Team North Star
**Problem:** Using revenue, profit, or cost as primary team metric.
**Issues:**
- Doesn't directly reflect customer value
- Influenced by pricing, marketing, sales, competition
- Lagging indicator
- Disconnects team from customer outcomes
**When Financial Metrics Work:**
- Company-level North Star
- C-suite dashboards
- Investor reporting
**How to Fix:**
Choose customer-centric metric that leads to the financial outcome.
**Examples:**
- Revenue → # transactions, # subscriptions, # purchases
- Profit → Cost per transaction, efficiency metrics
- CAC → Conversion rate, activation rate
**Connection:**
Customer metric → Intermediate outcomes → Financial metric
---
## Advanced Scenarios
### Evolving Your North Star Over Time
**Startup Journey Example:**
**Phase 1: Product-Market Fit (0-2 years)**
- North Star: # Weekly Active Users
- Focus: Are people using and loving this?
**Phase 2: Growth (2-4 years)**
- North Star: # New Activated Users per Month
- Focus: Can we scale adoption?
**Phase 3: Monetization (4-6 years)**
- North Star: # Paying Customers
- Focus: Can we build sustainable business?
**Phase 4: Expansion (6+ years)**
- North Star: Net Revenue Retention (NRR)
- Focus: Are we expanding within accounts?
**Key Point:** North Star should evolve with strategic focus, not change frequently.
---
### Platform with Multiple User Types
**Challenge:** Different users get different value.
**Example - Notion:**
- Individual users value personal productivity
- Team users value collaboration
- Enterprise users value governance and security
**Approach 1: Unified Metric**
Choose metric that captures value for all segments:
- **Notion's Choice:** # Weekly Active Workspaces
- Works for individuals, teams, and enterprises
- Different use cases all create value through workspaces
**Approach 2: Primary + Segmented**
- **Company North Star:** # Weekly Active Workspaces (all users)
- **Team metrics:**
- Individual growth team: # individual workspaces created
- B2B team: # team workspaces with 5+ members
- Enterprise team: # enterprise workspaces with governance enabled
---
### B2B vs B2C Considerations
**B2C North Stars** (Examples):
- Focus on individual user behavior
- Higher volume, lower value per user
- Can change more quickly
- Examples: # videos watched, # songs streamed, # purchases
**B2B North Stars** (Examples):
- Focus on account or team behavior
- Lower volume, higher value per account
- More stability required
- Examples: # active workspaces, # seats used, # transactions processed
**Key Differences:**
- B2C: Individual action metrics
- B2B: Organization/team-level metrics
- B2B often includes usage intensity threshold (e.g., "teams with 5+ active users")
---
## FAQ
### Can we have different North Stars for different teams?
**Yes, with structure:**
- **Company North Star:** One unifying metric
- **Department North Stars:** Support company metric
- **Team North Stars:** Support department metric
**Example:**
```
Company: # Orders Delivered (DoorDash)
├─ Consumer Team: # Orders Placed
├─ Dasher Team: # Active Dashers
└─ Merchant Team: # Active Merchants
```
All three teams' metrics ladder up to company North Star.
---
### Should North Star be a rate or absolute number?
**Both have merits:**
**Absolute Numbers:**
- Shows scale and growth
- Easier to communicate
- Better for early stage
- Example: # purchases per month
**Rates:**
- Shows efficiency and quality
- Better for mature products
- Easier to segment and compare
- Example: % weekly active users
**Best Practice:**
- Choose what better represents value delivery
- Track both in practice
- Use absolute for North Star, rates for diagnosis
---
### Our North Star hasn't moved in months. What does that mean?
**Possible Reasons:**
1. **Wrong Metric**
- Doesn't actually reflect customer value
- Solution: Revisit the 4 properties framework
2. **Right Metric, Wrong Focus**
- Not working on the right drivers
- Solution: Use KPI Tree to identify leverage points
3. **Execution Issues**
- Shipping features that don't impact metric
- Solution: Run experiments, measure impact
4. **Market Saturation**
- Reached natural ceiling
- Solution: Consider new market or new metric
**Diagnostic Process:**
1. Check if metric still reflects customer value (customers happy?)
2. Review recent initiatives (did they target North Star drivers?)
3. Analyze segments (is growth stalling everywhere or specific segments?)
4. Compare to market (are competitors growing?)
---
### When should we change our North Star?
**Valid Reasons to Change:**
- ✓ Product strategy fundamentally shifts (new market, new model)
- ✓ Company stage changes (startup → growth → mature)
- ✓ Current metric achieved sustained success (>80% of ambitious target for 2+ quarters)
- ✓ Metric no longer reflects customer value (product evolved)
**Invalid Reasons:**
- ✗ Metric is hard to improve (that's the point!)
- ✗ Leadership wants something different (educate, don't capitulate)
- ✗ Metric hasn't moved lately (diagnose root cause first)
- ✗ Competitor uses different metric (context matters)
**Change Process:**
1. Document why current metric no longer serves
2. Follow full North Star definition process for new metric
3. Plan transition period (track both for 1-2 quarters)
4. Communicate change clearly to all stakeholders
---
### Can North Star be revenue?
**Company-level:** Yes, especially for mature companies
- Revenue, ARR, or NRR can work
- Acceptable when:
- Company is established
- Used for board/investor reporting
- Leadership-level metric
**Team-level:** Generally no
- Teams should focus on customer-centric leading indicators
- Reasons:
- Revenue influenced by many factors outside product
- Lagging indicator (slow feedback)
- Doesn't directly reflect customer value
- Can optimize for wrong things (price vs. value)
**Better Approach:**
- Team North Star: Customer-centric (e.g., # active users)
- Demonstrate connection: Active users → Paid conversions → Revenue
- Track revenue as outcome, not North Star
---
### How do we balance multiple products/features?
**Company with Multiple Products:**
**Option 1: Unified Company North Star**
- Choose metric that works across products
- Each product contributes to same metric
- Example (Google): # Queries per user (Search, Maps, Assistant all drive queries)
**Option 2: Product-Specific North Stars**
- Each product has its own North Star
- Company North Star is weighted sum or composite
- Example (Amazon): # Purchases (e-commerce) + Hours Watched (Prime Video)
**Best Practice:**
- Product North Stars should be comparable or complementary
- Should ladder up to clear company objective
- Avoid competing North Stars that trade off against each other
---
### What if we're in a new market with no benchmarks?
**Approach:**
1. **Start with best hypothesis**
- Use analogous products as reference
- Apply 4 properties framework
- Document assumptions
2. **Set relative targets**
- Focus on growth rate vs. absolute numbers
- Compare to your own baseline
- Set "learning milestones" vs. fixed targets
3. **Iterate quickly**
- Review monthly in first 6 months
- Validate correlation with customer satisfaction
- Adjust if evidence suggests better metric
4. **Build your own benchmarks**
- Track cohort behavior over time
- Identify patterns in successful vs. churned users
- Use your data to validate or adjust
**Remember:** North Star is hypothesis at first, validated over time.
---
## Relationship to Other Frameworks
### North Star vs OKRs
**North Star Metric:**
- Singular focus, never changes (except strategy shift)
- Measures ongoing state/output
- Example: # Active Users
**OKRs (Objectives & Key Results):**
- Multiple objectives per quarter
- Time-bound improvement goals
- Example: Increase # Active Users by 20% this quarter
**How They Work Together:**
- North Star = What to measure
- OKRs = Improvement targets on North Star and its drivers
---
### North Star vs KPI Tree
**North Star Metric:**
- Top of the tree
- Single most important metric
**KPI Tree:**
- Breaks down North Star into component drivers
- Shows how to influence North Star
- Enables diagnosis and prioritization
**Structure:**
```
North Star
├─ Level 1 KPI (major driver)
│ ├─ Level 2 KPI (sub-driver)
│ └─ Level 2 KPI (sub-driver)
├─ Level 1 KPI (major driver)
└─ Level 1 KPI (major driver)
```
---
### North Star vs AARRR (Pirate Metrics)
**AARRR Framework:**
- Acquisition → Activation → Retention → Revenue → Referral
- Funnel view of customer journey
**North Star:**
- One metric from AARRR framework
- Usually in Activation or Retention stage
- Represents sustained value delivery
**Example:**
- Acquisition: # Sign-ups
- Activation: # Users who complete first key action
- **North Star often here:** # Weekly Active Users
- Retention: % 30-day retention
- Revenue: # Paid conversions
- Referral: # Referred users
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |