Innovation & Growth: what it is and how to measure it

Teams rarely stop innovating because someone tells them to. They stop because the fifth idea in a row went nowhere, because the backlog is full, and because the last experiment that failed was mentioned in a review. Innovation & Growth is the KPI that measures whether a team still has room to try things: a new idea, a different method, another answer when the situation changes.

What Innovation & Growth means

In PEAKTEAMS, Innovation & Growth is the team's openness to new ideas, its creative problem-solving, its adaptability to change and its willingness to experiment. Four things, one score. Together they describe a team that treats its own way of working as something to improve rather than something to defend.

It is worth being clear about what the KPI is not. It is not an R&D budget, a patent count or a product roadmap. A finance team that rebuilds its month-end close every quarter can score high. A product team that ships features from a fixed list and never questions the list can score low. The KPI is about behaviour inside the team, not about the kind of work the team does.

Why it matters for performance

Three findings from the team-effectiveness literature explain why this is a Process KPI rather than a nice-to-have.

• Learning behaviour predicts performance. Edmondson (1999) studied 51 work teams and found that teams which sought feedback, experimented and discussed their errors performed better, and that this learning behaviour depended on psychological safety. Experimentation is one of the behaviours she measured directly.
• Teams run in cycles, and the cycle has to adapt. Ilgen, Hollenbeck, Johnson and Jundt (2005) replaced the linear input-process-output picture with a cyclical one in which today's outputs become tomorrow's inputs. A team that does not adapt between cycles carries every mismatch forward.
• Creating and implementing are different jobs. West (2002) separated the generation of ideas from their implementation and argued that pressure pushes a team towards implementing what it already has and away from creating anything new. Teams under constant load therefore drift towards low scores on this KPI without anyone deciding to.

What high and low look like

The score shows up in small moments more than in strategy sessions. The same four situations play out differently in a team that scores high and one that scores low.

Notice that the low-scoring column is not a lazy team. It may be a very busy one. The defining feature is that nothing new gets a trial, so nothing new gets learned.

How PEAKTEAMS measures it

Innovation & Growth sits in the Process pillar of the Team P&L, alongside the other nine KPIs that describe how the team works together. The Snapshot survey asks two statements, each answered on a five-point agreement scale.

The Deep-Dive survey adds thirteen items: twelve positively phrased statements about curiosity, discussing new ideas, trying new tools and methods and talking openly about failures, plus one reverse-scored statement, "New ideas are usually met with reasons why they will not work." The second Snapshot item and all Deep-Dive items also feed the derived Adaptability score, which is why the two move together in most reports.

The KPI score is the mean of its items across all respondents, and the Consensus Matrix plots each of those items against how much the team agrees on it: an item with a high score and high agreement is a strength, a high score with low agreement means some members experience a team that experiments and others do not. Results appear only once at least five team members have answered; the owner's own answer does not count.

How to improve Innovation & Growth

1. Reserve a fixed slice of capacity for experiments, even a small one, because ideas without time stay ideas and pressure crowds out creation before anyone notices.
2. Make experiments small and time-boxed, with a stated success criterion, because a cheap trial lowers the cost of being wrong and makes the next trial easier to propose.
3. Review failures for what was learned, not who was wrong, because Edmondson's finding only works in one direction: discussing errors improves performance when it is safe to do so.
4. Rotate who brings one outside idea to the team meeting, because curiosity about trends and methods is a habit, and habits need a slot in the calendar.
5. Change one process on purpose each quarter, because a team that only adapts under pressure never practises adapting when it has the room to do it well.
6. Re-measure after a quarter, because the Deep-Dive items are specific enough to show which of the four behaviours moved and which did not.

Related KPIs

Innovation & Growth rarely moves alone. Trust & Safety is the precondition: nobody proposes an experiment they expect to be blamed for. Feedback & Development is the mechanism by which an experiment becomes a lesson. And Delivery Methodology is where adaptation shows up in practice, because a way of working that is never improved is the clearest sign of a team that has stopped trying things.