This message was deleted.

Hey Bartek, @Fernando Villalba did this amazing graphic on Linkedin that I think could help https://www.linkedin.com/feed/update/urn:li:activity:7056886814103478272?updateEntity[…]pdate%3A%28V2%2Curn%3Ali%3Aactivity%3A7056886814103478272%29

I’m trying to come up with a model to present how the internal platform for developers bring value to the business in terms of money, minimising costs of downtime, security, etc. Also indicate what’s the break-even point.

@Bartek Antoniak - I've gone through a similar exercise with my teams (did not result in a formal model) and it's pretty straight-forward once you understand and have measure for your current state cost drivers (we also included some anecdotal data points from platform customers as well as time tracking data to round out the story). <<< This was the hardest part for us. For us, then it was a simple extrapolation based on the projected efficiencies gained by platform adoption. Our output was a rough excel workbook...Not pretty, but allowed us to get things down on paper.

Thanks! This is exactly, what we are currently working on. Assuming the following state cost drivers: • One-off savings - set up the infrastructure, technology integration, security audit, etc. • Ongoing savings - maintenance and lifecycle management of the infrastructure • Engineering costs - costs of the engineering headcount • Operations costs - costs of the ops/SRE headcount However, this doesn’t show the full picture and do not include value opportunities that platform brings that are hard to calculate, namely lower leadtime to production, high availability, and security.

The other challenge is that it's tough to put a $ figure on 'Developer Happiness' other than hiring/retention costs, which are less of an issue this year than past years.

not exactly what you're asking for, but i wrote this -- and i have another post soon about the business case for platform https://www.swarmia.com/blog/making-the-case-developer-experience/

Thanks @Giulia Guizzardi for sharing. I’m wondering how can we “Measure developer churn” Any idea?

@Marcos Lobo count the developers who have left the company due to a frustrating developer experience. HR may be able to help as they usually have exit interviews

There is also this great Whitepaper around DevEx - which roughly can translate to developer happiness that is significantly improved by DevPlatforms: https://queue.acm.org/detail.cfm?id=3595878 You can definitely find a good influence of a Dev Platform in every area of the suggested metrics there.

Managing up is extremely important. I used to run monthly sessions with our VP of Eng, CTO and Director of Product where we would discuss platform outcomes like adoption rate of platform capabilities, survey results across engineering, our strategy and bets that we were working towards as well as stuff like team health. We typically used to present 3-5 slides that were more about outcomes or any specific asks we needed from those senior stakeholders