Landscape Architecture Doesn't Have a Value Problem. It Has a Value Communication Problem.

I sat through a public meeting a few years ago where a room full of neighbors stood up, one after another, and said some version of the same three words: we oppose this.

The subdivision plan on the screen was, by every technical measure, a reasonable one. Met code. Met setback. Engineer had run the drainage numbers twice. And it didn't matter, because nobody in that room was arguing about drainage numbers. They were arguing about a hundred-foot strip of woods that had been standing between their back porches and open field since before most of them owned their houses — and the plan, as drawn, cleared it almost to the property line.

Nobody on the development team had asked why they opposed it. They'd just heard opposed and started preparing rebuttals.

That meeting taught me something I've been chewing on ever since: landscape architects don't have nearly as much of a value problem as we think we do. We have a value communication problem. We're highly capable of creating value — preserving what matters, solving drainage problems, protecting a neighborhood's character while still getting a project built. We are considerably less capable of explaining what we did in a way that makes anyone outside the profession actually understand why it mattered.

We Talk About What We Did. Not What Changed.

Landscape architects write sentences like this all the time: we developed a stormwater-sensitive site plan incorporating green infrastructure and preservation of existing hydrological patterns.

Nothing wrong with that sentence. Every other landscape architect in the room understands it perfectly. So does the engineer. The problem is that sentence is being read by a homeowner who lives downstream from the project, and to her, it might as well be in Latin.

Try this instead: we reorganized the development around the site's existing drainage patterns, which cut unnecessary grading, kept more of the engineered pipe out of the ground, and reduced the risk of sending additional water toward the neighboring properties.

Same decision. Same engineering. Completely different sentence. The first one describes an activity. The second one describes a consequence. And consequences are the only thing anybody outside our profession actually cares about.

Clients don't buy master plans, planting plans, or grading plans. They buy outcomes. The developer isn't excited about a set of drawings — he wants to know if the site will get approved, if it'll be marketable, if the infrastructure costs stay in check. The homeowner isn't buying a planting plan — she wants shade over the patio, privacy from the neighbor, and a yard that doesn't turn into a retention pond every August. The drawing is the delivery mechanism. It was never the value.

Stop Selling the Noun

"We preserved the existing tree canopy" sounds fine. It also tells the listener almost nothing about why they should care.

"By reorganizing the lots around the existing canopy, we kept mature shade in place, protected privacy for the neighboring homes, cut clearing costs, and gave the new development an amenity that would've taken thirty years to grow back" — now everybody at the table finds something that speaks directly to them. The developer hears reduced clearing costs and a sellable amenity. The neighbor hears privacy. The environmental advocate hears habitat retained. The planning commissioner hears a project that responded to its site instead of bulldozing through it.

Same decision. Four audiences. Four reasons to care. Recognizing all four at once is one of the genuinely rare skills our profession has — and it does us no good whatsoever if we never say it out loud.

Don't explain what you designed. Explain what got better because you designed it.

We're Fluent in a Language Almost Nobody Else Speaks

Part of the problem is that we've built a rich professional vocabulary — resilience, biodiversity, green infrastructure, placemaking, ecological performance — and quietly assumed the rest of the world shares our reasons for caring about it.

They don't, not because they're unsophisticated, but because they're asking different questions. The homeowner isn't thinking about resilience. She's thinking: will my house flood again? The developer isn't thinking about ecological performance. He's thinking: can I still hit my numbers on this deal? The mayor isn't thinking about placemaking. She's thinking: will people actually show up downtown and spend money? The public works director isn't thinking about sustainable landscape systems. He's thinking: who's mowing this in ten years, and what's it going to cost the department?

Those are the real questions. They're the ones that decide whether a project gets funded, approved, built, and maintained. Translate for them, and the professional vocabulary doesn't disappear — it just finally does its job. Resilience becomes your business reopens faster after the storm. Green infrastructure becomes we're handling some of this water with landscape instead of another concrete box in the ground. Tree preservation becomes shade, privacy, lower cooling bills, and a mature yard on day one instead of year twenty. That's not dumbing the profession down. That's finally being understood by the people who fund it.

The Translation Runs Both Directions

Here's where that meeting with the woods comes back in. "We oppose this subdivision" is a position. It is almost never the actual concern.

Ask why, and you usually get somewhere real: my property already floods. That tree line is the only thing between my kitchen window and a new roofline. Traffic's already too fast on this road. Some of that will be wrong. Some will be exaggerated. Some of it will be dead-on and worth redesigning around.

In that particular case, it turned out the neighbors weren't opposed to the subdivision existing somewhere beyond those woods. They were afraid of watching it appear in their backyard. Once the team understood that, the options multiplied — a fifty-foot buffer preserved instead of cleared, lots reorganized without losing yield, supplemental planting filling the gaps, eventually a walking trail turning what had been dead acreage into a marketed amenity. Nobody won the argument. The design changed what the argument was even about.

Drainage works the same way. "This subdivision is going to flood us" gets a terrible response when the first words out of the engineer's mouth are "no it won't, we meet code." Even when that's technically true, it's lousy communication, because the neighbors aren't reciting a hydrology model — they're remembering three floods in twenty years and watching a hundred and fifty acres of woods get cleared. Their conclusion might be wrong. Their fear isn't irrational. Investigate it instead of dismissing it, and sometimes you get to walk back into that meeting and say: you identified a real problem, we redesigned part of the project around it, and here's how this will actually be better than what's there now. That's not spin. The project got better because somebody listened.

I think of it as a simple sequence: listen, identify, verify, respond, communicate. Listen without immediately defending the plan. Identify the actual interest underneath the stated position. Verify whether it holds up. Respond — through design, mitigation, or sometimes no change at all. Then communicate what you found, plainly. That verify step matters more than people think. "The public complained, so the public must be right" is bad practice. So is "the experts designed it, so the public must be wrong." The credible version is simpler: you raised a concern, we looked into it, here's what we found — whichever way it lands.

Credibility Is the Payoff

A landscape architect who agrees with every client position on every project eventually becomes background noise. If every plan is perfect and every objection is unfounded, why would anyone outside the development team trust your judgment on anything?

The moment you tell a client "the neighbors have a point, we need to fix this before we're back in front of the commission," you've spent something real. But it buys you something more valuable later — because the next time you say "we looked at that concern carefully, and the evidence doesn't support it," people believe you. Credibility isn't a personality trait. It's an asset you build one honest conversation at a time, and it's worth more than any rendering you'll ever produce.

The Translator's Seat

Landscape architects sit at an unusual intersection. We can speak developer — yield, feasibility, schedule, cost. We can speak engineer — grading, drainage, constructability. We can speak environmental — hydrology, habitat, soils. We can speak regulatory — approvals, entitlement, mitigation. We can speak community — privacy, traffic, character, fear of change. And we can speak design, which is really just the language of how all those competing interests get resolved on an actual piece of ground.

That doesn't make us experts in every one of those fields. It means we're positioned to understand how they connect — which, in an increasingly specialized world, might be a specialty all its own.

That translator's seat matters more, not less, as AI makes production faster for everyone. If contractors can generate a decent site plan and software can knock out a planting palette, "landscape architects design landscapes" stops being much of a pitch. "Landscape architects help people make better decisions about land" is a different claim entirely — and it only holds up if we can actually show what got better because we were in the room.

We Are About Solutions

Underneath all of this translating and listening is something worth saying plainly: landscape architects are not in the business of managing conflict. We're in the business of solving it.

It would have been easy, in that meeting about the hundred-foot woodland, to treat the neighbors' opposition as a public-relations problem — something to smooth over with a better rendering or a more patient tone. It wasn't a communication problem at that point. It was a design problem, and design problems have design solutions. A buffer preserved, lots reorganized, a trail added where there used to be a liability — that's not spin, and it's not compromise for its own sake either. It's a better answer than the one anybody started with.

That's the part of this work I'd put in front of every client and every neighbor who's ever doubted why a landscape architect belongs on the team. We don't just diagnose the flooding complaint, the traffic worry, the fear of losing the tree line. We're trained to sit inside the mess of competing interests — economics, ecology, regulation, community — and come out the other side with an actual answer, not just an explanation of why the problem is hard. Engineers solve for code. Attorneys solve for risk. We're one of the few disciplines on the team whose entire job is solving for all of it at once, on the actual ground where people will live with the result.

That's the sentence I'd want the profession to be known for. Not "landscape architects design landscapes." Landscape architects find solutions everyone else missed.

What This Means for the Next Generation

I'd change one question in the studio critique. Instead of starting with "tell me about your concept," start with: what became better because you were involved? What did you save? What did you create? What would've happened without you? And then make the student answer in language a person who's never sat in a design studio could actually follow.

That's a harder critique. It's also the one that prepares someone for a career where producing the plan keeps getting easier and explaining the judgment behind it keeps getting more valuable.

Boil all of it down and you get two translations. Outward, turn activity into outcome into value — don't just say what you did, say what changed. Inward, turn position into concern into interest — don't just hear what someone opposes, understand what they're trying to protect. One helps people see our value. The other helps us see theirs. And somewhere in between the two usually sits a better design than either side started with.

Landscape architecture doesn't have a value problem. We create it constantly, on nearly every project we touch. What we haven't gotten good enough at is saying so — plainly, in the other person's language, every single time. In a future where information is cheap and everyone has the tools to produce something, that may be the skill that decides who's still standing at the table.

~ Eric