Where I work the button request would just have to go through the correct channel. If it wasn't an extremely good, money-saving idea then it would likely be backlogged and we'll get to it when we're already tinkering around with something more high-value. If it wasn't a good idea at all it just won't get approved.

If it's backlogged we'll wait until we have a more substantial project for that application and time allocated to it, then we'll just slip it in.

It'll probably be a single developer that implements it. There's no need for a designer because we don't have any, we're all full-stack developers. We're also our own architects.

Then there's meetings with product owners who are responsible for said application and have the final say as to whether or not it goes in. They'll need to see the button and a demonstration of what it does. They'll also want to know (or decide) who has access to it.

If enough users will need this button, the proper departments will have to be informed so they can create training documentation and send out communications so nobody will be surprised. Everybody will be, because nobody reads that shit. But we have to do it anyway so our bases are covered and some dipshit manager can't use ignorance to claim they need 3 more weeks of prep for their team.

And of course there's testing, etc that must be done. And approval is required for the release, so that can take some time before the sys admins can actually deploy it.

So yeah, the button might only take an hour or two of my time to implement but there's a fuck load of overhead. I've had quite a few projects that were more business bullshit than code. Being an enterprise developer can be a soul draining job.