Ask HN: How do you measure a Developer Experience / Engineering Platform team?

I'm trying to set up OKRs for my team, which has the mission of making our hundreds of software engineers work better and faster.

To achive this, we develop internal tools, maintain web services for engineers, hold workshops, advise people on software architecture, and so on.

Sadly, any metric we'd examine, such as 'duration of CI pipelines that end with a production deploy' ends up being subpar. This one specifically has too many external factors influencing it, covers less than 10% of all the stuff we work on, and the metric just has too much random variance anyway.

How are other similar teams setting objectives, key results, KPIs, or any other measure of success?