Hey all, I've been working recently on platform KPIs and metrics, and the team and I have codified our thoughts into the first edition of this scorecard (taking inspiration from DORA et al). I would love to know your thoughts! https://www.syntasso.io/post/the-internal-platform-scorecard-speed-safety-efficiency-and-scalability

thanks for sharing, some quick thoughts as I scan this… • many people, myself included will likely trip up on Efficiency as it’s usually associated with cost discipline rigor. as currently written, the efficiency rubric reads like a subset, or a nuance, of speed. i would also consider how much perceived value the current definition of efficiency has for your customers in a business or a technical sense as the wall-clock savings may not be as material • i do like the concept of safety, policy may be a trigger word in some engineering cultures. i know many platform customers (product teams) may see that as a turn-off. guardrail may be a better fit in some environments but it’s also prone to the same challenges as policy • scalability comes across as onboarding time. i am not sure if that’s the intent behind it. maybe it needs better framing? • i would probably try to align the “one metric that matters” with a guardrail metric that tells you if the current measurement is on or off track. i’d also consider explicitly enumerating how each of these metrics maps to internal technical and business goals / outcomes so teams can clearly see the sometimes hidden, or implicit, connection in how they help influence and impact the business i hope this helps

This is handy, and it's going to help me shape an upcoming devosdays talk I'm building. Thank you.

Loving it, really like this and the shape is taking, ill suggest: • adding an attribute for: 'Usability or Adoption Experience', so how easily can customers of/consumers identify, understand, use! without needing to ask. • For Enterprises, ill add something on Safety- aligned to Enterprise security and compliance guardrails or controls. (this one is tricky because of words preferences) but thats my advise. • Also i kind of feel there should be something about relevance Happy to collab on this!

Thanks, @Jordan Chernev! These are all great points. Scalability was intended to capture "time to contribute", and I would be keen to dive into your thoughts on this. The guardrail suggestion is very interesting!

yes, relevance came to mind (im not precious on the word in use) but, if a platform is truly applying product mindset AND other product inherited principles such as CSI, value add, improvements etc. There should be a score related to the services on offer and how they fit, churn, lifecycle, deprecation comes to mind. I am thinking about the metrics to go with it... may expand/inspired by your table (attributes specifically) to incorporate to my upcoming talk at DevOps day, actually... need to think this through. 🙂

This is awesome! Great job! I need to go digest this some more...... 🍺