Very unlikely to be the technical build team at fault for that.

Real estate, legal, permitting, utility connections, construction, plant fit out, testing and certification, security, customs and immigration, and shipping all need to happen first - and every one of those has room for huge amounts of uncertainty and delay, more so if you're doing it internationally.

There aren't many shortcuts that you can take when you're dealing with a complex combination of hardware, property, and law.

Technical staff are easiest to pin the blame on in any given situation. All those other fields require enormously more people skills and political inclination.

If you are in an org like that and there is an effort to pin something on technical people inappropriately the reaction when there's solid push back approaches total hysterical breakdown since it's so unexpected. Even if the tech staff "win" they'll be marked for the rest of their time there.

That matches my experience at google. Getting the land and approvals was the most time, then the basic site prep and building shells and utilities, then basic building fit out, and then finally the actual tech installs.

Well I guess we can assume that this means it's not the reason senior leadership laid them off because senior leaders definitely never scapegoat their underlings or have too little competence to correctly assess why things failed!

yes but sometimes a VP gets fired, new VP comes in, and says "we'll outsource this" or "we'll use this home grown team doing something else" and unfortunately tons of people are caught in a layoff, even if they were good.