Change control and service delivery time-frames are two different things. When I left BOA in 2017, you could get most production changes implemented with only two days of lead time from a formal change control perspective. But, requesting a new Virtual IP on a load-balancer could easily take two weeks, just for every layer of bureaucracy to wet its beak. And it was impossible to request something so basic without an online service request, and then follow-up emails because the standard service offerings left all kinds of details undetermined and no structured way to provide the information.
Most production changes require a second set of eyes, sometimes from a particular team, but it's all "just" code review. You put your change in the team's queue, their oncall engineer reviews it the same day, you land the change and it gets executed automatically. Most have implemented namespacing so that changes that only affect your own team's stuff can be approved within your team.
This is all on owned hardware. The difference is that we're a SWE driven company (corporate IT is off in its own world, run in the more traditional way, but they don't touch engineering's production datacenters). Infrastructure teams provide APIs, not JIRA forms.
