There’s usually an entire approval process every software request goes through. First it needs a legit business use case that one of our current approved pieces of software cannot do. For example, they may not let you install Chrome because they officially support Edge since it’s heavily tied into the Microsoft ecosystem, and therefore don’t want to deal with managing Chrome in the environment.

If it’s a new piece of software, then it goes through a security review through the security team. Verify there’s nothing in it that oversteps it’s bounds, has no known security vulnerabilities, comes from a respectfully company that hasn’t done things like tax evasion, things like that. After security approves it then legal has to review the EULA or any licensing agreements. Company lawyers don’t really like doing this because it can be time consuming and low on their priority list.

After it’s approved, including any potential costs that the responsible parties accept, the operations team has a go at it. They don’t want to have to manually install it and maintain it on your computer, so they package it up and test it in a testing environment. After verifying the package can be deployed, configured, and kept up to date, or even completely removed remotely, then it gets put in to the production deployment, and finally sent to install on your machine.

Keep in mind that these employees are also doing all their other daily tasks. They’re not sitting there churning out app deployment packages. Maybe they only meet once a week for 30 minutes to approve software, and maybe they ran out of time before your request made the agenda. Maybe the security team held up on it because they had to deal with an emergency.

This is why some big companies can take a lot longer to get software approvals compared to places with one or two techs in the IT department.