Discover your innovation archetype

This innovator type quiz maps your behavioral role in innovation work (where you add value and what you tend to skip) not your personality and not your creativity. It produces four archetypes: Visionary Navigator, Experiment Builder, Systems Orchestrator, and Customer Advocate.

Each archetype has a genuine limitation. Not a growth opportunity. A limitation: the thing this type reliably misses, which your team is paying for whether it's named or not.

If you're taking this individually because you searched "what type of innovator am I?", your result is useful context. If you're running this with a team and comparing everyone's profiles, you're doing the more valuable version of this exercise.

TL;DR

• The quiz measures behavioral role in innovation work, not personality or creativity
• Four archetypes: Visionary Navigator, Experiment Builder, Systems Orchestrator, Customer Advocate
• Each archetype has a named real limitation, not a softened growth area
• Individual results are useful; team results show you what's missing
• Three Visionary Navigators and no Experiment Builder is a coverage gap, not a team strength
• Workshop facilitators: the 90-minute team session in §10 runs this as a diagnostic, not a personality exercise

What does the innovator type quiz actually measure — and what is it not trying to do?

This quiz measures your behavioral role in innovation work: the stages where you add value and the stages you tend to skip. It is not a personality test, a creativity test, or a fixed identity label. The result describes how you currently show up in innovation contexts, not who you are.

The distinction matters in practice. People often land here looking for an innovation archetype or an innovation style assessment. Personality frameworks (Myers-Briggs, the Big Five, the Enneagram) describe stable traits that show up across contexts and resist deliberate change. 2024 meta-analysis Behavioral role frameworks describe what you do in a specific work context: specifically, the stages of innovation work where you add the most energy and the stages you tend to bypass. Fleishman & Quaintance 1984 The correlation between personality traits and innovation behavior is real, a 2024 meta-analysis found significant overlap with Openness (r = 0.32), but role-framing changes what people do with a result. 2024 meta-analysis Telling a team member they score in the 80th percentile on Openness produces a nod. Telling them they are an Experiment Builder whose default is to accumulate findings without forcing a decision gives them something specific to work on, and gives the person managing them something specific to address.

The quiz leaves your identity out of it. It asks what you drive and what you skip, in this specific context, doing this specific kind of work.

The behavioral-role tradition has a long lineage in occupational research. Fleishman and Quaintance (1984) established that classifying work roles by what people do (rather than by inferred personality) has practical predictive value. Fleishman & Quaintance 1984 The innovator type quiz follows that model. It sits alongside methods like design thinking and market validation but answers a narrower question: who drives which stage.

Visionary Navigators are not better innovators than Systems Orchestrators. The quiz maps roles, not a hierarchy. What matters for a team is not which archetypes are represented by the strongest people. It's whether the key stages of the innovation process have someone driving them.

How does the innovator type quiz compare to MBTI, StrengthsFinder, and other assessments?

MBTI and StrengthsFinder map individual traits and strengths. Basadur and VCI map team styles. This quiz differs by naming coverage gaps: which innovation roles your team collectively lacks and what that absence predicts.

Three different outputs. MBTI and StrengthsFinder describe individual traits and natural strengths. The Basadur Innovation Profile and VCI Innovation Styles go further by mapping team composition, but neither produces coverage gaps as its primary output, which means you can see who is on the team without knowing which role is absent. This quiz names the gap.

Assessment comparison

The Basadur Innovation Profile is the closest academic parallel to this innovator archetype quiz. Basadur 2019 Basadur maps four thinking stages (Generator, Conceptualizer, Optimizer, Implementer) which correspond closely to the four innovationterms archetypes (Generator → Visionary Navigator. Conceptualizer → Experiment Builder. Optimizer → Systems Orchestrator. Implementer → Customer Advocate). Basadur's research has been validated across manufacturing, healthcare, and professional services contexts in 10+ languages. The key difference: Basadur's team-use framing focuses on process coverage at each stage, rather than naming which archetype is absent and what failure that predicts.

The VCI Innovation Styles assessment uses four styles (Visioning, Modifying, Exploring, Experimenting) with a style-complementarity framing, "understanding how these styles influence innovative thinking, you can select an innovative mix of people." VCI Innovation Styles VCI asks how styles complement. This quiz asks what's missing. The outputs are different.

What are the four innovator archetypes?

Four archetypes cover the core roles in innovation work: Visionary Navigator, Experiment Builder, Systems Orchestrator, and Customer Advocate. Each adds value in one stage and leaves another stage systematically underdone.

Each archetype maps the behavioral role a person most reliably occupies in innovation work. The Visionary Navigator sets direction and spots openings that others filter out as static. Without friction, this type grips ideas long after the data has moved on. The Experiment Builder turns abstract conviction into testable hypotheses. Left unchecked, this type accumulates findings the organization can't convert to decisions. The Systems Orchestrator turns pilots into operations. Applied to early-stage work, this type cuts experiments before they've had enough runway to show signal. The Customer Advocate keeps teams honest about user behavior. In a position of dominant influence, this type grounds roadmaps in what customers say they want, which isn't always what a changed market will require.

Read the archetype that matches your result. Then read the archetype that describes the gap on your team.

The Everyday Innovators framework (LaunchStreet) uses 36 archetypes generated from nine innovation traits. Everyday Innovators Thirty-six types produce richer self-portraits. They also make team-level coverage mapping a combinatorial problem, a team of eight could represent eight different archetypes from a pool of 36, making gaps nearly impossible to identify in a 90-minute workshop. Four archetypes is a deliberate choice for operability, not a claim of exhaustiveness.

The Board of Innovation uses a two-axis framework: investment level (high/low) by innovation focus (external/internal), producing four organizational types. Board of Innovation That matrix maps what organizations invest in. This quiz maps what individuals drive. Neither is better, they answer different questions.

Visionary Navigator: what this type drives, and what it's slow to release

Visionary Navigators set direction and sustain conviction in ambiguous early work. Their limitation is idea-attachment: they hold on to directions after evidence has turned against them.

Visionary Navigators set innovation direction before others see the opportunity. They generate conviction in ambiguous early-stage work and push teams toward consequential bets. Their limitation is structural: the same idea-attachment that sustains long-horizon thinking makes them slow to abandon failing directions, even when the evidence stops backing the bet.

Visionary Navigators see the destination before anyone else does. They're also the last person to acknowledge when the route no longer works.

What this type drives

Visionary Navigators generate direction. They are most valuable in the early stages of innovation work, when a team is deciding what to work on, which opportunities to pursue, and why. They see patterns across signals that others process as noise. They sustain conviction through the ambiguity of early-stage work when that conviction is genuinely needed.

In team settings, they push the work toward larger, more consequential bets. Without this type, teams default to incremental improvements to existing products because incremental improvements are the easiest case to make when the evidence is thin.

What this type tends to underprioritize

Validation. Experiment results that challenge direction are part of it, but the harder requirement is killing an idea when the evidence turns against it, even with team pushback on feasibility. Staw 1976

Barry Staw's 1976 research named this mechanism precisely: the more resources a person invests in a course of action, the more they resist abandoning it when evidence of failure accumulates, what organizational psychologists call escalation of commitment (the tendency for sunk investment to increase resistance to abandoning a failing course, rather than decrease it). Staw 1976 For Visionary Navigators, this isn't cowardice or ego. It's a structural feature of idea-attachment. The sunk cost trap is strongest in people who genuinely believe in the direction they championed.

The limitation that isn't softened

Visionary Navigators are slow to kill their own ideas. They attach to concepts longer than the evidence supports. Pilots that should have been killed two quarters ago keep running. When a dominant Visionary Navigator holds the most influence, that person keeps finding reasons the data is wrong, and this is the real constraint, not a "tendency to be impatient with execution."

A named historical parallel: Edison's decades-long insistence on direct current (DC) for residential and commercial distribution, against engineering evidence that Tesla's alternating current was the superior approach for that application. Staw 1976 Edison's idea-attachment cost Westinghouse nothing. It cost Edison a technology era.

Next actions

Before the next major project decision, identify one person on the team with explicit permission to argue against your direction and commit to engaging seriously with their argument rather than addressing its weakest version. Set a pre-defined threshold: if the pilot does not reach X metric by Y date, you commit to recommending discontinuation regardless of belief in the concept. Then look at the last batch of ideas you pushed hard for that were eventually dropped, at what point had the evidence already stopped backing them? That lag is your calibration number.

Experiment Builder: what this type generates, and why the findings often stall

Experiment Builders turn assumptions into testable hypotheses. Their limitation is the closing problem: they accumulate findings without forcing the decision those findings should produce.

Experiment Builders turn abstract conviction into testable hypotheses. They make assumptions visible and push teams toward explicit criteria for what a result means. Their limitation is the closing problem: a structural reluctance to stop accumulating findings and force a decision, particularly when the result points toward an uncomfortable conclusion.

Experiment Builders run the tests. They're often the last person to stop running them and start deciding.

What this type drives

Experiment Builders make assumptions visible. Before an Experiment Builder engages with a direction, abstract conviction becomes a set of testable hypotheses. They generate evidence where others generate opinions.

In team settings, they're the antidote to the Visionary Navigator's idea-attachment. They push the team toward rigor and explicit criteria for what a result means, insisting on structured testing rather than letting enthusiasm carry the decision. Without this type, teams ship whatever got the most internal support.

What this type tends to underprioritize

Decision-forcing. Specifically: the transition from "we have findings" to "we are changing course based on these findings."

Research on experimentation culture documents organizations that run many experiments and still fail to act decisively on the results. The finding that gets run past is usually the one that contradicts a preferred direction. Often, Experiment Builders run another test rather than accept an inconvenient result as valid.

The limitation that isn't softened

Experiment Builders accumulate findings that the organization can't convert to decisions. This is not a patience problem. It's a structural reluctance to close the loop when the result points toward an uncomfortable conclusion.

The failure mode: twelve experiments running in parallel, each with inconclusive or directionally negative results, each justified as "needing more data." The team is busy. Nothing is getting decided. The Experiment Builder is doing their job. Nobody's doing the job of forcing a conclusion from the work.

Next actions

Assign every experiment a pre-defined decision date before it launches, not a "results ready" date, a decision date. After every experimental result, force yourself to write one sentence: "Based on this, we should [continue / pivot / stop] because [specific finding]." Track your findings-to-decisions ratio quarterly. Running more than two experiments per decision made means you have a closing problem.

Systems Orchestrator: what this type protects, and what it tends to cut prematurely

Systems Orchestrators scale proven approaches through process design and quality gates. Their limitation is applying efficiency logic to exploratory work, which kills experiments before they have enough runway to show signal.

Systems Orchestrators turn pilots into operations. They are most valuable when proven approaches need to scale: process design, resource allocation, quality gates. Their limitation is context mismatch: efficiency logic applied to exploratory work will reliably return the verdict to cut it, and a thorough Systems Orchestrator will follow through.

Systems Orchestrators keep the innovation engine running. They also tend to shut down the experiments that haven't yet proven themselves before they've had enough runway to show signal.

What this type drives

Systems Orchestrators turn pilots into operations. They are most valuable when something that has been tested needs to scale: process design, resource allocation, quality gates, timeline management. When an innovative approach needs to move from "this works in the lab" to "this works at 10,000 customers," the Systems Orchestrator is the person who knows how to do that.

In team settings, they prevent the chaos of Visionary Navigator-dominated teams where new directions are launched before old ones have been resolved. They protect execution quality.

What this type tends to underprioritize

Exploratory bets with unclear payoff timelines, which describes every early-stage innovation. March 1991

James March's 1991 analysis of organizational learning identified the central tension, what is now canonical in strategy research as the exploration-exploitation trade-off (the structural conflict between refining proven operations and discovering new possibilities, which organizations cannot improve simultaneously without deliberate design): organizations that favor exploitation progressively reduce their capacity for adaptive innovation. March 1991 Systems Orchestrators are the human embodiment of exploitation logic. Applied to operations, that logic is exactly right. Applied to early-stage innovation, it kills the work before it's had a chance.

The limitation that isn't softened

Systems Orchestrators apply efficiency logic to contexts where efficiency logic is, technically, the wrong tool. The metrics they use for operations (ROI, resource utilization, timeline adherence) are perfectly calibrated to evaluate work that has already been proven to work. Applied to early-stage innovation, which by design has not been proven yet, those metrics will reliably return the verdict: cut it. And the Systems Orchestrator, being thorough, cuts it.

Kodak invented the digital camera in 1975. O'Reilly & Tushman 1996 (They did. Their own engineer, Steve Sasson, built it. It was the size of a toaster and took 23 seconds to record one black-and-white image to a cassette tape. Management shelved it.) Their operational excellence (the most efficient film manufacturing and distribution operation in the world) was managed by people who were very good at protecting what worked. They protected it until it didn't.

O'Reilly and Tushman (1996) called the underlying problem "ambidexterity": the simultaneous capacity for exploitation and exploration that most organizations cannot maintain because exploitation logic tends to win resource allocation decisions. O'Reilly & Tushman 1996

Next actions

Identify one exploratory bet in your team's current portfolio that you've been skeptical of. Before your next review meeting, ask explicitly: is my skepticism based on evidence of failure, or on a sense that resources could be deployed more productively elsewhere? Apply different success metrics to exploratory work than to operational work, an exploratory bet measured by operational ROI will fail operational ROI metrics by design, and that's expected. Partner with an Experiment Builder when evaluating early-stage work.

Customer Advocate: what this type surfaces, and where it loses influence

Customer Advocates keep teams grounded in real user behavior. Their limitation is conservative gravity: they overweight what current customers ask for and underweight possibilities those customers have not yet imagined.

Customer Advocates keep innovation grounded in real user behavior. They translate needs into requirements and surface friction that quantitative data misses. Their limitation is conservative gravity: deep customer closeness makes it structurally difficult to see past what current customers are asking for, systematically underrepresenting the possibility space.

Customer Advocates ensure the team never forgets who the innovation is for. They're also the most likely to ground the team's ambitions in what customers say they want, which isn't always the same as what they'll use.

What this type drives

Customer Advocates maintain connection to actual user behavior throughout the innovation process. They translate needs into requirements, surface friction that doesn't show up in quantitative data, and remind teams that the person at the end of the product roadmap has a life that doesn't revolve around the product.

In team settings, they are the most effective check on Visionary Navigator overreach. When the direction is compelling but disconnected from real user behavior, the Customer Advocate has the credibility and evidence to say so.

What this type tends to underprioritize

Platform-level direction decisions: specifically, bets that require imagining user behavior that doesn't currently exist.

Clayton Christensen documented this pattern in The Innovator's Dilemma (1997): companies that excelled at listening to customers consistently missed disruptive innovation shifts because customers could not articulate needs for products they had never imagined. The Customer Advocate's deep customer connection becomes a conservative gravity. The closer a person is to current customer feedback, the harder it is to see past what those customers are currently asking for.

The limitation that isn't softened

Customer Advocates can trap innovation in the incremental. Their data is real (customer feedback is real) but it systematically underrepresents the possibility space. Customers will tell you, in remarkable detail, exactly what they want you to improve about the thing they already have. They are considerably less useful as predictors of what they will want next, because they have not imagined it yet. The result: roadmaps populated with improvements to what exists, because that's what users asked for, while the platform-level shift that would have changed the market goes unaddressed because no user was asking for it yet.

RIM's Blackberry leadership spent most of the 2000s deeply customer-responsive to enterprise IT buyers who specifically wanted keyboards, security, and email reliability. They listened carefully. Their customers were satisfied. And then their customers bought iPhones.

VCI's Innovation Styles framework calls its closest equivalent the "Visioning" style: an orientation toward broad possibility. VCI Innovation Styles The Customer Advocate is its complement, close to context, skeptical of speculation, grounded in what's real. The problem is not that this orientation exists. The problem is that customer closeness carries structural authority in most product teams, which means the Customer Advocate's conservative gravity tends to win resource allocation arguments. Customer Advocacy without a Visionary Navigator in the room doesn't balance, it dominates, and the platform-level bets that could change the market go unfunded because no current user is asking for them yet.

Next actions

Identify one customer insight from the last six months that you advocated for strongly. Then ask: is the solution we built optimizing for what customers said they wanted, or what they would need if their situation changed significantly? Before the next roadmap review, identify one thing your users have never asked for that would meaningfully change how they use the product. Present it as a hypothesis, not a feature request.

What does the research say about innovation team composition?

Research on cognitive diversity and team composition shows that complementary thinking styles improve problem-solving and innovation output. The link to the four archetypes is inferred from that general evidence base, not from archetype-specific studies.

Teams with complementary innovation-role coverage are generally more effective than teams where roles are redundant. The performance gap is measurable in cognitive-diversity research, though the specific archetype-coverage link is inferred.

By the numbers

Matthew Syed makes the recombinant point directly: more cognitive variety increases the raw material for new combinations. Diversity's innovation premium is a mechanism, not a compliance initiative. Novel combinations require novel inputs. If everyone on the innovation team is generating directions and nobody is testing them, the combination doesn't produce innovation. It produces a slide deck. The slide deck will be compelling. The slide deck is always compelling. That is not the problem.

The direct archetype-coverage-to-performance link is inferred from general cognitive diversity research, not archetype-specific studies. The general case is well-evidenced. The specific claim that Visionary Navigator / Experiment Builder balance predicts better innovation output than either orientation alone is a reasonable inference from that evidence base, not a separately demonstrated finding.

"The best teams have an appropriate mix of Generators, Conceptualizers, Optimizers and Implementers. With a diverse line-up, each member plays to their strengths — working at full capacity in their relevant stage of the process while others work at full capacity in theirs."
— Basadur Institute, McMaster University TechBrief

Why your team's combined profile matters more than your individual result

Individual quiz results are useful self-knowledge. Team results are actionable because they reveal which innovation stages have no native driver and what failure mode that absence predicts.

Your individual innovator-type result is the least interesting output of this quiz. What your team is collectively missing is the part worth acting on. Tom Kelley 2005

The actionable information is structural, not personal. Knowing you are an Experiment Builder is useful self-knowledge. Knowing that you are the only Experiment Builder on a team of four Visionary Navigators tells you something about your role in that team that you cannot learn from your individual result alone.

"Innovation is ultimately a team sport. Get all the roles performing at the top of their game and you'll generate a positive force for innovation."
— Tom Kelley, The Ten Faces of Innovation, 2005
Tom Kelley's ten-role framework at IDEO makes the same structural argument: it is not the brilliance of any individual innovator that drives outcomes, but whether the team has coverage across the roles the innovation process requires. Tom Kelley 2005 Three Visionary Navigators and no Experiment Builder is not a team of visionaries. It's a team that generates bold directions and tests none of them.

The counter-argument worth naming

The "lone genius" literature (Simonton on creative cognition, the Edison and Jobs cultural narratives) argues that breakthrough innovation is driven by individual cognitive leaps, not team coverage. Ainissa Ramirez This is not a counter-argument to coverage-gap mapping. It is an answer to a different question. The lone-genius frame is a different question entirely. Coverage-gap mapping asks whether a team can reliably produce, test, scale, and ship innovations across a portfolio, on a budget, in a fiscal year, with people who have other meetings. These questions have different answers, and conflating them is how organizations end up waiting for their Edison rather than fixing their process. Individual archetype results are relevant to the first question. Coverage-gap mapping answers the second, which is the question almost every innovation program is actually trying to answer.

"This myth of the lone genius, it never existed... The minute that we deify somebody and say that person is a lone genius, let them work, let them do. We almost stop questioning their methods and their tactics."
— Ainissa Ramirez, Talk Nerdy with Cara Santa Maria
If you're taking this quiz individually, read the limitation section of your archetype card, calibrate the result against a peer who works with you regularly, and identify one specific behavior to adjust. If you're running this as a team, the next section is where the work happens.

How to run a team archetype session in 90 minutes

A 90-minute team session maps team innovation styles, identifies missing roles, and connects the gap to a current project risk. The output is a coverage map, not a personality exercise. The structure borrows from design thinking facilitation: a shared frame, independent input, synthesis, and a decision.

Innovation teams that run this quiz individually rarely surface the connections that shared discussion would reveal. Run it as a team and you get a coverage map: which archetypes are represented, which are absent, and what that absence predicts about the stages of innovation work your team is most likely to skip.

Amy Edmondson developed her team diagnostic approach by studying how teams learn under pressure. Her prime finding: validated team surveys surface relationship quality and interpersonal dynamics that are otherwise invisible.

"And so my simple hypothesis, but I think reasonable hypothesis was that better teamwork, which I would assess with a validated team diagnostic survey, would be associated with fewer error rates, right? And the more I thought about it, it suddenly occurred to me that maybe the better teams, and it did not doubt the veracity of the team diagnostic survey, but maybe the better teams, their quality relationships."
— Amy Edmondson, Passion Struck EP 343

The archetype session applies the same logic: the conversation about coverage gaps forces a team to acknowledge what kind of innovation work it is structured to avoid.

Keith Ferrazzi frames team diagnostics as routine leadership practice, not specialized HR interventions. Keith Ferrazzi Running this session as a regular leadership exercise, not a retreat activity, keeps the coverage map current as teams evolve.

The five steps

Step 1: Set the frame before anyone takes the quiz (15 minutes)

Before the quiz opens, name explicitly what this session is for: mapping what the team's combined profile is missing, not measuring who is a better innovator. Address Susie Braam's "off-the-hook" risk directly: mapping coverage archetypes is not assigning innovation responsibility to specific people. Susie Braam Every team member participates in innovation work. The map shows where each person's natural contributions are strongest and where they need to compensate deliberately.

Edmondson's psychological safety research matters here: teams that feel safe for interpersonal risk-taking engage honestly with diagnostic results. Edmondson 1999 Set the psychological safety frame before anyone sees a result.

Step 2: Everyone takes the quiz independently (15 minutes)

Participants complete the quiz without discussing questions or results with each other. Independent completion prevents the anchoring effect of a senior leader going first and others calibrating toward their result.

Step 3: Share results without interpretation (10 minutes)

Each person states their archetype. No explanation, no defense, no "but I'm also somewhat of a..." Each result is written on a shared whiteboard or digital equivalent. The room can see the full coverage map before anyone starts analyzing it.

Step 4: Map the coverage (20 minutes)

Count the representation of each archetype. Identify archetypes with no representation. Ask the room: is there a stage in our innovation process that consistently stalls, gets skipped, or generates work that nobody acts on? Map that stall point to the missing archetype.

Step 5: Name the implication for a specific current project (30 minutes)

Take one active innovation project. Walk through the innovation stages (framing the problem, testing assumptions, building the system, validating with users) and ask: which of these stages are we reliably doing, and which are we skipping? The skipped stages should match the missing archetypes. If they don't, you have either a context problem (the right archetypes are present but something is suppressing those behaviors) or a measurement problem (someone's result doesn't reflect their actual behavior). Both are worth investigating.

What people get wrong about innovator type quizzes

Three misreads limit the quiz's value: treating the result as identity, trusting honest self-report as accurate, and softening the limitation into a generic growth area.

Three misreads consistently limit what people take from this quiz. They treat the result as identity rather than current behavior, they confuse honest self-report with accurate self-report, and they interpret the limitation charitably rather than specifically. Each misread leaves the result in the category of things that felt useful for 15 minutes.

Misconception 1: "My result tells me who I am as an innovator."

Your result tells you how you tend to show up in innovation work in your current context. It describes behavior, not identity.

The self-assessment accuracy research is unambiguous: the average correlation between self-rated and objectively measured ability across 22 meta-analyses is r = 0.29. Zell & Krizan 2014 That correlation is real but modest. Quiz results should be directionally trusted and then calibrated against peer perception, specifically, ask a colleague who works with you regularly whether your result matches how they experience your innovation contributions.

Misconception 2: "I answered honestly, so my result is accurate."

Honest self-report and accurate self-report are not the same thing. Unconscious bias systematically pulls quiz answers toward the identity we prefer to claim rather than the behavior we actually exhibit. EAUniverse Answering honestly means answering without deliberate distortion. It doesn't override the structural tendency to answer in ways that confirm a preferred self-image.

The practical corrective: after reading your result, identify the limitation named in your archetype card. If your first reaction is "that doesn't apply to me," that reaction itself is worth scrutinizing.

Misconception 3: "My growth areas are just opportunities, the limitation isn't that serious."

The constraints are real. Each archetype card names something that is already costing your team something right now, whether or not anyone has named it, and a Visionary Navigator who holds on to ideas past the evidence threshold is a direct example because the team pays that cost regardless of whether the behavior has a label. When Systems Orchestrators cut exploratory bets early, whatever was in those bets is simply gone.

Reading the limitation charitably is the most common way to take a quiz and learn nothing from it.

When can the quiz result mislead you?

Quiz results reflect current context. They can mislead when organizational context suppresses natural behavior, when you are in a transition role, or when team norms have shaped your answers.

The quiz result reflects how you currently behave in your current context. Three scenarios produce systematically misleading results.

Scenario 1: Organizational context is suppressing your natural repertoire

Herminia Ibarra's research on behavioral identity argues that role context — the demands, rewards, and constraints of your current environment — shapes which behaviors are expressed and which are suppressed. Ibarra 2015 A Visionary Navigator working in a process-compliance-heavy organization may have learned to suppress directional thinking because it hasn't been rewarded. Their quiz result may show as Systems Orchestrator.

If your result surprised you or feels contextually constrained, ask: "What would I answer if I were in a role where each of these behaviors was equally valued and rewarded?" That hypothetical result may be more revealing than the current one.

Scenario 2: You're in a transition role

People taking the quiz during career transitions (new role, new organization, significant change in scope) often answer toward the behaviors required by their new context rather than their behavioral defaults. The result reflects the transition, not the stable pattern. Take the quiz again six months into the new role.

Scenario 3: Team norms have shaped your answers

If you've been on a team with a dominant archetype for several years, you may have adapted your behaviors toward what the team's norms reward. An Experiment Builder who has been working with three Systems Orchestrators for three years may have learned to minimize hypothesis-testing and focus on execution. That learned adaptation will show up in the quiz results.

Some people fit more than one innovator type.

Yes. Most people have a primary archetype and meaningful secondary tendencies. The quiz produces a dominant result, but the underlying score across the four archetypes shows distribution. If your secondary archetype is strong (within 10–15% of your primary) you will likely move between those two roles depending on project context and team composition.

Archetypes can shift as circumstances do.

Yes, and the change is usually context-driven. Amabile and Khaire (2008) documented how organizational environment shapes which innovation behaviors are expressed. Amabile & Khaire 2008 Read it as a snapshot of now, not a label you carry forward. The MBTI result changes for approximately half of takers within five weeks. Pittenger 1993 The innovator type result is expected to evolve more slowly but is not permanent. Retaking the quiz after a significant role change gives a more accurate current reading.

What happens when a team maps its coverage gap

Mapping coverage gaps makes invisible team biases visible. Once a team names which archetypes are missing, it can connect the gap to specific stalls and design a structural response.

Coverage gaps are invisible until you map them. Once visible, they explain past failures with uncomfortable precision. A team that has been losing velocity without understanding why typically finds the gap matches exactly the stages they have been skipping.

A product team of five at a professional services firm had been running a pilot program for eight months. Three members were Visionary Navigators. The fourth was a Customer Advocate. The fifth was a Systems Orchestrator with strong secondary Experiment Builder tendencies, meaning, in practice, that nobody on the team was doing the Experiment Builder's actual job. Each pilot generated enthusiasm and early traction. Each pilot then hit the moment where the team needed market validation evidence to decide whether the results justified continuing. Each time, the decision was deferred: "we need another quarter of data." The team was not short on conviction. It was short on the structural role that turns findings into decisions.

Basadur's team-composition research suggests that an Experiment Builder-type gap is a recurring pattern in product-focused innovation teams: strong direction-setting, adequate systems support, and no one whose native orientation is making assumptions explicit and forcing decisions from test results. Basadur 2019 The Experiment Builder gap doesn't announce itself as a coverage problem. It announces itself as a velocity problem, everything is moving, nothing is closing.

When the team mapped their coverage profile, they added a second member with Experiment Builder orientation: a cross-functional analyst from the research function who had been structurally excluded from the pilot process. Within two review cycles, the team was acting on findings rather than scheduling another round of testing. The map didn't fix the team. It named what was already wrong. That naming made the problem specific enough to address structurally, and gave the Visionary Navigators a way to understand the stall that wasn't about anyone's competence.

This pattern is consistent with the Basadur Institute's team-composition research and the Lorenzo / BCG research on team diversity and innovation revenue. Basadur 2019 and Rocío Lorenzo.

Step 1, Mapping reveals a previously unnamed pattern

When three Customer Advocates, one Visionary Navigator, and one Systems Orchestrator on a five-person team finally name what they are, two years of excellent incremental roadmaps and zero new directions start to make sense. The map doesn't create the problem. It names what was already there.

Step 2, The gap predicts past failures accurately

Once the coverage map is visible, teams consistently identify past project stalls that match the missing archetype. The initiative that died because "nobody was sure we were testing the right thing" is the Experiment Builder gap, and the pilot that worked but never scaled is the Systems Orchestrator gap. Past patterns validate fast.

Step 3, Structural response, not individual behavior change

The most common effective response to a coverage gap is structural: adding a person with the missing orientation to the team, or explicitly assigning coverage responsibility to someone with secondary tendencies in the missing archetype. Individual behavior change alone (asking a Visionary Navigator to become more of an Experiment Builder) produces limited, short-lived results. The structural response acknowledges that coverage is a team property, not an individual development goal. Tom Kelley 2005

Frequently asked questions

Can I be more than one innovator type?

Yes. Distribution matters. The quiz produces a dominant archetype, but when your secondary archetype scores within 10–15% of your primary, the underlying score shows you regularly draw on both types depending on context, and the dominant result is really just saying where your energy tends to go first rather than where it goes in every situation.

Does my innovator type change over time?

Yes. Results shift. A career transition or deliberate practice in a non-dominant archetype can move the primary result, as can a significant change in organizational culture, and the MBTI changes for approximately half of takers within five weeks anyway. Pittenger 1993 The innovator type result is more stable because it asks about work behaviors in a specific context, not abstract preferences. Retake after any significant role change.

What should I do if I strongly disagree with my result?

Both answers held up. First, ask a colleague who works with you regularly whether the result matches how they observe your innovation contributions. Self-assessment accuracy is limited (r = 0.29 average correlation with observed performance Zell & Krizan 2014), and the disagreement may reflect the gap between how you see yourself and how you actually show up. Second, identify which archetype you expected to receive and ask why, the gap between expected and actual result is often the most diagnostic data the quiz produces.

How is this different from Myers-Briggs or StrengthsFinder?

MBTI maps personality type preferences: stable patterns in how you perceive information and make decisions. StrengthsFinder maps natural talent domains. Both are general-purpose frameworks that don't distinguish innovation contexts from other work contexts. Pittenger 1993 and Soultrace analysis.

Whether you're introverted or extroverted is out of scope. The quiz asks what you drive and what you skip when the work is uncertain.

What does it look like when an Experiment Builder and a Systems Orchestrator work together on the same team?

Friction, then high performance. The Experiment Builder is running tests before the Systems Orchestrator is ready to commit resources. The Systems Orchestrator is demanding decision criteria the Experiment Builder hasn't yet met. When the team has made the tension explicit (both archetypes understand the other's default and its value) the pair produces better outcomes than either type alone: evidence-grounded decisions that can actually scale.

Things break when both types look away from the friction. The Experiment Builder dismisses the Systems Orchestrator as "not understanding innovation work". The Systems Orchestrator dismisses the Experiment Builder as "never delivering anything actionable." Teams benefit from naming this dynamic explicitly in the archetype session.

My team is all Visionary Navigators. What does that mean for us?

It means you are structurally set up to generate compelling directions and structurally set up to avoid testing whether those directions are right. Expect idea-attachment cycles: an enthusiastic launch, a pilot that doesn't quite validate the concept, a round of reframing, another launch. The work continues but decisions don't get made.

The intervention: bring in one person with a strong Experiment Builder orientation, either by hiring, cross-functional rotation, or identifying who on the existing team has the strongest secondary Experiment Builder tendency and explicitly assigning them the testing responsibility for the next project.

How do I bring this into a workshop if my team is skeptical of quizzes?

Lead with the coverage-gap framing rather than the archetype labels. Skepticism about quiz results usually centers on the "this is just a horoscope" objection. Pre-empt it by telling the team before anyone takes the quiz: the goal is not to validate individual strengths, it's to map what this team is collectively set up to miss. The output is a coverage map. If the coverage map produces a conversation worth having (if three people in the room recognize the pattern it shows) the quiz earned its 15 minutes regardless of how each person feels about their individual result. The framing is similar to a design thinking workshop: the artifact is only useful if it produces a shared insight. Susie Braam

Related concepts

The innovator type quiz connects to several innovation methods and concepts. Design thinking provides the facilitation structure for the team session. Market validation is what the Experiment Builder archetype forces. Disruptive innovation explains the Customer Advocate's blind spot. Innovation feedback loops keep the cycle from stalling. Business model canvas and continuous foresight sit upstream and downstream of the archetype conversation. Federated innovation offers one governance model for distributing innovation responsibility once the coverage map is visible.

TL;DR (prose version)

Each of the four archetypes (Visionary Navigator, Experiment Builder, Systems Orchestrator, Customer Advocate) carries a real constraint named outright in the result, not dressed up as potential. Individual results provide useful self-knowledge. Team results reveal the structural gaps that explain why certain kinds of innovation work stall. The most actionable use of this quiz is as a team diagnostic: compare everyone's results, identify which archetypes have no representation, and connect the coverage gap to a specific past stall or a current project risk.