ansoff-matrix
Skill2 starsChanged 3 months agoMITView on GitHub
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 88
Add new features to existing product
- Distinctive: line 89
Create adjacent product lines
- Distinctive: line 144
Create phased roadmap and milestones
- Distinctive: line 158
Avoid spreading too thin across all four quadrants simultaneously
- Distinctive: line 159
Consider sequential strategy: penetration first, then market development
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ansoff Matrix
Metadata
- Name: ansoff-matrix
- Description: Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification.
- Triggers: Ansoff matrix, growth matrix, market expansion, growth strategy options
Instructions
You are a growth strategist analyzing expansion opportunities using the Ansoff Matrix for $ARGUMENTS.
Your task is to evaluate growth options across product and market dimensions and develop specific strategies for each quadrant.
Input Requirements
- Current product(s) and market definition
- Current market penetration and performance
- Customer insights and market opportunities
- Company capabilities and constraints
- Growth targets and timelines
- Competitive dynamics
Ansoff Matrix Framework
2x2 Matrix: Products vs. Markets
| Current Market | New Market | |
| Current Product | Market Penetration | Market Development |
| New Product | Product Development | Diversification |
1. Market Penetration (Current Product + Current Market)
Grow revenue by increasing usage or sales in your existing market.
Strategies:
- Increase frequency of product usage
- Expand use cases within existing customer base
- Acquire competitors' customers
- Reduce churn and improve retention
- Upsell and cross-sell existing customers
- Lower prices to capture price-sensitive segments
- Increase marketing and brand awareness
- Improve customer experience to drive referrals
Examples:
- Netflix adding games to increase engagement
- Starbucks encouraging multiple visits per week
- Adobe expanding Adobe Creative Cloud subscriptions
Risk Level: Low (familiar market, product, capabilities)
Typical Timeline: 6-12 months
2. Market Development (Current Product + New Market)
Grow by selling your existing product to new customer segments or geographies.
Strategies:
- Expand into new geographies or regions
- Target new customer segments or personas
- Sell through new channels or partnerships
- Adapt product for new use cases
- Partner with complementary companies
- Localize product for new markets
- Build brand awareness in new markets
Examples:
- Facebook expanding internationally
- Uber moving into new cities and countries
- Slack selling to non-tech industries
Risk Level: Medium (new market dynamics, but proven product)
Typical Timeline: 12-24 months
3. Product Development (New Product + Current Market)
Grow by introducing new products or features to your existing customer base.
Strategies:
- Add new features to existing product
- Create adjacent product lines
- Bundle products for greater value
- Develop premium/lite versions
- Integrate adjacent capabilities
- Create complementary products
- Upgrade product experience or performance
Examples:
- Spotify adding podcasts
- Amazon Prime expanding services (video, music, grocery)
- Figma adding prototyping and FigJam
Risk Level: Medium (existing customers but new product)
Typical Timeline: 12-18 months
4. Diversification (New Product + New Market)
Grow by entering entirely new markets with new products.
Strategies:
- Related diversification: leveraging existing competencies
- Unrelated diversification: entering new domains
- Acquire companies in new markets/products
- Strategic partnerships or joint ventures
- Build new business units
- Apply capabilities to adjacent problems
Examples:
- Amazon expanding from books to cloud services (AWS)
- Apple expanding from computers to phones, wearables, services
- Microsoft moving from software to cloud (Azure) and gaming (Xbox)
Risk Level: High (new market, new product, new capabilities)
Typical Timeline: 24+ months, requires significant investment
Output Process
- Define current market and product clearly
- Analyze each quadrant:
- Identify 2-3 specific opportunities per quadrant
- Assess market size and growth potential
- Estimate required resources and investment
- Evaluate competitive dynamics
- Define success metrics
- Prioritize opportunities by:
- Strategic fit with company vision
- Revenue potential and growth rate
- Resource requirements and feasibility
- Competitive advantage and defensibility
- Timeline to profitability
- Develop go-to-market strategy for top 2-3 opportunities
- Create phased roadmap and milestones
- Identify risks and mitigation plans
- Define success metrics and leading indicators
Strategic Questions
- Which quadrant offers the best risk-reward profile?
- Where do our capabilities give us competitive advantage?
- Which opportunities align best with our vision and values?
- What partnerships or acquisitions would accelerate growth?
- How does each option impact our brand and positioning?
Notes
- Market penetration is lowest risk; diversification is highest risk
- Most companies should excel in one quadrant before expanding
- Avoid spreading too thin across all four quadrants simultaneously
- Consider sequential strategy: penetration first, then market development
- Reassess Ansoff Matrix annually or when market conditions shift
Further Reading
Other versions11 projects use a version of this.
Word for word · 6
- skytiger6724/qwen-skills★ 2100% same
- daviszhen/agent-skills★ 1100% same
- miovrag/claude-skills★ 1100% same
- xeroc/skills★ 1100% same
- maeng777/claude-skills★ 0100% same
- stefanomartiradonna/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 5
- deanpeters/Product-Manager-Skills★ 7.7ksame name
- ironyjk/strategy-frameworks★ 14same name
- deciqAI/knowledge-skills★ 11same name
- tupe12334/instinct★ 1same name
- CAPP-Financials/Consulting_Brain★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use mckinsey-7s, bcg-matrix and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ironyjkSkillmckinsey-7s
McKinsey 7S Framework — diagnose organizational alignment across 7 interdependent elements: Strategy, Structure, Systems, Shared Values, Style, Staff, Skills. Essential for change management and M&A integration.
Also in 3 projects that use this
- ironyjkSkill
bcg-matrix
BCG Growth-Share Matrix — portfolio management framework for allocating resources across business units. Classify units as Stars, Cash Cows, Dogs, or Question Marks based on market growth and relative market share.
Also in 3 projects that use this
- +1 more from ironyjk
In this repository383 other files it gives its agents.
- 37signals-waySkill
- ab-test-analysisSkill
- advisor-orchestrator-workerSkill
- ai-ml-engineeringSkill
- algorithmic-artSkill
- analyze-feature-requestsSkill
- animation-vocabularySkill
- apple-designSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- improve-animationsSkill
- pick-ui-librarySkill
- prototypeSkill
- review-animationsSkill
- api-and-interface-designSkill
- api-design-best-practicesSkill
- app-store-changelogSkill
- auth-authorizationSkill
- beachhead-segmentSkill
- blue-ocean-strategySkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- brainstorm-okrsSkill
- brand-guidelinesSkill
- browser-testing-with-devtoolsSkill
- bug-hunt-swarmSkill
- business-modelSkill
- canvas-designSkill
- ci-cd-and-automationSkill
- claude-apiSkill
- clean-architectureSkill
- clean-codeSkill
- cli-creatorSkill
- code-review-and-qualitySkill
- code-review-skillSkill
- code-simplificationSkill
- cohort-analysisSkill
- cold-start-problemSkill
- commit-archaeologistSkill
- competitive-battlecardSkill
- competitor-analysisSkill
- contagiousSkill
- context-engineeringSkill
- continuous-discoverySkill
- architecture-blueprint-generatorSkill
- azure-architecture-autopilotSkill
- cli-masterySkill
- codeqlSkill
- conventional-commitSkill
- create-implementation-planSkill
- csharp-asyncSkill
- diagnoseSkill
- dotnet-best-practicesSkill
- draw-io-diagram-generatorSkill
- git-commitSkill
- github-actions-efficiencySkill
- java-springbootSkill
- mcp-cliSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.