Are you a principal eng? The principal engs I’ve known express things in terms of measurable business problems. You have a list of practices with no success criteria.
A lot depends on exactly this, and what types of applications or features the developer org is responsible for building.
IaC could be useful if you're constantly spinning up new standardized apps, but if you're looking to increase deployment velocity it's not going to do much.
I'm also surprised that they're asking HN what should be improved -- I think HN is a random assortment of people working in or interested in tech, many of whom will happily give advice based on no expertise. I hope "ask on HN" is near the very end of their list, and they're just being thorough? ¯\_(ツ)_/¯
This sounds like mistaking five minutes of googling as research. Sorry, for being so snarky. Please look around you and talk to your new customers as other posters already suggested. And talk to the management. Which perceived problems lead to the creation of the position for someone responsible for developer experience?
IaC could be useful if you're constantly spinning up new standardized apps, but if you're looking to increase deployment velocity it's not going to do much.