Development Stewardship: Rethinking the Landscape Architect's Role in a Changing World

My uncle spent years of his career on a highway bypass that never got built.

He was a consulting engineer in eastern Pennsylvania, and the project was meant to route traffic around a string of towns that Route 202 ran straight through — trucks, commuters, delivery vans, all of it funneling down streets that were never built to carry that kind of load. The bypass drew fierce opposition. Environmental review dragged on. Delay bred more delay. And while everyone argued about what not to build, the land the road would have needed quietly got developed out from under it.

The highway problem didn't go away. Neither did the traffic. The towns everyone was trying to protect kept absorbing more of it every year, right through Main Street, exactly like before — just worse.

I didn't have a name for that lesson when I first watched it happen. I do now: doing nothing is also a decision, and it has consequences. Most development debates don't actually weigh a real alternative against another real alternative. They weigh a proposed project against an imaginary version of today that never changes. That imaginary version isn't on the table. It was never on the table. Something was always going to happen to that land — the only real question was whether we had any say in what.

That question is what I've spent thirty years circling, first as a landscape architect and contractor, and lately as a law student trying to understand the regulatory machinery underneath all of it. And it's led me to an idea I've started calling Development Stewardship.

The Question Isn't Whether We Grow. It's How.

I have enormous respect for the natural environment. Wetlands, forests, coastlines, floodplains, soils, and the flora and fauna they support — these aren't obstacles standing between a developer and a certificate of occupancy. They're the systems everything else depends on, including the development.

But I'm not anti-development. Not even close. Growth is how communities stay alive. People need somewhere to live. Businesses need somewhere to operate. A town that tries to freeze itself in amber eventually discovers that change happened anyway — it just didn't get a vote.

So the real question was never should development occur. It's how should development occur. That distinction is the whole ballgame, and it's the foundation of everything that follows.

Here's roughly how I'd define it: Development Stewardship is the responsible management of growth and change in the built and natural environment — one that takes the need for development seriously while protecting natural systems, respecting property rights, strengthening communities, and building something that actually holds up over time.

Notice what that rejects. It's not environmentalism that treats development as inherently bad. And it's not development advocacy that treats every proposal as fine simply because somebody owns the dirt and can get it through entitlements. It asks a harder question instead: Is this good development? And if the honest answer is "not yet" — what would it take to get there?

It is a step beyond, and more site specific, than simple planning.

As a Development Stewardship Advisor my job isn't simply to defend your plan. My job is to help you build a plan we can defend.

Development Is a System, Not an Event

Part of why these fights get so ugly is that everybody's arguing about a different slice of the same elephant. Environmental advocates are talking wetlands. Engineers are talking drainage. The developer's talking economics. Traffic engineers are talking level-of-service. Neighbors are talking about what the street used to look like. Attorneys are talking property rights. Everybody's right, within their lane.

The land doesn't experience any of that separately. Neither does the community living on it.

Change one variable in that system and the rest of it moves. An immediate environmental win in one spot can create an economic incentive that costs you more twenty years down the road. A project that disturbs land today might prevent a worse disturbance somewhere else tomorrow. And stopping a project in one location rarely kills the demand that produced it — it just relocates the demand, usually somewhere with fewer protections, not more.

I watched a version of this play out with farmland back in Pennsylvania, too. Family farms were getting squeezed — rising land values, rising taxes, agribusiness competition — until holding onto the property stopped being a legacy and started becoming a burden. Development offered an exit. Understandably, plenty of neighbors fought it: nobody wants to watch three generations of pasture turn into a subdivision with vinyl siding and a homeowners' association.

But here's the part nobody predicted. When entitlement gets expensive, slow, and legally brutal, small developers and creative development models can't absorb that risk anymore. Who's left standing at the end of a five-year approval fight? Usually the large corporate outfits with the capital and patience to wait it out — the exact players the opposition was trying to keep out in the first place. And once a developer has burned five years of carrying costs and legal fees just getting to a shovel, that money has to come from somewhere. Usually it comes from higher density, smaller lots, and pricier houses.

The process meant to prevent the outcome sometimes builds the very conditions that produce it. That's not an argument against regulation. It's an argument for smart regulation — the kind that asks what behavior a policy actually rewards, not just what it sounds like it's preventing.

The Landowner Matters Too

It's easy, sitting in a public meeting, to talk about a 300-acre farm like it's a public park somebody just hasn't gotten around to opening yet. It provides open space, habitat, groundwater recharge, a nice view on the drive to work — real values, all of them legitimate.

But somebody owns that land. And if farming it no longer pencils out, who's supposed to keep footing the bill for everyone else's view? The family? Forever?

Maybe the honest answer isn't "preserve all 300 acres" or "develop all 300 acres." Maybe it's 80 acres thoughtfully developed and 220 acres permanently conserved. Maybe it's clustered homes, a transfer of development rights, a conservation easement doing the heavy lifting. Development, restoration, agriculture, and conservation aren't mutually exclusive — they just require somebody willing to design for all four at once instead of picking a side and digging in.

That's the part of this work I find most interesting: development can sometimes be the mechanism that funds conservation, not the thing conservation has to fight off. We usually ask how little damage a project can cause. That's a low bar. The better question is what environmental value the project can create — restored wetlands, a remediated brownfield back in productive use, a stream brought back to life, a wildlife corridor protected because the project on the other side of the property line paid for it.

That's a much more interesting question to build a career around.

And it means Development Stewardship has to aim higher than simply reducing harm. A well-conceived project can sometimes leave important natural systems in better condition than it found them. Development can finance restoration, preserve interconnected open space, remediate damaged land, improve stormwater systems, protect habitat, or make permanent conservation economically possible in a way that would never have penciled out on its own. So the measure of responsible development shouldn't always be how close we came to doing nothing. Sometimes the better question is whether the project created environmental value that wouldn't otherwise have existed at all.

The Public Deserves Better Information Than They're Getting

Most people don't spend their careers studying drainage calculations, wetland delineation, or entitlement law — and yet they're routinely asked to form a confident opinion on a project involving all three, based on a rendering and a fifteen-minute public comment period. That's not a fair fight, and it's part of why these meetings get so tense.

A resident who's worried the new development will flood their backyard deserves a straight answer, not a brush-off. Sometimes that concern is dead-on and the plan needs to change. Sometimes the new stormwater system actually improves on what's there now — and if that's true, it deserves to be explained clearly, not buried in an appendix nobody reads.

A credible advisor's job is to sort legitimate impact from perceived impact from plain misinformation, and to say so out loud, including to the people paying the bill. Listening doesn't require agreeing. Advocacy doesn't require pretending the neighbors are wrong. Sometimes credibility means walking into a client meeting and saying: the neighbors have a point, and we need to fix this before we go back in front of the commission. That sentence, said early and said honestly, tends to make the eventual advocacy a lot stronger — and a lot cheaper.

Good Development Should Be Worthy of Advocacy

This might be the whole principle in one sentence. A Development Stewardship Advisor can't just be another hired voice defending whatever landed on the drafting table. Some properties shouldn't be developed the way they're being proposed. Some densities don't make sense. Some drainage strategies create problems downstream that nobody priced in. A good advisor has to be willing to say so — even to the client who's paying the invoice.

Which brings me back to where I started: my job isn't to defend your plan. It's to help build one worth defending.

Where AI Fits Into All of This

None of this is happening in a vacuum. I don't think artificial intelligence makes landscape architects obsolete — but I do think it's about to change how many of us it takes to get the work done, and that's not a small thing to sit with after thirty years in the field.

I watched CAD let a five-person firm do what used to take ten. AI may let one or two experienced practitioners do what used to take fifteen or twenty-five — research, drafting, alternatives analysis, quantities, first-draft reports, all of it accelerated. The profession isn't going anywhere. But the labor structure holding it up is going to look different, and probably sooner than most of us expect.

Here's the thing, though. The developer will have AI. So will the environmental group across the table, the engineer, the neighborhood association, and the planning department reviewing the application. Once everyone at the table has the same research assistant, information stops being the scarce resource. Judgment becomes the scarce resource.

Somebody still has to sit at that table and say: the neighbors are right about this one. This objection isn't supported by the technical findings. Cutting density this far kills the project's economics. There's an alternative nobody on this team has considered yet. And then that person has to explain, in plain language, exactly why. AI can generate the alternatives. It can't yet tell you which one you should be willing to stand behind in a public hearing.

That's decades of field experience talking, not a spreadsheet. And it's exactly where I think landscape architecture needs to move — upstream into due diligence and entitlement strategy, and outward into regulation, economics, and public engagement — rather than staying parked at the production end of the process, competing over who draws the plan fastest.

The Question Isn't Whether We Grow

Development Stewardship isn't a new credential or a rebrand. It's a way of thinking that treats land, ecology, economics, regulation, and community as one interconnected system instead of five separate fights — and asks, before the first line gets drawn, whether the plan on the table is one we'd actually be willing to stand up and defend.

Not development at any cost. Not preservation at any cost. Just the harder, more honest work of figuring out how growth happens well.

Because the question was never whether we grow.

It's how.

~ Eric