Master the 70-20-10 Rule for Innovation: A Practical Guide

You've probably heard of the 70-20-10 rule for innovation. It sounds great in a boardroom presentation. Allocate 70% of resources to core business, 20% to adjacent innovations, and 10% to transformational moonshots. It's neat, tidy, and promises balanced growth. But here's the thing I've learned after advising companies on this for years: most teams get it wrong. They treat it as a budget spreadsheet exercise, not a cultural and strategic framework. The real magic—and the real struggle—isn't in the percentages; it's in the mindset shift and operational rigor required to make each bucket truly work.

What Exactly Is the 70-20-10 Rule for Innovation?

Let's strip away the jargon. The 70-20-10 model is a resource allocation framework designed to manage the tension between exploiting your current business (which pays the bills) and exploring new opportunities (which secures your future). It's often credited to former Google CEO Eric Schmidt, who used it to structure Google's innovation efforts, though the concept has deeper roots in strategic management. The goal is simple: prevent your company from being disrupted by balancing your bets across three time horizons.

Allocation Focus Time Horizon Mindset Required Example Activities
70% - Core Business Incremental improvement, optimization, and defending market share. Short-term (0-2 years) Efficiency, reliability, scalability. Feature updates, cost reduction, A/B testing, sales process optimization.
20% - Adjacent Innovations Extending existing capabilities into new markets, products, or customer segments. Medium-term (2-4 years) Exploration, adaptation, calculated risk-taking. New product line for existing customers, entering a new geographic market, applying tech to a new industry.
10% - Transformational / Moonshots Radical, high-risk ideas that could create entirely new markets or disrupt your own. Long-term (4+ years) Experimentation, tolerance for failure, visionary thinking. Research into breakthrough tech, exploring completely new business models, "blue sky" R&D projects.

The biggest misconception? That this is just about R&D dollars. It's about talent, time, leadership attention, and capital. A team's best engineers stuck only on core bugs is a 100-0-0 model, regardless of the budget.

The 70%: Where Most Companies Get Too Comfortable

This is the foundation. If your core business isn't healthy, funding innovation is a fantasy. But "core" doesn't mean "static." The goal here is sustained innovation—making what you already do better, faster, and cheaper. The pitfall is letting this bucket become a graveyard for low-impact, busywork projects that feel safe.

I once worked with a SaaS company whose "70%" was entirely consumed by maintaining legacy code for a shrinking customer base. They were pouring water into a leaky bucket. We had to redefine "core" to mean "initiatives that directly improve profitability or competitive advantage for our primary, growing product lines." Everything else was sunset or outsourced.

Effective 70% work looks like:

  • Automating a manual, high-cost customer service process.
  • Redesigning the checkout flow to increase conversion by 1.5%.
  • Refactoring the codebase to reduce server costs by 15%.

It's not glamorous, but it funds everything else. The key metric here is efficiency and margin improvement.

The 20%: The Hidden Engine of Growth (And Common Pitfalls)

This is the sweet spot for most substantive growth. You're leveraging your existing strengths—your brand, customer relationships, technology, or distribution—into new but related areas. The risk is moderate, the potential reward is high.

Think of Apple moving from computers to music players (iPod), then to phones (iPhone). Each step was adjacent, building on core competencies in design, software, and ecosystem building.

The subtle mistake I see: Companies staff their 20% projects with B-team players and manage them with the same rigid, quarterly-goal processes as the 70% work. This kills the exploratory spirit. 20% projects need autonomous, cross-functional teams and success metrics focused on learning and validation (e.g., "achieve 1000 beta users" or "validate technical feasibility") rather than immediate profit.

Questions to find your 20% opportunities: What do our best customers keep asking for that we don't offer? What technology do we own that could solve a problem in the industry next door?

The 10%: How to Protect Your "Wild Card" Projects

This is the most misunderstood and vulnerable part of the model. The 10% is for ideas that might seem crazy today. They have a high probability of failure, but if they succeed, they change everything.

The critical failure point is applying core business logic to these projects. You cannot judge a moonshot by next quarter's ROI. I've watched CFOs strangle 10% projects in their crib by demanding a five-year financial model—for something that, by definition, has no existing market to model.

How to do it right: Physically or structurally separate these projects. Google's "X" lab (where Waymo started) is a classic example. Staff them with passionate visionaries and tinkerers. Fund them as an R&D bet, not a business unit. The success metric is knowledge gained and technical breakthroughs achieved, not revenue. The budget must be protected; it's the first thing cut in a downturn, which is exactly when you shouldn't cut it.

How to Implement the 70-20-10 Rule: A Practical Roadmap

Ready to move beyond theory? Don't try to overhaul everything at once. Here's a phased approach I've used successfully.

Phase 1: Audit & Baseline (Weeks 1-4)

This is the reality check. Categorize all current projects, initiatives, and—crucially—key personnel time across the three buckets. Use a simple spreadsheet. You'll likely find an 85-10-5 or 90-5-5 split. That's your starting point. Be brutally honest. Is that "new AI initiative" truly a 10% moonshot, or is it just a 70% efficiency project with a fancy name?

Phase 2: Redesign & Reallocate (Weeks 5-12)

Now, make intentional choices. For the next planning cycle (quarter or year), deliberately shift resources toward the 20% and 10%. This might mean:
- Stopping or deprioritizing a few low-impact 70% projects.
- Formally launching one or two 20% initiatives with a dedicated, temporary team.
- Creating a simple application process for employees to pitch 10% ideas, with a small, protected budget for the winners.

Communicate the why relentlessly. This feels like loss to teams whose core projects are slowed down.

Phase 3: Operate with Different Rules (Ongoing)

This is the long-term game. Establish different governance for each bucket.
- 70%: Standard KPIs, frequent reporting, focus on predictability.
- 20%: Milestone-based funding (tranches), regular "learning reviews" instead of profit reviews, more autonomy.
- 10%: Quarterly "show and tell" demos to leadership, funding reviewed annually, celebration of "smart failures."

Three Mistakes That Derail 70-20-10 Initiatives

Let me save you some pain. Here are the traps that kill this framework.

1. The Percentage Police: Obsessing over hitting 70-20-10 exactly. It's a guiding principle, not a law of physics. A 65-25-10 split in a year of aggressive expansion is fine. The model is a tool for balance, not a rigid accounting rule.

2. Innovation Ghettos: Walling off the 20% and 10% teams completely, creating resentment and preventing knowledge flow. The goal is separation with integration—different rules, but regular sharing of insights back to the core. The 70% team should learn from the experiments of the others.

3. Rewarding Only Success: If you only celebrate the 10% project that becomes a billion-dollar business, you'll never get another one. You must reward the team that ran a bold 10% experiment, gathered crucial data proving it wouldn't work, and shut it down efficiently. That saved the company $50 million in futile pursuit.

Your Burning Questions Answered (FAQ)

How do I convince my CFO to allocate budget to the 10% "wild card" projects?
Frame it as strategic insurance. Ask what it would cost to acquire a disruptive startup in your space in 5 years. The 10% budget is a fraction of that, and it gives you the option to build that capability internally. It's also an R&D tax deduction in many jurisdictions. Present it as a fixed, manageable line item for "long-term strategic exploration," with clear deliverables of prototypes or research papers, not revenue.
We're a small startup with limited resources. Is 70-20-10 even relevant for us?
Absolutely, but the scale is different. Your "70%" might be one founder focused on nailing product-market fit and getting the first 100 customers. Your "20%" could be the other founder spending a day a week exploring one potential partnership or up-sell feature. Your "10%" might be a monthly "crazy idea Friday" where the team brainstorms completely off-road ideas. The principle—balancing execution today with bets on tomorrow—is universal, even if your 10% is just 1% of your time.
What's the single biggest sign our 70-20-10 implementation is failing?
When projects in the 20% or 10% buckets keep getting "temporarily" pulled back to fight fires in the 70% core business, and never return. It means you haven't truly protected the resources or committed to the model. It becomes innovation theater—a list of projects on a slide that nobody is actually working on. The rule only works if the allocation is defended, especially when the core business feels pressure.
Can the 70-20-10 rule apply to personal skill development, not just company projects?
It's a fantastic personal framework. Allocate 70% of your learning to skills that make you better at your current job (a new software, industry knowledge). Use 20% to learn adjacent skills that open new doors (a marketer learning basic data analysis). Spend 10% on something completely unrelated but fascinating (philosophy, a new language, carpentry). That 10% often provides unexpected creative connections that boost your work in the other buckets.

The 70-20-10 rule isn't a magic formula. It's a discipline. It forces you to make explicit, uncomfortable choices about where to place your bets. It surfaces the tension between today and tomorrow and gives you a language to manage it. Start with the audit. Face the reality of your current split. Then make one deliberate move to rebalance. That's how you stop talking about innovation and start building a pipeline for it.

Join the Discussion