What the Wins Actually Demonstrate

Having spent a lesson on failure, let me be fair to success, but carefully, because successes are treacherous teachers. The danger with a win is that it invites you to credit whatever the developer happened to do, when the real cause may have been something the developer had nothing to do with. So the discipline in reading a win is subtraction: strip out the luck and the confounders, and ask what is actually demonstrated by the projects that clear the planning commission and get built without a scorched-earth fight behind them.

Start with the most important confounder, which is site quality itself. Some projects win because the site genuinely raises few of the concerns that mobilize opposition. It is far from existing homes, it uses a cooling design that draws little water, it connects to a part of the grid where new load does not threaten residential rates, and it sits in a jurisdiction that already zones the use by right. A win on a site like that demonstrates very little about community-relations skill, because the consent constraint was slack to begin with. This is worth stating plainly because the industry loves to attribute easy wins to clever engagement, and that attribution teaches the wrong lesson to the next team. When you read a win, first ask whether the constraint was ever actually binding. If it was not, the win is a fact about the site, not about the practice.

Now consider the wins where the constraint was binding, where the site raised real concerns, the opposition was organized, and the project got built anyway. These are the instructive ones, and the recurring pattern in them is consistent with everything this course has argued. First, the community work started early, before the site was locked and the design frozen, so the developer could still change something in response to what it heard. Second, the host agreement addressed the specific concerns this community held, which the developer knew because engagement was investigative rather than performative. Third, the permitting path was run honestly, so residents did not feel outmaneuvered and reach for a moratorium. Fourth, the developer arrived at the hearing with a substantially negotiated deal, so the vote ratified an agreement rather than adjudicating a fight. When you see all four together on a hard site, you are looking at the practice working, and it is worth studying.

But here is the subtraction I promised. Even in these wins, you must be careful not to overcredit any single tactic, because the four elements travel together and you cannot easily isolate which did the work. A developer who did all four cannot tell you whether the early start or the water commitment or the honest process was decisive; most likely they were jointly necessary and individually insufficient. This is why I distrust the confident case study that credits one clever move. The honest read of a hard-site win is that a bundle of substantive commitments, made early and negotiated in good faith, raised the probability of consent enough to clear the bar, not that any one gesture flipped the outcome. Treat community relations as a portfolio, not a silver bullet.

There is a subtler lesson in the wins, and it concerns what the developer had to be willing to lose. In several of the instructive cases, the project that got built was not the project that was originally proposed. The cooling design changed to cut water use. The footprint moved to increase setbacks. The generator plan changed to address air-quality concerns. The developer, in other words, treated the community's concerns as constraints on the design rather than as objections to be argued down, and the winning project was materially different from the one that would have lost. This is the deepest form of the practice: engagement that actually changes the thing being built. A developer unwilling to change the project can perform engagement but cannot practice it, and residents can tell the difference between a developer who is listening and one who is waiting for them to finish talking.

Let me connect this back to the domain thesis, because the wins clarify it rather than contradict it. Data centers are losing at the planning commission, as a general pattern the consent constraint has tightened and the failure rate has risen. But the thesis is not that data centers cannot win. It is that winning now requires satisfying a constraint that used to be slack, and that the developers who win are the ones who treat consent as real, price it early, and pay for it in substance. The wins do not refute the thesis; they illustrate what the thesis demands. A world in which some projects still get built, but only the ones that do the substantive work, is exactly the world the thesis predicts.

So the composite lesson from reading both losses and wins is a single instruction. Model consent as a constraint. Read the room before you file, using the observable proxies. Do the substantive community work early, aim it at the concerns this specific place actually holds, run the process honestly, and be willing to change the project itself. And keep reading the autopsies, yours and everyone else's, because the pattern keeps evolving and the practice that worked last year is the practice the opposition has already learned to counter. In the final module we widen the lens to the future of this constraint and what it means for anyone entering the field.