8 Ansoff Matrix Examples for Better Execution

Growth strategy often fails after the leadership team has agreed on the direction. UK evidence shows that only 18.4% of large companies achieved more than 80% of their aspirational growth goals within three years, while 41.2% failed to reach even 60% of their targets, as reported in UK evidence on growth ambitions and execution. The problem usually isn't a lack of ideas. Teams face competing priorities, unclear ownership, slow decisions, and weak follow-through.

The Ansoff Matrix gives leaders a clear way to name the growth bet. Are you selling existing products in existing markets, taking existing products into new markets, creating new products for current customers, or entering unfamiliar markets with unfamiliar offers? The model was first described by Igor Ansoff in Harvard Business Review in September–October 1957, and it remains a compact framework for discussing growth, risk, resource commitment, and route-to-market change through its original strategic context.

OKRs make the choice executable. They connect the strategic move to measurable outcomes, review rhythms, accountable owners, and decisions about whether to scale, adapt, or stop. These eight Ansoff Matrix examples range from lower-risk market penetration to high-risk diversification. Each shows what to measure, how to set stage gates, and how to stop execution becoming a tick-box exercise. Leaders can use the framework to build a growth strategy that teams can deliver.

1. Market Penetration with Amazon Web Services

Amazon Web Services is a strong market penetration example when the growth move is defined as deeper capture of the existing cloud infrastructure market. AWS built on scalable infrastructure expertise and continued to improve the core offer across compute, storage, databases, analytics, and related cloud services. The strategic choice wasn't to “sell more cloud”. It was to make the existing proposition more useful, easier to adopt, and harder to replace.

That distinction matters. A team can call almost any expansion penetration if it wants a low-risk label. Moving from core infrastructure into a materially different customer problem may involve product development or diversification. Leaders should classify the initiative by the customer job, the capabilities required, and the route to market, not by the company name attached to it.

Turn deeper share into accountable outcomes

An AWS-style penetration OKR might focus on increasing strategic account adoption of existing services. The key results should show whether customers are using more of the proposition and whether the company is winning for a defensible reason.

• Increase account depth: Track the number of priority customers using multiple core services, rather than relying on total revenue alone.
• Improve customer health: Measure retention, service reliability, support resolution, and renewal risk by segment.
• Understand competitive performance: Review win and loss reasons at executive level, with named owners for recurring objections.
• Protect roadmap discipline: Require product teams to connect feature work to adoption, retention, wallet share, or competitive conversion.

A useful governance rhythm combines commercial reviews with product reviews. Sales leaders should explain lost deals. Product leaders should show which improvements changed buying or usage behaviour. Finance should test whether investment is concentrating on the segments with the clearest growth potential.

Practical rule: A penetration OKR isn't “grow revenue”. It should explain which customers will buy more, why they will do so, and which team owns the constraint preventing that outcome.

2. Product Development with Apple's iPhone Ecosystem

Apple's iPhone launch illustrates product development. Apple brought an established brand, customer base, and distribution system into a new product category. Existing Mac and iPod customers reduced the market-entry risk, while new hardware, software, services, manufacturing coordination, and customer education created substantial product risk.

The same quadrant applies when Netflix creates original content for existing subscribers, Adobe shifts design customers from perpetual licences to Creative Cloud, or Tesla adds energy storage for vehicle customers. A trusted relationship helps secure initial attention. It does not prove that the new offer works.

Govern adoption, ecosystem value, and cannibalisation

Set one OKR for customer value and another for delivery readiness. A launch can attract attention while producing weak repeat use, or move revenue from an older product without improving the wider relationship.

Track the signals that separate those outcomes:

• Adoption within the existing base: Measure activation and sustained use among current customers, segmented by relevant customer type.
• Bundle behaviour: Monitor whether customers combine the new product with existing products. This shows whether the ecosystem is strengthening.
• Product-market fit evidence: Review repeat usage, retention, support demand, satisfaction, and referrals as leading indicators.
• Cannibalisation control: Define acceptable revenue movement before launch, then assess total customer value rather than one product line.

Assign owners for adoption, reliability, customer support, and commercial impact. Their key results should connect product usage with retention, bundle depth, and customer value. A monthly review can expose whether weak performance comes from the product, positioning, onboarding, or operational capacity.

Use stage gates to control investment. A power-user pilot can test usability and willingness to pay. Broader release should require evidence of a material customer problem, reliable delivery, and operational readiness. Increase go-to-market spending only after those conditions meet the agreed threshold. Governance should record the decision, evidence, owner, and next gate, so product development remains an accountable growth choice rather than a launch checklist.

3. Market Development with Starbucks in New Countries

Starbucks shows market development by bringing its familiar coffee-shop model into Japan, China, the UK, and the Middle East. The core offer remains recognisable, while customers, competitors, operating conditions, and cultural expectations change. Leaders should classify this move as geographic expansion, then govern it as a test of local demand and delivery capability.

The same uncertainty appears when a company enters a new segment, channel, or regulated environment. Internal familiarity with the product does not guarantee customer adoption or partner readiness.

Govern the market entry as a sequence of decisions

Separate the entry OKR from the operating OKR. The first should prove that the market wants the offer. The second should show that the organisation can deliver it repeatedly and profitably.

• Demand: Measure awareness, trial, repeat purchase, and local conversion.
• Competition: Track win rates, customer acquisition cost, and results against local alternatives.
• Adaptation: Give a named local owner authority over menu, marketing, service, and operating changes.
• Economics: Set the threshold for a credible route to profitability.

The accountable owners should report these measures together, because strong trial can hide weak repeat purchase, poor unit economics, or limited operating capacity. Central leaders retain visibility over investment, while local teams make changes that fit customer behaviour and regulation.

Use stage gates before adding locations, partners, or marketing spend. Leadership should approve the next gate only when demand, regulatory readiness, partner performance, capacity, and unit economics meet agreed criteria. A disciplined go-to-market planning approach connects the bet to launch sequencing, channel ownership, and measurable execution.

Record the decision, evidence, owner, and next review date. Without that governance, prior investment can become the reason to continue funding a weak market.

Market development fails when leaders standardise the offer but decentralise accountability. Local teams need authority to adapt, while central leaders need visibility of performance and investment decisions.

4. Diversification with Amazon Healthcare Services

Amazon's move into healthcare through Amazon Pharmacy and Amazon Care represents diversification because it combines new healthcare offers with customers and needs beyond its established retail and cloud markets. Healthcare demands regulatory knowledge, clinical processes, trust relationships, specialist talent, and operating controls. Amazon's brand and technology may support entry, but they do not provide permission to operate successfully.

Diversification carries the highest execution risk when leaders label a new business “adjacent” because the company has capital, data, or customer reach. Those assets can reduce some barriers. They cannot replace clinical accountability, regulatory readiness, or evidence that the service works in practice.

Turn the bet into a governed experiment

Set the first OKR around proof, not scale.

• Objective: Validate regulatory and clinical viability in one launch market.
• Key results: Secure required approval by the agreed milestone, onboard a defined pilot group of clinicians, meet the target for protocol compliance across pilot visits, and reach the service-quality threshold set by clinical and operations owners.
• Accountability: A healthcare general manager owns the objective, while regulatory, clinical, product, and operations leads own their respective results.
• Decision rule: Advance only when approval, clinician participation, protocol adherence, patient experience, and unit economics meet the gate criteria.

The measures should expose trade-offs. Faster launch may increase compliance risk. Wider service coverage may strain clinical capacity. High usage may still conceal poor retention, weak outcomes, or unsustainable support costs. Track these measures in one review rather than allowing growth metrics to dominate the decision.

Use stage gates from problem validation to controlled pilot, repeatable delivery, and selective scale. Each gate needs an owner, evidence standard, investment limit, and decision date. A failed pilot should trigger a defined pause, pivot, or exit, not automatic continuation because money has already been spent.

A credible company growth strategy therefore includes capability design, separate financial visibility, and governance rules that protect the core while testing the new venture.

5. Product Development with Twilio's Communications Platform

Twilio's move from SMS APIs into voice, video, email, security, customer data, and contact-centre services is a product development strategy. The company kept its developer and organisational customer base while adding products those customers could adopt within the same technical relationship.

That move expands account value, but it also expands the delivery burden. Every service adds integration, reliability, documentation, support, and commercial requirements. Leaders must decide whether a new product strengthens the platform or makes it harder to use.

Govern expansion by adoption and reliability

Classify the initiative as product development, then set an objective that connects customer expansion with dependable delivery. A useful OKR might pair increased adoption among existing accounts with targets for sustained usage, service performance, and account retention.

Track the operating evidence behind that objective:

• Adoption by cohort: Measure activation and continued use among existing-customer groups, with results separated by use case, industry, and company profile.
• Expansion quality: Monitor account value, cross-product adoption, contraction, and retention to test whether the new offer strengthens the relationship.
• Reliability: Set service-level, performance, incident, and resolution measures for each major product.
• Portfolio focus: Rank initiatives by customer demand, strategic fit, required capabilities, and commercial potential.

Use stage gates before increasing investment. Validate the use case, run a controlled launch, confirm repeatable adoption and reliable service, then approve wider rollout. Each gate needs an accountable product owner, evidence threshold, funding limit, and decision date. Governance should include product, engineering, support, sales, and finance, because a launch can appear successful while creating operational strain elsewhere.

Revenue alone does not prove product development worked. One-off demand, forced bundling, or a few large accounts can obscure weak repeat usage. Review customer behaviour, reliability, support load, and contribution economics together.

The quickest launch is not always the shortest build. A narrower release with clear ownership may produce stronger learning and fewer service failures. Teams can use reducing time to market as an execution priority, provided speed remains tied to adoption and reliability outcomes.

6. Market Development with Netflix's Regional Content Strategy

Netflix's global expansion fits the market development quadrant. The service entered new countries with a familiar platform, then adjusted content, payment methods, pricing, partnerships, and compliance for local conditions. The growth decision was to make an existing service relevant enough for customers in each market to subscribe and stay active.

Regional content also exposes the limits of calling the offer “existing product.” Local programming, licensing, payments, support, and regulatory arrangements can require new capabilities even when the customer interface looks familiar. Leaders should classify the move by its full operating model, then assign accountability to the parts that determine adoption and economics.

Set accountability by market tier

Global revenue can conceal weak performance in individual countries. Use three accountability tiers to match oversight and investment to market maturity.

• Tier-1 markets: Regional leaders own retention and content-market fit. Product teams address payment and experience barriers, while finance reviews market economics.
• Tier-2 markets: Content and commercial teams share responsibility for proving repeat engagement, renewal behaviour, and partnership effectiveness before broader spending.
• Emerging markets: Country teams define the local demand hypothesis, legal and regulatory requirements, and minimum operating conditions for launch.

Content OKRs should connect viewing behaviour with business outcomes. Measure acquisition, activation, churn, engagement, completion, repeat viewing, and retention contribution by market and content type. Commercial OKRs should link pricing and payment-method changes to conversion and renewal, rather than treating availability as success.

Use stage gates before expanding content, marketing, infrastructure, or partnership spend. The first gate confirms local demand and compliance. The next checks repeat engagement, reliable delivery, and sustainable renewal behaviour. Each decision needs an accountable owner, evidence threshold, funding limit, and review date.

A practical governance question separates the response: is demand weak, is the offer insufficiently local, or is the operating model failing? The answer determines whether leaders change content, commercial terms, platform capability, partnerships, or the investment decision.

7. Diversification with Alphabet's Moonshot Portfolio

Alphabet's moonshot portfolio illustrates diversification: Waymo, DeepMind, Verily, quantum computing, and augmented or virtual reality pursue different customers, capabilities, products, and commercial timelines from Google's advertising core. The governance problem is allocation, not naming the quadrant.

Each venture needs a distinct investment thesis and operating contract. Leaders should define the customer problem, capability milestone, evidence required for the next funding decision, and owner accountable for delivery. Applying the advertising business's short-term profitability targets would either restrict useful exploration or encourage weak proof of progress. Removing commercial scrutiny creates a different risk, allowing an initiative to continue without evidence that its problem matters.

A practical portfolio review can group OKRs by decision purpose:

• Exploration: Validate technical feasibility, customer pilots, talent formation, research progress, and commercial relevance.
• Scale readiness: Confirm repeatable demand, delivery capability, a credible route to revenue, and dependencies the core business must support.
• Portfolio: Set funding allocation, strategic balance, dependency ownership, and review timing.
• Exit: Specify the evidence that triggers a pause, redesign, or closure.

These measures are leading indicators, not substitutes for business outcomes. They show whether a venture has earned further investment. An executive sponsor can remove barriers, while a named venture leader remains accountable for the result. The investment committee should assess evidence at agreed stage gates, with funding limits and explicit decisions, rather than accept optimistic status updates.

The Boston Matrix model for leaders adds a portfolio view for prioritisation, resource allocation, and aligning OKRs across different business bets. Use it to frame trade-offs, not to replace venture-level evidence. A diversification review should end with one of three decisions: fund the next test, change the thesis, or stop.

8. Market Penetration with Salesforce's Land and Expand Model

Salesforce's land-and-expand model shows how market penetration works in enterprise CRM. The initial sale creates an entry point. Growth comes from adding service, marketing, commerce, and other connected functions within the same account.

The decision is not whether to sell more modules. Leaders must determine whether customers are adopting the first use case, whether implementation capacity can support wider deployment, and whether integration quality will protect renewals. Expansion without adoption creates contract value that later becomes churn risk.

A practical account-growth system assigns ownership across the customer lifecycle. Sales owns the commercial hypothesis. Customer success owns adoption risks and customer outcomes. Product and implementation teams decide which use cases can be delivered repeatedly rather than treating every request as a custom commitment.

Track four operating signals:

• Customer health: Connect health-score changes to adoption, support, implementation progress, and executive engagement.
• Use-case depth: Measure activation across priority products and business functions in target accounts.
• Retention and expansion: Review renewal risk beside expansion readiness, so commercial growth does not hide weak usage.
• Account plans: Name the owner, expected customer outcome, next decision, and evidence required to proceed.

Set stage gates before expanding an account. A team might require sustained usage of the initial product, resolved implementation blockers, a confirmed customer sponsor, and a credible business case for the next use case. If those conditions are absent, the decision should be to improve adoption, not push another module.

Governance must also control the roadmap. Building every requested integration increases complexity and spreads delivery capacity too thin. Customer success, sales, product, implementation, and finance should review expansion priorities together. That forum needs authority to reallocate resources, escalate blockers, and stop low-value work. The principle behind resource allocation decisions is direct. Funding should follow measurable customer outcomes and evidence supporting the growth strategy.

Ansoff Matrix, 8 Strategy Comparisons

Turn the Matrix Into Operating Decisions

The eight examples show that the Ansoff Matrix is useful because it makes the nature of a growth bet visible. Market penetration uses familiar products and customers. It usually needs disciplined commercial execution, strong customer-health insight, and close attention to competitive performance. The risk is lower than in the other quadrants, but poor governance can still waste resources. A company can spend heavily on features, campaigns, or sales activity without improving adoption, retention, or account value.

Product development keeps the customer relationship relatively familiar but introduces product risk. Apple and Twilio illustrate the need to validate adoption, usability, reliability, bundle behaviour, and cannibalisation before committing to full-scale investment. Product teams need clear stage gates. A launch isn't successful because it shipped. It succeeds when customers use the product repeatedly and the organisation can support it at scale.

Market development keeps more of the product proposition intact while changing the customer, geography, channel, or operating context. Starbucks and Netflix show why local adaptation matters. Leaders must separate entry metrics from operational and financial metrics. Awareness, trial, engagement, competitive conversion, payment performance, retention, and profitability each answer different questions. One broad international objective won't provide enough control.

Diversification carries the greatest uncertainty because both the product and the market are new. Amazon's healthcare initiatives and Alphabet's moonshot portfolio demonstrate why leaders need protected funding, different performance expectations, capability-building objectives, and explicit exit criteria. Diversification shouldn't be governed as a normal business line before it has earned that status.

A practical sequence keeps the framework useful:

1. Identify the quadrant: Classify the initiative by product, customer, channel, capability, and regulatory novelty.
2. Name the strategic bet: State what must be true for the growth move to work.
3. Assign one accountable owner: Give one leader responsibility for the outcome, even when several teams contribute.
4. Select outcome-based OKRs: Choose a small number of objectives with measurable key results tied to customer and business value.
5. Define leading and lagging metrics: Leading metrics show whether the team is learning or progressing. Lagging metrics confirm commercial and operational impact.
6. Agree stage gates: Decide in advance what evidence supports scaling, adaptation, continued experimentation, or exit.
7. Set the review rhythm: Match governance to risk. Penetration needs regular commercial and customer-health reviews. Diversification needs portfolio reviews, learning milestones, funding decisions, and stop criteria.

The historical longevity of the Ansoff Matrix helps explain why it remains common in UK business education and strategy practice. Its value isn't that it provides a perfect answer. The matrix simplifies a complex spectrum into a useful conversation about familiarity, risk, and capability. Leaders must then add the operating system that the matrix doesn't provide.

That system includes ownership, prioritisation, decision rights, review cadence, and resource choices. UK growth evidence shows that intent alone doesn't guarantee delivery. The difference comes from turning a selected growth quadrant into a governed set of outcomes and decisions.

The OKR Hub supports leadership teams with OKR consulting, implementation, training, and coaching. Its OKR Focus Flow is designed to diagnose execution issues, design a practical system, deploy it effectively, and build internal capability. For teams facing misalignment, unclear priorities, weak accountability, or slow delivery, that support can help turn growth priorities into a working operating rhythm.

The OKR Hub helps leadership teams translate Ansoff growth choices into focused OKRs, governance routines, and accountable execution. Visit The OKR Hub to explore consulting, implementation, leadership training, and hands-on coaching for making strategy deliverable.