Common Failure Modes and How to Avoid Them
Even teams that understand the scarcity thesis, the six variables, and the scoring framework fail in recognizable, repeatable ways. Learning the failure modes is as valuable as learning the method, because most site-selection disasters are not exotic; they are the same handful of mistakes made again and again. Study them so you can recognize the pattern before it costs you.
The first and most common failure is leading with real estate. A team finds an attractive parcel, large, cheap, well-located by conventional standards, and commits emotionally and sometimes financially before confirming the power path. Everything about the site pleases the eye except the one thing that decides its fate. The remedy is the inversion this course has stressed throughout: start from where power is deliverable and work backward to land, never the reverse. If you catch yourself excited about a parcel before you know whether it can be energized on a workable timeline, you are already in the failure mode.
The second failure is treating power as a single number. A team confirms that power is available and stops there, only to discover later that the price is punishing, the local grid is unreliable, or the delivery timeline has slipped by years. Power is a dashboard, availability, cost, reliability, timeline, and carbon profile, and a good site must be read across all of them. Confirming availability while ignoring price or schedule is a partial analysis that feels complete, which makes it dangerous.
The third failure is chasing incentives into a weak location. Because incentive packages are large, visible, and easy to compare, they exert an outsized pull on inexperienced teams. A jurisdiction dangles a rich tax exemption, and the developer talks themselves into a site that is marginal on power or hostile on community. Recall that incentives are the most mobile of the six variables and usually conditional; they should function as a tiebreaker among sites that already clear the real gates, never as the reason to accept a site that fails one. When the incentive is the most exciting thing about a site, treat that as a warning, not an attraction.
The fourth failure is underestimating water and community, the two variables that have moved fastest from footnote to gate. A team optimizes power, fiber, and land, secures its incentives, and is blindsided when a drought turns the facility's water draw into a public grievance, or when residents organize against the campus and the local board tightens or freezes approvals. Both water and community are gates, and both are cheap to assess early. Skipping them is not a shortcut; it is deferring a fatal question to the most expensive possible moment to answer it.
The fifth failure is over-engineering the analysis. Some teams, aware of the complexity, respond by building enormous models with dozens of factors and elaborate weightings, mistaking intricacy for rigor. The result is false precision: a tidy number that buries the few decisive variables under a mass of trivia and lends unearned confidence to whatever it outputs. The discipline is the opposite, a legible model built on a small number of variables that genuinely matter, populated with real evidence, and stress-tested for sensitivity. Complexity should be added only where a real decision hinges on it, never as decoration.
The sixth failure is sequencing diligence backward, spending expensive studies before checking cheap kill criteria, which the previous lesson dissected. Its signature is discovering a disqualifying fact after the money and months are already gone. The remedy is to run the cheap gates first, always, and to advance only survivors to costly diligence.
Behind all six failures sits a single deeper error, which is losing sight of the scarcity thesis under the pressure of a specific deal. Entitled, powered land is the scarce asset; power is the binding constraint; the other variables matter as gates and as trade-offs against that central fact. Teams fail when a deal's particular temptations, a beautiful parcel, a rich incentive, a friendly broker, pull their attention away from the one thing that actually determines whether a site can host a facility on a workable timeline. Faraday's read: the antidote is to return, at every decision point, to the ordering this course has built. Can I legally build here? Can I get firm power, at a tolerable price, on a survivable schedule? Will the community and the environment permit it to operate for decades? Only then do the finer trade-offs matter. Keep that order, apply the gates without sentiment, sequence your diligence from cheap to expensive, and stress-test every ranking you produce, and you will avoid the failures that routinely trap smarter, faster, better-funded teams who forgot what was actually scarce.