You Can't Automate Chaos - Hannah Garrett on Structure, AI, and the Data Center Boom

About half of all US data centers scheduled to open this year are delayed or canceled. Hannah Garrett isn't surprised. She's been watching tech and construction try to figure each other out for a decade, and says the real problem isn't energy, equipment, or even AI. It's that nobody fixed their operational structure before the boom hit.

Hannah Garrett has 10 years across both sides of data center delivery - five on the GC side at Hensel Phelps and Clark, and five more on the owner side at Meta, Aligned, Microsoft, and Oracle. She's a recognized voice in the industry, known for her LinkedIn post "You Can't Automate Chaos", and for saying out loud what most people in the room are thinking but won't say.  https://www.linkedin.com/in/hannahegarrett/

What You'll Learn

1. The Symptom-Root Cause Gap

Delays, burnout, and cost overruns in data center delivery are symptoms - not the disease. Hannah makes the case that most operational pain points trace directly back to systems and structures that were never built for the scale being demanded of them. Until leadership treats the root cause, adding technology only makes the chaos faster.

2. The Amplification Principle

AI doesn't fix broken systems. It accelerates them. Hannah's framework: understand your operations end-to-end, map out the full complexity across 40-plus stakeholders, establish structure and only then let AI scale what's already working. Applied too early, it amplifies every gap you haven't dealt with yet.

3. The Simplicity Paradox

The smartest people in complex industries tend to build the most complex tools, but complexity degrades data quality, because people stop updating systems they find painful to use. Hannah argues that simpler, centralized platforms (she points to Asana and Monday as examples) produce far better information than the highly engineered tools leadership tends to prefer.

4. The Change Management Translation Problem

"Change order" is a career-defining term on a job site. In software, it barely registers. Hannah breaks down the language and cultural gap between tech and construction teams and why the absence of a shared vocabulary means billion-dollar decisions are routinely being made in Slack channels, with no one raising the downstream impacts until it's too late.

Timestamps

[00:00:00] Introduction: Hannah's 10 years spanning GC and owner sides of data centers

[00:02:00] What the boom felt like: "a meteor overnight" — and why the industry wasn't ready

[00:04:00] What five years on the GC side taught her about change management

[00:06:00] Tech vs. Construction: two different organisms forced to work together

[00:09:00] Why projects are delayed: the leadership-to-delivery disconnect

[00:15:00] Ford's automation lesson: why structure has to come before AI

[00:20:00] PM as "the domino for AI": challenging Jack Dorsey's hierarchy quote

[00:22:00] "Chaos is a report card": what happens when you scale without systems

[00:29:00] The burned-out PM problem and the doctor/EHR parallel

[00:33:00] Dashboard overload: why qualitative metrics often beat KPI tracking

[00:37:00] How Hannah takes over a portfolio: her framework for finding the gaps

[00:43:00] The case for a central source of truth (and why no one has built it yet)

[00:49:00] Final challenge to leadership: bold plans must look nothing like the last 10 years

Episode Resources

• Connect with Hannah Garrett on LinkedIn https://www.linkedin.com/in/hannahegarrett/ 
• Referenced: Ford's quality automation and rehiring case
• Referenced: Jack Dorsey — "Hierarchy is an obsolete information routing protocol"

If this conversation hit close to home, subscribe to the Major Project Podcast wherever you listen — and leave a review. Every rating helps more project leaders find conversations like this one.