What is the 70 20 10 design principle

What is the 70 20 10 design principle

What is the 70 20 10 design principle

The 70 20 10 principle is basically a way to split your focus—mostly used in UX, product development, and innovation. It says you should put 70% of your effort into what already works, 20% into making things a little better, and 10% into wild experiments. Keeps things stable while still letting you grow and maybe stumble onto something big.

How does the 70 20 10 rule apply to UX design?

In UX, this rule gives you a clear way to prioritize. That 70% chunk? That's your bread and butter—the main flows and features people use every single day. Polish those, make 'em rock solid. Then 20% goes to tweaks and upgrades based on what users are complaining about or asking for. And that final 10%? That's for playing around—testing weird new interactions, tech you're not sure about, or completely fresh user journeys. Stops you from dumping all your cash into a crazy idea while still letting you improve steadily.

What are the benefits of using the 70 20 10 model in product design?

  • Risk Management: By shoving experiments into just 10%, you don't mess up the main product. Innovation without the chaos.
  • Resource Efficiency: Most of your design time goes where it actually matters—proven stuff that keeps users happy and numbers up.
  • Balanced Innovation: The middle 20% is for safe, regular improvements. The 10% is for those crazy "what if" ideas nobody's tried yet.
  • User Trust: Focusing on core features builds reliability. People stick around when things just work.

Can you provide a real-world example of the 70 20 10 design principle?

Google's the classic example here. They used to follow this split religiously. 70% went to core search and ads—their money makers. 20% went to stuff like Gmail, Google Maps, Google News—things that started as internal projects and grew into massive products. And that 10%? That got you self-driving cars (Waymo) and Google Glass. Some worked, some didn't, but it let them dominate search while planting seeds for the future.

How do you implement the 70 20 10 principle in a design team?

You gotta plan this out. First, figure out what's core—the stuff your product can't live without. That's your 70%. Second, look at user feedback and analytics to find things you can improve incrementally—that's the 20%. Third, carve out some time and budget for experiments—maybe a hackathon or dedicated sprint days. That's the 10%. Track metrics for each bucket separately or you'll lose control. And do quarterly check-ins to adjust the split as your product grows up.

Data Table: Resource Allocation Strategies

Category Percentage Focus Area Example Activities
Core 70% Stability, performance, usability Bug fixes, accessibility improvements, flow optimization
Adjacent 20% Incremental innovation New settings, dashboard widgets, small feature requests
Transformational 10% Breakthrough innovation AI-driven features, new platform concepts, radical UI paradigms

Checklist: Applying the 70 20 10 Principle

  • [ ] Define and document your product's core features (70%).
  • [ ] Identify 3-5 incremental improvements for the next quarter (20%).
  • [ ] Allocate a specific budget or time (e.g., 10% of sprint capacity) for experiments.
  • [ ] Create a simple tracking system to monitor time spent in each category.
  • [ ] Conduct a monthly review to ensure the balance is maintained.
  • [ ] Communicate the principle to all stakeholders to set expectations.

Frequently Asked Questions

Is the 70 20 10 principle only for large companies?

Nah, it scales. Small teams can just split their weekly hours—like 28 hours on core, 8 on improvements, 4 on experiments. Or even adjust to 80-15-5 if you're really stretched thin. It's about the mindset, not the exact numbers.

What happens if the experimental 10% fails?

That's kinda the point. Failure's expected. The whole idea is to keep risk contained so you can learn fast. The 10% zone is an investment in learning, not a guarantee. If it bombs, you take what you learned and feed it back into the core or adjacent work.

Can the 70 20 10 principle be applied to non-digital products?

Yeah, works anywhere. Car manufacturers use it—70% improving existing models, 20% new models in existing lines, 10% research into electric or autonomous tech. Fashion brands, service design—same deal. It's not just for apps.

How does this principle differ from the 80/20 rule (Pareto Principle)?

Different beasts. 80/20 is about finding the few inputs that give you most outputs. 70 20 10 is about how to split your resources across core, adjacent, and experimental work. They can work together though—you might use 80/20 to figure out which features are core enough to land in that 70% bucket.

Resumen breve

  • Definición: El principio 70 20 10 es una estrategia de asignación de recursos que dedica el 70% a funciones principales, el 20% a mejoras incrementales y el 10% a experimentos innovadores.
  • Aplicación en UX: Ayuda a los equipos de diseño a equilibrar la estabilidad del producto con la innovación, evitando la sobreexposición a riesgos.
  • Beneficio clave: Permite la mejora continua y la exploración de nuevas ideas sin comprometer la experiencia principal del usuario.
  • Implementación: Requiere una planificación clara, seguimiento de métricas y revisiones periódicas para mantener el equilibrio entre las tres categorías.