ansoff-matrix
Ansoff Matrix — 4-quadrant framework for growth strategy options: market penetration, market development, product development, and diversification. Use when evaluating growth bets, prioritizing investment across quadrants, and explicitly acknowledging the risk ladder from "more of what we know" to "new product in new market".
What this skill does
# Ansoff Matrix Igor Ansoff's product/market matrix for evaluating growth options. Forces explicit choice between four growth bets of increasing risk. ## The 2x2 | | **Existing Products** | **New Products** | |-----------------|------------------------|------------------------| | **Existing Markets** | Market Penetration (lowest risk) | Product Development | | **New Markets** | Market Development | Diversification (highest risk) | ## When to use this skill - **Annual / quarterly growth planning** - **Investment allocation** across growth bets - **Post-funding deployment** planning - **Board strategy discussions** - **Strategic-pivot decisions** (which quadrant are we really in?) - **Acquisition rationale** assessment ## The 4 quadrants in depth ### Q1 — Market Penetration (existing product × existing market) Sell more of what we have to people we know. **Tactics:** - Increase usage / frequency - Take share from competitors - Improve conversion rates - Pricing optimization - Loyalty / retention programs **Risk profile:** Lowest. You know the product + market. **Investment:** ~30-50% of growth investment for most companies. **When dominant:** Early-stage; high-growth market with share to take. ### Q2 — Market Development (existing product × new market) Take what works to a new market. **Tactics:** - New geography - New industry vertical - New customer segment (SMB → mid-market) - New use case - New channel (direct → channel; SMB → enterprise sales) **Risk profile:** Medium. Product known; market unknown. **Investment:** ~20-30%. **When dominant:** Product-market fit established in initial segment; proven by reference customers; ready to scale. ### Q3 — Product Development (new product × existing market) Build something new for people we know. **Tactics:** - New SKU / module / add-on - Adjacent product line - Platform extension - Feature line that becomes its own product **Risk profile:** Medium. Market known; product unknown. **Investment:** ~15-25%. **When dominant:** Captive audience with related JTBDs; distribution advantage; brand permission to extend. ### Q4 — Diversification (new product × new market) New thing for new people. **Tactics:** - Adjacent diversification (related to current) - Conglomerate diversification (unrelated) - Acquisition-driven new categories **Risk profile:** Highest. Both axes unknown. **Investment:** ~5-15% (or 0% — most companies should not diversify). **When dominant:** Few situations justify high diversification. Usually: mature core business with cash, declining core business needing pivot, or genuine adjacent opportunity with shared capability. ## Workflow ### Step 1 — Define "existing" precisely Most Ansoff confusion comes from vague boundaries. - "Existing market" = which segment, which geography, which buyer - "Existing product" = which SKU, which capabilities - "New" = anything outside those boundaries ### Step 2 — List current growth initiatives For each initiative, classify into a quadrant. Be honest: - "Adjacent vertical for our SaaS" = Market Development (usually) - "New module for existing customers" = Product Development - "Same product in EU" = Market Development (regulatory, cultural, linguistic differences = market difference) ### Step 3 — Score by risk-adjusted return Per initiative: - Investment size - Expected return - Risk of failure - Time to revenue - Risk-adjusted ROI ### Step 4 — Allocate across quadrants Most companies cluster in Q1 + one other. Pure diversification (Q4) is rare; usually disguised market or product development. ### Step 5 — Validate the mix Target mix depends on stage: - **Early:** 70% Q1 + 30% Q2/Q3 (split) - **Growth:** 50% Q1 + 25% Q2 + 25% Q3 - **Mature:** 30% Q1 + 30% Q2 + 30% Q3 + 10% Q4 If you're 90% Q1, you're not growing strategically. If you're 40% Q4, you're betting the company. ### Step 6 — Run `ansoff_growth_scorer.py` Score each initiative; surface mix; flag risky concentration. ```bash python3 project-management/strategy-frameworks/ansoff-matrix/scripts/ansoff_growth_scorer.py \ --input initiatives.json --format markdown ``` ## Decision frameworks ### What counts as "new market"? | Different... | New market? | |--------------|-------------| | Geography | Yes (regulation, culture, language, channel) | | Industry vertical | Yes | | Company size band (SMB → ENT) | Usually yes | | Use case (same persona) | Usually no | | Buyer persona | Yes | | Pricing tier (free vs paid) | Usually no | If you'd need a different sales motion or different channels, it's a new market. ### What counts as "new product"? | Different... | New product? | |--------------|--------------| | New SKU / module | Yes | | New pricing tier of same product | No | | New feature in existing product | No | | Significantly different value prop | Yes | | Different underlying tech | Yes | If you'd need a different roadmap and different success metrics, it's a new product. ### When diversification (Q4) makes sense - **Adjacent diversification:** shared capability or audience - Amazon → AWS: shared capability (infra) - Disney → theme parks: shared capability (IP) - **Acquisition-led:** buying expertise + product + market together - **Declining core:** need new business model When diversification fails: - "Synergies" overclaimed - Acquired company managed by incumbent culture - No shared capability or audience - Justified by spreadsheet only ## Common engagements ### "Help us prioritize growth bets" 1. List all growth initiatives. 2. Classify into quadrants. 3. Score risk-adjusted return. 4. Reconcile against stage-appropriate target mix. 5. Recommend top 5 with allocation. ### "We're considering acquiring company X" 1. Classify the acquisition by quadrant. 2. Q1 (existing × existing) = bolt-on; lower risk 3. Q2 (existing × new) = market expansion via M&A 4. Q3 (new × existing) = product line extension 5. Q4 (new × new) = highest risk; question hard ### "Should we enter market X?" 1. Confirm it's truly Q2 (new market for existing product). 2. Test: same value prop? same buyer? same channel? if all yes, it's really Q1 (different segment). 3. If true Q2, scope cost + time to validate vs Q1 alternatives. ## Anti-patterns to avoid - **Misclassifying initiatives.** Q4 dressed as Q3 or Q2 — gets approved that wouldn't pass Q4 scrutiny. - **All-Q1 portfolio.** Not strategic growth. - **All-Q4 portfolio.** Bet-the-company every quarter. - **"Adjacent" labelling.** Often hides Q4 as Q3. - **No investment percentages.** Just lists; no allocation. - **Static mix.** Should change with stage. - **Ignoring the boring Q1.** Penetration is unglamorous but highest-ROI. ## References - `references/ansoff-matrix-deep.md` — quadrant tactics, examples, risk patterns - `references/growth-strategy-patterns.md` — stage-based mixes, common pitfalls ## Related skills - `project-management/strategy-frameworks/business-model-canvas` — operational view of each quadrant - `project-management/strategy-frameworks/swot-analysis` — strategic context - `project-management/strategy-frameworks/porters-five-forces` — industry analysis - `c-level-advisor/ceo-advisor` — strategic context - `c-level-advisor/cmo-advisor` — Q1/Q2 marketing context - `c-level-advisor/cpo-advisor` — Q3 product development context
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".