You've probably heard of the 70 20 10 rule for innovation. It gets tossed around in boardrooms and strategy meetings like a magic formula. But here's the thingāmost people get it wrong. They treat it as a rigid budget mandate, a top-down order to "spend 10% on crazy ideas." That approach fails, every time. The real power of the 70 20 10 model isn't in the percentages; it's in the mindset shift it forces upon an organization.
At its core, the 70 20 10 rule is a framework for resource allocation. It suggests that to sustain long-term growth, a company should divide its innovation efforts and resources roughly into three buckets: 70% on core innovations, 20% on adjacent innovations, and 10% on transformational innovations. The goal is balanceāfeeding today's business while planting seeds for tomorrow.
I've seen teams kill themselves trying to make "10% time" work, only to have those projects canned the moment quarterly targets look shaky. The framework isn't the problem. The execution is.
What You'll Find Inside
Where It Came From (And What Everyone Misses)
The 70 20 10 rule is often credited to Eric Schmidt during his tenure at Google, who reportedly used it to manage Google's product portfolio. However, its conceptual roots go deeper, aligning with research on innovation horizons by management thinkers. A seminal report from Morgan McKinley on corporate growth strategies often gets cited as a key reference point, framing innovation across three time horizons.
The biggest misconception? People think it's primarily about time management for employeesā"give people 10% of their time to play." That's a nice perk, but it's not the strategic tool. The rule is about capital allocation, talent deployment, and leadership focus at an organizational level. It's a portfolio strategy, not an HR policy.
Another missed point: the percentages are a guideline, not a law. A startup might need a 50-30-20 split. A company in a dying industry might need to flip it to 10-20-70 to survive. The numbers prompt the conversation: "Are we investing enough in our future?"
Breaking Down the 70%, 20%, and 10%
Let's get concrete. What actually goes into each bucket? It's more than just project budgets.
| Bucket | Focus & "Job to Be Done" | Typical Activities & Examples | Risk Profile & Mindset |
|---|---|---|---|
| 70% - Core Innovations | Improving existing products/services for current customers. Defending and extending the core business. | Incremental feature updates, cost optimization, efficiency gains, geographic expansion for existing products. Example: Netflix improving its recommendation algorithm. | Low risk. Measured by reliable metrics like ROI, market share, customer satisfaction. Efficiency mindset. |
| 20% - Adjacent Innovations | Taking existing strengths into new, related markets or customer segments. Leveraging core capabilities. | New product lines for existing customers, serving new customer segments with adapted technology, strategic partnerships. Example: Apple using its chip design expertise for the M-series Mac processors (adjacent to its core iPhone business). | Moderate risk. Requires exploring new business models. Measured by new market penetration and growth potential. |
| 10% - Transformational Innovations | Creating fundamentally new offerings that could redefine the company or industry. Exploring disruptive technologies. | Moonshot projects, radical tech R&D, exploring entirely new business models. Example: Google's early work on self-driving cars (Waymo). | High risk. High failure rate expected. Measured by learning, option value, and potential for massive future impact. |
The 70%: Your Bread and Butter
This is the engine room. It pays the bills. The work here is about getting better, faster, and cheaper at what you already do. The funding is usually stable, the teams are large, and the processes are well-defined. The danger here is complacencyāpouring all your resources into this bucket leads to stagnation. Kodak was brilliant at the 70%. We know how that ended.
The 20%: The Growth Engine
This is where most successful growth comes from. You're not starting from scratch; you're using your brand, customer relationships, technology, or distribution network as a springboard. It feels risky but is often the most reliable path to significant new revenue. The challenge is internal politicsācore business units often see these projects as distractions or threats.
The 10%: The Lottery Tickets (That Need Careful Selection)
This is the most misunderstood part. It's not a "fun fund." These are strategic bets on the future. Failure is the default expectation, so you measure success differentlyānot by profit, but by knowledge gained, patents filed, or talent attracted. The biggest mistake is funding a dozen random "cool ideas" instead of 2-3 bets that align with a long-term vision of where the world is heading.
Key Insight: The rule applies to more than money. Think about talent. Do your best people only work on core projects? Apply it to leadership attention. Do execs only review quarterly core metrics? Apply it to meeting agendas. Is 10% of your strategic discussion about the future?
How to Make It Work in Your Company: A Real Case
Let's walk through a hypothetical but realistic scenario. Imagine a mid-sized SaaS company called "TechFlow Inc." that sells project management software. They've hit a plateau.
Step 1: The Audit. First, they audit last year's R&D spend and product team hours. They discover it's 95% on core (bug fixes, small UI tweaks), 5% on adjacent (a half-built integration), and 0% on transformational. This is the "aha" moment.
Step 2: Redefining Projects. They re-categorize their roadmap:
70% Core: A major performance overhaul of their core app, a redesign of the reporting dashboard requested by key clients.
20% Adjacent: Building a new, lightweight version of their software for freelancers (a new segment) and developing an API marketplace for deeper integrations.
10% Transformational: A small, skunkworks team explores embedding AI to predict project delays and automatically re-allocate resourcesāa feature that would make their product category-defining.
Step 3: Separate the Governance. This is critical. They don't measure all projects the same way.
The core team reports on velocity, uptime, and customer satisfaction scores.
The adjacent team reports on user acquisition cost for the new freelancer segment and API partner sign-ups.
The transformational team reports every quarter, not every week. Their update is a narrative: "What did we learn about AI model training? What technical hurdles did we overcome? What does this tell us about the feasibility of our vision?"
By giving the 10% team air cover from quarterly earnings pressure, they allow for real exploration.
The 3 Biggest Mistakes Teams Make
After advising on this for years, I see the same errors repeatedly.
1. The 10% Becomes a Dumping Ground for Pet Projects. Without a strategic filter, the transformational bucket gets filled with the CEO's hobby-horse or an engineer's niche passion project that has no link to the company's future. Every 10% project should answer: "If this works, how does it change our future in 5-10 years?"
2. Starving the 20%. When budgets get tight, the adjacent projects are the first to be cut because they're not "keeping the lights on" (core) and not "sexy future tech" (transformational). This is a tragic error. The 20% is your most efficient growth pipeline. Killing it guarantees mid-term decline.
3. Confusing Activity with Innovation. Holding a yearly hackathon and calling it your "10%" is not a strategy. It's an event. Sustainable innovation requires dedicated, protected resourcesāpeople, budget, and timeāthat are not the first to be borrowed when the core business sneezes.
Your Questions, Answered
The 70 20 10 rule for innovation isn't a magic bullet. It's a mirror. It forces you to look at how you spend your time, money, and brainpower. Are you only building for today? The framework provides a simple, compelling structure to start the hard conversations about tomorrow. The goal isn't to hit the percentages perfectly. It's to ensure that the future isn't something that just happens to your business, but something you deliberately, if cautiously, build towards.
