Picture a hectic Monday morning and the legal department calls to say that the acquisition closed over the weekend, three months ahead of schedule. Fifty people from the acquired company need working desktops, with the right applications and the right access, by Friday. Nobody asked IT whether Friday was realistic.
I asked Michael, who has spent years standing up these environments under exactly that kind of deadline, what breaks when a team tries to move that fast. His answer was blunt: "IT teams run out of time on image validation, license provisioning, and identity integration, the stuff that never shows up on the project plan until later."
What those fifty people need in order to log in and start working has nothing to do with company size, and everything to do with whether someone already built the capability to make it happen fast.
A Friday deadline for fifty desktops rarely comes from inside IT. It comes from somewhere else in the business, and by the time it reaches IT, the date is already fixed.
An acquisition is one trigger. A new location opening is another. One retail operator needed a new environment running in ten days, because that's how fast a store opening moves, whether IT is ready or not.
A hiring surge creates the same problem without any external deadline. Growth simply outpaces how fast IT can normally provision new desktops.
Whatever the trigger, day one looks the same. Those fifty people need a desktop that is already secure and already compliant, not one that gets configured correctly sometime during onboarding week. For a BPO handling a client's data, or a retail location taking its first card payment, that isn't a nice-to-have. It's the reason the business can legally open at all.
Nobody has time to design something custom either. A team spending a week validating a bespoke build no longer has a Friday deadline. It has a Friday-plus-three-weeks deadline, and someone still has to explain the gap to whoever set the original date. A standardized environment, already built, tested, and proven, holds up under a deadline like this. One being designed for the first time under pressure does not.
When Friday arrives, the real question isn't whether the team is big enough. It's whether anyone in the building has done this exact kind of setup before, under this kind of deadline, more than once.
Company size doesn't answer that question. A thousand-person company that has never had to stand up fifty desktops on a deadline is in the same position as a two-hundred-person company that hasn't, because the missing thing isn't headcount. It's a specific, narrow kind of experience: knowing which credentials, which images, and which licenses need to be ready before day one, and having done it enough times that nothing on the list gets discovered late.
Building that experience in-house, just to have it ready for the next time a deadline like this shows up without warning, is its own decision. For a lot of teams, it's the wrong one, since these deadlines don't come often enough on their own to justify keeping that expertise on staff year-round.