Strategy Methods

Business strategy

Decide where to play, how to win and how value is created.

Starts with the external environment and competitive context, then moves through positioning, value creation, growth choices and execution.

• 1. PESTEL / STEEPLE and Scenario Planning
• 2. Porter’s Five Forces
• 3. Value Chain and Value Driver Tree
• 4. VRIO and Core Competence
• 5. Porter’s Generic Strategies
• 6. Business Model Canvas
• 7. Ansoff, Adjacency or Blue Ocean
• 8. Three Horizons, BCG or Nine-Box
• 9. Strategy Map

Digital strategy

Start from the business strategy, then feed new digital options back into it.

Identifies where digital, data and AI can change enterprise value, competition, customer experience and operating performance, then translates those priorities into the capabilities, platforms, investments and operating-model changes needed to deliver them.

• 1. Business strategy and Value Driver Tree
• 2. S-Curve and Technology Adoption Life Cycle
• 3. Customer Journey Mapping and Jobs to Be Done
• 4. Value Proposition Canvas and Kano Model
• 5. AI Value Creation and Platform Strategy
• 6. Design Thinking and Business Model Canvas
• 7. Capability Map
• 8. Digital Maturity Model
• 9. Strategic Alignment Model
• 10. McKinsey 7S operating model
• 11. Digital Transformation Roadmap
• 12. Strategy Map and benefits tracking

Diagnosis

Strategic choices

Capability and operating model

Execution and measurement

Business strategy

• Where to play: customers, markets, segments
• How to win: sources of competitive advantage
• How value is created and captured
• Growth and investment priorities

Digital strategy

• How digital, data, AI, cyber and technology enable the objectives
• Digitally enabled options that extend or transform the strategy
• Required digital capabilities; platform, data and architecture decisions
• Governance of digital investment and risk; how digital value is measured

Business strategy → digital strategy

Sets objectives, priorities and constraints.

Digital strategy → business strategy

Opens options: new models, offers, markets, cost structures.

Strategic context

Core growth 2%, EBIT 9%; board wants 8% growth and 12% margin in five years.

Strategic questions

Where to play, how to win, what to build and measure?

Evidence

PFAS rule, segment margins, 40,000 connected units, cost by activity.

Analysis

PESTEL, Five Forces, Value Chain, Value Driver Tree, VRIO.

Insights

Margin sits in service (24% vs 6%); installed-base data is the advantage.

Strategic options

Seven growth moves, from PFAS treatment to desalination plants.

Evaluation

Distance and risk-adjusted value: PFAS moves at distance 5 and 8 lead.

Strategic decisions

Differentiate on guaranteed water quality for industrial sites; drop desalination.

Required capabilities

Remote monitoring, outcome pricing, fleet-based field service.

Operating model and architecture

Service P&L, connected-asset data platform, partner equipment financing.

Investments

Growth capital split 60/30/10 across three horizons.

Execution

Three-wave roadmap with stage gates on each horizon 2 and 3 bet.

Outcomes

Eight board measures, e.g. attach 18% to 35%, uptime 99.5%+.

Learning

Enforcement-pace signpost re-times PFAS capacity; strategy refreshed.

Evidence grades

• Verified: documented fact, checked against source
• Credible estimate: modeled from verified inputs; show a range
• Expert judgment: informed view; name the expert
• Assumption: taken as true to proceed; test it
• Unknown: material gap; decide whether to buy information

Confidence labels

• High · Medium · Low, recorded per finding beside its grade
• Confidence is not importance: a low-confidence, high-impact finding is a reason to test, not to ignore
• Where uncertainty is material, use ranges, sensitivities or scenarios

Phase 1 · Diagnosis

• External forces: PESTEL, Scenario Planning
• Industry structure: Five Forces
• Technology timing: S-Curve, Adoption Life Cycle
• Customers: JTBD, Journey Mapping, Kano, VPC
• Economics: Value Chain, Value Driver Tree

Phase 2 · Strategic choices

• Position and advantage: Generic Strategies, Blue Ocean, VRIO, Core Competence
• Model: Business Model Canvas, Platform Strategy
• Growth: Ansoff, Adjacency Expansion
• Portfolio: BCG, Nine-Box, Three Horizons; AI: AI Value Creation

Phase 3 · Capabilities and operating model

• Capabilities: Capability Map; readiness: Digital Maturity Model
• Business-IT fit: Strategic Alignment Model; organization: McKinsey 7S
• New offer or service: Design Thinking Double Diamond

Phase 4 · Execution and measurement

• Sequence and fund: Digital Transformation Roadmap
• Objectives and measures: Strategy Map
• Benefits: Value Driver Tree, benefits bridge

Purpose

Build a value-ranked, governed AI use-case portfolio tied to P&L drivers.

When to use

Business strategy is set and leaders want AI value beyond pilots.

When not to use

No data access, no named business owner, or the goal is technology exploration only.

Inputs and evidence

Value driver tree, process and journey pain points, data inventory, risk appetite.

Participants

Business owners, data and AI leads, risk, legal, finance.

Deliverable

Ranked AI portfolio with value cases and a benefits bridge.

Decision supported

Which AI use cases to fund, in what wave, under which guardrails.

Quality checks

Benefits split into gross, validated, realized and capacity; owner per use case; risk review done.

Value thesis

Where AI can change the economics.

Use-case portfolio

What to do first, across three horizons.

Operating model

AI as a product: who builds and owns adoption.

Data and ML platform

The shared stack every use case reuses.

Model choices

Fit-for-purpose models, not one default.

Responsible AI

Privacy, IP, bias, security and genAI risk controls.

Change and adoption

Adoption is designed, not assumed.

Economics and metrics

Benefits against cost; fund by evidence.

Decide where to play

• 1. Value thesis: link AI to outcomes such as NRR +8 pts or cost-to-serve −20%, anchored in value driver trees.
• 2. Use-case portfolio: a pipeline across three horizons: now, next and new.

Build the product

• 3. Operating model: cross-functional AI product teams own adoption and outcomes, not just accuracy.
• 4. Data and ML platform: lakehouse, feature store, model registry, MLOps and genAI tooling.
• 5. Model choices: foundation models, fine-tuning, classical ML, solvers or hybrids.

Safeguard and adopt

• 6. Responsible AI: privacy, IP, bias, robustness and genAI risks controlled by design.
• 7. Change and adoption: process redesign, new roles, incentives and training.

Prove and fund

• 8. Economics and metrics: benefits, TCO and time-to-value, funded by evidence through lean portfolio management.

Value thesis

Link AI to strategic outcomes (NRR +8 pts, cost-to-serve −20%, OTIF +5 pts, risk losses −30%); value driver trees anchor each use case.

Use-case portfolio

A managed pipeline of use cases across three horizons, from data-ready operational wins to new AI-enabled business models.

Operating model

AI as a product: PM, data scientists, ML and software engineers, designers, SMEs and risk and legal, with OKRs and ownership of adoption.

Data and ML platform

Lakehouse, feature store, registry, pipelines, observability and CI/CD for ML, plus genAI: model hub, prompts, vector DBs, RAG, evals.

Model choices

Commercial or open-source foundation models, fine-tuning or LoRA adapters, classical ML, optimization solvers and hybrid patterns.

Responsible AI

Privacy, IP, bias, robustness, model cards and audit trails, plus genAI risks: hallucination, prompt injection and data leakage.

Change and adoption

Process redesign, role shifts, incentives and training, such as agent handoff and decision rights with human override.

Economics and metrics

Benefits (lift, savings, risk reduction) against TCO (compute, storage, licenses, engineering) and time-to-value; fund by evidence.

Most helpful for

• Enterprise transformations: AI unlocks growth and efficiency across functions.
• Platforms and ecosystems: AI embedded in APIs, marketplaces and partner tools.
• Operations and service: supply chain, pricing, marketing, risk, customer service and field operations.
• Software and data products: adding assistants, summarization and recommendations.

Especially powerful when

• Repeatable demand: many decisions or events, with access to quality data.
• AI augments humans: in workflows where people stay in the loop and decide.
• Adoption can be embedded: in CRM, ERP, contact center tools and IDEs, or exposed via APIs.

Less effective when

• One-off problems: infrequent, with limited data or unclear decision criteria.
• No plan for process change: without new incentives, models go unused.
• Unresolved regulatory or privacy constraints: risk may outweigh value.
• Possible mitigations: synthetic data, on-prem inference and strict redaction.

Blend ROI with speed

Predictive AI for mature ROI; genAI for knowledge tasks.

Standardize the platform

One AI platform and shared evaluation methods.

Govern the risk

Model risk policies tailored to genAI.

Ambition and guardrails

Value drivers

Wave 1 portfolio

AI product teams

Data and platform

Model pattern

Workflow and controls

Evaluate and pilot

Adoption and change

Scale and govern

A · Set direction

Steps 1 to 3: Set 12 to 24 month outcomes and guardrails with finance sign-off, map where AI moves the value drivers, then score 15 to 25 candidates and pick a Wave 1 of 3 to 6.

B · Build and prove

Steps 4 to 8: Staff a cross-functional team per use case, ready the data and platform, choose the model pattern, embed AI in the workflow with controls, and pilot for 6 to 12 weeks.

C · Adopt and scale

Steps 9 and 10: Train users and align incentives, then move winners to production with SLOs and monitoring, retire underperformers and rebalance the portfolio quarterly.

Set the ambition

• Define 12 to 24 month outcomes, e.g. NRR +6 pts, cost-to-serve −20%, DSO −4 days.
• Agree constraints: privacy and IP, regulatory, brand.
• Set success measures and a benefits model with finance sign-off.

Map value drivers

• Build a value driver tree for the core economics.
• Find where AI moves drivers: conversion, churn, price realization, claims cycle time, MTTR, inventory turns.
• Shortlist 15 to 25 use cases across functions.

Prioritize Wave 1

• Score on impact, feasibility (data, integration), risk, time-to-value and adoption readiness.
• Select 3 to 6 use cases: a couple of operational AI workhorses and 1 to 2 genAI copilots.

Stand up AI teams

• Per use case: product manager, SME, data scientist or ML engineer, software engineer, designer, risk partner.
• Set OKRs tied to business outcomes.
• Name the owner of adoption and change.

Ready the data

• Confirm sources, access rights and quality.
• Stand up pipelines, feature store, model registry and evaluation harness.
• For genAI: model gateway, vector store, prompt management, content filters.

Choose the model

• Build or buy: commercial LLM via API, hosted open-source model, or classical ML.
• For genAI, favor RAG before fine-tuning; use adapters for domain fit.
• For prediction, proven methods: GBMs, time-series, RL where justified.

Embed and control

• Embed AI in user flows: CRM, service desk, IDE, ERP.
• Define human-in-the-loop steps, approval thresholds and escalation.
• Add PII redaction, access control and checks for bias and hallucination.

Evaluate and pilot

• Offline and online evaluation: accuracy, win rate vs. baseline, latency, citation metrics.
• Business KPIs in A/B tests or phased rollouts.
• A 6 to 12 week pilot with success thresholds and a rollback plan.

Plan adoption

• Deliver training, playbooks and in-product guidance.
• Align incentives and decision rights.
• For copilots, set expectations (assistive, not autonomous) and when to trust vs. verify.

Scale and govern

• Move winners to production with SLOs and monitoring of drift, abuse and cost per inference.
• An AI Council sets standards, risk and funding; retire underperformers.
• Track value monthly; adjust quarterly.

Care Copilot

Generative AI

What it does: RAG over policies, tickets and product docs; suggested replies, auto-summarization and next-best-action.

Where it runs: integrated in the CRM that care agents already use.

Churn Prediction and Next Best Offer

Predictive AI

What it does: a gradient boosting model scores churn risk, with treatment experiments to find the offers that save customers.

Where it runs: outbound campaigns and in-product prompts.

Network Incident Triage

Generative AI + rules

What it does: summarizes logs, suggests probable causes and recommends playbooks.

Where it runs: network operations, with a human in the loop for every dispatch decision.

Shared platform

• Data foundation: data lakehouse with a feature store and model registry.
• Model access: an LLM gateway across commercial and open-source models.
• Retrieval: a vector database for RAG over policies, tickets and docs.
• Quality: prompt management and an evaluation suite scoring answer correctness, citation coverage and harmful content.
• Privacy: PII redaction and consent controls.

Governance

• AI Council: Product, Operations, Risk, Legal and Security.
• Use-case review: the Council reviewed each use case before it went ahead.
• Guardrails: the Council approved prompts and guardrails before release.
• Documentation: model cards and audit logs maintained for every model.
• Traceability: genAI outputs logged with versioned prompts and model IDs.

Care Copilot

−19%

Average handle time. First-contact resolution +8 pts; CSAT +6. Hallucination complaints under 0.4% with mandated citations. 95th percentile latency 1.9s.

Churn and NBO

+14%

Save rate. Incremental ARPU +$2.30 a month in the pilot cohort. SMB churn −1.8 pts.

Incident Triage

−27%

Mean time to repair. False dispatches −11%. About 12,000 analyst hours released a year: capacity, not yet P&L.

$64M

Realized P&L a year.

$14M

One-time build.

Links AI to business outcomes

Prioritizes high-ROI use cases and scales the wins that prove out.

Owns adoption, not just accuracy

An AI product operating model makes teams accountable for use and results.

Governance by design

Balances innovation with privacy, security and responsible AI from the start.

Reusable platform

Shared RAG, evaluation and MLOps components cut time-to-value for each new use case.

Needs data and platform investment

Pilots built without data readiness and platform foundations stall at scale.

Depends on process change

Technology alone will not deliver adoption; capabilities and ways of working must change.

GenAI economics shift

Model pricing moves, so cost controls and vendor diversification are necessary.

Not every problem is an AI problem

Forcing AI where simple rules suffice erodes the return.

Upstream: provides inputs

• Value Driver Tree
• Customer Journey Mapping
• Porter’s Value Chain

This method

Output: Ranked AI portfolio with value cases and a benefits bridge.

Decision: Which AI use cases to fund, in what wave, under which guardrails.

Downstream: uses the output

• Digital Transformation Roadmap
• Strategy Map

Complementary: adds insight or offsets a limitation

• Digital Maturity Model
• Platform Strategy Framework

Offsets: Scores are judgments; value cases overstate benefit unless capacity conversion is proven.

Alternative: answers a similar question

• Design Thinking Double Diamond

Start from a value thesis

Tie AI to the economics first, then pick a balanced portfolio: high-ROI operational AI plus targeted genAI copilots for knowledge-heavy work.

Run AI as a product

Cross-functional teams own workflow integration, adoption and OKRs, not just model accuracy.

Reuse one platform

Invest once in MLOps, RAG, evaluation and guardrails, with responsible AI designed in from the start.

Fund by evidence

Measure business outcomes and cost-to-serve continuously; scale only what proves value and stop what does not.

Manage risk and cost

Watch rights, privacy, hallucinations, bias, vendor lock-in and inference spend as closely as the benefits.

Is AI value real beyond the hype?

Yes, when it is tied to specific workflows and measured. Predictive and optimization use cases routinely deliver double-digit improvements in conversion, cycle time or loss rates. GenAI shows fast wins in knowledge and coding tasks when it is grounded (RAG), evaluated and embedded in tools.

Build vs. buy vs. partner for genAI?

Mix them. Use commercial APIs for speed, open-source models for control and cost in stable tasks, and partners where time-to-market or specialized capability matters. Keep a model gateway and portable prompts and data to avoid lock-in.

How do we measure ROI?

Define baselines and use A/B tests or phased rollouts. Track hard metrics (savings, revenue lift, risk reduction) and costs (engineering, licenses, inference, change management). Convert time saved into P&L only where it replaces or redeploys labor; otherwise treat it as capacity.

How long to first impact?

Six to twelve weeks for a well-scoped use case with data access and a reusable platform, such as a care or coding copilot or next-best-action. Larger redesigns, such as supply chain or pricing, take three to six months to reach scale.

What skills do we need?

AI product managers, data scientists, ML, software and data engineers, designers, and risk and legal partners, plus change management. Upskill domain teams to work with AI: prompting, evaluation and oversight.

How do we handle hallucinations and safety?

Ground answers in retrieval with citations, constrain prompts, apply content filters, keep humans in the loop for critical steps, and measure hallucination rates in an evaluation harness. Log prompts and outputs with model versions for audit.

Do we need perfect data?

No, but data must be fit for use. Start with the sources that matter most, apply redaction and quality checks, and iterate. For genAI knowledge tasks, document quality and permissions matter as much as structured data.

What about regulatory risk?

Engage Legal and Risk early. Implement model cards, data lineage, access controls, audit logs and incident response. For regulated decisions such as credit or health, keep explainability and human oversight, and document validation.

How do we control costs?

Right-size models, cache and batch, distill where possible, and use smaller local models for routine tasks. Set budgets and alerts per use case, negotiate provider pricing, and track cost per successful task.

Purpose

Prioritize concrete growth moves by distance from the core and risk-adjusted value.

When to use

A growth gap exists and there is a list of candidate moves.

When not to use

The core itself is weak or unprofitable; fix it first.

Inputs and evidence

Core definition, candidate moves, market sizing, capability assessment.

Participants

Strategy, business-unit leads, finance, product.

Deliverable

Scored adjacency matrix and staged growth portfolio.

Decision supported

Which moves to fund now, pilot or drop.

Quality checks

Distance and value scored separately; probabilities evidenced; low and high cases shown.

What it does

• Evaluates and prioritizes growth moves that sit “next to” a company’s core.
• Covers new products, customer segments, geographies, channels, business models and value-chain steps.
• Answers which adjacencies to pursue, in what order, and with what level of conviction.

The two factors it weighs

• Distance: how far a move is from your core.
• Value: how much you can realistically capture (Risk-Adjusted Value).
• Plotting both separates near-core extensions with high odds of success from far-core distractions that strain capabilities and dilute focus.
• Broad growth tools stop at “new markets” or “diversification”; this one makes the trade-off explicit.

Where it is used

• Consultants and corporate strategy teams.
• Growth programs, portfolio reviews and M&A scans.
• Gives a shared, evidence-based way to prioritize a pipeline of expansion ideas.
• Translates strategy into staged bets, capability builds and governance choices.

Map opportunities

Plot potential moves based on how closely they align with our current business.

Evaluate

Score each move’s distance (0 to 21) and ability to win (low, medium, high).

Prioritize & act

Start top-left, then move every shortlisted option onto the principal matrix to size value.

Horizontal axis: Distance from the Core

A composite measure of how far the move is across common adjacency vectors.

• Customer segments and needs (same vs. new)
• Product and technology (same vs. new tech stack)
• Channel and go-to-market (existing vs. new)
• Geography (current vs. new markets)
• Value chain (current steps vs. upstream or downstream)
• Capabilities and operating model (same vs. new)
• Business model and economics (same vs. new logic)

Score 0 to 3 per vector and sum to a 0 to 21 index; ≤7 reads as low distance.

Vertical axis: Risk-Adjusted Value at Stake

Value at stake × probability of success, net of investment.

• Value at stake: capturable profit pool in 3 to 5 years
• Ability to win: advantage held or buildable
• Probability of success and time to impact

Score attractiveness and ability to win separately, then combine.

Core Extensions

Low distance, high value

• Expand where current assets and playbooks travel well
• Build on existing advantages
• Prioritize for near-term growth

Option Bets

High distance, high value

• Large upside with meaningful capability gaps or uncertainty
• Pursue as staged options
• Ring-fenced with clear milestones and decision points

Incremental / Efficiency Moves

Low distance, lower value

• Smaller wins and efficiency gains
• Pursue selectively
• Prioritize if they unlock capabilities or scale benefits

Distractions

High distance, lower value

• Weak value or poor fit
• Avoid
• Partner only if there’s a compelling strategic rationale not captured by the model (e.g., regulatory hedge)

Transparent scoring of distance

Breaking “distance” into vectors makes the trade-offs explicit and shows precisely why a move is hard, and what it would take to reduce distance (build or buy capabilities, hire talent, partner).

Value-at-stake and feasibility

The vertical axis is not just TAM; it’s your capture potential, adjusted for execution risk, timing, and required investment.

Horizontal axis: Distance from the Core

A composite measure of how far the move is across common adjacency vectors:

• Customer segments and needs (same customers vs. new buyers or needs)
• Product and technology (same platform vs. new technology stack)
• Channel and go-to-market (existing routes vs. new channels or partners)
• Geography (current markets vs. new countries or regions)
• Value chain (current steps vs. upstream or downstream integration)
• Capabilities and operating model (current playbooks vs. new capabilities)
• Business model and economics (same unit economics vs. new revenue or pricing logic)

Score 0 to 3 per vector (0 same, 3 entirely new) and sum to a 0 to 21 index. Treat ≤7 as low distance.

Vertical axis: Risk-Adjusted Value at Stake

Combine two separately scored judgments, then risk-adjust:

• Market attractiveness (1 to 5): size, growth and structural profitability of the profit pool
• Ability to win (1 to 5): advantage you hold or can credibly build
• Value at stake ($): profit pool × achievable share over 3 to 5 years
• Probability of success (0 to 1): evidence-based, informed by distance and ability to win
• Risk-adjusted value = value at stake × probability of success, shown net of investment and time to impact

Scores are ordinal judgments; only the dollar estimate is a financial value. Test it with a low and a high case.

Core Extensions

Low distance, high value: prioritize for near-term growth.

Option Bets

High distance, high value: stage with clear milestones.

Incremental Moves

Low distance, lower value: pursue selectively.

Distractions

High distance, lower value: avoid.

Most helpful for

• Established companies with a clear core seeking disciplined, non-speculative growth.
• Portfolio strategy and M&A to screen targets and opportunities by closeness to core and realistic value creation.
• Go-to-market and channel expansion (e.g., direct-to-consumer, marketplaces, enterprise vs. SMB).
• Geographic expansion where regulatory, channel, and customer differences drive distance.
• Vertical integration moves that may be “adjacent” in the value chain but differ materially in capabilities.

Especially powerful when

• You have distinctive capabilities and a scalable operating model (brand, technology platform, supply chain) that can travel to adjacent spaces.
• Leadership needs a single, comparable view across many ideas, with resource constraints forcing sharp priorities.
• There’s temptation to chase fashionable spaces (e.g., “AI,” platforms) without a clear path to advantage.

Less effective when

• Your “core” is not well-defined or underperforming; fix the core first, or the distance metric becomes meaningless.
• The industry is undergoing discontinuous change where adjacency logic breaks (e.g., disruptive platforms collapsing value chains).
• Data to estimate capture potential are extremely sparse; you may need discovery-driven planning or real options analysis first.

Experimentation

Pilot launches, A/B tests, and learning loops.

Real options

Value flexibility and stage investment.

Capability roadmaps

Close key gaps to reduce distance over time.

Iterate often

Rescore vectors as strategy, markets, and capabilities evolve.

Define and stress-test your core

State where you have a clear right to win, and test it with data.

Generate a concrete list of adjacency moves

List specific moves across the seven distance vectors.

Score distance from the core

Score each vector 0 to 3 and sum the scores to a distance index.

Estimate value-at-stake and capture potential

Size the prize, then adjust it for the probability of success.

Assess capability gaps and paths to close them

Name the capabilities needed to win; choose build, buy or ally.

Plot the Adjacency Expansion Matrix

Plot distance from the core (low to high) against risk-adjusted value at stake (low to high); size bubbles by value.

Prioritize and define the growth portfolio

Pick a balanced set of core extensions and option bets.

Design market tests and stage gates

Pilot the top moves behind stage gates with pre-set triggers.

Align operating model, capital, and incentives

Assign owners and governance; release capital in tranches.

Monitor, learn, and refresh

Re-score quarterly and reallocate as pilot results arrive.

Define and stress-test your core

Write a crisp statement of where you have a clear right to win: customers, needs, products, channels, geographies, capabilities, economics. Validate with data (relative market share, unit economics, NPS, cost position). Without a strong core baseline, adjacency decisions drift.

Generate a concrete list of adjacency moves

Across the seven vectors, brainstorm specific moves: sell the platform to mid-market healthcare, enter Mexico via distributor, add managed services, integrate backward into a key component, launch subscription pricing. Keep each move crisp enough to evaluate.

Score distance from the core

Use a rubric (0 = same, 1 = similar, 2 = different, 3 = new) for each vector. Assign scores per move and sum to a distance index. Document assumptions, and calibrate by scoring a few known in-core moves to anchor the scale.

Estimate value-at-stake and capture potential

Size TAM and reachable market, estimate unit economics, investment required and time to impact. Adjust for probability of success using analogous cases or pilots. Express as risk-adjusted NPV or EBIT at steady state with time to breakeven. Keep ranges.

Assess capability gaps and paths to close them

List the capabilities needed to win (enterprise sales, regulatory, data science, local channel partners). Rate current strength, then choose build, buy or ally. Estimate timeline and cost; this drives feasibility and staging.

Plot the Adjacency Expansion Matrix

Place each move on the matrix: horizontal is the distance index, vertical is risk-adjusted value at stake. Size the bubble by value-at-stake or required capital, and color-code by vector to spot patterns.

Prioritize and define the growth portfolio

Select a balanced set: a few Core Extensions for near-term results and a limited number of Option Bets with ring-fenced funding and milestones. Be explicit about what you will not do, and set guardrails such as 70/20/10 across near, mid and long term.

Design market tests and stage gates

For the top moves, define pilots with named customers, offer, channels and metrics. Tie stage gates to leading indicators (CAC and LTV, conversion, sales cycle, feasibility), and pre-define triggers to scale, redesign or stop.

Align operating model, capital and incentives

Assign accountable leaders for each move and decide governance: core business or ring-fenced venture. Align incentives to portfolio role and option value, release capital in tranches tied to milestones, and plan the capability builds.

Monitor, learn and refresh

Review the portfolio quarterly. Re-score distance as capabilities and partnerships change, update attractiveness with pilot results and market shifts, then reallocate: double down, pause or exit, and communicate the decisions transparently.

7%

Revenue growth in year two, up from 3%.

$18M

Energy-analytics ARR, ahead of the $15M gate.

62%

Of retrofit sales made to existing customers.

1 of 2

Option bets scaled; Mexico stopped at gate 2.

Strengths

• Brings discipline to growth by making “distance to core” explicit and comparable across ideas.
• Focuses on capture potential, not just market size, by integrating capability fit and feasibility.
• Creates a shared language for prioritization and portfolio balance (extensions vs. options).
• Translates directly into action: pilots, capability builds, partnerships and staged investment.
• Useful for M&A screening: filters targets by closeness to core and realistic synergy realization.

Limitations

• Distance is multi-dimensional and judgment-heavy; inconsistent scoring can bias decisions.
• Can anchor teams too tightly to the core, underweighting transformational opportunities in discontinuous markets.
• Static snapshots miss learning effects; distance can shrink quickly with capability acquisition or partnerships.
• Does not replace market structure analysis (e.g., Five Forces) or customer insight; it complements them.
• May undercount integration complexity and culture risk unless explicitly considered.

Upstream: provides inputs

• Ansoff Matrix
• Core Competence Framework
• VRIO / VRIN Analysis

This method

Output: Scored adjacency matrix and staged growth portfolio.

Decision: Which moves to fund now, pilot or drop.

Downstream: uses the output

• Business Model Canvas
• Digital Transformation Roadmap

Complementary: adds insight or offsets a limitation

• Porter’s Five Forces
• McKinsey Three Horizons of Growth

Offsets: Distance index is ordinal; value estimates for far moves are highly uncertain.

Alternative: answers a similar question

• Ansoff Matrix
• Blue Ocean Strategy Canvas

Compared directly in Commonly confused methods.

Prioritize on two axes

The Adjacency Expansion Matrix prioritizes growth moves by plotting risk-adjusted value against distance from the core.

Break distance into vectors

Use concrete vectors (customers, product and technology, channel, geography, value chain, capabilities, business model) to make capability gaps explicit.

Build a balanced portfolio

A few near-core extensions for reliable growth, plus a limited number of option bets with stage gates.

Pair it with other analysis

Combine the matrix with market structure analysis and pilots; it is a prioritization tool, not a substitute for diligence.

Refresh it frequently

Capabilities and market conditions evolve, and distance can shrink quickly with the right partners or acquisitions.

Is it still relevant in fast-moving, digital markets?

Yes. If anything, it’s more useful. Digital lowers barriers in some vectors (e.g., channels) but raises the bar on capabilities (e.g., product, data and AI). The matrix helps you see where your platform really travels and where to partner.

How is this different from the Ansoff Matrix?

Ansoff shows generic growth directions. The Adjacency Expansion Matrix evaluates specific moves by distance-to-core and capture potential, enabling apples-to-apples prioritization and staged investment decisions.

Can small or mid-market companies use it?

Absolutely. Keep it lean: list 8 to 12 concrete moves, score distance with a simple rubric, size value with ranges, and pick two or three to pilot. The discipline prevents overreach and focuses finite resources.

How long does a rigorous prioritization take?

Typically 4 to 6 weeks: 1 to 2 weeks to define the core and generate moves, 1 to 2 weeks to score distance and size value, and 1 to 2 weeks to design pilots, governance and capital tranches. A rapid workshop version can be done in days.

How do we quantify distance objectively?

Use vector-based scoring with clear rubrics and reference cases. Calibrate by scoring known in-core moves first. Involve cross-functional leaders to reduce bias, and document assumptions alongside scores.

How many adjacency bets should we run at once?

Most companies succeed with three to five active moves: two or three near-core extensions and one or two option bets. More than that often dilutes leadership bandwidth and slows learning.

Purpose

Frame growth options across existing and new products and markets.

When to use

Early growth framing or communicating options to leadership.

When not to use

You need to rank specific moves or quantify risk.

Inputs and evidence

Current products, markets, growth gap, market trends.

Participants

Strategy, marketing, product, BU leads.

Deliverable

Growth-direction map with option list.

Decision supported

Which growth directions to explore further.

Quality checks

Each option has a growth logic and a risk note; quadrant boundaries defined.

Market Penetration

Existing products × existing markets

• Grow share and usage where you already compete
• Pricing, packaging, distribution, loyalty and cross-sell
• Fastest and lowest risk; watch for price wars

Product Development

New products × existing markets

• New products and services for customers you serve
• Line extensions, data layers, bundles, outcome offers
• R&D and go-to-market load; cannibalization risk

Market Development

Existing products × new markets

• Take current products into new markets
• New geographies, segments, channels, price points
• Localization and compliance cost; refit the fit

Diversification

New products × new markets

• New-to-firm products for new customer groups
• Platform extensions, category creation, acquisitions
• Highest uncertainty; fund it in staged bets

Origin

• Introduced by H. Igor Ansoff in his 1957 Harvard Business Review article, “Strategies for Diversification”.
• Expanded in his 1965 book, Corporate Strategy.
• Written when large companies were rapidly widening portfolios and entering new markets.

Why it was created

• To give executives a clear map of growth alternatives and their relative risk.
• To separate the choice of what you sell from the choice of who you sell it to.
• To make the risk gradient between the four options explicit rather than intuitive.

How it became known

• Spread through business schools and consulting practice as a way to structure growth discussions.
• Adopted for portfolio planning and board conversations because the 2×2 is deliberately simple.
• Stays useful when paired with Jobs-to-Be-Done, Lean Startup, profit pools, VRIO and GE-McKinsey.

Market Penetration

Current products × current markets

What it is: Gain share and usage where you already compete.

Typical plays: Pricing and packaging, distribution breadth, sales coverage, loyalty and cross-sell.

Risks: Fastest and lowest risk; returns hinge on unit economics and competitive response.

Product Development

New products × current markets

What it is: Build new products or services for customers you already serve.

Typical plays: Adjacent features, line extensions, services, data layers, bundles, outcome-based offers.

Risks: R&D and go-to-market complexity; cannibalization risk offset by installed base and brand.

Market Development

Current products × new markets

What it is: Enter new geographies, channels, segments or use cases with existing products.

Typical plays: International expansion, vertical entry, e-commerce and OEM channels, tailored price points.

Risks: Distribution, localization and compliance costs; product-market fit must be revalidated.

Diversification

New products × new markets

What it is: New-to-firm products for new customer groups, related or unrelated.

Typical plays: Platform extensions, category creation, corporate venturing, acquisitions.

Risks: Highest uncertainty; the value case needs option value and staged learning, not just NPV.

Horizontal axis: products

Your current product is what you sell today, described precisely:

• The same platform, feature set and technology stack
• The same price band, packaging and licence model
• The same delivery, onboarding and support motion

Treat a product as new when it needs:

• New engineering, IP or a different technology base
• A new pricing or packaging logic
• A new support, service or delivery capability

Vertical axis: markets

Your current market is who you sell to today, described precisely:

• The same buyer persona and job-to-be-done
• The same geography, language and regulatory regime
• The same channels and routes to market

Treat a market as new when it needs:

• A different segmentation or buying center
• New geography, localization or compliance work
• A new channel, partner or distribution model

Market penetration

Current products, current markets. Lowest risk.

Market development

Current products, new markets. Distribution and compliance risk.

Product development

New products, current markets. Build and cannibalization risk.

Diversification

New products, new markets. Highest uncertainty.

Most helpful for

• Strategy and portfolio offsites: a shared view of growth pathways and relative risk.
• Annual planning: balancing near-term penetration with product and market adjacencies.
• Board and investor narratives: explaining where growth comes from and why it is credible.
• Build-buy-ally decisions: clarifying whether the gap is product, market or both.

Especially powerful when

• You need a shared language to compare disparate growth ideas.
• Debates confuse how to grow with where to grow.
• Resources are constrained and you must pick a few coherent bets.

Less effective when

• “Product” and “market” are defined vaguely, producing apples-to-oranges comparisons.
• The matrix is used alone, without customer insight, capability assessment or economics.
• The risk gradient is applied mechanically; adjacency logic matters more than labels.

Jobs-to-Be-Done

Anchor growth in real customer needs.

Profit Pool Mapping

Understand where value is created and captured.

VRIO capability fit

Assess whether you can win and sustain advantage.

Lean Startup

Test assumptions and learn before you scale.

Stage-gate funding

Fund in stages with clear milestones and exit criteria.

Define products and markets precisely

Write down the current product and current market, then specify what is new about each proposed move and why.

Build the idea backlog and classify

Assign every idea to a quadrant with a one-line hypothesis. Break ideas that span quadrants into testable increments.

Link to customer need and structure

Articulate the job-to-be-done and buying criteria, then summarize industry structure and profit pool potential.

Assess capability fit and complexity

Score each idea on capability adjacency and organizational readiness. Note the gaps to build, buy or ally.

Quantify economics and risk

Develop directional unit economics, market size, investment required and time to revenue. Use ranges and scenarios.

Prioritize a balanced portfolio

Typically 50 to 70% penetration and near adjacencies, 20 to 40% product or market development, 10 to 20% diversification.

Design experiments and stage gates

Define MVPs, pilots and lighthouse customers with explicit success thresholds and pre-agreed stop, pivot or scale rules.

Choose build, buy or ally paths

Decide whether to build the capability, acquire it or partner. Diversification often leans on tuck-in M&A or alliances.

Align operating model and incentives

Penetration relies on sales excellence, market development on channel muscle, product development on engineering.

Track leading indicators and refresh

Build a growth dashboard by quadrant covering pipeline, activation, adoption and learning. Refresh choices quarterly.

Market penetration

Moves: Good/better/best repackaging with usage-based add-ons, stronger customer success, targeted pricing, referral and champion programs.

Impact: NRR rises from 112% to 118%, win rate up 4 points, +$60M ARR over three years.

Product development

Target: Analytics and workflow automation add-on for existing customers.

Moves: Automation templates, usage-based pricing, top-five integrations, 50 lighthouse customers.

Impact: 28% attach by Year 3, +$95M ARR, lower churn from embedded workflows.

Market development

Target: Professional services and healthcare in Europe, via channel partners.

Moves: Localized compliance, two EU identity providers, five regional SIs, EUR and GBP list pricing.

Impact: $85M ARR by Year 3 with acceptable CAC payback through partner-led deployments.

Diversification

Target: Field collaboration for frontline workers in manufacturing and logistics.

Moves: Acquire a $20M ARR mobile-first startup, pilot with two logistics firms, partner with a device OEM.

Impact: $40M ARR by Year 3 if pilots clear their gates, plus a capability lift in mobile and offline sync.

55%

To penetration and product development.

30%

To market development in Europe.

15%

To diversification options.

Strengths

• A simple, shared language for cataloguing growth paths and their relative risk.
• Forces clarity about what is actually changing: the product, the market, or both.
• Supports a balanced portfolio of near-term plays, medium-term adjacencies and options.
• Works across industries and company sizes.
• Pairs well with modern experimentation and stage-gate funding.

Limitations

• Over-simplifies when “product” and “market” are loosely defined.
• Does not quantify attractiveness or feasibility; needs Five Forces, profit pools and VRIO.
• Underplays operating model implications such as channels, service, compliance and localization.
• The risk gradient can mislead: a close adjacency can be safer than defending a hostile core.
• Says nothing about sequencing or capacity to execute in parallel.

Upstream: provides inputs

• PESTEL / STEEP / STEEPLE Framework
• Porter’s Five Forces

This method

Output: Growth-direction map with option list.

Decision: Which growth directions to explore further.

Downstream: uses the output

• Adjacency Expansion Matrix
• Business Model Canvas

Complementary: adds insight or offsets a limitation

• Core Competence Framework

Offsets: Binary existing/new axes hide degrees of distance.

Alternative: answers a similar question

• Adjacency Expansion Matrix
• Blue Ocean Strategy Canvas

Compared directly in Commonly confused methods.

Four paths, four risk profiles

Penetration, market development, product development and diversification each carry distinct risks, economics and capability needs.

Definitions come first

Define product and market precisely, classify every idea, and build a balanced, stage-gated portfolio matched to risk appetite and capacity.

The 2×2 is a frame, not an answer

Layer in customer insight, industry structure, economics and capability fit to choose where to play.

Buy knowledge before scale

Design experiments and milestone gates, especially for product development and diversification, to convert uncertainty into evidence.

Fit the operating model to the path

Align channels, incentives and capability builds to the quadrants you chose, and refresh the portfolio quarterly.

Is the Ansoff Matrix still relevant?

Yes, provided you pair it with customer insight, experimentation, profit pools and VRIO, and treat it as a portfolio with staged funding rather than a one-shot bet.

How is Ansoff different from BCG?

BCG classifies businesses by growth and share to guide cash flows. Ansoff structures growth moves by product and market newness. Use BCG to decide where you are strong, Ansoff to decide how to grow.

How do we quantify risk and return?

Build directional unit economics, capability fit through VRIO and structural attractiveness through Five Forces and profit pools. Use scenarios, not point estimates.

Should startups use Ansoff?

Yes, lightly. Focus on penetration and product development tied to the core job-to-be-done. Treat market development and diversification as options once repeatability is proven.

How long is a planning cycle?

Typically 4 to 6 weeks to define, classify, analyze and set a staged portfolio. Penetration can start immediately; the development quadrants need 1 to 3 quarters of validation.

What is the biggest mistake teams make?

Treating the 2×2 as the answer rather than the beginning. Without precise definitions, evidence, capability fit and stage-gate discipline, Ansoff becomes a slogan.

Purpose

Classify businesses by market growth and relative share to guide cash allocation.

When to use

Multi-business portfolio with comparable market data.

When not to use

Single business, or share is a poor proxy for advantage.

Inputs and evidence

Market growth rates, relative market share, cash flows by unit.

Participants

Corporate strategy, finance, BU heads.

Deliverable

Portfolio matrix with role and cash stance per unit.

Decision supported

Invest, hold, harvest or divest per business.

Quality checks

Market definitions defensible; relative share = own share ÷ largest rival.

Stars

High growth · High share. Invest to lead.

Question Marks

High growth · Low share. Bet selectively or exit.

Cash Cows

Low growth · High share. Defend and harvest.

Dogs

Low growth · Low share. Harvest, exit or hold.

Origin

Developed by Bruce D. Henderson at the Boston Consulting Group in the early 1970s, and published in BCG’s Perspectives series.

It was an answer to a live leadership problem, not an academic exercise: diversified groups had no shared way to compare unlike businesses competing for the same capital.

The problem it solved

Conglomerates and diversified corporations needed a systematic way to allocate scarce capital among business units with very different growth prospects and competitive positions.

• No common yardstick. Each unit argued from its own numbers, so capital followed advocacy rather than logic.
• Cash, not just profit. Growth consumed cash faster than mature units could report it.

Two ideas, linked

BCG linked two powerful ideas to build a portfolio view that balanced cash generators against cash consumers.

• Experience-curve effects. Scale lowers unit costs over time, so share is a proxy for cost position.
• The cash demands of growth. Fast-growing markets absorb working capital, marketing and capacity.

How it spread

The Growth-Share Matrix became widely known through BCG’s Perspectives series and has been taught in business schools and used on consulting engagements for decades.

• Critiqued for simplicity. Two proxies cannot capture every portfolio.
• Still influential. Its vocabulary and cash logic shape how leaders discuss portfolios today.

Stars

High growth · High relative share

Leaders in fast-growing markets. They absorb heavy investment to keep pace, but become tomorrow’s cash engines.

Posture: invest to hold leadership, drive scale and prepare the shift to Cash Cow.

Question Marks

High growth · Low relative share

Also called Problem Children. Attractive markets where you lack scale, so they consume cash without assured leadership.

Posture: bet selectively to build share, or exit where the path to leadership is weak.

Cash Cows

Low growth · High relative share

Mature, dominant businesses that generate more cash than they need to fund their own growth.

Posture: defend efficiently, optimize margins and harvest cash for Stars and selected Question Marks.

Dogs

Low growth · Low relative share

Small players in mature markets. They generate modest cash and have limited potential.

Posture: harvest or exit; hold only for a defensible niche or cash-positive role.

Experience curve

Unit costs fall as cumulative output doubles, so share proxies cost position.

Cash flow balance

Growth consumes cash; mature leaders generate it. A portfolio balances both.

Lifecycle movement

Units travel Question Mark to Star to Cash Cow to Dog; strategy manages it.

Market growth rate

Vertical axis

A proxy for how attractive the market is. High-growth markets demand more investment (working capital, marketing, capacity) but offer headroom to build scale and value.

• Setting the threshold. Define high against low using the company’s weighted average market growth, or an absolute cutoff agreed up front.
• Where the number comes from. Growth is read from market data for the whole segment, not from internal sales, and forecast growth matters more than history.
• Reading the matrix. High growth sits at the top; low growth at the bottom. Movement downward is normal as markets mature.
• Cash meaning. Growth is a claim on cash before it is a source of it, which is why Stars and Question Marks sit in the top half.
• What it does not tell you. Growth is not the same as industry attractiveness. A fast-growing market with poor structure can still destroy value.

Relative market share

Horizontal axis

A proxy for competitive advantage, usually tied to scale and experience-curve efficiency. It is measured against the leader, not the whole market.

Relative market share = your market share divided by the largest competitor’s share.

• Reading the ratio. Above 1.0 means you are the leader; below 1.0 means you are a follower.
• Test the definition. Check sensitivity to the competitor you benchmark (global or regional leader) and to the market boundary you drew.
• Reading the matrix. High relative share sits on the left; low share on the right.
• What it does not tell you. Share is a weak proxy where differentiation, defensible niches or network effects drive economics instead of scale.

Most helpful for

• Diversified corporations, multi-brand or multi-product companies, and private equity platforms needing a top-down view of where capital should go.
• Portfolio reviews across business units, product lines, geographies or customer segments with reasonably clean market boundaries and comparable data.
• Annual planning, strategy offsites and pre-deal screening, to set invest, hold, harvest and exit priorities.

Especially powerful when

• Scale effects are meaningful (manufacturing, consumer goods, industrials) and reliable market share and growth data exist.
• You need a common language and a simple visual to align an executive team quickly on portfolio choices.
• Capital is constrained, so the portfolio has to fund its own growth agenda from internal cash.

Less effective when

• Businesses are deeply interdependent through shared platforms or cross-selling, or sit on multi-sided platforms where share on one side does not map to economics.
• Network effects, winner-take-all dynamics or regulatory shifts can overwhelm the growth and share proxies.
• Data on market definitions, size and competitor shares is unreliable or varies by source.

Clarify scope

Define the portfolio, the decision horizon and the capital choices at stake.

Define the units

Pick SBUs with distinct customers, competitors and economics; record each market boundary.

Gather data

Market size and growth, your share and the leader’s, profit, cash and capital needs.

Compute relative share

Your share divided by the largest competitor’s; test alternative definitions.

Set thresholds and plot

Agree high against low growth, then plot units with bubbles scaled by revenue.

Assess cash balance

Identify which units generate excess cash and which consume it.

Assign postures

Set the default play for each quadrant, then tailor it unit by unit.

Stress-test

Layer economics, industry structure, disruption scenarios, synergies and options.

Allocate capital

Reallocate opex and capex, set targets, define deals, codify exit plans.

Align and implement

Socialize the picture, settle definitions, stand up governance and KPIs.

Revisit periodically

Refresh at least annually, and more often in volatile sectors.

Clarify scope and decision

Define the portfolio, a three-to-five-year horizon and the choices at hand: invest, maintain, harvest, exit.

Define the units of analysis

Choose SBUs with distinct customers, competitors and economics. Avoid over-aggregation or false precision.

Gather data

Market size, historical and forecast growth, your share and the leader’s, profit, cash and capital intensity.

Compute relative market share

Your share divided by the largest competitor’s. Test global against regional leaders and other boundaries.

Set thresholds and plot

Define high against low growth using weighted average growth; scale bubbles by revenue or profit.

Assess cash flow balance

Estimate which units throw off cash and which absorb it, then test whether growth can be self-funded.

Assign strategic postures

Set the default play per quadrant, then tailor it: invest to lead, defend and harvest, bet selectively, exit.

Stress-test with other lenses

Layer ROIC and economic profit, Five Forces, disruption scenarios, synergies and real options.

Translate into capital allocation

Reallocate opex and capex, set growth and margin targets, define deals, codify harvest and exit plans.

Align stakeholders and implement

Socialize the picture, settle definitions and thresholds, then stand up reviews, KPIs and tracking.

Revisit periodically

Refresh at least annually, and more often in volatile sectors, as growth, share and economics shift.

Insights

Cash came from pumps and selected service regions, but sensors were underinvested and capital was sprayed across too many valve bets. The hydrogen opportunity was real, though leadership was not assured in every subsegment.

Decisions

Raised capex and go-to-market spend in sensors. Defended pump margins and redirected 15% of pump cash to growth. Concentrated hydrogen bets on two subsegments with a path to #1 to 2 share and exited a third. Left three loss-making service geographies.

Outcome after 12 to 18 months

Sensors grew more than 20% with improved margins. Pump margins held despite inflation. The valve portfolio clarified: one subsegment moved toward Star status and another was exited, freeing capital for higher-return uses.

Clarity and speed

Distills a complex portfolio into a simple visual map that anchors executive dialogue.

Allocation discipline

Forces an explicit trade-off between funding growth and harvesting mature assets.

Cash flow logic

Links growth demands and scale economics to the company’s own funding capacity.

Common language

The Star, Cash Cow, Question Mark and Dog taxonomy builds shared understanding across functions and units.

Simplifying proxies

Market growth is not industry attractiveness, and relative share is not advantage where niches or network effects rule.

Static snapshot

It captures today’s position, not the trajectory or the speed of change.

Ignores synergy and fit

Interdependencies can justify holding or investing in a Dog or a Question Mark.

Data sensitivity

Results hinge on market definitions and share estimates; inconsistent boundaries mislead.

Not sufficient alone

Without ROIC, economic profit and risk analysis it overweights growth and scale, and underweights returns.

Upstream: provides inputs

• Porter’s Five Forces

This method

Output: Portfolio matrix with role and cash stance per unit.

Decision: Invest, hold, harvest or divest per business.

Downstream: uses the output

• Digital Transformation Roadmap
• Strategy Map

Complementary: adds insight or offsets a limitation

• McKinsey Three Horizons of Growth

Offsets: Two variables only; share-profit link is weak in many digital markets.

Alternative: answers a similar question

• GE-McKinsey Nine-Box Matrix

Compared directly in Commonly confused methods.

Two axes, four postures

The matrix maps businesses by market growth and relative share to guide portfolio resource allocation.

It suits diversified portfolios

Most powerful where data is reliable and scale effects are meaningful enough to make share a real advantage.

Cash Cows fund the agenda

Stars and selected Question Marks warrant investment; Dogs are harvested, exited, or held only for strategic reasons.

It is a starting point, not a verdict

Augment it with ROIC, industry structure, synergies and scenarios to avoid simplistic conclusions.

Definitions decide the answer

Get market boundaries and share estimates right, and revisit them as growth and economics shift.

Is it still relevant today?

Yes, with judgment. It still frames portfolio discussions and resource allocation well, especially where scale effects matter. Leading practitioners pair it with ROIC and economic profit, industry structure analysis and scenario planning to capture platforms, digitization and regulation.

How does it differ from the Nine-Box?

BCG uses two simple proxies, growth and relative share, which buys speed and clarity. The GE-McKinsey Nine-Box uses multi-factor scores for attractiveness and competitive strength: more nuance, more work. Use BCG for fast triage, the Nine-Box when other factors decide.

Can early-stage companies use it?

A firm with a handful of products can use a simplified version to prioritize bets, but data is often thin and network effects distort share. Focus on unit economics, acquisition dynamics and real options, and treat BCG as a heuristic rather than a gatekeeper.

How long does it take to apply?

A rapid diagnostic for a mid-size portfolio takes two to four weeks with existing data. A rigorous exercise (refreshed market definitions, external benchmarking, profitability and cash modeling, executive alignment) typically takes six to ten weeks.

What data do I need to get started?

At minimum: market size and growth, your share and the largest competitor’s share, and basic financials such as revenue, margin and capex. Quality improves substantially with cleaner market definitions, external benchmarks, and an understanding of capital intensity and synergies across the portfolio.

Purpose

Compare offerings on competing factors and design a differentiated value curve.

When to use

Crowded markets with converging offers.

When not to use

Regulated offers with little design freedom.

Inputs and evidence

Competing factors, customer and non-customer research, cost data.

Participants

Strategy, product, marketing, customers.

Deliverable

Strategy canvas and ERRC grid.

Decision supported

Which factors to cut, raise and create in the offer.

Quality checks

Factors come from customer evidence; cost impact of each change estimated.

Four Actions Framework

Eliminate, Reduce, Raise, Create. The mechanism for redesigning your value curve once the baseline is plotted.

Six Paths Framework

Reconstructs market boundaries by looking across industries, strategic groups, buyer groups, complementary offerings, functional and emotional appeal, and time.

Buyer Utility Map

Designs adoption and usage value across the buyer experience cycle, removing the hurdles that stop people buying.

Competing factors

The x-axis. The buyer-relevant elements the industry invests in and communicates. For airlines: price, lounges, schedule variety, hub convenience, meals, seat pitch, on-time performance.

Factors must reflect customer value as outputs, not internal activities as inputs. “24/7 chat support” is a factor only if customers see it as a tangible benefit, rather than “resolution speed and confidence”.

Offering levels

The y-axis. Using a normalized low-to-high scale, draw a line for each major competitor showing how much value it delivers on each factor.

Those lines are the value curves.

You will often see rivals’ curves cluster tightly. That clustering is the evidence of head-to-head competition, and the reason incremental differentiation stops paying.

The redesign

The Four Actions Framework. Eliminate factors the industry takes for granted but customers no longer value; reduce those that can sit below standard; raise a few far above standard; create new ones that unlock demand.

Eliminating and reducing frees the cost that funds raising and creating, which is what makes the move affordable.

The x-axis: factors of competition

• What belongs on it. The buyer-relevant elements the industry invests in and communicates, from price through service to convenience.
• How many. Ten to fifteen at most. More than that becomes noise and hides where the focus is.
• How to phrase them. As outcomes the buyer feels: setup time, confidence in the result, availability at short notice, total price transparency.
• Where they come from. Customer interviews, win-loss analysis and jobs-to-be-done work, not an internal feature list.
• The common failure. Inside-out factors such as “AI” or “24/7 chat” describe activities. “Resolution speed and confidence” describes value.

The y-axis: offering level

• What it measures. How much value each player delivers on each factor, on one normalized low-to-high scale. A 1 to 5 rating is enough.
• What to score. Three to six primary competitors and substitutes, including the do-nothing workaround, which usually scores near zero on almost everything.
• Evidence to use. Customer research, third-party benchmarks and observable proxies such as published prices, service levels and feature availability. Record your confidence level.
• High is not always good. A high level on a cost-driving factor customers do not value is overserving, and it is where the funding for your raises comes from.

Where curves cluster

Every player has converged on the same profile. That is a red ocean, and one more increment buys nothing.

Where the industry overshoots

High levels on factors buyers shrug at: cost carried with no reward, and the first candidates to eliminate or reduce.

Where buyers report pain

Low levels on outcomes that matter most. Raise these, or create a factor that removes the barrier entirely.

Eliminate

Which factors does the industry take for granted that customers no longer value? Removing them strips out cost and complexity at the same time.

Example: in-site upsell scripts, obscure billing codes and non-essential paperwork at check-in.

Reduce

Which factors can sit below the industry standard? Curate rather than bloat: most feature lists carry weight no buyer asked for.

Example: the long-tail test menu at retail sites, decorative facility frills and manual phone scheduling.

Raise

Which factors should be far above the industry standard? Overdeliver on the few attributes that decide the purchase.

Example: all-in price transparency, evening and weekend availability, time in site under ten minutes.

Create

Which new factors could unlock demand or remove adoption friction? These usually come from noncustomers’ jobs rather than current users.

Example: pharmacy micro-sites, same-day results and patient-controlled sharing links.

Most helpful for

• Strategy refresh. When markets have converged and “differentiation” has become incremental. The canvas shows how tightly rivals have clustered.
• New venture. To define a distinctive value proposition for a new business or category, grounded in buyer utility and a cost logic rather than ambition.
• Turnarounds. To simplify a bloated offer, cut cost drivers customers do not value, and refocus on the few factors that decide the sale.
• Portfolio. To rationalize products, tiers and prices around clear value patterns instead of accumulated feature creep.

Especially powerful when

• Customers are over-served. They pay for features they never use, so the industry is carrying cost that buys no preference. That is funding waiting to be redeployed.
• Customers are under-served. Incumbents underweight dimensions buyers care about most, typically convenience, speed and risk reduction.
• Noncustomers rely on workarounds. People avoid or delay the purchase because existing offers are too complex, expensive or inconvenient. Removing that barrier is where most blue oceans start.

Less effective or misleading when

• Factors are defined inside-out. If the x-axis lists activities and technologies rather than buyer outcomes, every curve on the chart is measuring the wrong thing.
• It is run as a branding exercise. No ERRC cost logic and no willingness-to-pay evidence produces a nice picture and an unfunded promise.
• Structural barriers dominate. Network effects, regulation or platform gatekeepers sit outside the canvas, so pair it with ecosystem and industry-structure lenses.

Define arena

Set product scope, buyer group and geography, then list the noncustomers who avoid the category.

Find factors

From interviews, win-loss analysis and jobs-to-be-done work, agree 10 to 15 buyer-relevant factors.

Benchmark

Rate three to six rivals and substitutes, including do-nothing, on a 1 to 5 scale. Plot the curves.

Diagnose

Mark where curves cluster, where the industry overshoots, and where buyers report real pain.

Apply ERRC

Choose what to eliminate, reduce, raise and create, then draft the new value curve.

Test utility

Concept-test with buyers and noncustomers. Check utility gains, the tagline and willingness to pay.

Cost model

Quantify savings from the cuts and the investment in raises. Confirm more utility at equal or lower cost.

Go to market

Align channel and message to the new curve, and clear the remaining adoption hurdles.

Pilot

Launch in one segment or region. Track outcome KPIs, cost to serve and uptake of created factors.

Scale

Codify the operating model, standardize the cuts, deepen the moats and refresh the canvas annually.

Steps 1 to 5

Establish the baseline and design the new curve.

Steps 6 to 10

Turn the picture into a funded, operating business.

Define the arena and target buyers

Specify the product or service scope, the buyer group (user, purchaser, influencer) and the geography. List the noncustomers who avoid or underuse the category and the jobs they are trying to get done; blue ocean opportunities often start there.

Identify the competing factors

Through customer interviews, win-loss analysis and jobs-to-be-done work, compile the factors customers use to compare alternatives. Keep them buyer-relevant and finite, 10 to 15 at most, phrased as outcomes such as setup time, confidence in the result or total price transparency.

Benchmark the current value curves

For three to six primary competitors and substitutes, including the do-nothing workaround, rate offering levels on each factor using a 1 to 5 scale. Use customer and third-party evidence where possible, note your confidence level, then plot the curves.

Diagnose convergence and overserve

Highlight where curves cluster, which is me-too competition; where most players overshoot, carrying high cost for little incremental value; and where customers report pain, meaning low offering levels on the outcomes they rank highest.

Apply the Four Actions Framework

As a team, propose factors to eliminate and reduce to free cost and simplify, select a few to raise dramatically, and brainstorm new factors to create that address noncustomer barriers or high-friction jobs. Draft the new value curve.

Test utility and willingness to pay

Run concept tests with target buyers and with noncustomers. Validate that the new curve produces clear utility gains and a tagline people repeat back to you. Estimate willingness to pay and place the offer inside a strategic price corridor.

Build the cost model

Quantify the savings from eliminated and reduced factors across materials, labor, channel and service, and the investment required for what you raise and create. Confirm value innovation: higher utility at equal or lower cost to serve, with healthy margins at the chosen price.

Design go-to-market and adoption

Align channel and messaging to the new curve. Use the Buyer Utility Map to remove the hurdles that remain across purchase, delivery, use, supplements, maintenance and disposal. Craft a bold, credible tagline.

Pilot and iterate

Launch in a focused segment or region. Track outcome KPIs such as time saved, conversion, repeat purchase and NPS, alongside cost to serve and uptake of the factors you created. Adjust the factors and the price corridor, then prepare to scale.

Scale and defend

Codify the operating model and standardize what you eliminated and reduced so the cost base stays low. Where imitation risk is real, deepen the moats through data, brand promises, partnerships and process IP. Refresh the canvas annually.

8 minutes

Median time in site.

72%

Same-day results on targeted panels.

+23

NPS against baseline.

−30%

No-show rate, on SMS reminders and easy rescheduling.

−18%

Cost to serve per test.

3

Companies in employer subscription pilots, which created steady volume.

A shared picture

It creates a common, visual understanding of how the industry competes today and where you could diverge, which is hard to reach through discussion alone.

Value and cost together

ERRC forces simultaneous attention to both, which reduces the risk of expensive differentiation theater.

Centered on buyer outcomes

It integrates naturally with jobs-to-be-done research and adoption design.

Portable

It works across B2C and B2B, and applies equally to services, digital products and physical goods.

Subjectivity

Factor selection and scoring carry judgment, so the chart needs customer evidence and external benchmarks to be trusted.

It ages

A static snapshot can date quickly as platform rules, regulation and technology shift the factors of competition.

Blind to structure

Network effects and control points sit outside the canvas unless you pair it with ecosystem and Five Forces lenses.

No funding, no value

A great curve without cost alignment or price discipline destroys value rather than creating it.

Upstream: provides inputs

• Jobs to Be Done
• Porter’s Five Forces

This method

Output: Strategy canvas and ERRC grid.

Decision: Which factors to cut, raise and create in the offer.

Downstream: uses the output

• Business Model Canvas

Complementary: adds insight or offsets a limitation

• Value Proposition Canvas
• Kano Model

Offsets: Uncontested space rarely stays uncontested; imitation follows.

Alternative: answers a similar question

• Porter’s Generic Strategies

One page, one picture

The canvas captures how an industry competes today and where you can focus and diverge to create a blue ocean. Its value is that a mixed group of executives can argue over one chart instead of five competing presentations.

Factors first, then ERRC

Define buyer-relevant factors, plot the current value curves, then use eliminate, reduce, raise and create to design the new one. Skipping the baseline turns the exercise into wishful drawing.

Value and cost together

Value innovation comes from utility shifts and cost moves at once. Price inside a strategic corridor so the offer reaches the mass of target buyers rather than a premium fringe.

Start with noncustomers

Include noncustomers and substitutes, including the do-nothing workaround, in the baseline. Many blue oceans come from removing adoption barriers rather than beating a rival on a factor everyone already competes on.

Operationalize, then refresh

Align channel, process, sourcing and KPIs to the new curve, and give the eliminates and reduces an owner so costs stay out. Then refresh the canvas as factors, technology and market structure move.

How many factors should the canvas hold?

Keep it to 10 to 15 buyer-relevant factors. More than that becomes noise and hides where the focus is. Use jobs-to-be-done interviews to confirm that each factor describes an outcome the buyer feels rather than an internal feature.

How do we score competitors objectively?

Use customer research, third-party benchmarks and observable proxies: published prices, service levels, feature availability and the drivers behind Net Promoter scores. Note your confidence level on each score and update it as you learn, and avoid self-serving internal ratings.

Is the canvas only for consumer markets?

No. It works well in B2B and in services, from professional services to SaaS and logistics. The factors change, moving toward integration, risk, compliance and total cost of ownership, but the method is identical.

Do we always have to lower cost?

The goal is value innovation: higher buyer utility at lower or equal cost. Eliminating and reducing factors buyers do not value should fund any raises or creations. Without that funding you risk a fragile premium niche rather than a scalable blue ocean.

How long does a canvas project take?

Typically four to eight weeks: one to two weeks to define scope and factors, one to two to collect data and build the baseline curves, one to two for the ERRC design and the cost and price model, and one to two for concept tests and go-to-market alignment. Piloting then continues in market sprints.

What if platform or regulatory gatekeepers limit our moves?

Overlay an ecosystem perspective, such as an extended Five Forces view or an ecosystem map. Sometimes the blue ocean is a change of role, becoming an orchestrator or a risk and identity layer, rather than a product shift. Engage standards bodies and policymakers early.

Should we build a separate brand for the new curve?

Only if the new curve conflicts with your existing brand promises or channels. Otherwise lead with a bold sub-brand and a clear tagline, and test with customers to see whether the brand stretch helps or hurts adoption.

How do we stop the curve drifting back to the industry norm?

Institutionalize the eliminates and reduces in process and governance, set KPIs that reward the raised and created factors, appoint a curve steward in product or marketing, and review the canvas in quarterly strategy cadences.

Purpose

Describe and redesign the business model in nine linked blocks.

When to use

Designing a new model or testing changes to an existing one.

When not to use

You need detailed financials or competitive analysis.

Inputs and evidence

Value proposition, segments, cost and revenue data.

Participants

Strategy, product, finance, operations.

Deliverable

Current and target business model canvases.

Decision supported

How value will be captured and what must change.

Quality checks

Revenue and cost blocks reconcile to unit economics; assumptions tagged.

Key Partnerships

Suppliers, platforms, channel partners, regulators, financiers.

Key Activities

What we must do exceptionally well.

Key Resources

Tech, data, brand, IP, talent, capital.

Value Propositions

The bundle that solves pains and creates gains for each segment.

Customer Relationships

Self-serve to personal, by segment.

Channels

How we reach, sell and deliver.

Customer Segments

Distinct groups defined by needs and behaviors.

Cost Structure

Fixed and variable costs the model implies.

Revenue Streams

How and what each segment pays.

Market-facing (right)

Customer Segments, Value Propositions, Channels and Customer Relationships: who you serve, what you offer and how you reach, sell to and keep each segment.

Operations (left)

Key Resources, Key Activities and Key Partnerships: the assets, capabilities and outside parties that make the offer possible and reduce risk.

Economics (bottom)

Revenue Streams and Cost Structure: how customers pay, the pricing logic and unit drivers, and the fixed and variable costs the other blocks imply.

Segment-specific logic

Treat each meaningful segment as its own mini-model.

Many failed canvases come from averaging across segments that differ in their jobs, channels, pricing and economics.

Draw a separate canvas, or a lane, wherever those differ, so each segment carries its own value, channels, pricing and unit economics.

Evidence over assumption

Annotate each block as hypothesis or validated.

Upgrade confidence with experiments (MVPs), cohort data and unit economics rather than opinion.

A block without evidence is a claim still to be tested; the riskiest claims get the first experiments.

Most helpful for

• New venture design: clarify the end-to-end model before deep build or go-to-market spend.
• Strategy refresh or pivot: visualize shifts such as product to subscription, on-prem to SaaS or linear to platform.
• Portfolio and M&A: compare targets or units on model logic, synergies and integration needs.
• Executive alignment: give product, sales, finance and operations a common language.

Especially powerful when

• Customer needs are clearer than the model: test pricing, channels and delivery before scaling.
• You orchestrate an ecosystem: show multi-sided platform or marketplace logic on one page.
• Unit economics matter: connect them to operating choices (they always matter).

Less effective when

• Static poster: used without experiments, metrics or economic proof.
• Complex, regulated operations: banking or healthcare simplified without compliance and risk controls in activities, resources and partners.
• Averaged segments: hides that segments need different offers, channels and pricing.

Define scope and segments

Customers and value

Channels and relationships

Revenue and pricing

Resources, activities, partners

Costs and unit economics

Assumptions vs. evidence

MVP learning loops

Stress-test structure and risk

Execution and governance

A · Design the model

Steps 1 to 6: Scope the canvas, split it by segment, then work from customers and value through channels, revenue, the operating backbone and the cost structure until each segment has unit economics.

B · Test the evidence

Steps 7 to 9: Mark every block as hypothesis, validated or unknown, test the riskiest ones with MVPs against set thresholds, then stress-test the model against industry structure and risk.

C · Execute and govern

Step 10: Turn the validated canvas into OKRs, an initial operating model and a roadmap, and release funding in stages as the evidence builds.

Scope and segments

Write a one-sentence scope (product or service, geography, customer type). Identify distinct segments, such as SMB vs. enterprise or buyers vs. users; give each its own mini-canvas where jobs and economics differ.

Customers and value propositions

For each segment, set out the job to be done, pains and desired outcomes, then draft value propositions that address them. Capture proof (benchmarks, case studies, SLAs); mark unknowns as hypotheses to test.

Channels and relationships

Detail how prospects discover, evaluate, buy, receive and get support. Separate direct, partner, marketplace and self-serve motions, and set the relationship model: self-serve or high-touch, onboarding, expansion.

Revenue and pricing logic

Choose revenue types (subscription, usage, transaction, licensing, ads, financing) and pricing metrics (per seat, per transaction, % of GMV). Sketch price corridors by segment and link them to willingness to pay.

Resources, activities, partners

List the few things you must be world-class at, such as matching, risk assessment or fulfillment. Name enabling resources and partners or gatekeepers (cloud, payment rails, app stores, regulators) and their control points.

Costs and unit economics

Outline fixed and variable costs: CAC, COGS, delivery and operations, support, R&D, compliance and partner fees. Calculate contribution margin and payback per segment (LTV/CAC, gross margin, key drivers), with ranges and sensitivity bands early.

Assumptions vs. evidence

Color-code or annotate each block as hypothesis (H), validated (V) or unknown (?). Add planned experiments (MVPs) to test the riskiest assumptions, such as price acceptance, partner readiness or channel effectiveness.

MVP learning loops

Design tests for the riskiest blocks: price tests, concierge pilots, channel trials, partner integrations and limited rollouts. Set decision thresholds (e.g. activation of at least X%, payback within Y months) and update the canvas.

Stress-test structure and risk

Overlay competitive structure (Five Forces), platform and gatekeeper risk, regulatory constraints and supply-chain resilience. Note mitigations in partnerships, activities and resources; adjust pricing and costs to match.

Execution and governance

From the validated canvas, define OKRs, an initial operating model (organization, processes, KPIs) and a roadmap. Use an Agile Stage-Gate cadence to release funding in stages as the evidence builds, so money follows proof rather than the plan.

Renters

Profile. Urban, price-sensitive, DIY install, short tenure.

Value proposition. “Instant, flexible protection with month-to-month plans; move-with-you simplicity.”

Homeowners

Profile. Suburban, willing to pay for peace of mind, higher ARPU potential.

Value proposition. “Professional-grade security with proactive detection; lower insurance; family safety features.”

Small businesses

Profile. Need compliance and multi-site cover; willing to pay for an SLA.

Value proposition. “SLA-backed monitoring, compliance reports, multi-site dashboard and incident evidence.”

Channels

D2C web and app; retail trials for Segment A; insurance brokers and local installers for B and C; property-manager partnerships for A.

Customer Relationships

Self-serve onboarding with optional paid install; 24/7 support; customer success for C; community features for B.

Revenue Streams

Tiered subscriptions (Basic, Plus, Pro), device financing, add-ons (cloud storage, AI analytics, share of insurance discounts) and business SLAs for C.

Key Resources and Activities

AI models for proactive detection, monitoring-center integration, device firmware and platform, and an installer network for C.

Key Partnerships

Monitoring centers, insurers (discount programs), a financing partner for device loans, property managers and local installers.

Cost Structure

Device COGS, cloud costs for video, monitoring fees, CAC through retail and partners, AI R&D, support, and the cost of capital for financing.

64%

Subscription share of revenue, up from 38%.

59%

Service gross margin.

2.5 months

Faster blended payback.

113%

Segment C NRR.

Shared visual language

Describes and innovates business models; fast to create and easy to iterate.

Links value to operations and economics

Keeps teams honest about viability.

Works at any scale

From start-up to enterprise, and for product, service and platform models, including multi-sided canvases.

Makes trade-offs visible on one page

Clarifies what the business will not do.

Superficial without evidence

Needs MVPs, unit economics and structural analysis behind it.

One canvas hides segment differences

Requires multiple canvases or lane overlays.

Snapshots go stale

In dynamic markets it needs a cadence to refresh and govern it.

Silent on competitive strategy and industry power

Complement it with Five Forces and profit pools.

Upstream: provides inputs

• Value Proposition Canvas
• Porter’s Generic Strategies

This method

Output: Current and target business model canvases.

Decision: How value will be captured and what must change.

Downstream: uses the output

• Capability Map
• Strategy Map

Complementary: adds insight or offsets a limitation

• Platform Strategy Framework
• Value Driver Tree Analysis

Offsets: Static snapshot; no competitor view.

Alternative: answers a similar question

• Porter’s Value Chain

Compared directly in Commonly confused methods.

A one-page blueprint

Nine blocks show how you create, deliver and capture value, and force clarity and trade-offs on a single page.

Build it by segment

Start with customers and value, connect channels, pricing, operations and costs, then quantify unit economics for each segment.

Keep it living

Annotate assumptions vs. evidence, validate the riskiest blocks with MVPs and refresh the canvas regularly.

Pair it with other tools

JTBD and the Value Proposition Canvas for customer truth, Lean and MVP loops for evidence, Five Forces and profit pools for structure.

Align, then execute

Use the canvas to align teams and investors quickly, then turn it into OKRs, roadmaps and an operating model.

What are the nine blocks?

Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships and Cost Structure: customers, value, routes to market, operations and economics.

How is it different from the Lean Canvas?

Lean Canvas, built for start-ups, swaps some blocks for Problem, Solution, Key Metrics and Unfair Advantage to stress hypothesis discovery. The BMC is broader and better for operating detail, multiple segments and scaling.

Can it handle platforms and marketplaces?

Yes. Use one canvas per side plus an interaction map of cross-side value, pricing (take rates, subsidies) and governance (quality, leakage). Many teams add a network-effects overlay.

How often should we update it?

At every major learning event (pilot result, price test, channel trial) and at least quarterly during build and scale. Date and version each canvas and keep a change log.

What level of detail belongs on it?

Enough to drive decisions: segment definitions, outcome-based value statements, main channels and pricing metrics, top three to five costs, key partners and gatekeepers, unit-economics ranges.

How do we connect it to financials?

Turn Revenue Streams and Cost Structure into a unit-economics model (ARPU, CAC, gross and contribution margin, payback), then a P&L and cash-flow forecast with scenarios; validate with MVPs.

What if we have multiple products?

Draw a canvas per product or segment where the model differs, then a portfolio canvas showing shared resources, channels and partnerships and the consolidated Cost Structure.

Where do risk and compliance fit?

In Key Activities (controls, monitoring), Key Resources (licenses, data governance), Partnerships (vendors, regulators) and Cost Structure; SLAs and certifications go in Value Propositions.

Purpose

Model stable business capabilities and highlight strategically critical gaps.

When to use

Translating strategy into investment, operating model or architecture.

When not to use

Strategy choices are not yet made.

Inputs and evidence

Strategic choices, value streams, process and application inventory.

Participants

Business architects, BU leads, IT, operations.

Deliverable

Capability map and strategy heatmap.

Decision supported

Which capabilities to invest in, fix, outsource or retire.

Quality checks

Capabilities are outcome-based, not org units; ratings evidenced.

Define

Build a taxonomy of business abilities, named as nouns and agnostic of org, process and technology.

Decompose

Break Level 1 into Level 2 to 3 only where a decision needs the extra granularity.

Attach facts

Add diagnostic attributes and overlay heatmaps that show gaps, spend and risk hotspots.

Govern

Use the map to prioritize investment and steer change through owners and a review cadence.

Core concepts

• Capability. A business ability to achieve an outcome, e.g., Fraud Detection, not “detect fraud in system X.”
• Level 1. About 15 to 30 top-level capabilities, e.g., Order Fulfillment, Risk & Compliance.
• Level 2 to 3. Decompose where decisions need it: Customer Onboarding → Identity Verification → KYC/AML Monitoring.
• Heatmaps. Red, amber and green overlays that show gaps, investment needs or risk hotspots.

Outputs

• An enterprise capability taxonomy (L1 to L2/3) with clear definitions
• Heatmaps for maturity, performance, spend, risk and technology fit
• Traceability to value streams and the application portfolio
• A prioritized, evidence-based investment portfolio: modernize, build, buy, partner or retire

Strategic importance

Must-win or parity: is the capability differentiating, parity or utility?

Performance and maturity

Current versus target state, rated 1 to 5 with evidence.

Cost to serve

Run-rate opex and capex, plus FTE.

Technology fitness

Fit-gap against the target architecture, including technical debt.

Risk and compliance posture

Control effectiveness and open issues.

Owner and metrics

Accountable owner, decision rights and key metrics.

Strategy → Capabilities

Strategic themes decide which capabilities are differentiating (invest) and which are utility (standardize or outsource).

Capabilities ↔ Value streams

Map capabilities to end-to-end flows such as Acquire → Onboard → Serve → Expand to see where weakness hurts outcomes.

Capabilities ↔ Applications and data

Show which applications support each capability, often many-to-many, to expose duplication, technical debt and modernization priorities.

Capabilities ↔ Organization

Name accountable owners, such as capability councils, regardless of current functional silos.

Most helpful for

• Strategy execution. Translate themes such as “move to subscription” into upgrades: Usage Metering, Pricing & Packaging, Customer Success.
• Operating model design. Define what needs an owner across business and technology; clarify decision rights and skills.
• Technology modernization. Link capabilities to applications and data to rationalize platforms and set the target architecture.
• M&A. Compare acquirer and target maps to find overlaps, integration hotspots and synergy plays.
• Cost & complexity resets. Find non-differentiating capabilities to standardize, automate, outsource or sunset.
• Risk & compliance. Confirm that critical control capabilities exist and meet evidence thresholds.

Especially powerful when

• Functional views create blind spots and business and IT need one stable language
• Priorities are contested and heatmaps with data create fact-based alignment

Less effective when

• Taxonomy theater: boxes with no attributes, owners or decisions
• Built by IT or the business in isolation
• Used as a rigid blueprint that does not evolve

Clarify purpose and scope

Why you map, for which entity, and which decisions.

Draft a Level 1 taxonomy

15 to 30 abilities in plain business language.

Decompose to Level 2/3 where needed

Only where decisions need the granularity.

Attach attributes and baseline

Criticality, maturity, spend, tech fit, risk, owner.

Link to value streams and applications

Expose pain points and duplicate systems.

Identify gaps and investment options

Build, buy, partner, outsource or retire.

Prioritize with a transparent lens

Impact × feasibility × risk × time-to-value.

Assign ownership and governance

Business owner, tech co-owner, decision rights.

Embed in portfolio and OKR cycles

Fund the gaps; tie OKRs to maturity targets.

Refresh quarterly

Update evidence; keep versions and decision logs.

Clarify purpose and scope

• Decide why you are mapping (technology rationalization, operating model redesign, M&A integration) and for which entity: enterprise, business unit or region.
• Set a time horizon and list the decisions the map must inform in the next 3 to 6 months.

Draft a Level 1 taxonomy

• Start with 15 to 30 Level 1 capabilities. Use industry templates as prompts, but write in plain business language: what the business must do, not how or who.
• Prefer specific abilities (Record to Report) to function names (Finance).

Decompose to Level 2/3

• Drill down selectively for capabilities central to your decisions, e.g., Customer Onboarding → Identity Verification → Watchlist Screening.
• Give each capability a concise definition to cut debate.

Attach attributes and baseline

For each scoped capability, collect:

• Strategic criticality: differentiating, parity or utility
• Maturity/performance: 1 to 5 scale with evidence (KPIs, SLAs, audit results)
• Spend: run-rate opex/capex and FTE estimates
• Technology fitness: fit to target architecture, technical debt, vendor risk
• Risk/compliance: control effectiveness, open issues
• Owner & metrics: accountable leader and key KPIs/OKRs

Use simple RAG heatmaps and annotate every source: H = hypothesis, V = validated.

Link to value streams

• Map each capability to the value streams it supports and the applications and data domains that enable it.
• This exposes process pain points and application redundancies, such as three systems supporting one capability.

Identify gaps and options

For red and amber differentiating capabilities, define options: build, buy, partner, outsource or retire. Quantify rough value, cost, risk and dependencies, then place them on a multi-quarter roadmap.

Prioritize transparently

Score options on impact × feasibility × risk × time-to-value. Keep traceability to strategy, value stream outcomes and architectural principles, and show trade-offs in a visual investment heatmap.

Assign owners and governance

Appoint capability owners: business accountable, technology co-owner. Define decision rights over standards, tooling, data policies and process changes, and set a cadence to review KPIs, maturity and progress.

Embed in portfolio and OKRs

Turn prioritized gaps into funded initiatives and link OKRs to capability maturity or outcome targets, e.g., onboarding time-to-first-value ≤ 1 day. Require a capability impact statement in every business case.

Refresh quarterly

Update attributes with new evidence and adjust priorities as outcomes and constraints change. Keep versions and decision logs for transparency.

−61%

Median onboarding time, from 7.5 to 2.9 days.

−24%

Fraud loss rate, with regional control variance reduced.

+9%

ARPU in the embedded cohort after tiered and usage pricing.

−38%

Manual reconciliation effort; close time down 25%.

Common language

A stable, strategy-led vocabulary that bridges business and technology.

Focused investment

Directs money to the few capabilities that drive outcomes and takes politics out of prioritization.

Operating model clarity

Clarifies ownership, skills and decision rights across functions.

Evidence-based rationalization

Ties systems to capabilities, so application decisions rest on facts.

Taxonomy risk

Can become a naming exercise if not tied to attributes, owners and decisions.

Cross-functional effort

Needs engagement from business and technology; siloed creation undermines adoption.

Not a process or change method

It must link to value streams and governance to change outcomes.

Upfront data effort

Initial collection takes work; resist overengineering and start where decisions need facts.

Upstream: provides inputs

• Business Model Canvas
• Core Competence Framework
• Customer Journey Mapping

This method

Output: Capability map and strategy heatmap.

Decision: Which capabilities to invest in, fix, outsource or retire.

Downstream: uses the output

• Digital Transformation Roadmap
• Strategy Map

Complementary: adds insight or offsets a limitation

• Digital Maturity Model
• Strategic Alignment Model
• McKinsey 7S Framework

Offsets: Can become an inventory exercise detached from decisions.

Alternative: answers a similar question

• Porter’s Value Chain

Compared directly in Commonly confused methods.

A stable blueprint

The map shows what the enterprise must be able to do, independent of the current org, processes or systems.

Facts, then heatmaps

Attach criticality, maturity, spend, tech fit and risk, and heatmap the gaps to prioritize on evidence.

Linked to execution

Trace capabilities to value streams and applications to connect strategy to delivery and modernization.

Owned and refreshed

Assign owners and decision rights, embed the map in portfolio, OKR and governance cycles, and refresh quarterly.

Used with other frameworks

Combine it with operating model and architecture frameworks to align people, process and technology on outcomes.

Level 1

15 to 30 abilities, named as nouns.

Attributes

Criticality, maturity, spend, tech fit, risk, owner.

Linkages

Strategy, value streams, applications, organization.

Cadence

Attributes quarterly, taxonomy annually.

What is the difference between a capability and a process?

A capability is a stable business ability, the what; a process is the flow of activities, the how, that realizes it. Capabilities change slowly with strategy; processes change often as you optimize delivery.

How many Level 1 capabilities should we have?

Typically 15 to 30. Fewer hides important distinctions; more becomes unmanageable. Decompose selectively to Level 2/3 where it informs real decisions.

Who should own a capability?

A senior business leader accountable for outcomes, with a technology co-owner. The owner sets standards, KPIs and investment priorities across functions and geographies.

How do we measure capability maturity?

Define a 1 to 5 rubric per capability covering people, process, technology, data and controls. Anchor ratings in evidence (KPIs, SLAs, audit findings, architecture fit) and reuse the rubric to show progress.

How often should we refresh the map?

Quarterly for attributes and priorities, annually for the taxonomy, and after major strategic shifts, acquisitions or platform changes.

What tools should we use?

Start with spreadsheets and visualization tools for speed, then move to EA or portfolio tools, such as capability modeling in architecture suites, as governance matures.

The tool matters less than clear definitions, evidence and ownership.

How does it help rationalize tech?

Mapping applications to capabilities shows duplication and gaps.

You can then consolidate to one platform per capability where appropriate, plan retirements, and invest where technology fitness constrains outcomes.

Can small companies benefit?

Yes, if it stays light: a concise Level 1 map and 2 to 3 attributes (criticality, maturity, tech fit).

Focus on the top 5 gaps tied to your near-term objectives.

How do we avoid taxonomy debates?

Agree decision principles upfront (purpose, scope, naming), name one editor and timebox the work.

Build the taxonomy only to the level current decisions need, then iterate with real use.

Purpose

Identify and exploit competences that underpin several products.

When to use

Diversified firms planning growth or sourcing choices.

When not to use

You need a test of advantage for a single resource; use VRIO.

Inputs and evidence

Product portfolio, technology and skill inventory, customer value data.

Participants

Strategy, R&D, BU leads, HR.

Deliverable

Core competence inventory with product linkages.

Decision supported

Where to build, protect and extend competences; what not to outsource.

Quality checks

Each competence contributes to customer value in more than one market.

What it is

The collective know-how that lets a firm combine skills, technologies and organizational learning into a stream of differentiated products and services.

What it is not

A single product, department or technology. A competence travels across product lines, opens new markets and is hard to copy quickly.

What it is for

Focusing investment, make-buy-ally choices, roadmaps, M&A and the operating model on a few competences, not a spread of features and silos.

How to spot one

It passes three tests: customer benefit, market access and inimitability.

Before: the portfolio of businesses

Capital and talent allocated unit by unit, product by product; shared know-how is invisible.

After: the portfolio of competences

Capital and talent allocated to the few competences that feed many units and future products.

Customer benefit

The test. The competence makes a significant contribution to the benefits customers perceive in the end product or service.

In practice. It directly underpins outcomes customers care about, such as reliability, security, precision or ease of use.

Evidence. Price premium, win/loss reasons, NPS and outcome metrics.

Market access

The test. The competence gives potential access to a wide variety of markets.

In practice. It is useful in more than one current product and can seed adjacent offerings.

Evidence. How many current and planned offerings it underpins, and where else it could credibly travel.

Inimitability

The test. The competence is difficult for competitors to imitate quickly.

In practice. Protection comes from accumulated learning and the integration of technologies, data, culture and relationships.

Evidence. What makes it hard to copy, and how fast a rival could match it.

Core competences

The source of advantage. Fund and protect it.

What it is. Deep, cross-cutting know-how that no single unit or product owns.

Examples. High-precision motion control; end-to-end identity and security; real-time perception and planning; clinical workflow integration.

Why it matters. Few in number, typically three to five. Built over years; lost fast without investment.

Core products

Also called platforms: where competences become reusable.

What it is. Subsystems or modules that embody a competence and are reused across product lines.

Examples. A motor control module, an inference engine, a secure ID SDK.

Why it matters. Speed up innovation and lower cost, provided product teams actually consume them.

End products and services

Where value is captured.

What it is. Customer-facing offerings that combine core products with other elements to deliver benefits.

Examples. The offers customers buy and compare, and the layer rivals see and copy first.

Why it matters. Many and changing. Judge them by how well they carry the competences to market.

Identify

Use the three tests to separate true competences from functional strengths such as “marketing” or standalone technologies.

Map

Build a competence-product matrix: which competences enable which current and planned offers, and where the gaps and overreliance sit.

Invest

Put capital and talent behind a small number, typically three to five. Avoid spreading effort across too many “priorities.”

Exploit

Turn competences into reusable core products and platforms to speed innovation and cut cost; make sure product teams use them.

Defend

Build isolating mechanisms such as data and IP, playbooks, partner ecosystems and certification, so rivals cannot copy quickly.

Valuable

It lifts the customer benefits or the economics that the first test identified.

Rare

Few rivals hold it at the same depth, so it sets the firm apart.

Inimitable

Rivals cannot copy it quickly, because of learning, data, IP or integration.

Organized

Decision rights, processes, talent and technology are in place to exploit it consistently.

Most helpful for

• Strategy refresh. Refocusing on differentiating capabilities once product competition has commoditized.
• Portfolio and platform design. Deciding which technology and subsystem platforms to build and reuse across offers.
• Adjacency expansion. Choosing new markets and products where your competences naturally travel.
• Make-buy-ally decisions. Deciding which competences to own and where to partner for non-core elements.
• M&A and alliances. Screening targets for competence fit and integration potential, and avoiding deals that distract from core strengths.

Especially powerful when

• Rivals copy product features fast, and lasting advantage lies in embedded know-how and integration.
• You need to cut complexity by building shared platforms instead of bespoke solutions per product or team.
• You are moving from products to solutions or ecosystems (services, data, platforms) and need an anchor for investment.

Less effective or misleading when

• Competences are vague functions (“innovation,” “quality”) with no measurable link to customer benefit or economics.
• Markets are strict commodities or tightly regulated, leaving little room for know-how to change outcomes.
• Teams use the language of core competence to justify pet projects, without evidence or selection discipline.

Anchor on benefits

Segments, valued outcomes, WTP.

Inventory candidates

Deep skills across the value chain.

Apply the three tests

Plus VRIO; most will fail.

Build the matrix

Competences against offers.

Pick three to five

Explicit trade-offs.

Build platforms and offers

Reusable modules, APIs.

Invest, protect and grow

Fund competences as assets.

Make, buy or ally

Own the core, source the rest.

Align operating model

Owners, budgets, incentives.

Refresh annually

Update the evidence.

Find and choose

Steps 1 to 5.

Build, fund and renew

Steps 6 to 10.

Anchor on benefits

Define target segments and the outcomes customers value most: uptime, precision, safety, time-to-value, total cost. Quantify willingness to pay, retention drivers and cost-to-serve where possible, so only competences that move the economics stay in the field.

Inventory candidates

List the deep skills and technologies across the value chain: R&D, product, operations, data, sales and service. Focus on integrated know-how (“real-time scheduling under uncertainty”), not tools or departments, and include relational assets such as ecosystems, channels and regulatory expertise.

Apply the three tests

• Customer benefit: which end-user outcomes does it enable? Evidence: price premium, win/loss, NPS, outcome metrics.
• Market access: how many current and potential offers does it underpin, and where else can it travel?
• Inimitability: what makes it hard to copy (data, IP, path dependence, social complexity)? How fast could a rival match it?
• Organization (VRIO): are decision rights, processes, talent and tech in place? Most candidates should fail a test.

Build the matrix

Map shortlisted competences against current and planned offers. Look for under-exploited strengths (applied to too few products), over-dependence (one competence carrying too much without redundancy) and white spaces where competences could create advantage.

Pick three to five

Select the competences that best align to customer benefit, travel to several offers, and can be defended and scaled. Make the trade-offs explicit: what you will not pursue, and what you will source from partners.

Build platforms and offers

Create core products that embody each competence: SDKs, control modules, data services, playbooks. Define APIs, documentation and governance so product teams adopt them, and align roadmaps for reuse and continuous improvement.

Invest, protect and grow

• Fund competences like assets: talent systems (hiring pipelines, guilds, rotations); tooling and data (labs, datasets, infrastructure); IP and data rights and partner contracts; training and codified practice.
• Track: leading indicators (adoption, reuse, performance) and lagging economic impact (price premium, cost reduction, retention).

Make, buy or ally

Own the competences you bet on; consider alliances or sourcing for non-core elements. Build where you can be distinctive, partner where the market is superior, and acquire selectively to accelerate a competence.

Align operating model

Appoint competence owners (centers of excellence or platform product leads) with decision rights and budgets. Reward product teams for reusing core platforms through funding models and performance reviews, and avoid P&L silos that fragment competence investment.

Refresh annually

Competences erode as rivals learn and technologies shift. Review the evidence, update the matrix, and adjust the portfolio of competences and platforms.

Motion control

Precision motion control. Low jitter and path accuracy lift quality and cycle time. Reused across every arm; protected by proprietary control algorithms and calibration routines.

Passes all three tests

Safe interaction

Safe human-robot interaction. Force and torque sensing plus safety certifications that customers value. Reusable across lines; hard to copy fast because of standards and certification know-how.

Passes

Fast reconfiguration

Rapid cell reconfiguration. Modular tooling, drag-and-drop programming and validated task templates cut time-to-value across verticals. Moderate imitation barrier, strengthened by data and templates.

Passes with investment

Systems integration

On-site systems integration. Strong individuals but inconsistent playbooks, and not rare. Fails the organization test; needs standardizing or a partner model.

Not a core competence

3 to 4%

Price premium where advanced safety is needed.

41%

Of new installs attach the safety subscription.

10 → 6 wks

Deployment time where templates were used.

+11 pts

Customer NPS.

70%

Of projects now partner-led integration.

+250 bps

Internal services margin.

~20%

Less engineering effort per product update.

Focus on what lasts

Shifts attention from products and organizational boxes to the few capabilities that generate enduring advantage.

A basis for platforms

Gives a practical reason to build and reuse platforms, cutting complexity and speeding innovation.

Coherent expansion

Supports adjacency moves that carry existing competences into new markets.

Links to operating choices

Pairs well with VRIO and Make-Buy-Ally to turn strategy into operating choices and governance.

Slogan risk

Becomes sloganistic when not grounded in evidence of customer benefit and economics.

Selection bias

Leaders label many strengths “core,” diluting focus and returns.

Erosion

Competences decay without continued investment and codification, and rivals catch up.

Inward focus

Overemphasis on internal strengths can hide shifts in customer needs or industry structure.

Upstream: provides inputs

• Porter’s Value Chain

This method

Output: Core competence inventory with product linkages.

Decision: Where to build, protect and extend competences; what not to outsource.

Downstream: uses the output

• Adjacency Expansion Matrix
• Capability Map

Complementary: adds insight or offsets a limitation

• VRIO / VRIN Analysis

Offsets: Competences are hard to define and measure objectively.

Alternative: answers a similar question

• VRIO / VRIN Analysis

Compared directly in Commonly confused methods.

Focus on a few deep capabilities

The framework centers strategy on a small set of integrated capabilities that drive customer benefit, open several markets and are hard to copy.

Test before you label

Use the three tests (customer benefit, market access, inimitability) plus VRIO to separate true competences from parity strengths.

Build platforms, then align

Turn competences into reusable platforms and modules; align the operating model, incentives and governance so teams adopt and scale them.

Own the core, partner the rest

Invest in and own core competences, partner for non-core work, and protect the advantage with IP and data, playbooks and ecosystems.

Refresh every year

Competences evolve as technologies and customer needs shift; review the evidence and the portfolio annually.

How many core competences should a company have?

Typically three to five. Fewer risks overconcentration; more dilutes focus and investment. Each competence should map to several products or markets and be backed by a dedicated owner, platform and metrics.

What is the difference between a capability and a core competence?

A capability is what a firm can reliably do. A core competence is the subset of capabilities that passes the three tests: it drives key customer benefits, opens several markets and is hard to imitate. All core competences are capabilities; not all capabilities are core.

Can core competences be outsourced?

By definition, no. You can outsource non-core activities or complements, but outsourcing a core competence risks hollowing out the advantage. Partner where it speeds learning within the competence, and keep control of the differentiating know-how.

How do we measure a core competence’s impact?

Link it to economics and outcomes: price premiums, win/loss reasons, time-to-value, cost-to-serve, retention, reuse across products and adoption of core platforms. Treat competences like assets, with ROI and health metrics.

How often should we revisit our core competences?

Annually, and after major shifts in technology, regulation, customer behavior or M&A. Expect competences to evolve as markets change and new know-how becomes differentiating.

Is this only a corporate-level tool?

No. It originated with corporate portfolios, but it works well at business-unit level to focus product and platform investment, and operating model choices, on the few capabilities that drive advantage in that unit’s market.

What if our “core” is becoming commoditized?

Use dynamic capabilities to evolve it: invest in adjacent know-how, combine competences (for example, adding data and AI to a hardware competence), and redesign offers as solutions or platforms to move the basis of competition.

Purpose

Map stages, touchpoints, emotions and pain points to target improvements.

When to use

Experience problems, digital redesign, service design.

When not to use

No access to customers or operational data.

Inputs and evidence

Research, journey analytics, VOC, operational data.

Participants

CX, product, operations, frontline staff, customers.

Deliverable

Current and future-state journey maps with prioritized pain points.

Decision supported

Which journey fixes to fund and in what order.

Quality checks

Each pain point evidenced by data; backstage owners named.

What it maps

Stages, touchpoints, customer goals, emotions and pain points, plus the people, processes and systems that enable or block each step.

What it shows

Where you win or lose customers, what they need to succeed, and what has to change in the operation. Friction and the moments that matter sit on one page.

Where it is used

Aligning leaders on the real experience, prioritizing what drives revenue and retention, and fixing marketing, sales and service handoffs. B2C, B2B and B2B2C.

Persona, scenario

Whose journey, in what context: an SMB finance director trialing a SaaS product, or a policyholder filing a claim. Journeys differ by segment and job to be done.

Stages

The high-level phases, from discover and consider through buy, onboard, use and support to renew, expand or advocate. Tailor the labels to your business.

Touchpoints

Web and app screens, email and SMS, sales calls, store or branch visits, partners and third-party reviews, across owned, paid and earned media.

Customer lens

At each stage and touchpoint: the customer’s goals, actions, questions, emotions and pain points. Verbatims from research keep it real.

Backstage lens

The people, processes, policies and systems behind the scenes (CRM, billing, KYC, fulfilment, data quality) and the handoffs between functions.

Metrics, evidence

Traffic, conversion, time to value, CSAT or NPS, SLA attainment, repeat rate and churn by stage, each marked as observed or hypothesized.

Opportunities

Quantified fixes mapped to friction points, with estimated impact (conversion, cost to serve, NPS), effort and risk, ready to rank into a roadmap.

What the map produces

• A visual map of the end-to-end journey for one persona and scenario
• A shortlist of the moments that matter
• Diagnostic metrics by stage and touchpoint
• A ranked backlog of improvements with owners, KPIs and economic cases

Service blueprint overlay

Adds swimlanes for frontstage and backstage actions, support processes, systems and evidence lines. It makes the “how” explicit, which is what a root-cause fix needs.

Use it when the friction traces back to a policy, a process or a system.

Journey analytics overlay

Feeds web and app analytics, CRM, contact-center logs and product telemetry into the map, so drop-offs and variation by segment or channel carry numbers.

Use it when you need to size a problem and show that a fix worked.

Most helpful for

• Growth and conversion. Find where prospects stall, what messaging or UI is missing, and which fixes lift conversion.
• Onboarding and activation. Cut time to first value, clarify setup steps, and match marketing promises to the product.
• Support and retention. Diagnose high contact rates or churn, then redesign self-serve and assisted service.
• Omnichannel orchestration. Make app, web, stores or branches, partners and the contact center work as one experience.
• Brand promise to operations. Turn positioning such as “fast, trusted, easy” into concrete SLAs, policies and design standards.

Especially powerful when

• Several functions own pieces of the experience and their incentives pull apart.
• Metrics look strong in silos but weak overall: leads rise while trial-to-paid stays flat.
• You are entering a new segment and need its distinct jobs, obstacles and channels.

Less effective or misleading when

• It is a workshop exercise without customer evidence or data: posters, no lift.
• It maps an “average” journey, when journeys diverge by segment and channel.
• It stops at insights: without owners, KPIs and a funded backlog, nothing changes.

Set scope

Persona, scenario and business targets such as trial-to-paid +5 pts. Agree the horizon and channels.

Collect evidence

Blend interviews, voice of customer and frontline insight with analytics. Tag each insight H or V.

Draft the skeleton

Stages from trigger to advocacy with goals, emotions, pain points, touchpoints and backstage.

Add metrics

Overlay stage and touchpoint KPIs, then name the 5 to 10 moments that matter.

Find root causes

Trace each friction point through people, process, policy and tech, and size its impact.

Design and value

Options with impact, effort, risk and dependencies, ranked into now, next and later.

Assign owners

One accountable owner per fix, with success metrics and a test plan with decision thresholds.

Test and implement

A/B tests and pilots up front, limited rollouts backstage; track KPIs and economics.

Scale and govern

Journey managers, a journey council and a quarterly review keep map and backlog current.

Frame · Steps 1 to 3

Set scope, collect evidence, draft the skeleton.

Diagnose · Steps 4 to 6

Add metrics, find root causes, design and value.

Deliver · Steps 7 to 9

Assign owners, test and implement, scale and govern.

Set scope

Scope, objectives and guardrails

Define the persona or segment and the scenario, for example “SMB admin trialing our software,” and the business objectives: lift trial-to-paid by 5 pts, cut onboarding time by 30%, lower support contacts by 20%. Agree the time horizon and channels in scope.

Collect evidence

Qualitative and quantitative inputs

Blend interviews, usability tests, voice of customer and frontline insight from sales, success and support with journey analytics: funnels, CRM and billing data, contact-center logs, time-to-value telemetry. Add competitor scans and regulatory constraints. Tag each insight hypothesis (H) or validated (V).

Draft the skeleton

Stages, lenses and touchpoints

Lay out the stages from trigger to renewal or advocacy. For each stage, capture goals, actions, questions, emotions and pain points, then add the top touchpoints and channels and the backstage processes and systems involved.

Add metrics

Metrics and moments that matter

Overlay traffic, stage conversion, activation rate, NPS or CSAT, SLAs and repeat behavior. Name the 5 to 10 moments where experience drives conversion, cost or loyalty, such as pricing-page clarity, first value or the first support contact.

Find root causes

Diagnose root causes

For each friction point, examine upstream and downstream causes across people, process, policy and technology. Use a service blueprint to show the handoffs, and quantify the impact in lost revenue and added cost to serve.

Design and value

Design improvements, quantify value

Generate solution options. For each, estimate the impact (conversion lift, churn reduction, lower handle time), the effort, the risk and the dependencies. Build a simple value case and prioritize the options into a now, next and later roadmap.

Assign owners

Owners and embedded KPIs

Give each improvement an accountable owner in product, marketing or operations. Define its success metrics, such as trial-to-paid lift or a shorter time to first value, and set a test plan with decision thresholds.

Test and implement

Run experiments and implement

Run A/B tests and pilots on copy, design, flows and policy changes. Roll backstage fixes out to a limited group first. Track the effect on journey KPIs and on the economics: contribution margin, cost to serve and NRR.

Scale and govern

Institutionalize ownership

Appoint journey managers, set up a cross-functional journey council and hold a quarterly review. Keep the map and metrics current, and update the backlog as new evidence comes in.