A building of this scale is a coordination problem wearing a construction problem's clothes. The concrete was never the hard part — keeping dozens of stakeholders, contracts, and approvals moving in the same direction was.
The mandate
Deliver a landmark national convention complex — a signature piece of public infrastructure — on a timeline that left no room for the usual sequential hand-offs. I owned the program: schedule, contracts, and the interface between everyone who could accelerate or block it.
The approach
Compress the timeline by attacking the two things that actually slow megaprojects: decision latency and mis-alignment. That meant running workstreams in parallel rather than in series, and being the single, reliable point of coordination for the PMO, federal, and state stakeholders so decisions didn't stall in the gaps between them.
- Parallelized workstreams with tight interface management between them.
- A single liaison point for the PMO and federal/state agencies — fewer gaps for decisions to fall into.
- Contract structure and sequencing designed to keep the critical path moving.
The result
Concept to execution in 14 months against a two-year norm — a national landmark delivered at roughly 7× the usual pace, with six contracts and $0.45Bn+ under management along the way.
Speed on a program this size isn't about working faster. It's about removing the waiting.
Why it connects
This is the "concrete" node of the career arc — and the origin of a lesson that carried straight into software: parallelize, remove decision latency, own the interfaces. The same instinct now shapes the Automation Intelligence Layer.