brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next.
$ npx -y skills add getcrew44/crew44 --skill organic-growth-advisor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/organic-growth-advisorContext preview
The summary Claude sees to decide when to auto-load this skill.
Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next.
name: organic-growth-advisor description: "Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next." intent: >- Guide product managers through a fast triage to identify which of four organic growth paths fits their current constraint: new customer segments (L2), new geographies (L3), new distribution channels (L4), or new products or services (L5). Uses a 2x2 diagnostic based on customer/market context familiarity and degree of product change required. Outputs a growth path recommendation with rationale and immediate next steps. type: interactive best_for: - "Choosing which organic growth motion to pursue when multiple seem viable" - "Diagnosing whether the constraint is in reach, access, market context, or product value" - "Setting up an AI-assisted growth experiment with the right starting hypothesis" scenarios: - "We need to grow but aren't sure if we should go after new customer segments or new geographies" - "Help me figure out which McKinsey growth level we should focus on" - "We have strong product-market fit but growth is stalling. Where should we look?" - "Which organic growth path fits our current situation?"
Help product managers identify which organic growth path to pursue by diagnosing where the constraint actually lives. This is not a comprehensive strategy tool. It is a fast triage that puts you in the right lane before you start building hypotheses or running experiments.
The four growth paths covered here are drawn from the McKinsey Growth Pyramid (Levels 2 through 5). Levels 1, 6, and 7 are out of scope: Level 1 (existing products to existing customers) is a retention and optimization problem, not a growth motion. Levels 6 and 7 (new industry structure, new arenas) require capital and executive mandate beyond typical product team scope.
This skill does three things and nothing more: 1. Diagnoses where your growth constraint lives using two questions 2. Places your situation on the Growth Path Matrix (customer/market context vs. degree of product change) 3. Recommends one growth path with rationale, a diagnostic question, and a first experiment
---
Two questions place your situation on the matrix:
**X axis: Customer/Market Context** How familiar is the next customer or market you want to reach?
**Y axis: Degree of Product Change** How much does the product itself need to change to unlock the next wave of growth?
**L2: New Customer Segments** (Known context + Low product change) You already solve a real problem. A nearby buyer may need it too.
**L4: New Distribution Channels** (Known context + High product change) Product offers same value. People need a better way to find or access it.
**L3: New Geographies** (Less Known context + Low product change) The product may travel. The market context does not come with it automatically.
**L5: New Products or Services** (Less Known context + High product change) Customers are pulling you toward adjacent jobs your offer does not fully solve.
Risk scales with distance from your core. L2 is closest: same market, same product. L5 is furthest: new product, less familiar context. Most teams overinvest in L5 before they have exhausted L2 and L4. If your core product-market fit is strong and your current market is not saturated, L2 or L4 is almost always the right move first.
Innovation at any level is downstream of accumulated contextual knowledge. The teams that succeed at L3 are not the ones who moved fastest. They are the ones who studied how value actually travels in the new market before they tried to scale it. The teams that succeed at L5 are not the most creative. They built the adjacent product their existing customers were already asking for, in language they already understood.
---
Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill.
It defines:
Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.
Repo: getcrew44/crew44
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes