Innovation culture assessment: how to measure what your organization actually does

Culture is the hardest thing to assess in any organization. It is also the most frequently assessed — and the most frequently misassessed. Every company I work with has done some version of a culture survey. Most of those surveys report a healthy, open, innovative culture. And most of those companies have an innovation program that is not working.

The survey is not wrong because people lie. It is wrong because surveys measure the wrong thing.

An innovation culture assessment is only useful if it measures what people actually do, not what they intend to do or believe about themselves. This guide explains how to do that — and why the standard approach consistently produces misleading results in B2B and industrial companies.

Why culture surveys fail the innovation test

The standard approach to assessing innovation culture is a survey. Questions like: “Does leadership support experimentation?”, “Is failure tolerated in our organization?”, “Do we have the resources to pursue new ideas?” Responses on a 1 to 5 scale. The aggregate becomes the culture score.

The problem is structural. Surveys measure intentions and beliefs. They do not measure behavior.

When I ask a senior engineer whether their organization tolerates failure, they think about the official position. The values on the website. The innovation day where the CEO said “we need to think like startups.” They answer based on that framing, and they answer honestly: 4 out of 5.

Then I ask what happened the last time their project failed. Who was in the room. What were the first questions. Was the conversation focused on “what did we learn?” or “what went wrong and who is responsible?” Was the person leading the project promoted in the following year, or quietly moved to a less visible role?

That second conversation tells me the actual culture. Not the belief, the behavior.

This gap between stated culture and actual culture is consistent across industries, but it is especially wide in industrial B2B. The reasons are structural.

Long tenures mean norms are deeply embedded. A company that has been rewarding execution over exploration for 30 years has those norms encoded in who gets promoted, what gets discussed in leadership meetings, and what kind of behavior earns recognition. A survey cannot detect that encoding. Behavioral evidence can.

Hierarchy creates honest-answer problems. In companies with strong hierarchical norms, survey responses about leadership behavior are systematically more positive than cross-functional workshop responses. People answer based on what it is safe to say, not what they observe. This is not dishonesty. It is the rational behavior of someone who understands the power structure they operate in.

The core business dominates the frame of reference. When someone at a manufacturing company answers “does our organization support innovation?”, their frame of reference is the core business. And the core business is probably well run. The survey measures the wrong thing: it measures whether the organization is good at what it already does, not whether it is capable of doing something new.

The backwards approach: from outcomes to root causes

A more useful innovation culture assessment starts at the other end. Not “what do you believe about your culture?” but “what does your organization actually produce?”

Start with outcomes. Trace backwards to behaviors. Then trace backwards to root causes.

Step 1: Measure outcomes

Look at the observable outputs of innovation activity over the past 12 months. Not inputs — budget allocated, people hired, workshops run. Outputs:

• How many new business ideas were tested with real customers?
• How many assumptions were validated or disproven through structured experiments?
• How many projects were stopped based on evidence, rather than budget cuts or management changes?
• How many ideas moved from exploration to a funded pilot?
• How quickly can a team go from idea to first customer evidence?

These numbers tell you what the culture actually produces. A company that ran 40 experiments last year has a different culture than a company that ran zero, regardless of what their survey scores say. And a company with a kill rate of zero — where no projects are ever formally stopped based on evidence — is running an assumption portfolio, not an innovation portfolio.

Step 2: Trace to behaviors

Once you have the outcomes, identify the specific behaviors that produce them. For each outcome gap, ask: what does someone actually do in this organization when they want to run an experiment?

Walk through the sequence: a product manager has an idea. She wants to test it with a customer before building anything. What does she do first? Who does she tell? What approval does she need? How long does that take? What evidence is required before she gets a budget, even a small one? What happens if the experiment fails?

The answers reveal the behavioral reality. A company where an experiment requires a three-year financial forecast has a culture that prevents early testing. Not because people are hostile to innovation, but because the process was designed for a different purpose and nobody has changed it. How to test business ideas systematically is one part of the solution, but only after the organizational blockers are identified.

Step 3: Identify root causes

Behaviors are produced by systems. The system that produces the behavior “experiments require three-year forecasts” is probably the capital allocation process, which was designed for large investments in the core business and applied wholesale to innovation because nobody created a separate process.

Root causes fall into three categories:

Incentive misalignment: the reward system optimizes for the core business and makes innovation behavior a career risk. If a manager’s bonus depends on this year’s margin and innovation projects carry uncertainty costs, the rational choice is to protect the margin. The behavior is not irrational. The system is misaligned.

Process mismatch: the organization uses core-business processes for innovation projects. Stage-gate works for product development inside a known market. It does not work for exploring a new business model. When teams are forced through a stage-gate process before they have any customer evidence, the process selects for projects that sound credible in a meeting room, not projects that have been validated with customers.

Structural isolation: innovation is separate from the core business in name but not in resource access. An innovation team that needs engineering time, manufacturing capacity, or customer access from the core business will always lose to the core business’s own priorities. The structural connection between exploration and execution is absent or non-functional.

Why leadership self-assessment is unreliable

The most common way companies assess their innovation culture is to ask the leadership team. This is also the assessment method most likely to produce a misleading result.

Leadership teams consistently overestimate their organization’s innovation culture. The pattern is consistent enough that I now treat any leadership-only self-assessment as a starting point for investigation, not a conclusion.

The reasons are predictable.

Leaders judge from intent, not impact. The CEO announced the innovation strategy. The CFO protected the budget in last year’s planning cycle. The board approved the new innovation function. From the leadership team’s perspective, the conditions are in place. What they do not see is what happens three layers down when someone actually tries to act on that strategy. The approval process that takes four months. The manager who kills ideas to protect his business unit’s margin. The incentive structure that makes experimentation a career risk for anyone below director level.

The signal does not travel up. In most organizations, bad news about innovation does not reach the leadership table. A team that gave up on an experiment because they could not get budget approval does not file a report about it. The innovation manager who has been spending most of her time navigating bureaucracy instead of building things does not send that information to the CEO. Leadership sees the projects that survived. They do not see the projects that died before they started.

As Gary Pisano noted in Harvard Business Review: innovative cultures require tolerance for failure but no tolerance for incompetence. Most industrial companies have the opposite: very low tolerance for failure of any kind, combined with wide tolerance for organizational dysfunction that blocks innovation. Leadership often does not see the dysfunction because it is invisible from the top.

What cross-functional assessment reveals

When you run the same assessment with a cross-functional group — including middle managers, product teams, engineers, and customer-facing staff alongside the leadership team — you consistently get lower scores and more specific problem identification.

Middle managers see the resource conflicts that leadership does not. They are the people who have to tell an innovation team “no, I cannot release that engineer for six weeks, his utilization is at 95%.” They live the conflict between exploit and explore every week. Their score on the “bridge to the core” dimension reflects that reality.

Product teams and engineers see the process problems. They are the ones who have tried to run experiments and hit the approval process. They know which requests take three months and which take two weeks, and why. Their score on the “process management” dimension is based on direct experience.

A cross-functional assessment does not produce a lower score because the participants are more pessimistic. It produces a lower score because they have more direct evidence about what actually happens.

The four diagnostic questions

When I run an innovation culture assessment, the four questions that reveal the most in the shortest time are:

1. What happened the last time a project failed?

The answer to this question tells you more about innovation culture than any survey. Not “what is supposed to happen” or “what our values say should happen.” What actually happened. Who was in the room. What the first question was. Whether it was treated as a learning event or a failure event. Whether the project leader’s career was affected.

A culture where failed experiments are treated as evidence is an innovation-ready culture. A culture where failed experiments trigger blame, budget cuts, and career damage is not, regardless of what the values statement says.

2. How long does it take to get budget for a small test?

Define small: €5.000 to test an assumption with a customer before investing in a prototype. The answer should be days. In most industrial companies, the answer is months.

The gap between days and months is the process problem made visible. It is not that people are hostile to the test. It is that the approval process was designed for investments, not experiments, and nobody has built a fast path for small tests.

3. What happens when an innovation project threatens core revenue?

This is the cultural stress test. Every company’s culture supports innovation when it does not threaten anything. The culture question is: what happens when it does?

A subscription model for industrial equipment threatens service contracts. A direct sales channel threatens distributor relationships. A new material threatens existing supplier agreements. The company’s response to these moments is where the actual culture lives, not in the innovation day presentations.

4. Who has the authority to say yes to an unproven idea?

Map the decision path for a new innovation project. Who decides it gets resources? How high does it have to escalate before someone can say yes? What is the minimum viable approval process?

In many industrial companies, a €25.000 experiment requires CFO sign-off. That tells you the organization was designed to optimize large investments in known directions. Changing that requires a specific decision by specific people. It does not change through culture workshops.

The nine-dimension walk-through

The innovation readiness assessment structures culture measurement across nine dimensions. Here is what low and high look like in behavioral terms for each one.

Strategic guidance (Leadership support) Low: leadership has announced innovation as a priority but cannot articulate specific exploration bets or how they differ from core business improvements. High: leadership can name two or three specific markets, business models, or customer segments they are actively exploring, separate from the core business roadmap.

Resource allocation (Leadership support) Low: innovation budget exists on paper. The first time quarterly numbers disappoint, it gets reallocated. Teams doing innovation work do it in the margins of their regular jobs. High: there is a protected budget that survived at least two consecutive reallocation pressures. Innovation has dedicated headcount, not borrowed time.

Portfolio management (Leadership support) Low: leadership reviews project status updates. They do not make active allocation decisions based on evidence. No project has ever been formally stopped based on a readiness assessment. High: leadership reviews the innovation portfolio quarterly and makes explicit decisions: fund this, stop that, redirect this team.

Legitimacy and power (Organizational design) Low: the innovation function has an innovation manager at a mid-level who spends most of their time in meetings explaining why innovation matters. High: the innovation leader has direct access to the executive team and can get decisions made without navigating three layers of approval.

Bridge to the core (Organizational design) Low: the innovation team can theoretically use core business resources but every request requires a formal work order and competes with customer priorities. High: there are explicit policies for innovation team access to production, engineering, and customer relationships, with a designated senior owner who resolves conflicts.

Rewards and incentives (Organizational design) Low: innovation is an additional expectation on top of operational KPIs. Nobody is evaluated based on innovation-specific criteria. High: people working on innovation projects are evaluated on learning milestones, assumption testing, and customer discovery — not on delivery KPIs designed for the core business.

Innovation tools (Innovation practice) Low: the Business Model Canvas and the Value Proposition Canvas are known but used only in workshops. Day-to-day innovation work happens without structured tools. High: teams use structured canvases and experiment design methods as standard practice. The tools are integrated into how innovation work gets done, not saved for retreats.

Process management (Innovation practice) Low: innovation projects go through the same stage-gate process as core business projects. Business case requirements are defined before any customer evidence exists. High: there is a separate, lightweight process for innovation projects that measures risk reduction through evidence, not forecast accuracy.

Innovation skills (Innovation practice) Low: technical competence is deep. Nobody can answer “who in this company knows how to design a business experiment?” Ask the room and it goes quiet. High: there are people with documented customer discovery, assumption testing, and business model design skills. These capabilities are tracked and developed intentionally.

What to do with what you find

An innovation culture assessment is only useful if it leads to action. The most common mistake: conducting a thorough assessment, producing an accurate diagnosis, and then treating the diagnosis as the output.

The assessment tells you what the culture is. It does not change it. What changes culture is changing the systems that produce the behavior.

Prioritize root causes, not symptoms. If the assessment reveals that experiments take three months to approve, the symptom is slow decision-making. The root cause is probably that the innovation budget is inside the core business capital allocation process. Fixing the symptom means training leaders to make faster decisions. Fixing the root cause means creating a separate fast-path budget for experiments below a certain threshold, with different approval criteria. Fix the root cause.

Start with the highest-leverage change. You cannot fix everything at once. Identify the one change that would most improve innovation output. Often this is the incentive structure or the approval process. Both are fixable, but both require explicit decisions by the people who own them.

Reassess regularly. Culture changes slowly. The gap between stated culture and actual behavior is closed by consistent changes to systems and signals, not by single events. Track the same behavioral metrics quarterly: experiments run, time-to-first-evidence, kill rate, reward and recognition actions. The trend tells you whether the changes are working.

For a structured approach to running the assessment with your leadership team, see How to run an innovation readiness workshop.

Frequently Asked Questions

What is an innovation culture assessment?

An innovation culture assessment is a structured analysis of whether your organization’s culture supports or blocks innovation. Unlike a general culture survey, it focuses on the specific behaviors that enable or prevent experimentation, learning from failure, and resource allocation to new ideas. The most useful assessments trace backwards from observable outcomes — how many experiments ran, how failures were handled, what happened when someone challenged the status quo — to the root causes in organizational structure and incentive systems.

Why do most innovation culture surveys produce misleading results?

Culture surveys measure stated values and intentions. They ask people whether they believe their organization supports innovation. People answer based on what they want to believe, not what they observe. The result is consistently optimistic scores that do not match actual behavior. A more reliable approach: look at what actually happened. How many experiments ran last quarter? What happened the last time a project failed? How quickly can a team get budget approval for a small test? Observable outcomes reveal the real culture, and they are consistently lower than survey scores at the same organization.

Why is leadership self-assessment unreliable for innovation culture?

Leadership teams systematically overestimate their organization’s innovation culture because they judge from intent, not impact. They announced the strategy, protected the budget, and said failure is acceptable. What they do not see is what happens three layers down: the approval process that takes four months, the manager who kills ideas to protect his unit’s margin, the incentive system that makes experimentation a career risk for anyone below director level. Cross-functional assessment — including people who are not leadership — consistently produces lower scores and more accurate diagnoses. The gap between leadership scores and cross-functional scores is itself a diagnostic finding.

What are the key dimensions of innovation culture?

The dimensions that matter most are behavioral: how the organization responds when someone proposes an idea that threatens existing revenue; what happens when an experiment fails and who gets blamed; how quickly a team can get approval and resources for a small test; whether rewards and career progression explicitly recognize innovation behavior; and whether there is a functioning bridge between the exploration team and the core business for scaling proven ideas. These behavioral dimensions reveal more about actual culture than any values statement or org chart.

How do you improve innovation culture in a B2B industrial company?

Start by assessing what is actually blocking the culture you want, not what you wish were true. In industrial B2B, the most common root causes are: incentive systems that reward efficiency and punish the uncertainty of experimentation; approval processes designed for the core business that make small experiments impossible to run; and leadership that says the right things but does not allocate protected time and budget. Fix the root cause, not the symptom. Running culture workshops without changing the reward structure produces no lasting change.

How is an innovation culture assessment different from an innovation readiness assessment?

An innovation culture assessment focuses specifically on behaviors: what people do when someone proposes a new idea, how failure is treated, what gets rewarded. An innovation readiness assessment covers culture as one of nine dimensions, alongside leadership support, organizational structure, and innovation practice. If you already know your culture is the problem, a focused culture assessment is the right tool. If you are not sure where your biggest gaps are, a full readiness assessment gives you the complete picture.