Growth Lever Picker logo

Growth Lever Picker

Community
ojiudezue
growth-lever-picker

Use when the user is choosing which growth lever to pull next or building a growth roadmap. Triggers on phrases like "growth", "growth lever", "how do we grow", "ICE score", "growth experiments", "acquisition vs retention", "what should we focus on for growth", "growth portfolio". Implements the 10 Growth Levers + ICE framework from Ch 12 of Building Rocketships.

Overview

Publisherojiudezue
Repositoryproductmind-skills
Skill namegrowth-lever-picker
Stars
81
Forks
18
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ojiudezue on GitHub. Read the source before you install it.

Installation

Install the Growth Lever Picker AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/ojiudezue/productmind-skills/tree/main/skills/growth-lever-picker
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ojiudezue/productmind-skills.git /tmp/productmind-skills
mkdir -p .claude/skills
cp -r /tmp/productmind-skills/skills/growth-lever-picker .claude/skills/growth-lever-picker
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Growth Lever Picker in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Growth Lever Picker on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Growth Lever Picker is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Growth Lever Picker

What this does

Runs Ch 12's 10-Lever Growth Framework. Scores candidate levers via ICE (Impact, Cost, Effort), returns a ranked shortlist, names the opportunity costs of paths not taken, and enforces the 70/20/10 portfolio split (short-term / medium-term / exploratory). Refuses to recommend levers the team cannot credibly execute given current resources.

When to use

Trigger when the user:

  • Has a North Star + Tier 1 metrics defined (or vmsoop-strategy ran) and now needs to pick growth bets
  • Is at the "we need to grow but don't know how" stage post-PMF
  • Has 5+ candidate growth ideas and wants to prioritize
  • Is debating acquisition vs. retention focus
  • Needs a portfolio of bets, not a single lever

When NOT to use

  • Pre-PMF — growth before product-market fit accelerates churn; route to sharp-problem-test + aha-mapper first
  • User wants a single experiment design — too narrow; this picks the bet to run
  • User is building the roadmap from already-chosen levers — that's roadmap-from-strategy

The 10 levers (from Ch 12)

Reach levers (4) — bring more users to the product

  1. Paid acquisition — ads, sponsorships, content syndication
  2. Organic content / SEO — long-tail discovery
  3. Channel partnerships — distribution via integrations, marketplaces, OEMs
  4. Referrals / virality — existing users invite new ones

Value levers (6) — make the product worth more to each user

  1. Activation — % of signups who hit the aha (pairs with aha-mapper)
  2. Retention — repeat use over time
  3. Expansion — usage breadth (more workflows, more seats)
  4. Monetization — pricing, packaging, tier moves
  5. Resurrection — bringing dormant users back
  6. Reduced churn — fewer cancellations

The book's running observation: most teams over-index on reach when value levers are higher ICE. Reach without value is a leaky bucket.

ICE scoring

Each lever gets three 1–10 scores:

  • Impact — how much it moves the North Star if it works
  • Cost — financial, time, opportunity cost (HIGHER = WORSE; the book inverts the conventional ICE so higher cost reduces score)
  • Effort — how hard to execute (HIGHER = WORSE)

ICE = (Impact × 2) − Cost − Effort

The book weights Impact double because most growth failures are high-effort small-impact work.

The decision rule

Pick the highest-ICE lever the team can credibly execute on with current resources. Credibility matters more than score: a top-scored lever the team can't pull is worthless.

Portfolio split (Ch 12)

The book is explicit on allocation:

  • 70% — short-term, high-confidence bets (3-month payoff)
  • 20% — medium-term bets (6–12 month payoff)
  • 10% — exploratory / 10x bets (12+ months, uncertain)

If the portfolio is 100% short-term, you'll plateau in 12 months. If it's 50% exploratory, you'll run out of runway.

Refusal mode

If the user is pre-PMF, refuse and route to discovery. Growth pre-PMF accelerates the wrong thing.

If the user proposes a reach lever while activation < 30% or churn > 10% monthly, refuse — refer to the value-lever rationale. The leaky bucket dominates.

If the team has no execution capability for the top-scored lever (e.g., #1 is paid acquisition but no one on the team has run paid campaigns), drop to the next viable option. Don't recommend the fictional best.

Inputs

  • North Star metric + current value
  • Current activation rate, retention, churn
  • Available execution capabilities on the team
  • 5+ candidate growth ideas (or "we don't know what to try")
  • Budget / runway constraints

Output structure

## Growth pick verdict: [READY | NEEDS_MORE_INPUT]

### Top 3 lever shortlist
| Rank | Lever | Impact | Cost | Effort | ICE | Credible? |
|---|---|---|---|---|---|---|
| 1 | ... | 9 | 3 | 4 | 11 | ✓ |

### Recommendation
[The single lever to execute first, with rationale]

### Portfolio allocation
- 70% short-term: [items]
- 20% medium-term: [items]
- 10% exploratory: [items]

### Opportunity costs (paths not taken)
- [Lever cut and the cost of cutting it]

### Sequencing
- Now: [...]
- Next 3 months: [...]
- 6-12 months: [...]

### Recommendation
[Concrete next step]

### Analogous case from the book
[A named example]

Worked example from the book

Calendly's growth choice (Ch 12)

  • Candidate levers: paid acquisition, SEO content, integration partnerships, referral loop, activation, retention
  • ICE scores:
    • Referral loop (invitation is the product): Impact 9, Cost 2, Effort 3 → ICE 13
    • Integration partnerships: Impact 8, Cost 3, Effort 4 → ICE 9
    • Paid acquisition: Impact 7, Cost 8, Effort 5 → ICE 1
  • Pick: referral loop — every meeting invitation introduces the brand to a new potential user; near-zero cost, embedded in the product use itself
  • Portfolio:
    • 70% short-term: referral loop optimization, activation polish
    • 20% medium-term: top-3 integration partnerships
    • 10% exploratory: enterprise admin features

Gotchas

  • Reach without value loses money. If activation < 30%, fix activation BEFORE adding paid acquisition. Run aha-mapper if you haven't.
  • Credibility > raw ICE. A 13-ICE lever the team can't execute is worth less than a 9-ICE lever they can.
  • Don't run 5 bets simultaneously. Pick 1–2 short-term; one medium-term setup; one exploratory thread. More dilutes attention.
  • Re-score quarterly. Effort drops as the team learns; impact changes as the market shifts.

Anti-patterns to flag

If the user's plan has any of these, surface them:

  • Heavy paid-acquisition spend with weak activation/retention — refuse, recommend the value lever first
  • 100% short-term portfolio — name the medium-term gap
  • 50% exploratory portfolio — name the runway risk
  • "Let's just go viral" with no referral mechanism designed — recommend starting with the loop design, not the wish
  • Same lever recommended for two consecutive quarters with no impact — drop, try the next

Source

Ch 12: The 10 Growth Levers and ICE prioritization.


About this skill

This skill is part of the ProductMind Skills catalog — open-source product-judgment skills for AI coding agents.

Source: Building Rocketships by Oji and Ezinne Udezue — Chapter 12. This skill applies one named framework from the book. It works standalone in any agent that supports the SKILL.md standard.

Want the orchestrated version? The RocketshipsGPT agent runs all 13 book skills together, with persistent memory, framework-fidelity evals, voice-checked output, and the book's anti-pattern catches built in. → rocketshipsgpt.productmind.co

License: Skill content licensed under CC BY-SA 4.0. Attribution required; derivative works must share alike. See ADR 0005 for rationale.

Skill version: 1.0.0 · Published: 2026-06-05

Frequently asked questions

What does the Growth Lever Picker AI skill do?

Use when the user is choosing which growth lever to pull next or building a growth roadmap. Triggers on phrases like "growth", "growth lever", "how do we grow", "ICE score", "growth experiments", "acquisition vs retention", "what should we focus on for growth", "growth portfolio". Implements the 10 Growth Levers + ICE framework from Ch 12 of Building Rocketships.

Why use Growth Lever Picker on TypingMind?

Because you install it once and use it with any model. Growth Lever Picker is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Growth Lever Picker in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ojiudezue/productmind-skills/tree/main/skills/growth-lever-picker. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Growth Lever Picker?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Growth Lever Picker?

As many as you like. As long as a model supports skills, you can use Growth Lever Picker with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Growth Lever Picker AI skill free?

It is published on GitHub by ojiudezue. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇