O'Hare's $8.8 billion build runs on approval to disrupt

The $8.8 billion ORD Next program is adding two concourses and doubling the size of a new terminal at O'Hare International Airport, which cannot close, the busiest in the world by takeoffs and landings, and the crews have to finish it while minimizing disruption to passengers moving through the same ground. The source frames the tension exactly that way: the finished project will streamline traffic through the hub, while every phase of construction works against that outcome in the interim.

The person carrying that tension is Zach Baughman, chief development officer and managing deputy commissioner of the Chicago Department of Aviation, and his qualification for the job is the one he does not have: he is a lawyer rather than a contractor, a gap he argues is advantageous. His test is translation: if a contractor or one of his own people cannot explain a decision to someone with no construction background, he says, that person probably does not understand the decision well enough themselves. Because nobody expects him to know the engineering calls in advance, he questions them freely and, by his own account, extracts more information that way.

He extends the same license to the room, asking in meetings for the opposing case—tell me why this is wrong, what else we should be thinking through—and treats those objections as the route to a consensus a large group will hold to. That is an argument about how decisions get made, and the interview does not test it; what it does show is where a delivery executive on a program this size spends his attention: at the point where work has to be explained, long before it is designed.

Interviews with the people running large public builds are common enough, and they usually produce a schedule and a number. This one yields the middle of the job, the part where the development chief's value is measured in how fast a decision can be explained to people who do not work for him. For ORD Next, the years between groundbreaking and opening are one long negotiation over access to a working airfield, and the published account is unusually specific about who sits on the other side of that table.

The passage that matters more for anyone pricing infrastructure comes when Baughman describes what the job involves day to day: extensive coordination with the airport's airline partners, the Transportation Security Administration and the Federal Aviation Administration whenever construction affects security lanes or the FAA's movement area — the layer where a live-airport program is won or lost. Steel and concrete are bought in competitive markets on sequences contractors have executed many times before, while permission to shut a security checkpoint for a night shift or stage equipment inside federally controlled airfield space is granted by parties with their own operating mandates and no stake in the construction calendar.

The scarce commodity at O'Hare is not construction capacity but approval to disrupt, and the critical path — the sequence that decides when new concourses open — likely runs through the carriers, the TSA and the FAA rather than through the trades. Consent is the product in data center siting, where permitting and local opposition decide what gets built regardless of the capital available, and the same logic lands here in a different asset class, with three consent-holders who each answer to a live operation. Read that way, the non-builder in the development chair is less a management curiosity than a control: a development chief whose one repeatable skill is forcing plain-language accounts of the work is also the earliest point at which a scope dispute surfaces, back when a change order is still cheap.

The interview is a delivery conversation rather than a financing one, and that limits what can be concluded about the money: it does not say how the $8.8 billion is funded, who absorbs an overrun, or how far the program extends beyond the note that crews are just over a year into construction on the new Concourse, where the published excerpt ends. That gap separates ORD Next from the assets this desk usually prices. Airport capital money can be tied to a passenger-volume entitlement, as our reporting on Washington's $1.1 billion airport round set out, which makes throughput during construction a revenue question and not only a service one; where private capital does take an infrastructure asset, as the Georgia toll-lane leases showed, the concession fee is really a price on decades of revenue. As presented, O'Hare's program is the agency-delivery version: the department keeps the asset and carries the delivery risk itself.

That leaves the next phase as the test: as work moves into the security lanes and the movement area the FAA controls, the questions are how many disruption windows the program needs and whether the airlines, the TSA and the FAA clear them on the first ask. Candor inside a project office costs nothing, but a carrier's operations desk approving a closed checkpoint at the peak of a bank is a different negotiation entirely — and it is the one the translation habit was built for. If the closures clear cleanly, the non-builder was the right instrument for this job; if they bog down, no amount of internal philosophy will move an opening date.