[http-teapot]

> How does the metrics shown in the action help you?

We've mostly looked at "Total reviews" and "Total comments". When I put the action in place, I told the team that the goal was for everyone to contribute to the process.

I was expecting to look at the stats, make some observations and action items and bring it up during our 1:1. I didn't even need to do that. Everybody took it to heart and contributed in different ways. Our most junior engineer ended up contributing in the most meaningful way and set a new standard for how far we take testing.

At this point, it's pretty clear that I see this more as a tool for individuals. For me, I am a bit constrained on time, I can check the table, notice a variation in the number (the action doesn't show variation so I do it out of memory) and decide to take an hour to explore the contributions. The goal being: how can I help them grow?

As an IC, I perhaps could project myself a bit based on my experience, if I am a junior engineer then I can see who comments the most, explore their comments and learn from them. As a tech lead, I'd want to make sure the tone of the comments are constructive (ie. definitely not toxic).

[jameslao]

That's actually a use case I've thought about. When review time came around, one of my past managers would compile statistics on everyone's reviews to see how much they've been participating.

Another feature I've thought about is "show me all of person X's reviews and comments across all repos". That would have been super useful when I was on promo panels to go through and see if a promo candidate's review comments were useful, constructive, kind, etc.

Thanks for the feedback. I really appreciate it!

[http-teapot]

Exactly! You bring a great point with promo panels where the difference between the amount of time put into building a promo package and the amount of time the panel spend on it can be considerable (my experience at Twitter).

I think when it comes to per-seat pricing, it's good to remember that engineers don't put the credit card in. The person with the credit card will want to know ROI before investing. The engineers will want to try out first as a group and if their experience is positive (some of it might be subjective) then they'll need to build a case for why the company should pay for your product and that's where analytics can be leveraged for sales.