how? management in most Tech companies are incentivizing them to do just that, so if you bring it up, they'll happily trot over to your manager to complain and then the uncomfortable conversation is you with management about why you're getting in the way of AI uptake by the team.
Or maybe they just didn't have the time (left it to the last minute and ran out of it), and went with the first thing that AI proposed which was said CLI with documentation.
SLO timelines are usually over 7d, 30d etc no? and also often don't work that great for backend services in my experience ... they can't give you the level of reactivity that defining alerts about things you care about give you. I'd argue that moving from that direction upwards to figure out what alerts to aggregate and define SLOs around, rather than the other way around in those cases.
The people who like your new stuff will help you figure out how to fix it and make it good enough so the old system truly becomes obsolete, otherwise the old system will continue to exist and people will continue to use it, so that now, theres 2 options instead of just one.
I used to think the same but with IM, you have to find out the right account and add it (someone might prefer their personal gmail over corporate or whatever) ... but with this, everything is right there. completely replaced any need for im for me.