“Most of those metrics are focusing around development related activities and almost none of the metrics around collaboration. And the challenge is that developers spend maybe 30, 40, 50% of their time in collaboration and communication. But with those dashboards, we don't really understand how this part is impacting their work lives.”

…the compass really helps you to navigate this fragmented landscape by exploring metrics, by comparing or benchmarking against other companies that are maybe similar to you, and also by allowing you to receive an actionable report at the end to sort of know where to get started and what to do next.

…many different metrics are sort of mapped together to different frameworks. And it's like, it's a lot of fun to go and dive into. And so as you were creating it, as you were diving into all of these metrics in use across the industry, what surprised you most about what companies choose to measure?

I think collaboration is part of the very definition of developer productivity. It is one of the dimensions of space and has been often the hardest to understand because collaboration is incredibly important to delivering innovation, but it can also be an incredibly large source of toil. And I'm…

Not that I've seen, to be honest. And there are only very few collaboration metrics that we actually have. That's the opportunity, I guess. Exactly. That's an opportunity for researchers, for DX and many others to contribute. I think that some good measures would evolve around finding a balance…

Which is like a huge shout out to the idea of measuring sort of meeting like clustering. And do you have sufficiently large gaps between meetings to do deep focused work? Found that that can be substantially more predictive of how much work devs get done than just like the total number of meetings.…