> Because that's exactly what his job was for the previous 5 years...
Or possibly senior leadership isn’t happy with the pace of DC buildout over the last 5-years.
Or possibly senior leadership isn’t happy with the pace of DC buildout over the last 5-years.
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.
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.
The real way to increase throughput is to first slow down and smooth out the inevitable bumps by adding adequate slack and building up an inventory of shovel-ready projects as a buffer - and then to start running multiple teams in parallel.
The fact that OP's friend experienced Oracle doing the exact opposite of this lends credence to the idea that they're under pressure and are perhaps panicking.