Friday, August 14, 2015

Please, let's start "educating community leaders about placemaking."

I consider this a must-read. It's what we're saying. They're ideas that matter.

Hmm -- wonder if David Duggins has finished reading Jeff Speck's book after a year and a half?

The last time I asked him, he had not. Sad, isn't it?

Top 10 techniques for educating community leaders about placemaking, by Nathan Norris (Better! Cities & Towns)

Extraordinary strides have been made in the advancement of placemaking over the past twenty-five years.

Think about it. In the years prior, the term “placemaking” wasn’t even in common use by developers, designers and planners. Nor were terms such as form-based code, new urbanism, smart growth, transect, charrette, visual preference survey, traditional neighborhood development, transit-oriented development, sprawl repair/suburban retrofit, return on infrastructure investment analysis, tactical urbanism, WalkScore, complete streets, context sensitive thoroughfare design, LEED-ND, light imprint infrastructure, WalkUP, the original green, lean urbanism, the high cost of free parking, etc.

What has not changed over the last 25 years is that decisions regarding the growth and development of our communities are still being made by community leaders who might be experts in politics, but do not have an adequate understanding of placemaking principles.

Uninformed decisions can lead to bad results. You are familiar with the types of poor policy decisions that spring from this uninformed position— all road widenings are “improvements,” all density is bad, the public works department should treat an urban area exactly the same as a suburban area, etc. For those of us who are focused on improving our communities through competent urban design, this is a source of great frustration.

So here are my Top 10 Techniques for Educating Community Leaders about Placemaking. If you find yourself similarly frustrated, consider the following tools for those you believe are open to enhancing their knowledge (not everyone is).

No comments: