ROI and being able to measure is probably one of t...
# general
l
ROI and being able to measure is probably one of the biggest questions in Platform Engineering. Even understanding WHAT to measure can often be up in the cards
s
There is also this one from @Max Griffiths - @Luca Galante @Mattia Minotti You can go the other direction in measuring ROI

https://youtu.be/K3q7oB6Ki4U

m
A big issue is certainly the need of quantitative measures BEFORE a platform engineering initiative, while you probably understand the need of them WHILE you are adopting the platform and then you are without good data to compare.
Another problem, in my experience, is that kpi like devex are not easily measurable. You can try with surveys, but it's not a measure that could be directly connected to ROI.
I think that the key, unresolved in my context, is a way to reliably measure the improvement in the SDLC and in the feature delivery flow. There's a lot to do there, because I know of no established methodologies. Am I wrong?
m
Whilst we wait for Manuel to come back online I would just like to say that before (baseline) and current metrics are only required to justify what you’ve spent so far on the initiative. If you’re already in the middle of a platform engineering initiative, and without those BEFORE metrics, it might be good enough to forecast what a future/continued investment could achieve. That requires some canvassing of your dev org to understand the problem space or opportunity for improvement. If you can start to assign lost developer time to certain sub optimal (wasteful) processes eg ticket processing, handovers, discovering information, manual processes, wait time etc, then you could be on your way to connecting ROI to platform eng.