5 Things Mega Project Teams Should Know Before They Select and Implement Technology

There is a pattern that plays out on nearly every large capital program that brings in new technology. Leadership identifies a problem - cost overruns, schedule slippage, fragmented data, too many claims - and the instinct is to go find a system that fixes it. But too often, teams move straight to the solution before they have fully diagnosed the problem. They buy technology for the symptom they can see, not the underlying issue driving it. And that is where things go wrong. The result is usually a mismatch: the organization invests time, money, and change management effort into a platform that looks promising on paper but does not actually solve the real operational breakdown. The pain is not just wasted spend, it is that the program still carries the same core risk, just with a new tool layered on top of it. I recently spoke with three practitioners who have lived this challenge from the inside: Cari Stieglitz, President of Kvolve, who has worked on programs ranging from a 95-building campus in Dubai to Sound Transit's enterprise systems overhaul; Mike Marcel, President of the Integrated Solutions Group at K2, whose work with WMATA became a case study in what it takes to bring order to 25 years of organizational chaos; and Rich Miesemer of Parsons, currently serving as PMIS Director on the Hudson Tunnel Project, a $16 billion program connecting New Jersey and New York that carries Amtrak, NJ Transit, and effectively the entire Northeast Corridor on its shoulders.