Productboard adoption metrics and key results


Userlevel 1
Badge +1

I am trying to establish “healthy” Productboard adoption metrics for the company I am working for as a consultant (CDK Global - software development for the automotive industry), and I was wondering what others have implemented for their organizations. I am trying to stay away from “vanity” metrics, like the % increase in the number of makers, and use more impactful metrics, like % increase in the number of active makers. Please let me know your thoughts.

When would you say that an organization has “fully” adopted Productboard? Also, what would be the Key Results by which you could assess the adoption process? (just an example: if in average, 90% of all the Productboard makers at company X are active, then we have full adoption). This is the type of information I am looking for.

Any advice is highly appreciated!

Thank you!

Cristian Dumitrescu


3 replies

Badge +1

@dumetre Great question! Curious, what have you learned/how has this project been going since you posted this earlier in the month? 

Badge

@dumetre How are you currently defining Adoption?

Userlevel 4
Badge +2

Super interesting question @dumetre! It’s always tricky with metrics and how you define them. I think what important to remember is what is the key reason you would like users in the platform, then you’ll be able to work your metrics out from there. If it’s keeping up to date with product plans” then maybe roadmap views or interaction would be handy. If it’s contributing to product problem validation maybe it’s the amount of feedback contributed.

Think about the outcome or the ‘job’ they are trying to get done with using productboard and then you will have a clearer idea of the measure of success.

Reply