Data center programs stall in predictable ways. The land has constraints that weren't modeled. The community has concerns that weren't heard. The ecology pushes back in ways the site plan didn't account for. I've spent a decade at Microsoft learning that these aren't separate problems. They're symptoms of designing a site as if it exists in isolation from the system it's actually part of. The programs that move are the ones that start with local understanding.
Thinking
Building digital infrastructure now means navigating land acquisition, water use, energy access, and community trust at a scale and speed the industry has not faced before. All four are tightening simultaneously. The organizations that are moving well through that pressure are not the ones with the deepest legal budgets or the fastest construction teams. They are the ones who found a more productive frame at the beginning.
The standard approach sequences the problem: acquire the land, design the site, then manage the ecological and community variables as they surface. That sequence is expensive. By the time a permitting process stalls or organized opposition appears, the design decisions that produced both problems are already built in. Undoing them costs far more than getting them right from the start would have.
What I have learned from a decade doing this work at Microsoft is that ecological health, community trust, and land strategy are not three separate tracks to be managed in parallel. They are facets of the same underlying question: what kind of presence does this program want to be in the places it occupies? Organizations that answer that question deliberately, before the design starts, tend to move faster and encounter less resistance than those that answer it reactively.
The design principles embedded in living systems are the clearest guide I have found to answering it well. Nature has been building durable, resilient, community-integrated systems across every climate on earth for a very long time. That record contains real instruction for infrastructure programs, not as analogy but as applied method.
Practice
The work spans land, ecology, community, and systems. Each domain is distinct in practice. They all pull toward the same answer.
Embedding biodiversity, hydrology, and soil health into infrastructure from the earliest design stages, so sites contribute to the ecological function of the land they occupy rather than drawing it down.
Treating the surrounding community as a design input rather than an approval hurdle. The trust built through genuine co-design produces access and goodwill that no compliance program produces on its own.
Building the frameworks and measurement tools that make ecosystem health readable and usable for executives making land and site decisions across global portfolios on compressed schedules.
Translating nature's design record into concrete site interventions, from native habitat systems to stormwater infrastructure that performs like the landscape it replaced.
Perspective
The digital infrastructure sector will keep growing. That is not in question. What is in question is whether the land, water, and community capacity that growth depends on gets treated as a finite resource to be consumed or as a set of relationships to be tended.
I think regenerative infrastructure at genuine scale is achievable. I have not seen it done yet. That gap is where my attention goes.
Middenmeer in Noord-Holland is a partial answer. A data center campus redesigned around native ecology, regional hydrology, and the specific concerns of the surrounding community. The site functions differently than it would have under a standard development approach, and the community relationship that produced it is still active years later. It is one site. It is also a repeatable method.
One campus is not a transformed industry. Getting from a single site to a portfolio-wide standard, and from a portfolio standard to an industry norm, requires executives who are willing to ask the question earlier than the current development process demands. Those conversations are the ones I find worth having.
Work
Each of these programs began with a version of the same pressure. What produced a different outcome was not more budget or a different permitting strategy. It was a different starting question.
A new Microsoft data center campus in agricultural Noord-Holland. Community friction was developing. A standard landscape plan was on the table. The relationship between the site and its surroundings was transactional.
Six months of community listening before any species were specified. Ecological research followed the community's questions rather than the site plan. The result was 150 native trees and 2,300 square meters of regional habitat that the community helped shape and co-owns. The campus now functions as a biodiversity corridor and a local school resource. Friction became sustained engagement.
A new regional context with its own ecological character and community history. The Middenmeer approach applied to a different landscape: ecological restoration and community partnership built into the premise of the project rather than layered on at review. A design rooted in the specific place, with community members invested in its long-term health.
A community that had watched a data center arrive. The question was what genuine neighboring looks like beyond regulatory compliance. A partnership with BiomimicryNL brought ecological education into local schools using the campus as the teaching environment. The site became a reason for the community to engage with rather than against.
Recognition
Press & Media
Background
Contact
The conversations I find most useful are with people whose programs are running into resistance they did not plan for and who are willing to ask whether the plan itself needs to change.
Available for keynote speaking, executive advisory engagements, media and podcast appearances, and policy or academic collaborations focused on land, infrastructure, and ecological practice at scale.