IDEO Ten Faces of Innovation

1. What Is IDEO Ten Faces of Innovation?

The IDEO Ten Faces of Innovation is a practitioner framework for building innovation capability by making the roles behind successful innovation visible. Rather than treating innovation as the work of a few naturally creative people, the framework argues that strong innovation comes from a set of complementary behaviors that can be cultivated across a team or organization.

Popularized by IDEO, the framework describes ten “faces,” or personas, that appear repeatedly in effective innovation efforts. Some roles are focused on learning, some on organizing people and momentum, and some on turning ideas into compelling experiences that customers and stakeholders will actually adopt.

Consultants often use it as a discussion and diagnostic tool. In practice, it is most valuable when a company is trying to strengthen innovation capability as an organization challenge, not merely generate more ideas in a workshop.

2. Origin and Background

The framework was popularized by Tom Kelley of IDEO, together with Jonathan Littman, in the 2005 book The Ten Faces of Innovation. Kelley, then IDEO’s general manager, built the model from recurring roles he had observed in IDEO’s design and client work. The framework is best understood as a field-tested management model from a leading design firm rather than as a formal academic theory.

Its purpose was straightforward: many organizations said they wanted innovation, but they either over-relied on brainstorming or assumed innovation depended on hiring a few “creative geniuses.” Kelley’s model reframed the problem. Innovation, in this view, is sustained by a broader cast of people who observe customers closely, experiment rapidly, connect ideas across domains, remove obstacles, shape experiences, and tell persuasive stories.

The framework became widely known because IDEO played a major role in popularizing design thinking in business. As executives looked for practical ways to make innovation more repeatable, the Ten Faces gave them an accessible language for discussing roles, behaviors, and capability gaps.

3. How IDEO Ten Faces of Innovation Works

The framework groups ten innovation personas into three broad families: learning personas, organizing personas, and building personas. The logic is that innovation fails when one of these families is missing. A team may have ideas but no discipline to carry them through, or it may execute efficiently without learning enough about unmet customer needs.

The ten faces are not meant to be job titles or fixed personality types. One person can play several roles, and the same team may emphasize different faces at different stages of a project. The value comes from asking a practical question: which roles are present, which are weak, and which are absent when innovation work breaks down?

The three families of roles

Family	Face	What it contributes
Learning	Anthropologist	Observes customers in context to uncover unspoken needs and real behavior.
Learning	Experimenter	Tests ideas through prototypes, pilots, and iteration rather than debate alone.
Learning	Cross-Pollinator	Imports ideas, analogies, and practices from other industries or functions.
Organizing	Hurdler	Finds practical ways around constraints, bureaucracy, and limited resources.
Organizing	Collaborator	Builds trust and alignment across disciplines so good ideas can move.
Organizing	Director	Shapes the effort, sets boundaries, and keeps the work coherent and on pace.
Building	Experience Architect	Designs the end-to-end customer experience, not just the product feature.
Building	Set Designer	Shapes the physical or digital environment to support creativity and behavior.
Building	Caregiver	Brings empathy into delivery and service so the solution feels human in use.
Building	Storyteller	Communicates the idea in a way that creates understanding, belief, and adoption.

What the framework is really assessing

At its core, the model is a capability-balance framework. It helps leaders assess whether their innovation system is over-weighted toward planning, selling, analysis, engineering, or execution at the expense of observation, experimentation, empathy, or collaboration. A team strong in Storytellers and Directors, for example, may launch initiatives with energy but miss customer needs if Anthropologists and Experimenters are weak.

That is why the framework is especially useful in workshops, project retrospectives, leadership off-sites, and team diagnostics. It creates a shared language for discussing behaviors that are usually felt but not clearly named.

4. When to Use IDEO Ten Faces of Innovation

This framework is most helpful when the business problem is not “Do we have ideas?” but “Why does our innovation system underperform?” It works well for product teams, service-design teams, transformation programs, customer-experience efforts, and leadership groups trying to make innovation more repeatable across functions.

It is especially powerful when a company faces recurring symptoms such as weak customer insight, too much internal debate, slow prototyping, silo friction, or promising ideas that fail to gain adoption. In those cases, the framework often becomes most useful as input to a broader organizational effectiveness effort that addresses roles, routines, governance, and culture together.

The data required are usually more qualitative than quantitative: interviews, project postmortems, customer observations, meeting observations, role maps, and examples of how decisions actually get made. A light application can be done in a workshop in a day or two; a serious diagnostic across multiple teams usually takes several weeks.

It is not a good fit when the main question is market attractiveness, competitive positioning, valuation, or capital allocation. It can also mislead if teams use it as a personality label, or if they assume all ten faces should be equally present at all times. Modern practitioners typically use it less as a rigid taxonomy and more as a practical lens within product management, agile, service design, and innovation-capability building.

5. How to Apply IDEO Ten Faces of Innovation: Step-by-Step

1. Clarify the innovation challenge. Define the decision the team is trying to support. Are you improving new-product development, redesigning customer experience, strengthening cross-functional innovation, or diagnosing why ideas stall? Set the time horizon and the business units or teams in scope.
2. Gather evidence, not opinions. Collect interviews, customer research, examples of past innovation projects, project review materials, and observations of team interactions. Look for behavioral evidence of each face rather than asking people which persona they “like.”
3. Define the unit of analysis. Decide whether you are assessing an executive team, a product-development process, a business unit, or a specific innovation initiative. The framework works best when the unit is clear and the comparison set is consistent.
4. Map current versus desired faces. For each unit, identify which faces are strong today, which appear occasionally, and which are largely absent. Then define the mix of faces that would be needed to win in the target context.
5. Build a simple role map. Create a visual summary, often a heat map or team grid, showing where the ten faces are concentrated. Include examples. “Strong Experimenter” should mean there is a real prototyping habit, not just enthusiasm for testing.
6. Interpret the gaps and tensions. Look for patterns. Are customer-facing roles weak? Is there plenty of storytelling but too little experimentation? Are Directors overpowering Collaborators? Separate structural problems from individual capability problems.
7. Translate the gaps into interventions. The output should lead to specific actions: new routines, training, role assignments, governance changes, hiring priorities, and organizational design choices that make the missing faces more likely to show up in daily work.
8. Test assumptions, align stakeholders, and iterate. Revisit the map with leaders and team members. Ask what would change if the business model, growth stage, or project type changed. Then refine the analysis and agree on a short list of actions, owners, and milestones.

6. Example: IDEO Ten Faces of Innovation in Action

The situation

A $500 million B2B software company had a familiar problem: plenty of product ideas, but too few successful launches. Sales said the roadmap missed client pain points, engineering said priorities changed too often, and executives felt innovation had become a sequence of presentations rather than a repeatable system.

Why this framework was selected

The leadership team did not need another market-sizing exercise. It needed to understand which innovation behaviors were missing. The Ten Faces framework was chosen because the issue appeared to be organizational and behavioral, not simply strategic or technical.

How it was applied

The company assessed two product lines and one shared platform team. It reviewed launch postmortems, interviewed product, engineering, sales, and customer-success leaders, and observed roadmap and sprint-planning meetings. Each team was then mapped against the ten faces, using concrete examples to support the assessment.

What the analysis showed

The teams were strong in Director and Storyteller behaviors: roadmaps were well packaged and leaders drove decisions forcefully. They were moderately strong in Hurdler behaviors because teams could work around technical constraints. But Anthropologist, Experimenter, and Experience Architect roles were weak. Customer insight came mostly from sales anecdotes, prototypes were rare, and end-to-end workflow design received little attention.

The actions that followed

The company introduced monthly customer-observation sessions, rapid prototype reviews before roadmap approval, and cross-functional journey-mapping for the highest-priority use cases. To make the new behaviors stick, it also launched a focused change management effort around meeting routines, decision rights, and manager expectations. Within two planning cycles, product concepts were being tested earlier, and roadmap debates became more evidence-based.

7. Strengths and Limitations

Strengths

• Makes innovation concrete. It translates an abstract goal into observable roles and behaviors.
• Creates a shared language. Teams can discuss capability gaps without immediately personalizing the conversation.
• Balances the innovation system. It highlights missing roles, not just missing ideas.
• Works across industries. The framework is adaptable to products, services, customer experience, and internal innovation efforts.
• Supports action. It often leads naturally to decisions about roles, routines, hiring, training, and governance.

Limitations

• It is not a quantitative tool. The model depends heavily on judgment and evidence quality.
• Role boundaries overlap. In practice, several faces may be played by the same person or team.
• It can become superficial. Used badly, it turns into a fun workshop exercise with little operational consequence.
• It does not replace strategy. It will not tell you which market to enter or which portfolio bets to fund.
• It may underplay structural barriers. Incentives, budgeting, compliance, and legacy systems can block innovation even when the right behaviors are present.

8. Common Pitfalls and How to Avoid Them

• Treating the faces as personality types. The model describes roles in innovation work, not fixed identities. Use behavioral evidence and avoid boxing people into labels.
• Running it as a popularity contest. Teams often overrate visible roles like Storyteller and underrate quieter ones like Anthropologist. Ask for examples from real projects.
• Ignoring context. The right mix of faces varies by business model, maturity, and project stage. Define what “good” looks like for this specific situation before scoring gaps.
• Assuming all ten must be equally strong. Balance matters more than symmetry. Focus on the few missing roles that most constrain performance.
• Confusing ideas with experiments. Many teams claim to value testing but rarely prototype with customers. Look for actual pilot behavior, not stated intent.
• Stopping at diagnosis. The framework only creates value when role gaps lead to concrete changes in routines, governance, staffing, and leadership expectations.

9. How IDEO Ten Faces of Innovation Relates to Other Frameworks

Compared with Design Thinking

Design thinking is primarily a process for solving problems through empathy, ideation, prototyping, and iteration. The Ten Faces of Innovation is more about the roles and behaviors that make such a process work. If design thinking tells you how to innovate, Ten Faces helps explain who must show up, and in what ways, for the process to succeed.

Alongside McKinsey 7S or other organization diagnostics

The Ten Faces framework is strong at identifying behavioral and cultural gaps. Frameworks such as McKinsey 7S go further in aligning structure, systems, skills, style, and shared values. A common sequence is to use Ten Faces to spot innovation-role gaps, then use a broader organization framework to redesign the conditions that produce those gaps.

Alongside Stage-Gate, Agile, or Three Horizons

Stage-Gate and agile methods help manage workflow, decision points, and delivery cadence. Three Horizons helps leaders think about time horizons for growth. Ten Faces complements these tools by addressing human capability: customer insight, experimentation, collaboration, and storytelling. Choose Ten Faces when the problem is capability and behavior; choose the others when the problem is governance, portfolio timing, or delivery mechanics.

10. Key Takeaways

• The IDEO Ten Faces of Innovation is a role-based framework for building innovation capability, not just generating ideas.
• It helps answer why innovation efforts stall by revealing missing or weak behaviors across teams.
• Its ten personas span learning, organizing, and building roles that together support repeatable innovation.
• It is most useful for diagnosing teams, redesigning innovation routines, and strengthening culture and collaboration.
• It works best when grounded in real evidence from projects, customer interactions, and team behavior.
• Its biggest limitation is that it is qualitative and can become superficial if not translated into concrete action.

11. FAQs About IDEO Ten Faces of Innovation

Is IDEO Ten Faces of Innovation still relevant today?

Yes. It remains relevant because many organizations still struggle less with idea generation than with the behaviors required to turn ideas into outcomes. Today, teams usually use it as a flexible capability lens within product management, design, agile, and innovation programs rather than as a standalone doctrine.

What is the difference between IDEO Ten Faces of Innovation and design thinking?

Design thinking is a problem-solving approach and process. Ten Faces is a role framework that highlights the behaviors needed to make innovation work. They complement each other well: one structures the work, and the other sharpens the human capabilities required to do it effectively.

Can small or early-stage companies use it?

Absolutely. Small companies often benefit because one person may need to play several faces at once, and the framework makes those gaps visible quickly. A startup does not need a formal diagnostic; even a simple founder workshop can reveal whether customer observation, experimentation, or storytelling is being neglected.

How long does it typically take to apply in a real project?

A light-touch workshop can be done in one or two days. A more credible assessment across multiple teams, with interviews and evidence gathering, usually takes two to six weeks depending on scope, access to stakeholders, and how much behavioral proof is available.

What data is needed to use the framework?

The minimum useful inputs are interviews, examples from recent innovation efforts, and evidence of how customers are understood and how ideas are tested. The analysis becomes stronger when you add customer observations, postmortems, meeting observations, role definitions, and examples of where projects slowed, failed, or succeeded.