Why Innovation Teams Have To Be Measured Differently and How To Do It

About the Episode

In this episode, Elijah Eilert is talking to Tristan Kromer about measuring innovation teams.

Fundamentally, teams should be measured against something they can control. What does it mean for innovators who are largely in pursuit of a new business model? How exactly can it be put into practice? What do specific metrics look like? Discover all of that in this episode.

Please let us know what measures you would add and why in the comments!

Innovation Team Metrics Covered in this Episode

  • Experimentation Velocity / % of teams that run experiments 
  • Insight Velocity / % of experiments that generate insights
  • % of falsified hypothesis (validated/invalidated experiments ratio) 
  • Retrospectives / % of weeks teams have run retrospectives in the last month 
  • Qualitative data – team sprint demo (weekly, biweekly)

Topics and Insights 

  • (01:40) The problem – why do we need to measure innovation teams differently.
  • (05:00) All teams should be measured against something they can control.
  • (06:00) For innovation teams, even product related “lead indicators” can often not be applied, as those are not known in the early stages of the innovation process.
  • (10:00) If Zombies were chasing Tristan, his attempt to escape will likely be over after running 5 blocks.
  • (11:00) Nobody knows what product team will win. What we do know, is that teams that experiment and learn faster, have a much better chance to achieve Product-Market-Fit. Tom Eisenmann from Harvard University just released data to back this up.
  • (14:30) The solution – how to fairly and effectively measure innovation team.
  • (15:00) It is important to separate the measurement of the product from the measurement of the team.
  • (15:40) Experimentation Velocity and Insight Velocity.
  • (19:00) Accounting for experiment and research cost.
  • (22:20) Elijah is having problems formulating a proper sentence and Yoga with Adriene comes up.
  • (23:30) The difference between an evaluative experiment and generative research.
  • (29:00) Should the evaluative experiment to generative research ratio be measured?
  • (31:00) Product teams should never stop running interviews.
  • (31:30) Teams are likely to be more successful when they use a greater variety of experiments. A call for more academic research into this topic.
  • (33:15) We need better tools to record experiments and insights from innovation teams.
  • (36:50) Tools for recording experiments.
  • (41:30) Going deeper into measuring Experimentation and Insight Velocity.
  • (46:20) Discussing the percentage of falsified hypotheses as another team measure.
  • (52:00) Measure but don’t count.
  • (52:50) Teams also need to be measured against lead product/project indicators but each team needs to find out their own indicators or levers for success.
  • (55:00) Retrospectives, another important team measure.
  • (56:00) The importance of qualitative data like sprint demos when measuring innovation teams.

About the Guest

Tristan Kromer helps product teams go fast.

As a Silicon Valley-based lean startup coach and founder of Kromatic, Tristan works with innovation teams to run at least one experiment/research per week to improve their product and business model.

For larger companies and governments, Tristan and his team work with corporate teams and leaders to build innovation ecosystems.

Tristan designed lean startup programs such as the Build or Die Bootcamp for TechBA (Mexico) and the Innovation Partnership Program (Vietnam-Finland) in addition to being part of Luxr, whose Core Curriculum has been used by 13 accelerators internationally, including Singularity University, 500 Startups, & The United States Innovation Fellows.

He has worked with companies ranging from early stage startups with zero revenue to established businesses with >$10M USD revenue (Kiva, Cancer Research U.K., TES) to enterprise companies with >$1B USD revenue (Unilever, Swisscom, Salesforce, Fujitsu, LinkedIn).

Tristan regularly speaks, appears on panels, and gives workshops internationally with organizations such as the Stanford Center for Entrepreneurial Studies & D-school, Dubai Chamber of Commerce, General Electric (GE), and more.

Originally from New York City, he has lived in Germany, Switzerland, Taiwan, and Vietnam, and currently resides in San Francisco, USA. With his remaining hours, Tristan volunteers his time with early stage startups.

Connect with Tristan

Website / LinkedIn / Twitter

Show Transcript

Sign up for the latest on Innovation Accounting, Lean Startup, Workshops and Innovation Ecosystem Design.


Innovation courses and workshops - a pirate and an astronaut are fixing a rocket.

Team Building & Accountability

  • Building Teams 
  • Team Accountability 
  • Creating Effective Exercises 

It takes effort to build and maintain a great team, especially those faced with a lot of uncertainty. Learn the key ingredients to actively create an effective cross functional team that truly collaborates. In an environment of fast pace and constant change, accountability plays an important role in keeping the team together and ensuring that things get done. This module will enable your team to agree on an accountability framework for innovators they can adopt and own. Lastly, participants will learn how to effectively pass on their knowledge on a specific topic to their team.

learn more

Sign up for the latest on Innovation Accounting, Lean Startup, Workshops and Innovation Ecosystem Design.

One Comment

  1. […] Teams  […]

Leave A Comment