In July, Michigan City's mayor said no to an $800 million data center. She had clear reasons: limited job creation, no assurances of community reinvestment, no binding commitments that would benefit residents.
"Any major project of this magnitude must bring tangible value and benefits to Michigan City residents." —Mayor Angie Nelson Deuitch
By November, construction was underway.
The mechanics of how you get from a mayor saying "we have no plans to pursue this" to bulldozers breaking ground four months later. I'm trying to figure out what it means when your criteria for what benefits your community are clear, reasonable, publicly stated—and still don't matter.
How It Happened
| Timeline | Event |
|---|---|
| June | Indiana's Economic Development Commission approved sales tax exemptions—before the mayor's rejection |
| July | Mayor Deuitch issued her statement rejecting the project |
| August | City council moved forward with resolutions for economic revitalization and tax abatements, despite mayoral opposition |
| October | Construction advanced far enough for union protests |
| November | Full construction underway |
Michigan City is a town of about 31,000 people, median household income around $53,000. The city has been working on revitalization for years. It needs development. Everyone knows that.
The mayor had articulated specific criteria for what kind of development would actually help: substantial job creation, community reinvestment, lasting benefits for residents. The data center proposal didn't meet those criteria. She said no.
And then it happened anyway.
Your leverage can be real—abundant fresh water, climate positioning, the power to set terms—and still not work the way you thought it would.
I genuinely don't know whether the data center is good or bad for Michigan City. But the discovery itself: your leverage can be real, you're positioned on Lake Michigan, you have abundant fresh water, you face less climate risk than much of the country, and it still doesn't work the way you thought it would.
The mayor's rejection was based on legitimate concerns. Data centers typically employ between 10 and 100 people directly. They generate tax revenue, but often require infrastructure upgrades that strain municipal capacity. Whether that tradeoff benefits a specific community depends entirely on the details: how many jobs, what kind of tax structure, what infrastructure commitments, what timeline.
Mayor Deuitch was asking for those details to add up to something that would actually help Michigan City residents. When they didn't, she said no.
The project proceeded because state-level incentives and private development rights created a pathway that didn't require local approval in the way she'd assumed. The city council moved forward despite her position. The mechanisms of economic development—tax abatements, revitalization zones, state tax exemptions—operated on a logic that didn't need the mayor's yes.
By November, the conflict had shifted to different ground entirely. It wasn't about whether the data center would happen. It was about who would build it.
Local 150, representing operating engineers, was protesting the use of out-of-state and non-union contractors. Ashley Williams, executive director of Just Transition Northwest Indiana, told reporters: "Bad-faith development has neighbors looking over their shoulders."
State Representative Carolyn Regnitz said she'd support the project if developers used local workers: "It's mind-boggling to even imagine that we're seeing Georgia license plates, we're seeing Wisconsin license plates, and we're seeing Illinois license plates."
Even the opposition had shifted to terms the city hadn't chosen. Whether this development served Michigan City's interests—that question had already been answered, or bypassed, or rendered irrelevant. Now: whether Michigan City workers would at least get the construction jobs.
The mayor's response: "We're not anti-union. We're pro-Michigan City, and we're pro-Northwest Indiana." But also: the city isn't involved with the construction. It's a private project.
The city rejected the project. The city approved resolutions enabling the project. The city isn't involved with the construction. All of these things are apparently true simultaneously.
Michigan City didn't get to make a choice in the way they thought they would. The mayor's criteria were reasonable. Her rejection was based on protecting residents' interests. But the architecture of economic development in 2025 means that local rejection can be overridden by state incentives and private property rights, especially when a community needs development badly enough that its own council will move forward despite mayoral opposition.
Michigan City is learning something about being a climate refuge that the positioning doesn't mention: having the resources everyone wants doesn't mean you control how those resources get used. Having clear criteria for what benefits your community doesn't mean those criteria will be honored. Saying no doesn't mean no if the economic and political structures are aligned differently than you understood.
The data center is being built. In five years this might look like development that worked out despite the messy process. Tax revenue might fund the infrastructure Michigan City needs. Indirect jobs might matter.
Or Michigan City will look back and realize that the moment they lost control of the decision was the moment they discovered they'd never really had it. Being positioned as a climate refuge with abundant resources just makes you a place where development happens to you, not with you.
They learned: the leverage they thought they had—abundant water, climate positioning, the power to set terms—turned out to be leverage someone else could use. Their resources made them valuable. Being valuable made them a target. Being a target meant discovering that local control was more theoretical than real.
The construction continues. The protests continue. The mayor says the city isn't involved. And Michigan City knows something now about what its positioning as a climate refuge actually means.