You’re out of free articles.
This Halloween, get 20% off using code ADVANCED
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
Sign In or Create an Account.
By continuing, you agree to the Terms of Service and acknowledge our Privacy Policy
Welcome to Heatmap
Thank you for registering with Heatmap. Climate change is one of the greatest challenges of our lives, a force reshaping our economy, our politics, and our culture. We hope to be your trusted, friendly, and insightful guide to that transformation. Please enjoy your free articles. You can check your profile here .
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Subscribe to get unlimited Access
Hey, you are out of free articles but you are only a few clicks away from full access. Subscribe below and take advantage of our introductory offer.
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Create Your Account
Please Enter Your Password
Forgot your password?
Please enter the email address you use for your account so we can send you a link to reset your password:
A podcast by GBH News reporter Ian Coss gives this notorious project a long-overdue reappraisal. Bonus: The show comes with lessons for climate infrastructure projects of the future.

If you’ve lived in Massachusetts at any point in the last 50 years, you’ve heard of the Big Dig. It’s infamous — a tunnel project that was supposed to bury an elevated highway in Boston to the tune of $2 billion that eventually ballooned in cost to $15 billion and took a quarter of a century to finish.
The Big Dig was more than just a highway project, though. It was a monumental effort that Ian Coss, a reporter at GBH News, calls a “renovation of downtown Boston.” The project built tunnels and bridges, yes, but it also created parks, public spaces, and mass transit options that transformed the city. In a nine-episode podcast series appropriately called The Big Dig, Coss dives into the long, complicated history of the project, making a case for why the Big Dig was so much more than the boondoggle people think it was.
I talked to Coss about how the Big Dig came to be and the lessons we can learn from it as we continue to adapt our built environment to a changing climate. Our interview has been edited for length and clarity.
I moved to Boston for college in 2010, and I remember going to the North End and being struck by how beautiful it was. I didn’t realize how recently that view had changed until I listened to your podcast — I mean, the Big Dig had only wrapped up a few years earlier.
It’s easy to forget how quickly it transformed. I grew up in Massachusetts, so when I would come into the city I would see [the Big Dig] being built — I have vague memories of the elevated artery. And when I moved to Boston Proper in 2013, which was less than a decade after the project wrapped, it was stunning for me to be like, “oh, this is what that project was,” because I definitely didn’t understand it at the time.
What made you decide to create an entire podcast about this “renovation” of Boston?
I think part of it was this disconnect where I grew up hearing about the Big Dig and mostly hearing bad things about it — it was behind schedule, it was a disaster, a boondoggle, etc. — because that really was the reputation of the project, nationally and locally. And then moving to the city and seeing the fruits of it, it was hard to reconcile those things. Like, this “disaster” created a greenway through the middle of the city. Now you can actually get to the airport.
What was driving that narrative of its being a disaster?
The Big Dig went on a very long emotional journey. It started as this kind of visionary, idealistic project championed by activists and supported by politicians of both parties. And then, after navigating the process of funding, permitting, contracting, managing, and designing, by the time it's in construction, it really is not a source of pride.
There are a number of technical things about the Big Dig that could have been done better, and we can learn lessons from it. The way it was contracted could have been done better. The management structure could have been done better. There were flaws in the design, including a fatal flaw that cost the life of a driver in the tunnel.
I think a lot of it is about the storytelling. Just to give one example, so much of the negative narrative around the Big Dig was around the cost. You often hear about how it started with an estimated cost of $2 billion and wound up costing $15 billion. But I think that narrative misses a few things.
One is that it was never going to cost $2 billion. That was not a realistic estimate. But in our country, it is so hard to get approval, political support, funding, and permitting in place that there is a very strong incentive all throughout the process to downplay the costs, downplay the risks, downplay the disruption, make it sound like this is going to be quick and easy and painless and cheap, just to get to the starting line. Because the paradox of it is that if we had known in 1983 or 1987 or 1991 that this was going to be a $15 billion project, it would have never happened. And yet, in hindsight, there are many smart people who told me that this project was a bargain at $15 billion because of what we got in terms of economic benefits, transportation improvements, and environmental improvements.
There’s almost an element of asking for forgiveness rather than permission here, but that forgiveness is inevitably laced with anger because of those expectations.
Right. If only it were just forgiveness.
The Big Dig had its roots in the National Highway Program. Were all those projects going constantly over budget?
There’s a great paper that I cite in episode four where the authors studied the cost of highway building per mile every year from the 1970s through the 1990s, and it’s actually a great sample set because we’ve built so many highways of different sizes in different states. Basically, what they found is that highway costs per mile really ramp up significantly in the 1970s. And that’s, of course, the period when the [Big Dig] was first getting conceived.
So the short answer to your question is, it was cheaper once. But there were other costs, in that those early highways in the ‘50s and ‘60s largely did not consider the impact on communities or on the environment. They did not make a lot of mitigation efforts to minimize the day to day disruption caused by those projects. So I think part of what the Big Dig captures is this really historic change in the way we build things in this country that was ushered in by the anti-highway movements, by citizen activism, and by the National Environmental Policy Act. Over the course of the 1970s we made it much harder to build things, for very good reasons.
I think the Big Dig — which some people describe as the last great project of the interstate era — captures an attempt to do a massive, ambitious infrastructure project that is also loaded with environmental mitigation and also has a robust community process. Part of what we learned through that is that you can have a project that’s cheap and efficient, you can have a project that’s democratic and humane, but it’s tough to have it all. And the Big Dig was trying to have it all, and we did get it all, but at enormous cost. That was the thing that could never be solved.
You make a connection between the Big Dig and climate change right from the first episode. What are the climate lessons we can learn from the Big Dig?
In some ways, it’s ironic to hold up the Big Dig as a case study for climate change because it’s a highway project. My point is not that the Big Dig is, like, the future of infrastructure. But what it offers is a recent case study on a massively ambitious building project. We have some distance, and you can see the whole arc of it, but it very much lives within our era. It’s not the Hoover Dam or the Golden Gate Bridge or any of those other big projects built in a different time under different conditions.
The way I see it is that in order to mitigate or prevent the worst effects of climate change — and you can feel free to disagree with me — we’re going to need to build a lot of stuff. This is not a problem that we’re going to solve by riding bicycles and growing vegetables in the backyard, both of which I do and hope everyone does. And of course, those projects might look different than the Big Dig because building a wind turbine isn’t exactly analogous to building a downtown tunnel. But I think there are relevant analogies, especially things like coastal mitigation in cities, improving mass transit, building high energy transmission lines — these large scale projects that will affect people but also are an important public good.
You talked on the show about the Big Dig as an attempt to make this process more democratic at some level. People on both sides had very strong feelings about it. This reminded me of the NIMBY/YIMBY dichotomy of climate projects. Did anyone mention any best practices that could be applied to future projects of this kind?
I’ve talked with Fred Salvucci [former Massachusetts Secretary of Transportation and driving force of the Big Dig] about this. He mentioned this biblical parable — he’s full of parables — about Jesus walking across the water and then turning to his disciples and telling them to follow. But they step into the water and fall right in, and when they get back out they say it’s impossible. And then Jesus says, “It’s easy to walk across the water. You just have to know where the stones are.”
And Fred said the lesson there is that, in order to navigate this kind of process, you have to know where the flashpoints are, what the issues will be. That way you can anticipate them rather than just going in and saying “this is my project, I’m going to do it this way and you can fight me on it.”
Part of what I think is really interesting about this, which I think speaks to present-day projects like offshore wind, is that in that fight, you have very well-intentioned actors who are trying to make the project better and using the environmental process to do that. And you also have bad actors who are weaponizing and manipulating the environmental process to their own personal ends. And those two things get all mixed up.
You know, I’m an environmentalist. I believe in environmental review. I don’t want to sit here and say that we need to get rid of all environmental permitting because it makes it too hard to build things. But I think it’s also important to recognize that these things can be weaponized.
Scheme Z, which proposed this big spiral loop of ramps and a bridge over the river, is a good example. Politically, that became very messy — they were trying to impose concentrated harm in the name of a public good. And I know, strategically, maybe there are things [Salvucci] could have done to mitigate that or circumvent that, but given the structures in place, the logical outcome is that it spends a decade in lawsuits and review committees and you wind up with something that’s okay, that everyone can live with.
The funny thing about that is that it turned into the Zakim Bridge, which is now a Boston icon.
Right. I mean, that’s part of the communication piece, too.
I was biking under the Zakim bridge the other day, and I biked through where there’s a nice pedestrian and bicycle bridge and this skate park that is always filled with people. Truly, that is maybe the best utilized public space created by the Big Dig.
It’s easy for me to play Monday morning quarterback and say “oh, you should have communicated that better, you should have told the story better.” I mean, he was saying all the right things. But then all you had to say on the other side was “it’s 18 lanes and five ramps,” and that sounded terrible and looked terrible on the page. And I mean, sure, I wish there weren’t all those ramps there, but like you said, ironically, the bridge became an icon of the city.
I think a big part of the lesson for me is how hard it is to build infrastructure democratically because the timescales are all wrong. These things have short-term costs and cause short-term disruption and bring very long-term benefits.
I was constantly struck by this issue of scale, both in terms of time and money. It’s hard to wrap your head around the idea of billions of dollars and projects that span decades. These are just things that are impossible for any regular person to really plan out.
I was talking to someone who said that their dad was in his 70s when the Big Dig was just getting started. And for him, it was like, “my city’s going to be torn up for the rest of my life,” right? That’s what this project meant for him — he would live with this mess of a project and never see the results. And he had to deal with that so that you could move to Boston in 2010 and never know the city another way. The cost of that benefit is borne by another generation.
And it’s the same thing with climate change. It moves on a scale that is so much longer than politics. The Big Dig took almost 40 years from conception to completion. So if you’re thinking about political capital, if you’re thinking about two- and four-year election cycles, it’s very, very hard to conceive, plan, and deliver a project on that kind of time scale.
The benefits and costs are almost inverted in climate change, in a way. We’re talking about future benefits, yes, but we’re also talking about future costs if we don’t do anything. But it’s so hard to make people think in a 40- or 50-year timescale.
If the Big Dig was so hard to make happen politically with what I think was a more genial political environment overall, it feels kind of impossible to think of building anything on that scale right now.
I gave a talk at City Hall a few weeks ago and I was talking with some of the young planners there, people who are in their 30s. Some of them have been listening to the series, and they told me they could not imagine what it would be like to get that kind of federal funding out of Washington, get all the local players on board, get it through the permitting process, and get it contracted. Because right now if they try to take away one parking spot and put in one bike line, they’re bogged down in meetings for a year.
I think climate change is also the inverse of projects like this because with the Big Dig, for example, you can feel the tangible benefits of a quicker commute and a more beautiful city. But with climate change, if the projects work, you’d actually feel nothing.
Exactly. Climate change is way, way harder. A road project or a rail project will have benefits. You get ribbon cuttings and photo ops. But if we make Boston resilient to flooding or something, you know, do some big project that would improve the shoreline or whatever ideally, that historic storm surge may never come, or it’ll come and we’ll be prepared for it and nothing will happen. But yeah, you’re working with long term counterfactuals.
It feels to me like climate change was designed in a laboratory to flummox institutions. It takes all of our cognitive biases, our ingrained social and biological blind spots and weak points and just flicks them all at us at once.
All nine episodes of The Big Dig are out now. You can listen on the WGBH website, Apple Podcasts, Spotify, or wherever you get your podcasts.
This Halloween, get 20% off using code ADVANCED
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
Proposed changes to the National Historic Preservation Act risk disturbing the fragile relationship between the U.S. and Native governments.
In spite of some loud voices both for and against it, the Bipartisan American Affordability and Jobs Act has so far cruised through the Senate. That could change as soon as today as lawmakers begin to consider amendments ahead of a final vote.
One of the main outstanding issues is how the bill’s changes to the National Historic Preservation Act would affect tribal sovereignty. Nevada Senator Catherine Cortez Masto, a Democrat, warned before the initial motion to proceed on the proposed legislation last week that she would not vote for the final bill unless lawmakers struck that section entirely. Since then, nearly 30 Democrats have signed onto an amendment proposed by California Senator Adam Schiff that would do just that.
One of the lead authors of BAAJA, Democrat Martin Heinrich of New Mexico, has dismissed this approach, arguing it would forfeit Republican support. On Tuesday, Punchbowl News reported that Senate Indian Affairs Committee Chair Lisa Murkowski, a Republican, was working on a more targeted amendment with Democrat Brian Schatz. Republican senator Alan Armstrong of Oklahoma has also reportedly sought changes to the bill that would clarify some of the language without stripping it.
The debate over the NHPA primarily concerns a process known as a Section 106 review. Under current statute and regulations, federal agencies are required to consult with state and tribal historic preservation offices before funding or approving projects that stand to affect cultural resources such as sacred spaces, burial grounds, and ceremonial sites. Altering this process is emotionally charged because it is one of few federal mechanisms through which the U.S. government recognizes and gives shape to tribes’ sovereign status.
Proponents of permitting reform complain that the Section 106 process takes too long, however, as there are no deadlines built into either the law or the regulations designed to implement it, and the tribal offices involved often have limited financial and staff capacity. The process is especially lengthy for linear projects like power lines, pipelines, and highways, which typically cross multiple jurisdictions that each have their own preservation offices.
Consultation is not the same as the notice and comment periods that accompany most federal decisionmaking, in which the government gives the public a set amount of time to submit a response and often has a duty to explain why it did or did not incorporate the comments it received. Tribal consultation, by contrast, is “a meaningful dialogue that is intended to resolve differences,” according to Wesley Furlong, a senior staff attorney for the Native American Rights Fund, “It doesn't have to resolve them,” he said, “but the purpose of it is to try to resolve differences when possible.”
BAAJA lays out a new Section 106 review process with fewer opportunities for this dialogue and stricter time limits each step of the way. It also gives agencies broad discretion to determine that a project doesn’t have the potential to cause any effects to historic properties before conducting any public process at all, and thereby forgo NHPA review altogether.
If an agency decides a project does qualify for a review, it must put together a comprehensive report that defines the project’s “area of potential effects,” identifies historic properties within that area, and describes any adverse effects the project may have on those properties. Under the existing statute, those three activities are distinct processes that each require consultation. Under BAAJA, they would be lumped together, with a mandate for agencies to “solicit information” from tribes and tribal historic preservation offices in developing this report. Stakeholders would have just 30 days to respond.
To Furlong, this is equivalent to cutting tribes out of the process. “Generally, soliciting information from a tribe and then either incorporating it or not into a report is not consultation,” he told me.
The next step would require consultation, at least in theory. BAAJA gives agencies 60 days to complete their report, at which point they would have to “initiate consultation” with preservation offices. Tribes would then have 45 days to raise any objections to the report’s findings, but if they miss the deadline, the agency can proceed to make a determination without their participation. If there are objections, the agency would have 30 days to respond and explain how it considered them.
Alternatively, the federal government could forge an agreement with the relevant preservation offices that lays out how the project will avoid adverse effects to historic properties, but it is not required to do so. So long as the agency simply provides a response to objections, its consultation obligations “shall be considered fulfilled,” the bill says.
Even though the bill nominally requires consultation, Furlong argued, the deadlines and procedure it describes don’t support meaningful dialogue. “The idea that handing off a report in a final draft version and asking for comments on it, and then saying, ‘Well, we don't actually have to consider your comments’ — to say that that is consultation is a real affront to Indian country,” he said.
An earlier version of the bill contained a more extreme provision that would have given the Interior Department the authority to take over a tribal historic preservation office if it was out of compliance with the law — i.e. failing to meet deadlines or other required metrics. To some Native critics of the legislation, the provision echoed the termination era, a period in the 1950s and 1960s when the U.S. enacted a series of policies to roll back tribes’ rights to self-governance. The current version of the bill moves away from that, requiring the department instead to offer technical assistance and give time for tribes to come back into compliance. It does still allow the Department to take away the office’s funding, however.
To Ira Matt, the executive director of the National Association of Tribal Historic Preservation Offices, any changes made to the NHPA without tribe involvement are unacceptable. “What began as a termination-era approach of cutting tribal nations out has shifted to an assimilation-era tactic of telling us how and when we can participate, what matters to our cultures, and which harms we must accept,” he wrote in a memo to the association’s members.
Tribes generally support of permitting reform, Mayane Chavez Barudin, the executive director of the nonprofit Sovereign Energy, told me. But she told me this legislation misses the mark. “There is no doubt that tribes are understaffed, and there is a huge demand on them to be responsive to all of the different projects and different permits that need attention,” she said. “Rather than trying to work with tribes and meeting their needs, we see this as just completely sidestepping them in a very harmful way.”
The bill does authorize $200 million per year to be divided between state and tribal preservation offices, which is more than they have received in most recent years. But that is not the same as a commitment to actually appropriate that money, Furlong pointed out to me. Congress would still have to put the money into the Historic Preservation Fund every year in order for it to be made available.
The other major change the bill would make to the NHPA is that it would bar courts from issuing injunctions on projects or vacating permits if agencies do not follow the law. If a federal court found that an agency failed to consider an eligible historic site, for example, the court’s only available remedy would be to instruct the agency to correct the deficiencies on paper. It would not be able to order the agency to halt the project’s construction. BAAJA also makes the same change to the National Environmental Policy Act. Some legal scholars have argued that this change effectively renders both laws toothless, as it removes a powerful incentive to challenge agency decisions, and therefore weakens the incentive for agencies to conduct thorough reviews.
“If litigants know that courts can never grant them meaningful relief, there would be little incentive to ever bring another NEPA case,” David Tatel, a retired judge for the U.S. Court of Appeals for D.C. Circuit, wrote in a recent piece for Bloomberg Law. “And without the potential for litigation, there would be little constraint on agencies and project sponsors that would prefer not to consider environmental consequences and not to hear the public’s views.”
A group of western Democrats led by California Senator Alex Padilla have proposed an amendment to the bill that would exempt claims brought by tribal governments from this limit on judicial review under NHPA. Such a fix would be awkward, however, as it raises the question of why the same exemption shouldn’t apply to tribal NEPA claims.
BAAJA proponents argue that the Trump administration is already proposing sweeping changes to the federal regulations that govern how agencies implement the NHPA that would strip tribal consultation in more explicit ways than this bill does, and that BAAJA would protect consultation by enshrining it in law. When I put this to Furlong, he did not agree that the draft regulations were worse than what was in the bill, and noted that at least regulations could be challenged in court or changed by a future administration. “Even if this permitting reform bill was theoretically better, it will become law, and that is permanent, and the only way that can change is if Congress amends it,” he said.
To be clear, the NHPA is not the only section of the bill that critics say impinges on tribal sovereignty. “Many tribes retain off-reservation treaty-reserved rights, whether it's hunting, fishing, gathering,” Daniel Cordalis, a staff attorney at the Native America Rights Fund, told me. They rely on NEPA, the Endangered Species Act, and the Clean Water Act to assert those rights. The Clean Water Act’s Section 401 certification process, for example, enables tribes to protect their water from upstream polluters. BAAJA “significantly narrowed the way the tribes can engage in that now,” Cordalis said.
To some, the way BAAJA was negotiated violates the precarious trust between tribes and the U.S. government, regardless of what is actually in the bill. The four authors of the bill — Senators Martin Heinrich and Sheldon Whitehouse on the Democrat side, and Mike Lee and Shelley Moore Capito on the Republican side — brokered it behind closed doors, without any of the hearings, committee markups, or reports typical to the lawmaking process. An October 23 letter from dozens of indigenous-led nonprofits and their allies called the exclusion of tribes from the development of the legislation “unacceptable” and stated that “Congress should not rewrite the processes through which sovereign tribe governments defend their cultural survival without their meaningful involvement from the outset of legislative drafting.”
Despite all of this, not all indigenous-led groups are advocating for Congress to reject BAAJA. The National Tribal Energy Association and the Apsåalooke Nation/Crow Tribe both submitted letters of support for the bill. The Coalition of Large Tribes, an advocacy group representing 12 tribes with large land bases, submitted a “discussion paper” offering a series of redlines “necessary to protect tribal sovereignty.” The National Association of Tribal Historic Preservation Offices is calling for the removal of the NHPA section of the bill “so Congress can start over with a process that includes tribe consultation.”
As of now, even the more targeted fixes submitted by the Coalition of Large Tribes look unlikely. The amendment filed by Senators Murkowski and Schatz on Tuesday would make one small change, ensuring that all projects that receive federal funding go through NHPA reviews instead of just those that also require some form of federal approval.
While Murkowski suggested that the text of their amendment was still in flux, NHPA-related concerns may not constitute a real threat to the bill’s passage in the Senate. The most recent procedural vote saw 70 senators agree to advance the bill, and many of the lawmakers advocating for NHPA-related changes — Cortez-Masto, Schiff, Padilla, Mark Kelly, and others — were not among them.
Now the question is, how many of them are actually good?
I am, I confess, a bit of a climate media skeptic.
The literary sub-genre of “cli-fi” has become so bogged down by tropes that even the judges of a prize for the best climate fiction of the year made reading the contenders sound like a slog. (“So many small groups of humans roaming a post-apocalyptic landscape,” bemoaned one adjacent novelist.) On TV, climate protagonists frequently serve as mouthpieces for big ideas, backgrounded by cartoonishly greedy capitalists and bad CGI. At least watching a disaster movie, you get to enjoy the spectacle of a firenado taking out the Golden Gate Bridge before sitting through a moralizing speech at the end about “coming together” and “protecting the planet.”
My skepticism about Hollywood’s penchant for turning liberal consensus causes into “important,” “urgent,” and narratively and artistically hollow products is part of why I still haven’t seen the marquee climate movie of the year, Digger. (Having a 13-month-old is, admittedly, the other part). But there is no denying that climate movies are having a moment: Spotlight director Tom McCarthy’s adaptation of Nathaniel Rich’s book Losing Earth, A Statement, is due out early next year, and premiered this fall at festivals to generally positive reviews (though a trio of adjectives from The Daily Beast suggests it hasn’t entirely escaped the pitfalls of the genre, with the outlet’s critic calling it “preachy, humorless, and unenlightening”).
“Five years ago, I could not have imagined that back-to-back, with that level of talent and that level of investment,” Bruno Olmedo Quiroga, the director of strategy at Good Energy, a nonprofit consultancy that supports climate change narratives on screen, told me of the double-whammy of Digger and A Statement coming out within six months of each other. “That is really amazing.” Heck, climate change even made it into Coyote vs. Acme as a plot point.
It’s not just vibes — data supports the uptick. In collaboration with the USC Norman Lear Center, Good Energy on Tuesday released its latest report about the portrayal of climate change on screen. In it, the researchers found that “climate-inclusive” films and television — that is, scripts that included one or more of 36 keywords or phrases that include “fracking,” “save the planet,” “carbon dioxide,” and “sea level” — increased from appearing in 2.8% of all English-language scripts aired from 2016 to 2020 to 3.2% of all scripts from 2021 to 2024, the latest year of data available.
“Let’s be honest, it’s still a modest number,” Olmedo Quiroga said. “But the rate of change” — 14% over five years — “is significant.”
In addition to the updated frequency analysis of the original set of keywords, the USC and Good Energy researchers broadened their keyword range to capture what they describe as a “wider vocabulary of the ways climate shows up on screen.” Those results, which added an additional 69 keywords including “air pollution,” “heat pump,” “Greta Thunberg,” and “vegetarian,” appeared in 4,992 of the 35,120 scripts that aired from 2021 to 2024 — about one in seven scripts. “We can actually see how it is that writers are reflecting the actual experience of living in a world where climate change touches every aspect of our lives,” Olmedo Quiroga explained.
He offered another example. In the original analysis of scripts that aired between 2016 and 2020, 10% of the movies and episodes that included the word “climate change” also included some kind of extreme weather event. In the latest study, the number of scripts that included the word “climate change” and an extreme weather event dropped to 7%. “At first, we were very concerned about that data,” Olmedo Quiroga said. “But as I layer my interpretation of it, I’m thinking, How is it that climate change is growing but extreme weather events are decreasing in the presence of climate change? And I think it’s because storytellers are diversifying climate stories.”
In other words, climate change is no longer just an explanation offered by an ignored and bespectacled scientist for why Afghanistan has frozen solid, or why a cargo ship is drifting down New York’s Fifth Avenue, but also the reason why people are showing up in the ER with heat stroke in The Pitt — even if “climate change” doesn’t actually appear in that script in so many words. (The study also breaks out 100 films for a closer narrative analysis to account for when climate change is referenced as, say, a joke, or for something like Landman, which disparages renewable energy resources.)
My recent examples also don’t appear in the new study, which only runs through 2024, and therefore doesn’t offer the most current picture. That excludes, off the top of my head, the data center plot of Eddington, the reveal at the end of Bugonia, and the furry subplot that unfolds in Dr. Robby’s ER. The report also doesn’t account for the quality of a story, a potential shortcoming I raised with Olmedo Quiroga, given the divisiveness over Digger. After all, what’s the good of having climate stories on screen if they mostly, as I contend, suck?
“This idea that climate stories are too moralizing and this and that — it is not a climate-specific issue,” he pushed back. “I think every time a storyteller tries to tell a story about something that is systemic, that matters, you run into the same issue and the same risk.” Love it or hate it, Digger is “not forgettable,” he argued, and even as a “quote-unquote ‘box office failure,’ as people are saying online, it still reached more people in box office than the most-watched climate documentary ever,” An Inconvenient Truth. (Approximately 4 million people saw Al Gore’s documentary during its original theatrical run; exact numbers have not been released for Digger.)
To that point, Good Energy’s report doesn’t capture some of the exciting things happening in tandem in the documentary space. I recently enjoyed Gasland director Josh Fox’s latest, The Welcome Table; John Wilson danced around the environmental implications of his subject matter in The History of Concrete, which sold out nearly every night at my local theater; and I’m especially hopeful that Weather Under Fire, which Yale Climate Connections’ Jeff Masters described as “the best climate change documentary I’ve ever seen,” gets picked up by festivals next year.
Maybe I’m also missing the point by focusing on movies that don’t make me want to bash my head against a wall with their familiar dystopias, their obvious metaphors, or their kumbaya final notes about community and mutual aid. Olmedo Quiroga pointed me to research that suggests a heat wave storyline without direct mention of climate change doesn’t actually increase support for climate-related policies.
Then again: So what?
To me, the bigger takeaway from the Good Energy and Norman Lear Center report isn’t just that we’re telling more climate stories than ever before; without subjective or critical analysis, it’s not even clear that we’re necessarily telling better ones. Rather, it seems that “climate,” in all that word now encompasses and means, touches everything more and more, including in the imagined lives of fictional characters. A heat wave or a smoke event or an EV aren’t even necessarily key tells of a “climate movie”; they’re just how we live now. A cool car might just be a cool car; the appearance of a passive house is not some treatise on how we should all live, it’s also just really funny.
“Climate change reaches us in every aspect of our lives,” Olmedo Quiroga said, declining to get into the merits of one film or another and taking the big picture view. “Why decide that one story is better than another?”
This transcript has been automatically generated.
Subscribe to “Load Bearing” and find this episode on Apple Podcasts, Spotify, Amazon, or wherever you get your podcasts.
You can also add the show’s RSS feed to your podcast app to follow us directly.
Allison Clements:
ON.energy is making data centers grid safe. On's medium voltage AI uninterruptible power system is the only UPS proven to meet ERCOT's interconnection requirements.
It's been validated at a Department of Energy lab and has three gigawatts deploying across four hyperscale campuses. The solution combines energy storage and power conditioning into a single technology, making it better than a BESS. This all-in-one power architecture meets your uptime needs with zero transfer time and exceeds grid operators' emerging ride-through and ramp rate requirements. The race is on. Learn more at ON.energy.
Allison Clements:
I'm Allison Clements, Principal at 804 Advisory and former Commissioner on the Federal Energy Regulatory Commission. And welcome to Load Bearing, my new podcast series about the people, politics, and power behind today's data center development boom. Well, the voters have spoken. If the midterms taught us anything, it's that people are worried about artificial intelligence and data center development.
News Waterfall:
Corruption, immigration, health care and data centers.
In the midterm elections bridged Americans' partisan divide quite like opposition.
AI data centers hit the ballot box hard. 56 percent of voters said AI and data centers were crucial.
Allison Clements:
44 local governments made rules either restricting or making it harder to build data centers in this year's election. When I left FERC a couple of years ago, I wasn't really sure what I wanted to do, but I did know I needed to figure out this data center rise, this rise in load growth and what it meant for our electricity system. Two years later, here we are, and I could honestly not have imagined that this issue would become the political juggernaut that it is today. So what are we going to do about it? We need to figure out a way to bring nuance to this conversation. Compute demand, compute ability is becoming as ubiquitous as gas and electricity and water, services that Americans expect to have. Yet at the same time, they're really genuinely worried about their own family, their futures, their communities, and even our country and the path we're taking. So I thought to myself, let's have some conversations. I decided to do this podcast series and talk to the people who are thinking about these issues. Over the next nine weeks, we're going to talk to a utility executive, a data center CEO, an innovative investor, independent power providers, state regulator, experts on cost allocation, community advocates, and more. I'm really excited to try and find points of alignment to hear different perspectives and to start figuring out ways that we can create nuance in this conversation. I'm glad you're here to join me, and I'm looking forward to getting started. So let's dig in.
Allison Clements:
I'm really excited to welcome Deborah Stewart to the podcast as our very first guest. Deb is the city manager of Mason, Michigan, and she's actually the reason I decided to do this podcast series in the first place. I had listened to her speak at a conference on data center development back in Ann Arbor in the spring, and I just thought, wow, she's got a really clear perspective on the challenges that are facing her, as a city manager, her council, as well as her community. And she's been in Mason since 2016, where she's helped to lead more than $80 million in public investment, including two of the largest capital projects in the city's history. Before coming to Mason, Deb worked at the Michigan Economic Development Corporation. So she brings a really interesting perspective on both the local and state sides of economic development generally, and this data center conversation more specifically. And as you'll hear, Deb is deeply focused on making sure that communities have a voice in the decisions that shape their future. I'm really glad she's here to help us kick things off. Hey, good morning, Deb. Thanks for joining us.
Deborah Stuart:
Thank you for having me.
Allison Clements:
Tell us a little bit about yourself.
Deborah Stuart:
My name is Deb Stewart. I'm from Jackson, Michigan, just 20 minutes south of Mason, where I'm the city manager. I didn't actually grow up going to Mason very much, but over time, it really became a community that I really enjoyed visiting. And my family and I decided that this would be our home.
Allison Clements:
And I hear your family has a pretty interesting University of Michigan connection.
Deborah Stuart:
My family's farm was originally where the Michigan Stadium is. And so I grew up listening to games on my grandfather's porch and hearing the crowd and the delay on the TV and all of that good stuff. And I grew up a big Michigan fan, although I am a Chippewa. Go Chips. But we do love Michigan football for sure.
Allison Clements:
I spent a lot of time very close to your grandfather's farm. That's pretty cool. So you've been Mason City Manager since 2016, and you spent your career working in local government and economic development. Can you tell me briefly about your professional journey that had you land where you are today?
Deborah Stuart:
Sure. I started in local government in a larger community and really got excited about economic development. And then I shifted to the state where I ran some large programs to help communities be successful with economic development. But at the end of the day, I really liked that problem solving at the local level. And so my husband and I chose to move to Mason, and the position of a city manager came up, and I was really interested in having a larger impact on a community that I cared about. And so that brought me to Mason, where I am the city manager, and I wear lots of hats, but one of those hats is economic development, and I really get to put to use some of the work that I've grown over the years in different roles.
Allison Clements:
Let's talk a little bit about Mason. Take a minute and tell us what we should know about your community. Describe Mason for those of us who've never been there.
Deborah Stuart:
We have a traditional courthouse lawn where lots of activities happen. That's where our community gathers. Everyone in our community is dedicated to being a part of our school. We just had a homecoming parade and homecoming this last weekend where I think majority of the community was present. We really are that traditional small town where people locate if they want to be connected. If they want to know their neighbors and they want to be part of the schools, we're the great place for that. But we're also in really close proximity to a large job market for Michigan. Like you mentioned, we're just 10 minutes south of MSU. We're about 15 minutes away from the state capitol. So we have a lot of state workers, MSU professors, and employees that really well round our community into this great mix of agriculture, professionals, all range of individuals. And they all kind of have that same purpose, which is being connected to a small town.
Allison Clements:
So what did you think when you first heard that data centers might be coming to Michigan and specifically might be coming to Mason?
Deborah Stuart:
Well, the way that it happened for us is we had someone interested in land and asked us about our utility capacity. And we had done some really large investments, and we're in the process of investments in our water and wastewater. And we knew that that was putting us in a position for future economic development, but also being resilient as a community. And so, honestly, we were expecting it. We had some other developers interested in what our capacity was, and they didn't mention what their use was at the time. And it was a couple months later that we realized that it was related to a data center. And to be honest, we have small data centers in Mason and around this area, so that wasn't actually that concerning to us. But we didn't have an idea of the scale of what we were talking about at that time, and we started to do a lot of research. We had quite a bit of a concern as we started researching because we saw all the horror stories and the horror stories that are still being promoted today, which are true. There are certain communities and states that really maybe were behind the eight ball and did put in the regulations that they needed to at the time because they were learning. And so we really focused on spending time figuring out what was working in other places, what communities were mitigating the impacts as much as possible and how we could do the same here in Mason.
Allison Clements:
When was this? What time?
Deborah Stuart:
So this was probably now about a year ago, a year and a half ago. It was shortly after Michigan had passed the incentives to attract data centers. But to be honest, local communities weren't very aware of those incentives. We actually learned about them from the developers, not from the state, which is unusual. Coming from an economic development background, usually the state rolls those out and talks to communities and engages them to be prepared. And so when we were approached by a developer, they were the ones that shared that there was this new incentive at the state that was attracting them to Michigan, and that's why they were interested in the area.
Allison Clements:
That's really interesting. So fast forward a year and what has happened since they first approached you and today.
Deborah Stuart:
Yeah. So over that course of the time, we really did a lot of research talking to communities, looking at their ordinances, talking to communities where it didn't go well. And what do they wish they had done? What do they wish they had put in place? And we worked on an ordinance that we really felt was legally defensible, mitigated as many issues as we could while still taking the benefits of development because that is an area that Mason does need development as well. We need investment. And so balancing how can we get the benefits of this development by mitigating the impacts to our neighbors as much as possible. And so over that time, we drafted an ordinance. We started that process. It kind of took a left turn that we can talk about. And so that ordinance...
Allison Clements:
Yeah, before we get to that left turn, tell me what the ordinance said.
Deborah Stuart:
So the ordinance really focused on how do we regulate water? How do we regulate development standards? How do we make sure that there's large buffers? How do we regulate noise? How do we regulate lighting? And some things that we felt were unique to the size of this development compared to other manufacturing development in our city. Because you have to make a clear differentiation of why are there additional requirements for this type of use compared to your other uses. And we really felt like we were putting some strong standards in there that we could defend compared to our other ordinances, that because of the mass of this type of development, they needed more items than was required in other manufacturing areas.
Allison Clements:
Right. And so we should say that you are the city manager for Mason and you have an elected city council as well.
Deborah Stuart:
Yes, yes. And so our city council really gave us the focus of, you know, we can't say no to development. So how do we mitigate the impact as much as possible? And how do we position ourselves in the best spot when a project comes forward? We were very aware that we were on a clock. There was interest in property. We had to get something in place before something was submitted. Or they would fall under our existing ordinances.
Allison Clements:
And did the ordinance come before you started to feel community pushback or was it something that was kind of proactively in place or was it all happening at the same time?
Deborah Stuart:
It was before. So we had our initial ordinance first reading and we had some open houses where we got some feedback that we made adjustments. And then kind of surprising us all, there was a meeting organized locally that brought and other people that focused on recalls and focused on recalls,
Allison Clements:
Recalls of who?
Deborah Stuart:
The elected officials for putting in an ordinance. And I think the thought process was that they were concerned the ordinance was actually a welcome to data centers instead of the ordinance was they were already allowed to come into our community. It was an ordinance to treat them differently and uniquely based on their impacts. And so we were surprised. We were surprised at how quickly that happened. And that quickly turned into, you know, hours long of public comments and people concerned about issues. And it was really difficult to come back from that as far as trying to explain the ordinance was actually to mitigate some of those factors.
Allison Clements:
So the ordinance comes out and you mentioned this meeting that was localized, but that people were brought in. Can you tell us a little more about that?
Deborah Stuart:
Yeah, we heard about it kind of after the fact that there was a meeting being organized that brought in individuals from across the state who had been successful in recalling elected officials when they didn't like an issue that was being brought forward. And so they really, at that meeting, positioned the elected officials locally as an enemy and the staff as an enemy and a concern about data centers wrecking our community, coming into our community. And to be fair, I think a lot of our community members had legitimate concerns and really wanted to understand the impacts. The challenge was we really didn't have the opportunity or, to be honest, the capacity to really do public relations and hire firms to help counter and educate on some of the messages that were being misinformed to our residents.
Allison Clements:
And so what were the concerns that were rising to the top? And did they stay the same throughout the last year?
Deborah Stuart:
To be honest, I mean, we've described it when I talked to other city managers as a little bit like whack-a-mole. When you have a topic, you spend a lot of energy addressing that topic. And then the next meeting, it's a completely different topic. And then you spend a lot of energy addressing that topic. And then you move to a different topic. And then three months later, you go back to the first topic because new people have joined the conversation and they didn't hear the part. We tried FAQs. We had 30-page FAQs trying to track these issues and concerns. But that's a lot for a citizen to get up to speed on if they're just entering the conversation months later. And so we just really had this challenge. And we still have the challenge of we'll have a public comment where someone will bring up an issue that we felt we addressed six months ago. But for them, they see something on the news or something on their social media. And for them, it's a very fresh issue and concern.
Allison Clements:
Are there some issues that seem harder to you to mitigate or to protect against or that are just realities of the development that you didn't have a particularly good answer for?
Deborah Stuart:
I think the challenge we're facing is that there's some issues that are really complicated. It's not as straightforward as a yes or no. And I think in today's social media, quick information, it's hard for people to hang on to the nuance of the issue. You know, people are concerned about water usage, and they talk about a lot of different things. Water usage is complicated. There's dewatering during construction that is regulated completely differently than long-term water usage. They're required to hook to us in Michigan, which means we mitigate that and we regulate that. And we do that through utility agreements. That's a very complicated discussion. It's not just, are they going to use too much water? And how do you have those conversations when it's a, I'm angry about this, I'm throwing this issue out, when we really just need to sit down? I offer to meet with anyone that has a concern. And when I sit down with them, it's usually like an hour and a half meeting where we're just talking through the issues. It's not a short discussion.
Deborah Stuart:
And that makes it a lot more challenging. I mean, I think the biggest challenging issue that communities are struggling to get their arms around is noise. Noise and vibration in particular. It's just not an area local government is great at regulating. I'll just be honest. It takes expertise. It takes when does it trigger, enforcement, all of those things. And so we actually decided to consult with an expert on noise because it was too much for us to figure out. It's just not something we typically do. And we've never been asked to regulate noise in the way that is being asked with data centers for any other manufacturing.
Allison Clements:
So there's just a lot of resources involved. If you're hiring experts on noise, if you're spending an hour at a time on a particular issue, I mean, I'm an expert in the power industry, and I'm still, when I sit down to try and figure out how the contracts go, who's paying for what, it confuses me before I can turn around and talk to other people about it. So how are you paying for all this?
Deborah Stuart:
We are pushing our capacity to its limits. I mean, our staff is being pushed to work more hours than they've ever had to work, myself included. And where we can use expertise, we do. We also consult regularly with other communities that are going through the same thing we are and figuring out, did you learn anything? Did we learn anything that we can share across communities? That's really been helpful. We've had great responses from people in Ohio and Virginia communities to give us feedback on what's working, what's not working. All of that is just utilizing the resources, but the reality is we need to run a city, a normal city the rest of the time, and it's really pushing on our capacity.
Allison Clements:
Yeah, I bet. And to be clear, who gets to say yes or no to whether or not this data center development moves forward?
Deborah Stuart:
So there's a lot of decision points that have nothing to do with local government that is, I think, often confusing. There's the decision point right now where they're in land negotiations and they're talking about annexing into the city, which is a state process. If they're successful in getting annexed into the city, then they have to follow the regulations we have on the books. It's not regulations based on the user. It's regulations based on the type of use and the mitigation. And I know there's this big push for users to disclose their names and things like that. For local government, that shouldn't make a difference. What should make a difference is the use and how you mitigate those impacts.
Allison Clements:
Have you been asked to sign NDAs or are there NDAs with the data center developers that are in place vis-a-vis the city?
Deborah Stuart:
I have not been asked to sign an NDA, but I said very early on that I would not. So I don't know if that would have changed if I was more open to signing an NDA.
Allison Clements:
So getting back to all the decision points, right now there are the data center developers and land negotiations, which are private, or to the extent there's an annex that's a state process. What other decision points are there?
Deborah Stuart:
So at this point, they have to get through annexation before they could request a rezoning of the property because annexed property in Michigan immediately is agriculture, and then and it has to be rezoned. And so they have to do a rezoning request, which we have to evaluate based on our rezoning criteria. And then they pursue a site plan and all of those things that have to meet all of our requirements for that district.
Allison Clements:
ON.energy is making data centers grid safe. In fact, ON builds and operates the only data center UPS system proven to meet ERCOT's interconnection requirements, and they have the data to prove it. ON's AI UPS is validated at a Department of Energy lab and has 3 gigawatts deploying across four hyperscale campuses already. This all-in-one power architecture meets your uptime needs with zero transfer time and exceeds grid operators' emerging ride-through and ramp rate requirements. ON.Energy's medium-voltage AI UPS protects your data center from the grid and the grid from your data center. The solution combines energy storage and power conditioning into a single technology, making it better than a best. The race is on. Learn more at ON.energy.
Allison Clements:
What's the status today? Where are we in the question about whether this data center is going to get built in Mason?
Deborah Stuart:
If they're successful in annexing the land into the city, then I think it's a pretty high likelihood that they will pursue a data center in Mason and go through the next steps. Each step has a process, and the city definitely can say no, but there's also the ability of the private developer to counter that with, was that a legally appropriate and defensible decision.
Allison Clements:
Did the data center company engage with the community or have they engaged with the community? Did the people in Mason know who they are and are they working together at all?
Deborah Stuart:
So we've been working and communicating with a land developer. That is not the end user. That is the developer who will pursue an end user during their process. We've been told there is an end user committed to this site, but really the end user name doesn't make a difference to us. It's, you know, what the use is and how the site will be designed and things like that. And so they have not engaged with the community, which I think is a challenge. And I think part of that is, which I understand, they're in private development negotiations. Their property is not in the city yet. And so how do you have these kinds of discussions when you feel like you're early in the process? However, the community feels like they're not being included early in the process. So that's the balance.
Allison Clements:
And this is something that I didn't understand when I started working on the data center issues a couple of years ago, is that oftentimes the party that is trying to come into the community to secure the land, to secure the power, is not going to be the same company or entity that's going to be there at the end of the day that is going to have to become a partner with the city or the location over time. We'll talk about that more in some upcoming episodes.
Deborah Stuart:
Can I just add that that has been one of the biggest disconnects with the public? They want to know, is it this name or this name? And they don't understand that the person we're working with is not any of those. And that's very frustrating to them. They assume that is the process. But to be honest, coming from economic development, this is very normal. We have site selectors often identifying property before we know the end user in different manufacturing. It's just not often that the public is so interested in who the end user is.
Allison Clements:
Yeah. Is there anything that those site selection teams or the developers could do differently?
Deborah Stuart:
It's challenging because, to be honest, some of the questions that we had early on, they couldn't answer because it depends on the end user. It depends on how much water they're going to use. Well, we don't know until we know the end user. What is the height of the building that they're going to be requesting? Well, we don't know because we aren't the end user. And so things that our residents really think are important and are, we just are too early in the process to know.
Allison Clements:
And has there been any mention about partnering with the community, community benefits, contributions to, you know, issues the community is dealing with?
Deborah Stuart:
So Mason has taken a very firm position that we will not provide any local incentives. They will pay the full tax rate. And so our argument to them when requesting incentives has been the best incentive you can get is for everyone in our community to have a lower tax rate because of the contribution you're making. And just as a reference point, Ingham County is the highest tax county in Michigan, and it has to do with a lot of non-tax-exempt properties at the state government and MSU. But our residents really feel it. And so it's important to us that we don't provide tax incentives. We're not trying to recruit them. But if they are here, they're going to pay their full boat. And so with that position, we've taken the position of we're not negotiating any community benefits. If you want to negotiate community benefits with the school or other entities that's on you directly. We want you to pay your full taxes and we will handle your request in that manner as far as following all of the regulations.
Allison Clements:
We're going to just have to check in every 12 months because this is a really long process. I mean, how long could this keep going on?
Deborah Stuart:
I think it could go on for years. I mean, that's the reality of, and I mean, Mason is positioned where we have energy access, we have utilities, we have land. I mean, it's the things that data center developers are looking for. And so I don't believe that this is a situation where they're going away. I think it's an issue of how do we mitigate and work with them to provide the best benefit to the community.
Allison Clements:
What kind of impact has this whole process and experience had on Mason?
Deborah Stuart:
I think the hardest part for myself and my staff is how mentally draining it is. We have community members who have served our community for years on our council. Two of them are up for recall. There's been a campaign to remove the rest. And these are people who are really just doing what they think is best for the community based on legal guidance and what we have within our control. And it's heartbreaking to see that be potentially the end of their service and the community in this way. But I also know that these controversial issues are happening all over. And it's becoming more and more that this is what local governments are facing, more than we've ever had before on various issues. And so I'm not sure that it's any different than anywhere else. But it's just hard to see community members give so much and not people pausing and giving them the benefit of the doubt to have a conversation.
Allison Clements:
Yeah. I remember you talking about the social media part of that and the fact that it's been very specifically targeted. Could you say a little bit more about that?
Deborah Stuart:
The social media in particular has been really brutal. It's really targeted personal attacks on our council members and staff. It's really making the issue very personal and a lack of understanding of the role that the city council and staff have to play, which is mitigating the risk to the community. And that risk includes lawsuits. It includes mitigating the impacts to neighbors. We're balancing a lot of different issues that we're trying to manage the best that we can. And we're using the best practices. But if there's no experience of that and you're just concerned about the use and we see them all over the community, no data centers, that's just not a choice that we can make as a community in our roles. That's a position a community member can take, but not something we can say in our rules.
Allison Clements:
Not something you can say by the law or by the levers you have available to you as the city council.
Deborah Stuart:
Correct.
Allison Clements:
So what should other communities learn from what you've experienced and what has gone on in your town?
Deborah Stuart:
Our community our size, which is under 10,000, we just don't have the capacity to manage the communication needed to deal with a controversial issue like this. We debated in the beginning talking with a public relations firm or things like that. But to be honest, we've never had to do anything like that before. And we really were worried that our community would view that as like us trying to market it or do some other things. I really wish we would have engaged someone to just help with communication because it's nonstop. And it's really, it's hard to counter social media today and the misinformation with facts. Misinformation spreads way faster than our FAQ and detailed summary of the specific reaction to it.
Allison Clements:
How has this affected you personally and kind of your outlook on economic development and your role in Mason?
Deborah Stuart:
I still love our community, and we have great people. We have a great team. But I can tell you it's really been challenging from a mental health perspective. In fact, this week I'm speaking to other elected officials on some of the things I've learned over this process that I wish I didn't have to learn on how to take care of yourself better in these situations because I know a lot of communities are facing it. It's been really challenging, and it worries me that who is going to sign up for these roles in the future? Who is going to be willing to put their name out there, whether it's a council member or a staff or a city manager, when the attacks and toll are so great.
Allison Clements:
We really appreciate that you've been willing to kind of hang out in the middle of this messy situation and share some of your perspective with us. So thanks for being on.
Deborah Stuart:
Thank you so much.
Allison Clements:
I really appreciate Deb taking the time to give her perspective on what was going on in Mason and her honest feelings about how it had affected her and how it had affected her town. She mentioned that she was worried about people who were up for recall elections. So now we are post-election, as I'm talking to you, and her fears came true. There was a turnover of five people on the Mason City Council, all who lost their roles because of this data center controversy. And I don't mean to suggest I know the details or who was right or what should have happened along the way. But it is really telling to me that Deb didn't view her role as a political one. She was trying to do what she thought her job was, which is to operate within the local and state rules and laws as they existed and to do her best by Mason. And so I think it's just one really powerful example of the extent of the politics of this issue, bringing it to life a little bit more than just the polls coming out of the midterm elections can. The congressional seat also flipped in Michigan 7, which is a district that Mason's in. So quite a setup to our series and the conversations that we're going to be having in light of where we are today.
Allison Clements:
Thanks for joining me today and for being part of the conversation, you can get load bearing wherever you find your podcasts thanks to Heatmap News and Nick Woodbury for producing this episode thanks also to Adam Rubenstein for the great music and to my team Alex Mcdonough, Alden Stanley, Emily Pappas, and Tania Pucasu. I'm Allison Clements and this is Load Bearing.