This message was deleted.

Personally I don’t think thats the right framing. Its a short vs long term projection. Platform needs to be able to understand the business need and design a financial model for either revenue or COGS reduction. If the company cares about revenue then it has to fit into that story. The problem you’re going to run into is if the company isn’t really a growth stage company but is trying to get into growth (again) then reduction of COGS isn’t super important short term bc its about growth. I’d push leadership right now to explain if you’re chasing efficiencies or growth - macro economic climate seems to indicate caring about efficiencies(?). YMMV though depending the market segment etc

I work on related insurance/home loan/ long lived products in this business. My focus is just the platforms that keep using the latest. There is a humanitec webinar on it if it is interesting

Thanks, Andrew!

I'll definitely watch as it's highly relevant to what we're doing, but it doesn't seem to address the question. Thank you for the link!

Happy to connect if you’re interested. My employer is in fintech and we have a 60 person dev team my PE org serves!

The most compelling arguments are the ones that convincingly supply dollar values for platform initiatives. There’s material on the impact on organizational performance in chapter 2 of Accelerate and in the McKinsey report on Developer Velocity. I learned a long time ago that getting the business side of the house to believe cost reduction claims requires careful attention to the counterfactual in advance.

@Ryan Grimard I find Jean-Michel Lemieux’s “3 buckets” mental model helpful - essentially he posits that eng investments generally fall into one of 3 buckets - experiments, features or platforms. He recommends targeting a certain investment ratio among the 3 buckets (10%, 40%, 50%, respectively) to maximize the flow of value and feedback among assets in each of the 3 categories. He offers more commentary in this podcast at `25:41` (+ transcript). ^^ I think an implication of embracing this 3-bucket model - regardless of your target ratio - is that platforms don't go toe-to-toe with features for $$$. Maybe the org’s ratio is way off, but negotiating the ratio gives platforms a fighting chance vs features.

@Cruise Hall Not only can anything be measured*, but “appraisal” as you describe it is a measurement. *That anything can be measured is a literal consequence of the definition of measurement, “[a] set of operations having the object of determining a value of a quantity”, which means that guesstimating based on prior experience qualifies. Importantly, and perhaps surprisingly, anything can be practically and usefully measured. See Doug Hubbard’s book How to Measure Anything.