About this episode What if the reason American streets keep getting built wrong isn’t that engineers are careless, but that a whole profession is missing from the room? In this episode Seth Zeren talks with Steffen Berr, a civil engineer trained in California who moved to the Netherlands to learn and practice in a human-centered transportation system. Steffen made the case in his essay “America Has No Transportation Engineers”: in the Netherlands, transportation engineers and civil engineers are educated on separate tracks and work side by side, while in the US, civil engineers inherit transportation decisions they were never trained to make, so those decisions end up hard-coded into manuals. They talk about why “double it for safety” fails on roads, how outsourcing spreads responsibility until no one owns a project, the role of professional licensure, how Steffen talked his way into a Dutch firm by learning Dutch in seven months, and why Morgan State University’s transportation engineering program is worth a look. Steffen also walks through a redesign of a crossing near Sacramento State, shares what he learned serving in Ukrainian air defense, and previews his forthcoming book on the science of movement. Links Articles * America Has No Transportation Engineers, Steffen Berr, Next City (also republished by Strong Towns) * American-Dutch engineer calls out root problem with American DOTs, Streetsblog USA profile of Steffen Books * Paved Paradise: How Parking Explains the World, Henry Grabar * Recoding America, Jennifer Pahlka * The High Cost of Free Parking, Donald Shoup * The Death and Life of Great American Cities, Jane Jacobs * On Movement, Steffen Berr (forthcoming working title) Organizations and programs * Arcadis, the consultancy where Steffen worked as a designer * City of Haarlem, where Steffen worked as a traffic advisor * Strong Towns, founded by Chuck Marohn * Morgan State University, Transportation & Urban Infrastructure Studies, home of an ABET-accredited B.S. in Transportation Systems Engineering * Sierra College and Sacramento State, where Steffen studied * ASCE Mid-Pacific Student Symposium, the student competition Steffen mentions * ASCE “Raise the Bar” (Policy 465), the push to require a master’s degree for licensure * HS2, the UK high-speed rail project * Not Just Bikes (YouTube) * BicycleDutch, Mark Wagenbuur * Jonathon Stalls / Pedestrian Dignity Build the Next Right Thing is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. Transcript Seth: Hello and welcome to the New School for City Builders. I’m your host, Seth Zeren, a recovering city planner turned neighborhood developer in Providence, Rhode Island. This is a podcast about how we can transform the education of city builders. If we want to change how our cities and towns work, we need to change the people who run them. We need a new generation of city builders: architects, engineers, planners, developers, city managers, and civic leaders. We need a new school for city builders. Today I’m joined by Steffen Berr. Steffen is a civil engineer who designs transportation infrastructure to connect communities. Steffen has a BS in civil engineering in the US, but then moved to the Netherlands to learn and work in a human-centered transportation system. Steffen, welcome to the New School for City Builders. Steffen: Thanks so much for having me. I would say I’m still a recovering American civil engineer, but I became a Dutch transportation engineer. Seth: That’s going to be really interesting to talk about, that transition. The reason I reached out to you is you wrote a piece, maybe a couple of years ago now, for Next City entitled “America Has No Transportation Engineers.” That’s a spicy take. What do you mean? Steffen: That title is something that I thought about for a very long time when I was writing this, because I was trying to come up with how I could describe the problem in just a single sentence. I wrote this article after I had worked in the Netherlands for around two years. I’d worked for the private company Arcadis, which is a Dutch company that does civil engineering work and transportation work for Dutch cities as a private consultant. And then I was also working for the City of Haarlem, I believe, at the time. Working in the profession, I worked in the US industry, I worked in the Dutch profession, and I just noticed how projects were handled differently: the phases that projects would move through, how people would work on it. It differed quite a lot from my experience in the US. There’s lots of arguing in the US, and people say, “Man, these guys are uneducated, they’re stupid, they’re out of touch,” or “They’re bought by the car lobby,” or something like this. And I thought there’s a more fundamental issue here. How do I describe it? The conclusion I came to was that there’s a completely missing profession in the whole project delivery process in the United States. In the Netherlands, you have both transportation engineers and civil engineers working on projects at the same time. Whereas in the US, it seems like you only have civil engineers, not really any transportation specialists. It’s kind of like if you’re trying to build a building and you have a structural engineer and you don’t have an architect. That’s where so many of the issues in these transportation projects come from: there’s truly not a transportation expert who works on these projects. And the reason that these transportation experts don’t work on the projects is that we are not producing them at the university level, because there’s no separate education track for them. It was never about trying to call somebody unqualified or stupid. It was just saying people are trying to do something they haven’t been properly prepared for, and how could anybody do it if they haven’t gotten the proper qualifications? So it’s not necessarily a criticism of the civil engineers. It’s just saying that you need a civil engineer and you need the transportation engineer, and the transportation engineer is missing. Seth: That’s really interesting. Civil engineering as a concept, I’ve talked with other folks about this, comes out of the division between military engineering and civil engineering. The military engineers build the forts, civil engineers build the bridges and the roads, and so civil engineering as a discipline has come up as the civil side of building stuff. And today, if you go to a civil engineering program in the United States, there are a few different “specializations,” in air quotes, that you can do, but it’s generally a very generalist education. Everyone’s expected to take structures, everyone’s expected to take geotechnical, everyone probably has to take highway engineering; there’s that one class that people will take. Walk us through the different specializations that do exist in American civil engineering and why that’s not adequate preparation for what you’re describing as an alternate role. Steffen: Civil engineering has five classical subfields, as the US system is set up: transportation, structures, environmental, water resources, and geotechnical. Geotechnical focuses on foundations, retaining walls, things like this; soil is the most complex material in the world. Transportation is anything having to do with roads and streets. Structures is anything to do with upright structures. Water resources has to do with dams, aqueducts, things like that. And environmental engineering has to do with handling environmental issues on a large scale, like how to decontaminate a construction site. For example, if you had an army base with lots of toxic chemicals, how do we engineer the environment to make it safe again for other uses? So those are the classic five. I think you actually hit on something when you said a civil engineer will take highway engineering, and that goes to show you a lot. A civil engineer is going to know a lot about how to build the structure of the road itself: where the drainage pipes go, where the culverts go, what the slope of the road is, what the cross section of the asphalt surface is, how thick certain layers need to be. But what you’re not learning about is the nature of what’s using the road, and how the road itself needs to be configured in relation to everything else. Civil engineers take introduction to highway engineering, but in this class you’re not learning where highways are supposed to go. Are highways supposed to run through cities? What impact do highways have on cities? Are highways a better solution? Why only highways? If you make everything based on highways, maybe you’ll think of all roads as highways. In a way, you kind of answered the question right there: there are all of these pre-questions that need to be figured out before you even start building your road, and you need a professional to set them up and solve them. Instead of that phase, all these assumptions get made instead, for example that traffic will always grow, more roads are always better, wider is always better, and they get written into codes. So all of this real transportation engineering ends up basically getting automated and coded, and then the civil engineer takes over. A lot of times people yell at the civil engineer, but the real issue is upstream, where all of this has been automated because we’re missing the person who’s supposed to do this work. Seth: Right. If you’re an architect or a developer designing a building, you’re going to hire a structural engineer to make sure it doesn’t fall down. But you’re giving the structural engineer direction on how big it is, mostly what it’s made out of, and what uses are going into it. You’re giving them a bunch of parameters, and those parameters come from an awareness of a bunch of other values (economic value