What I Would Tell a Landscape Architecture Student Today

A young designer I know spent her first year out of school drawing grading plans for a firm twice her age's worth of experience older than her. Tedious work. Redlines came back covered in red ink more often than not. She complained about it once, and the principal reviewing her plans said something I've never forgotten: you're not learning to draw a grading plan. You're learning to understand where water goes. The drawing's just how we're making you prove it.

That's the sentence I keep coming back to, because AI is about to take a fair amount of that drawing away from young landscape architects, and I don't think our profession has fully reckoned with what that means yet.

If you're studying landscape architecture right now, you're entering a profession that may change more during your career than it has during mine — and I started when a set of construction documents required a small army of people to produce. CAD changed that. GIS changed it again. Digital modeling, drones, LiDAR, cloud rendering kept the trend going. None of it eliminated landscape architects. It just meant fewer of us were needed to produce the same output.

AI is going to accelerate that, probably by more than any technology that came before it. Work that once took a team of ten may soon get done by one or two technologically fluent people. That's not a doom prediction. It's the plainest read of where things are headed, and I think it changes what your education needs to actually accomplish.

The Paradox Nobody's Solved Yet

Here's the uncomfortable part. Much of the entry-level work landscape architects have traditionally cut their teeth on — drawing details, calculating quantities, laying out planting plans, correcting redlines — is exactly the kind of work AI is getting good at. And that work was never just busywork. Draw enough grading plans and you start to actually understand grading. Watch a contractor struggle with a detail you drew, and you learn something you don't forget. Technology may be about to automate the very production work through which young professionals traditionally built the judgment that technology can't replace.

Nobody's figured out the fix for that yet. Not universities, not firms, not the professional organizations. So don't wait for us. Build that experience yourself, on purpose.

Get Out From Behind the Computer

This is the most practical advice I've got. Get onto job sites, every chance you get. Watch concrete get placed. Watch someone actually establish grade with a laser and a shovel instead of a drawing. Look inside a catch basin. Watch what happens when tree roots meet a gas line. Go back to a site five, ten, twenty years after it was built and figure out what survived and what didn't.

And don't just study the good projects. Study the failures — the retaining wall that heaved, the dead tree, the plaza nobody uses, the drain somebody put in the wrong spot. A bad project teaches you as much as an award-winning one, sometimes more. AI can describe a thousand construction failures in perfect detail. Standing next to one and figuring out why it happened is a completely different kind of learning, and it's the kind that sticks. Don't let technology rob you of the mistakes you need to make while there are still experienced people around to catch them before they become expensive.

Learn the Fundamentals Before You Automate Them

Use the tools aggressively. Just don't let them hide gaps in what you actually know. If software calculates a slope, you should understand what that number means on the ground. If AI recommends a plant, you should know enough horticulture to push back on it. If a drone hands you a beautiful point cloud, you should know where that data came from and whether it's accurate enough for what you're about to do with it.

Nobody's asking you to do long division by hand to prove you understand math. The point is that technology should amplify what you know, not paper over what you don't — and the gap between those two things is invisible right up until it isn't, usually in front of a client or a permitting agency.

Learn AI. Aggressively. Just Don't Build a Career on Knowing It.

Learn to use it for research, visualization, writing, precedent studies, alternatives generation, all of it. But don't make "I know AI" your professional identity — that advantage has an expiration date. Give it a few years and AI literacy will be about as remarkable as knowing how to use email.

The skill that doesn't expire is knowing when it's wrong. AI can hand you twenty design alternatives — which one actually makes sense? It can produce a stunning rendering — can it be built? It can summarize a zoning ordinance — did it get the jurisdiction right? It can recommend a stormwater strategy — will it actually work on this particular site? AI can supply endless information. You're still the one holding the judgment.

Learn Construction

If I could add one thing to design education, it'd be more time in the field. Water runs downhill whether or not your drawing says it should. Plants die. Concrete cracks. Roots grow into places you didn't plan for. Gravity remains completely unimpressed by design intent. Spend real time with contractors. When someone in the field tells you your detail can't be built the way you drew it, don't assume they're looking for a shortcut — ask why. Sometimes they're wrong. Sometimes you are. Learning the difference is most of what experience is.

Learn Business, Too

I know this doesn't sound as exciting as ecology or design. Learn it anyway. Understand what overhead actually is, why your salary costs your employer a lot more than the number on your paycheck, how fees get built, why change orders happen, what a developer means when they say a project "doesn't pencil out." You don't need to become an accountant. But a brilliant idea that can't be financed, approved, built, or maintained doesn't change much of anything. Understanding the economics your designs have to survive in doesn't compromise your ideals — it's what actually gets them built.

Learn to Communicate What You've Actually Done

This might be the single most underdeveloped skill in our profession, and it's worth practicing while you're still in school. Landscape architects describe activities: I prepared the master plan. I designed the planting. I incorporated green infrastructure. Learn instead to say what changed because of it. Not "I designed a stormwater-sensitive site plan" — try "we reorganized the site around its natural drainage, cut unnecessary grading, and lowered how much engineered infrastructure the project needed." Same work. Completely different sentence, and the second one is the only one that tells anyone why your involvement mattered.

Next time you present a studio project, don't stop at the concept. Ask yourself what problem you solved, for whom, what you preserved, what risk you reduced, what would've happened without you. Eventually you should be able to answer one question, cleanly, every time: what became better because I was involved? That's your value proposition, and it's worth having an answer ready before someone asks you to justify your fee.

Learn to Talk to People Who Don't Think Like You

Most of your career will be spent working with people who aren't landscape architects — developers, contractors, engineers, attorneys, elected officials, the neighbor standing up at a public meeting. Learn enough about their world to speak it, without pretending to have expertise you don't. And learn to hear what people actually mean. "I oppose this development" might really mean I'm afraid my house will flood or I don't want to lose the woods behind my property. Those are different problems, and some of them you can actually solve. Learn the difference between someone's stated position and what they're really worried about — and be willing to admit when they've got a point.

Become Broad First. Then Become Someone Known for Something.

Early on, explore everything — residential, parks, planning, grading, construction, urban design, environmental work. Over time, though, get exceptional at something specific: ecological restoration, coastal resilience, water, healthcare landscapes, development strategy, whatever pulls at you. Think of it as deep expertise in one thing, broad competence across the disciplines next door, technology-assisted capability across a lot more, and the judgment to connect all three. Don't rush the specialization. But don't avoid it forever either.

Find mentors — plural, and not just people with impressive titles. A superintendent can teach you construction. A nursery professional can teach you plants better than any textbook. A developer can teach you why projects actually succeed or fail financially. Build your own informal faculty, and once you've got something to teach, return the favor.

Keep a notebook, too — not a portfolio, a knowledge base. Details that worked. Plants that failed. Mistakes contractors caught before they became expensive. Your own mistakes, especially. Over decades, that notebook becomes something no software can hand you: your own accumulated judgment.

Expect to Reinvent Yourself

A student graduating today may still be practicing in the 2070s. Nobody can tell you what software you'll be using by then — it hasn't been invented yet. So don't build your professional identity around a particular tool or platform. Build it around your ability to keep learning. You may need to reinvent yourself at thirty, again at forty, maybe again at fifty. That's not a threat to a good career. It's what makes one interesting.

The Schools Have Work to Do, Too

I've put a lot on students in the preceding paragraphs, and that's not entirely fair — there's only so much a person can reasonably shoulder while they're still trying to graduate. Schools have a real responsibility here too, and I don't think it's optional anymore.

A curriculum built fifteen years ago can be full of excellent fundamentals and still leave a graduate poorly prepared for a professional world fifteen years further along. That's not a knock on tradition — grading, drainage, plants, ecology, construction, spatial thinking, none of that stops mattering. But preserving fundamentals isn't the same as preserving a syllabus, and schools have to keep asking what their graduates are actually being hired to do, what's disappearing, and what's emerging that barely has a name yet.

They should let students chase the edges of the field instead of pulling them back toward the traditional center — a student fascinated by environmental law, real estate economics, remote sensing, or coastal adaptation should be encouraged, not redirected. And studio critique could use the same question I'd ask any working professional: not just tell me about your concept, but what became better because you were involved, and could you explain that to a developer, a neighbor, and a contractor, in terms each of them would actually understand?

Above all, no school should think its job is to hand students a finished profession. Four or five years can't do that. The honest goal is a strong foundation, real curiosity, and enough confidence to keep learning once everything the student was taught stops being enough — because it will, probably more than once.

The Difficult Part, and the Optimistic One

I won't pretend this is all upside. Some entry-level work will get automated. Some firms will get smaller. Some services will get commoditized, and the tools you master sophomore year may be obsolete before you're forty. Those are real pressures, and the profession — schools included — is going to have to keep confronting them honestly.

But here's the other side of it. You may enter this profession with analytical, visualization, and research capabilities that would have looked like magic to the people who trained me. A small, sharp team can now analyze hundreds of acres, model a dozen alternatives, and produce documentation with a speed that used to require a much bigger firm. That's real leverage. What you do with it is the whole question.

I think the future actually raises the ceiling for the best landscape architects — not the fastest drafters, not the ones who know the most software, maybe not even the ones producing the prettiest renderings. The ones who matter will be the practitioners who can walk onto a complicated piece of ground, understand what's actually happening on it, hear out people who see the problem completely differently, use extraordinary tools without being replaced by them, and say with real confidence: here's what I think we should do, and here's why.

That's a bigger job than producing a beautiful plan. It's worth spending your career preparing for.

Learn the craft. Get in the field. Learn construction and business. Learn AI without letting it become a crutch. Learn to write, speak, and explain your value in plain language. Find mentors. Get specific about what you're going to be known for. Stay curious, and expect to become someone slightly different every decade or so.

Your degree gets you into the profession. It doesn't finish your education. Nobody's finishes. That's not a flaw in the plan.

It's the whole point of having one.

~ Eric