70-20-10 Rule

By Sandra

Last updated May 12, 2026

The 70-20-10 rule is a practical framework for dividing innovation resources across three horizons of growth. It suggests spending 70% of effort on improving existing products and services, 20% on expanding into adjacent markets or capabilities, and 10% on transformational or disruptive bets.

This split helps organizations balance short-term stability with long-term exploration. It prevents overinvestment in safe, incremental work while still funding the core business that pays the bills.

How the 70-20-10 Rule Works in Practice

The framework is intentionally simple. The 70% slice funds the core business — product updates, process improvements, and customer experience enhancements that protect current revenue. The 20% goes to adjacent moves — new customer segments, geographies, or business models that leverage existing strengths. The remaining 10% funds experimental, high-risk projects that could redefine the company.

Google is often cited for using a version of this approach. The majority of its engineering resources support Search and Ads, while a smaller portion develops adjacent products like Cloud and Workspace, and a sliver funds moonshot projects through X Development.

Why the 70-20-10 Rule Matters

Without a structured allocation model, organizations tend to overinvest in the core and starve future growth. The 70-20-10 rule forces explicit trade-offs. It makes resource allocation visible and debatable, rather than automatic.

The rule also acknowledges that different horizons require different management styles. Core improvements need efficiency metrics and tight governance. Adjacent moves need portfolio thinking and stage-gate decisions. Transformational bets need tolerance for failure and long timelines.

Common Misconceptions

Many people assume the 70-20-10 rule is a rigid formula. It is not. The exact ratios vary by industry, company maturity, and competitive pressure. A mature industrial firm might weight the core higher. A startup might flip the ratios entirely.

Another misconception is that the three buckets should be managed the same way. They should not. Each horizon needs different KPIs, timelines, and talent.

Related Terms

• Innovation Portfolio
• Adjacent Innovation
• Breakthrough Innovation
• Innovation Strategy

Frequently Asked Questions

Is the 70-20-10 rule applicable to all industries?

The principle applies broadly, but the ratios should flex. Capital-intensive industries may need a heavier core weight. Tech companies often push the transformational slice higher. The key is making the allocation deliberate, not copying the exact numbers.

How do you measure success across the three horizons?

Core innovations use operational metrics — revenue, margin, customer retention. Adjacent moves use growth metrics — market share, new customer acquisition. Transformational bets use learning metrics — validated assumptions, option value, and strategic positioning.

What happens if an organization ignores the 10% transformational slice?

Companies that underinvest in transformational work often find themselves disrupted. They optimize the core until it becomes irrelevant. The 10% acts as insurance against strategic obsolescence.

Contributor

Sandra @san_broddersen

Writes about innovation systems, venture design, and practical methods for student-led entrepreneurship.

Sandra writes with an editorial lens shaped by innovation workshops, product discovery sessions, and practical student entrepreneurship work at ITU Entrepreneurship and ITU NextGen. She focuses on helping teams separate fashionable jargon from methods that actually improve decision quality.

Her favorite topics sit at the intersection of strategy and execution: innovation portfolios, governance rhythms, and how to build durable learning loops inside organizations. She often references public frameworks and programs such as ITU Entrepreneurship, ITU NextGen, and the Digital Innovation and Management program to keep guidance grounded.

Outside publishing, Sandra supports student and early-career founders navigating their first experiments. She prefers practical tools, clear language, and examples that can be reused in real project settings.