“running transit like a business”: digging under the slogan

Now and then, the media (New York Times, Atlantic Cities) rediscovers Mark Aesch, the executive who turned around the performance of Rochester, New York's transit system, and even succeeded in lowering fares.  (Aesch now has his own firm promoting his consulting services, to the transit industry and beyond.)   Here's a sample of what Aesch did:

[The Rochester authority] has, for instance, reached agreements with the local public school district, colleges and private businesses to help subsidize its operations, warning in some cases that certain routes might be cut if ridership did not increase or a local business did not help cover the cost. In recent years, income from these agreements has equaled or exceeded the income from regular passenger fares.

On the one hand, bravo.   Aesch was ready to push back against the near-universal tendency of  government agencies to save money by dumping the costs of their own choices onto the transit authority.  

But at it's core, Aesch's work in Rochester expresses a value judgment that shouldn't be hidden behind puff-words like "creative" or wrapped in the mantra of "business":  Fundamentally, Aesch was willing to cut low-ridership services — or what I call coverage services.  And so, it seems, was his elected board.  

That's very unusual in North America, for democratic reasons.

Demands for coverage service — defined as service that is unjustifiable if ridership is the main goal — are powerful forces at most transit agencies.  Practically any American transit system could drastically improve its ridership by abandoning service to low-ridership areas and concentrating its service where ridership potential is high — which is what "running transit like a business" would mean.  Ridership goals also meet other goals important to many people, including maximum impact on reducing vehicle miles travelled, and maximum support (through high-intensity service) for the dense, walkable and attractive inner-urban redevelopment.

But coverage goals have powerful constituencies too, including outer-suburban areas that get little or no service when agencies pursue ridership goals, as well as people with severe needs — seniors, disabled, low-income, whose travel needs happen in places where high-ridership service is impossible.  

My approach to these issues as a consultant is never to brush aside coverage goals through a mantra like "run transit like a business," but rather to start by being clear exactly why most transit is not run like a business, and coverage goals, enforced by elected officials, are one major reason.  I then encourage communities and ultimately transit boards to form clear policies on how much of their budget they want to devote to coverage, so that the rest can be devoted to chasing ridership unequivocally.

Like many slogans, "running transit like a business" can sound like just good management, but it is actually a strongly ideological stance that values some transit outcomes (low subsidy, environmental benefits) over others (social service needs, equity for all parts of the region that pay taxes to it). 

If an elected board chooses that path, and understands what it's sacrificing, then fantastic: I'm ready to help "run transit like a business."  But if an elected board decides that transit needs to be pursuing goals other than ridership — as practically all of them in the US and Canada do — I'm equally ready to help with that.  Most of all, I recommend having a clear conversation about what goal the agency is pursuing with each part of its budget.  The key is to notice that these are different goals, that both reflect valid government purposes, and elected officials have to choose how to divide their resources, and staff effort, between these competing goals.  

(My professional approach to this issue is explained in Chapter 10 of my book Human Transit, and here).

Again, what's most impressive about Aesch is that even in a city where transit plays a minor role, he refused to let the transit agency be forced to subsidize the needs of other agencies without their financial participation.  Crucial, this required credibly threatening not to serve these agencies' needs.  Many transit agencies I've known in similar cities simply have not had the management culture — or elected board — that was ready to be that forceful. 

But simply cutting low-ridership services is a value judgment, not a technical decision.  It reflects a community's about the community's view about why it runs transit.  In an ideal democracy, making those decisions is not the task of managers or consultants.  It's what we pay elected officials for.  

slippery word watch: commute

When journalists reach for a word meaning "transit riders" or "constituents of transit" they often seize on the word commuter.  

Definitions of to commute (in its transportation sense) vary a bit.  Webster says it means  "to travel back and forth regularly (as between a suburb and a city)."  Some other definitions (e.g. Google) suggest that commuting  is specifically about travel to work or (sometimes) school.  The core meaning seems to be a trip made repeatedly, day after day.

But in practice, this meaning tends to slip into two other meanings.  As with most slippery words, confusion between these meanings can exclude important possibilities from our thinking.    

One the one hand, the meaning is often narrowed to "travel back and forth during the peak period or 'rush hour.'"  This narrowing arises from the inevitable fact that most people engaged in policy conversations — especially in government, business, and some academia — have jobs that lead them to commute at these times.  What's more, many people who are happy to be motorists often care about transit only during the peak period, when it might help with the problem of congestion. Reducing the meaning of commute to "rush hour commute" narrows the transportation problem to match these people's experience of it. 

Of course, cities, and especially transit systems, are full of people traveling to and from work/school at other times, most obviously in the service sector (retail, restaurants) but also in complex lives that mix work, school, and other commitments.  But these trips, even if made regularly, are quietly and subconsciously excluded from the category of commutes, when the term is used to mean only "rush hour commuter."

There's nothing wrong with talking about rush hour commute trips, of course.  They're an important category that must be discussed, but I am always careful to call them peak commutes. The problem arises when commute can mean either the narrow category of peak trips or the larger category of all regularly repeated travel.   That's the essence of a slippery word, and the danger is higher because this slip is exclusionary.  When the word is used in a sense that is narrower than its definition, large numbers of people are being unconsciously excluded from the category it defines, and thus from our thinking about that category.

The word commute can also slip in the other direction, becoming broader than its literal meaning.  It's common to see the word commute used as a one-word marker meaning "movement within cities."  The excellent Atlantic Cities website, for example, uses "Commute" as the name of its section on urban movement in general.  This, presumably, is also what the New York Times means when it refers to San Francisco's BART system as a "commuter train."  BART runs frequently all day, all evening, and all weekend, serving many purposes other than the journey to work or school, so its effect on urban life is much broader than just its commuting role.  When a word's meaning slips to a broader one, it can falsely signal that the broad category is actually no bigger than the narrow one — in this case that all urban travel is just regular trips to work or school.  This takes our eye off the remarkable diversity of urban travel demands, and the much more complex ways that movement is imbedded in all aspects of urban life.

So commute – and the category word commuter — refers technically to a regularly repeated trip, usually for work or school.  But in journalism, and in the public conversation, it's constantly being either broadened to mean urban movement in general, or narrowed to mean "rush-hour commuter."

What can you do?  Be careful.  When you mean "regularly repeated trips," say commutes.  When you mean "regularly repeated trips at rush hour", say peak commutes or rush hour commutes.  When you mean "all travel at rush hour, regardless of purpose or regularity," say the peak or rush hour.  When you mean "all urban mobility or access," speak of urban access or mobility.

Any linguist will tell you that the slippage in word meanings — especially their tendency to slide to broader meanings or narrower ones — is a normal feature of the evolution of language.  I have no illusions that this process can be stopped.  But when we're having public conversations, slippery word usages are the most common way that strong claims to hegemony or exclusion can hide inside reasonable-sounding statements — often hiding even from the person speaking them.  Learn to recognize slippery words (see my category Words, Unhelpful) and look for them, especially in journalism. 

Yet another reason, by the way, to hire literature students! 

the new look at humantransit.org

 We're pleased to introduce the new "look" for Human Transit, including a more readable serif font (Georgia) and I hope a cleaner, more legible feel.  Big thanks to my associate Evan Landman for building and sculpting the design.

As with any change to a transit system, most comments are from existing users disoriented by change of any kind.  So: Calm down, everything you love is still here.  It's just moved around like this:

  • Most content that was in the right-hand columns of the old design is now in the new menu bar above.
  • The Links menu has subcategories, which will open to the right when you click on a menu item.
  • Categories referring to cities have now been separated from other categories.

One note: If you browse the category menu by just clicking and pulling your mouse down, the menu will seem to extend beyond the screen.  Instead, hold the menu by leaving your cursor on it, then use your arrow keys to move the scroll down in the window.   We're working on a better way to handle that.

Some older posts are likely to look messy for a while.  It will take Evan a few days to go through all 942 past posts and clean up anything that didn't translate cleanly.  Be patient and we'll get to them.

I'm sure I don't need to tell you to share your feedback, and any bugs, in the comments!  Please be constructive!

Here's one question that you can answer in comments.  Historically, this blog has used all-lower-case post titles, even for proper names.  Is this (a) a nicely distinguishing bit of "design" or (b) an irritating affectation or (c) you've never noticed or cared one way or the other.  Now everyone can make a one-letter comment!

is walkability a right? how would this work in india?

Sarah Goodyear in Atlantic Cities asks today if walkability should be conceived as a right.  She's talking, though, about India:

To call attention to the appalling situation faced by pedestrians in the city of Chennai, the newspaper The Hindu has launched a campaign called “Right to Walk,” which aims to "reclaim our city’s footpaths" and "goad local officials to act."

So far, dozens of readers using the Twitter hashtag #righttowalk have sent in photos and detailed accounts of sidewalks completely blocked by trash, parked cars and motorbikes, vendors, road signs, and construction.

All good.  In the US, which is much more accustomed to the language of rights, the argument should be even more effective.

As for India: obviously I sympathize with the pedestrians there, having been one myself. It's typically a brutal urban environment, and arguably even worse for cyclists, who are legion.

Dscf2117But one fact of life about the Indian city is that it's very difficult to keep any public space empty enough to offer unimpeded transport by any mode. Just as any unfenced patch of urban land is quickly claimed as somebody's home, an empty patch of street tends to be seen as available for either transport or business purposes, and naturally evolves a locally best use that may not be transportation at all.

Even the car lanes of Indian streets can be gradually reduced, in width and number, though a purely natural and unregulated process. The process goes like this: (1) so many people walk and bike in the curb lanes that motorists start avoiding them, (2) people set up tables in the curb lanes and sell things to the people walking there, and cars begin stopping to make purchases, (3) eventually the whole lane fills up with a mix of peds and commercial activity and the occasional random patch of customer parking, even to the point that durable private structures get built in the public right-of-way. In Visakhapatnam, Andhra Pradesh, I once toured a former 4-lane street that had gradually turned into a narrow 2-lane street through this gradual process that Indian planners call "encroachment."  

Key take-away:  Developing-world infrastructure has to be self-enforcing of its assignment of space, and this is a tough design problem that runs contrary to the instincts of developed-world urbanists.  Otherwise, the natural jostling process by which uses compete for available vacant space tends to prevail over all but the most vigorous demarcations.  This is why developing-world Bus Rapid Transit, and any other single-mode transport infrastructure, must have hard physical barriers to its right-of-way in order to function at all.  Otherwise, space is gradually lost to the sheer pressure from other uses.  

(The problem is especially severe for transit lanes because these only function of they are literally empty most of the time, thus allowing each bus to move through rapidly.  And in the Indian city, empty space looks like available space.)

The process by which available space gets used is comparable in some ways to the self-organization of public space that characterizes the famous developed-world shared spaces, but in India the process tends to be much more responsive to immediate physical and economic forces, including the urgency of commercial activity and the danger presented by the motor vehicle.  Cars do retreat in the face of a sufficiently large volume of pedestrians, bicycles, and informal commerce, but the struggle along this ever-moving frontier is certainly not safe, or pleasant.  

And I'm not sure how defining a "right" would change that.  Perhaps it would.

quote of the week: on modeling

There is a popular illusion that confronting a computer with one’s ideas enforces rigor and discipline, thereby encouraging the researcher to reject or clarify fuzzy ideas.  In the very narrow sense that the human must behave exactly like a machine in order to communicate with it this is true.  But in a more useful sense, the effect is the opposite; it is all too easy to become immersed in the trivial details of working with a problem on the computer, rather than think through it rationally.  The effort of making the computer understand is then mistaken for intellectual activity and creative problem solving.

Douglass B. Lee, Jr., “Requiem for Large Scale Models
Journal of the American Institute of Planners
May 1973, Vol. 38, No. 3 (emphasis added)

end of the loop for sydney’s transit toy

DSCF4158
This weekend, Sydney will complete a long and predictable narrative that cautions us yet again about the danger of relying on tourist experiences as a basis for transit planning.

The Sydney Monorail, built in imitation of Seattle's, has now been through the predictable phases of exuberance, delight, irritation, and boredom, and has finally arrived at the point of being more of an obstacle than a service.  The Sydney Morning Herald interviews longtime monorail fan Michael Sweeney who says what little can be said in the thing's defense.  He even uses the word groovy, reminding us (and the interviewer) that he's expressing a definition of coolness that prevailed in one historical moment. There was never any reason to assume the monorail would be cool forever.

Why?  The usual things.  It was conceived as part of a redevelopment, designed to be part of the excitement that would sell expensive real estate.  Like many new North American streetcars, the point was solely to achieve a development outcome and nobody much cared whether it would be useful as transit, especially decades into the future.
Map_sydney_monorail

It was a tiny one-way loop, only about 1 km in diameter, connecting some key tourist destinations into downtown.  Even for tourists it had limited use because — like most North American streetcars again — the route was so short that you might as well walk, as most people do in this area.

As urban design, the monorail wasn't that bothersome when it sailed over the open spaces of Darling Harbour, but when it snaked through the narrow streets of the CBD, it was a heavy weight in the air on narrow streets that were already oppressive to the pedestrian.

DSCF4174

 It's not surprising that it took a new redevelopment plan to sweep away the toys of the old.  Still, the calculus came down to this:  It's not very useful.  If you want to get somewhere on the loop, and back, you might as well walk.  And there are far fewer people riding it than walking under it, perceiving it as an oppressive weight.

So it's coming down.  Last ride is this Sunday. 

please forward! a quick job for a small web developer

UPDATE:  FIRST FOUR QUESTIONS ANSWERED IN COMMENTS BELOW.

My firm Jarrett Walker + Associates is looking for quick assistance in designing a web-based tool, designed to sit on a transit agency or project website, that will help citizens think through some transit planning choices and suggest priorities.  It requires the user to select different types of network for different parts of a city, and cover the whole city within a fixed budget of service.  

We need the product in a month.  Our absolute maximum budget $9000 but we will be very interested in proposals that come in substantially lower.  

This job is likely to be suited to a small, low-overhead web programmer who can do it quickly, efficiently, and yet creatively.  It could lead to a future relationship assisting us with more tools of this type, as the need arises often in our planning projects.

Everything is explained in our simple Request for Proposals, along with two attachments referenced in it.  (All materials are copyright Jarrett Walker+Associates and should not be reproduced for other purposes.)  All you need to do is reply with a quick letter.  

Download Service Allocation Exercise RFP


Download Service Allocation Game


Download Population and Employment Data

If you have a question:

  • Look at the comments below.
  • If your question hasn't been answered, add a comment beginning with the words "Question __:" where the space is the number of your question (the last number you see, plus 1).  I will then reference these numbers in my responses, which will also appear as comments.  (Alas, TypePad does not support threaded comments.)
  • Come back in a day or so to check for your answer.

Note:  To keep the flow of critical information clear on this procurement, I am reading but then unpublishing comments that are extraneous to the question-and-answer process.  

Thanks!  

Paul Mees, 1961-2013

Art-353-paul-mees-300x0

Paul Mees, the Australian public transit scholar and author of Transport for Suburbia, passed away June 19 after a battle with cancer. 

Paul was an important voice in the struggle to bring contemporary transit planning techniques to Australia in particular.  Transport for Suburbia, like much of his other writing, contains eloquent arguments for the basic geometric principles of ridership-oriented transit planning, ideas that are second nature to most transit planners but that have been extraordinarily hard to convey outside the profession.  

Sadly, I dealt with Paul mostly as an adversary.  We had one meeting in person, in which we drove around Canberra together mostly agreeing about what needed to be done there, but Paul chose, in print, to be mostly a critic of my work.  We certainly had a long-standing quarrel about the role of density in transit ridership, though I think this was mostly a problem of audience and language, not real opinion.  He was certainly caustic at times, and could certainly present is ideas in ways that sounded like personal attacks.

And certainly, there were reasons to be frustrated.  He worked in an era where the very possibility that transit could be planned as a citywide network, and that it was a crucial area of public interest and discussion, was at a low ebb in Australia, lost in the obsession with privatization and narrowly defined "benefit cost analysis".  Media coverage about transit was either about infrastructure debate or about whether some service should be "privatized" or "profitable."  The concept of networks — different kinds of services working together and serving an entire city — was only beginning to emerge.  For years, much of the essential work of transit planning had been outsourced to operating companies that planned for their own turf, not for the network as a whole.  There were few motivations to innovate, and many to suppress innovation.

This was the world in which Paul and I both had to work, and I'm grateful that he lived to see some of the subsequent revolution.  Australian governments are now re-asserting their right to control the design of their transit networks on behalf of the cities that depend on them so profoundly.  Many of the ideas that Paul helped promote are finally surfacing and taking hold.

All progress comes from a broad front of voices, and nobody hears the moderates ones unless more extreme and uncompromising ones are also present.  Paul Mees was, in many ways, the uncompromising conscience of Australian transit planning.  His passion and persistence on the topic will be missed.  

Photo:  Michael Clayton-Jones, The Age.

how to (not) sound elitist when discussing transit

 

PTOD240x300.ashx

This is not a balanced book review. While I will start with some general praise of this new book, I must focus on a few passages about public transit that are both misleading and potentially harmful.  I do this not to challenge these authors in particular, but because these mistakes are so common in urbanist writing and need to be called out wherever they appear.

Reid Ewing and Keith Bartholomew, both at the University of Utah, have a new large-format paperback offering a concise overview of the basics on Pedestrian and Transit-Oriented design.  If you want a good glossary of key urbanist concepts such as imageability and coherence, or you want a good and well-cited argument for local street connectivity, this is your book.  

Very usefully, the book is organized as a series of checklists:  Here are the features that you must have to be considered transit-oriented design, here are others that are desirable.  It's designed to be handy to the time-crunched developer or policy person.  In fact, it meets one of the most important standards for an influential book in our distracted age:  You can get most of the message by just looking at the pictures and reading the section headings.  

The writing is good, too, clear and with careful attention to explaining and demystefying concepts.  With one exception, I could recommend this as a good reference guide to the key concepts of pedestrian-oriented design.  

As a guide to transit-oriented design, however, it has a fatal flaw:  The authors make recommendations about transit that make sense from a design and development point of view but are nonsense to many experienced transit planners.  These recommendations will sound elitist and tone-deaf if you present them to your transit agency.  As always, I emphasize sound; I've talked with enough urbanist writers to know how good their intentions are; they are mostly genuinely surprised when their comments about transit backfire.  But it's not a hard mistake to avoid.  I am going to take apart a critical passage in the book not because it's typical — it's an unusual flaw in a good book — but because it illustrates a lingering problem with urbanist discussions of transit in general, one that I hope we are close to moving beyond.

Ewing and Bartholomew lead off their transit discussion with this tired old chestnut:

In the quest for efficiency, transit has become dull and utilitarian, part of the problem reather than the solution to today's lifeless streetscapes (Coppe 1991).  [p 82]

If this generalization is really about "today," then how is it bolstered by a 22-year old citation?  Obviously it's true to a degree, more in some cities than others,  but there has been transformative progress in the last two decades.  Fleet, facilities, and technology have been upgraded across the developed world, often with the input of great designers.  Do transit agencies get no credit for the evolution in the comfort, openness and access that have happened over the last generation?  

More fundamentally, this line conveys disinterest of the  nature of transit's success, a disinterest that is tragically common in urbanist professions.  The word efficiency is used as though all readers would agree it's a misguided goal.  But when working under any fixed budget as transit agencies do, efficiency is the same thing as abundance.  (When something called efficiency is genuinely destructive or unsustainable, it should be called false efficiency.  Freeways, fracking, and industrial farming may be less efficient than they look because of externalized negative impacts.  Questioning those things doesn't amount to questioning efficiency.)

As for the word utilitarian, it has a technical meaning in philosophy but here it's a dismissive word meaning useful.  Anything that scales to a vast network that's potentially useful to thousands or millions of people can be called utilitarian.  Great transit agencies wear this term as a badge of honor.  What's more they prove that usefulness is beautiful.

But the authors dig themselves deeper.  After showing us pictures of charming, distinctive bus shelters in two wealthy communities that can afford them, they write:

In some cases, transit operators might do better by putting fewer buses on the street at times of low demand, and diverting the money they save into bus stop amenities and fleet facelifts.

This, urbanist friends, crosses a bright red line called upward redistribution of wealth.  

This book appears at a time when many US transit agencies have been slashing transit service for the last five years, driving away legions of riders.  Portland, for example, has had its inner city grid network gutted — mostly cut to 20 minute frequencies at which the connections on which it relies are almost impossible — even though frequent transit service is a foundational element in the City of Portland's neighborhood development policies. 

Any "low-ridership" services that have survived all that carnage are serving popular and important non-ridership goals.  They are not going to be cut to build nicer bus shelters.  Doing so could also be illegal in the US if you're using Federal funds: US Title VI legislation (part of the 1964 Civil Rights Act) is designed to prevent exactly this kind of upward redistribution of the benefits resulting from public investment.  All US transit agencies that receive Federal funds must do extensive analysis to prove they are treating low-income and minority riders fairly in both service and infrastructure.

So if you follow this book's advice, and tell your transit agency they should cut service and force lower income riders to buy cars so you can pay for  nicer bus shelters, it doesn't matter how noble your intentions are.  You will sound elitist.  You will sound especially hostile to the burgeoning environmental justice agenda that is already embodied in civil rights legislation, and that has its own strong nexus with the ultimate outcomes that we call sustainability.  If you prevail in guiding the policy of your transit agency, that agency could be exposed to civil rights lawsuits as a result.  Do you really want this many enemies?

It doesn't help that in suggesting service cuts at "times [rather than places] of low demand," the authors are just repeating a common misconception.  Ridership at different times of day is interdependent, if only for the obvious reason that most transit trips are round trips.  If you cut service and thus reject a customer at one time of day, you'll likely lose their business in the other direction as well.  The most obvious "time of low demand," the late evening, is also a "guaranteed ride home," which means it affects the overall attractiveness of the product.  Finally, lower-income riders who form the bedrock on which transit grows are especially likely to be travelling in the evening; cut their service, force them to spend their scarce money on cars, and you've shoved them further into poverty.

A consistent pattern of all-day service (including "times of low demand") is a powerful tool for fostering lower vehicle ownership.  That's is why many transit agencies are now committing to a policy "Frequent Network" that guarantees service over a certain span regardless of trip-by-trip ridership.  (These policies, important in guiding true Transit-oriented Development at regionwide scale, deserved a mention.  Policies in the Portland and Vancouver BC regions could both have been cited.  Indeed, the book is silent on the urgent question of how to recognize a suitable site for TOD.)

I love distinctive transit shelters as much as anyone, but not if they are defined as an alternative to the sheer quantities of service that cities need and that ridership would reward.  (Canadian midsized cities, for example, generally have about twice the ridership per capita of similar US cities, not becuase their shelters are cuter but becuase they run about twice as much service per capita.)

Distinctive, adorable shelters can still come about in one of three entirely reasonable ways.  Either:

  1. they have been paid for by developers, or by neighboring landowners who will profit most directly from any uplift in land values, or
  2. they have been paid for by city governments as a form of beautifcation, or
  3. they are transit agency investments that are affordable and suitable for mass production, like the San Francisco shelters with the characteristic wave roofs.  

Developer-funding (also endorsed in the book) is often the purest nexus of all, but city funding is also a healthy trend.  City governments are much better placed than regional transit agencies to make investments that express civic identity and character.  Most US cities can also do improvement districts that focus the cost on the landowners who will most benefit.  Still, it's usually wealthier communities that can afford to do this, so it's deeply misleading to present these specialized shelters as realistic examples for cities in general, let alone to suggest that cash-strapped agencies should reject existing riders in order to pay for them.

It's hard to even criticize Ewing and Bartholomew for these howlers.  As long as I've been in the business, I've heard leading urbanists lecturing transit planners about how they should abandon their obsession with abundant service and focus on aesthetics instead.  As someone with serious credentials in the arts, my response is always that I understand the aesthetic values that the urbanist is describing, but that their recommendation is pointless until they own the consequences of the cuts they are implicitly proposing to fund these things. 

To be fair, transit agencies have been slow to engage urbanists in their own language, which requires staff with appropriate expertise.  This, however, has improved dramatically over the last decade.  Most leading transit agencies in major US cities have design and land use professionals on staff.  Working urban designers and architects are responding constructively to transit agency input, and respectful conversations between the fields are happening more than ever.  Most urban design and architecture professonals that I deal with are sensitive to real-world transit issues and open to learning about transit agency perspectives, so we can hope for a continued spread of insight on these issues.  

Indeed, Ewing's and Bartholomew's book shows how far the urbanist discourse has come in respecting transit and the diversity of its riders.  They speak mostly of "transit," avoiding rail vs. bus arguments, and their photos show buses as accepted parts of the urban landscape deserving of attention.   This is real progress, still controversial in some quarters.  It was partly in the context of this larger sensitivity that the passages quoted above were so shocking.

In the long run, urbanist thinkers who discuss transit must learn to respect transit network design and policy as a genuine expertise — something that's worth learning about before you comment on it.  Again, my own experience suggests that the practice is ahead of the literature in this regard.  This book — very useful on all subjects except transit policy — shows how far urbanists' respect for transit agencies has come since the early days of the New Urbanism, and how much — or perhaps how little — remains to be done.

Cynicism is Consent

Now and then I think of an aphorism that’s so self evident that surely some guru must have said it by now. Perhaps someone did before 1990, but Google finds nothing for “cynicism is consent.”

So I’ll say it.  Cynicism is consent.

Currently I’m having a small, polite dust-up with the Cincinnati Enquirer about a false headline on a story.  When I tweeted about it, I got this tweet from a leading urbanist thinker whom I very much admire:

“You expect a headline writer to understand subtlety? Hah!”

To which my response is:  Not unless I force them to.

I cannot begin to describe how much better public transit would be if people who feel cynical about it would complain constructively instead of languishing in the dead-end expressed by that tweet.  And yes, you have to do it over and over.  Patiently.

As a consultant with 20 years under my belt in this business, I have seen enough of “what really goes on behind closed doors” that if I wanted to express cynicism, I’d be way more qualified than most folks to back it up.  But you’ll notice I don’t.

As with many issues, public transit in America is neglected because of apathy, not opposition.  The opponents are not the problem.  The apathy of supporters is.  And cynicism is a big part of that apathy.

Cynicism often dresses itself up as wisdom and worldliness.  Often it sounds like the voice of older folks warning young ones against idealism.

But in the end, the cynic who presumes the worst is as useless as the pollyanna who presumes the best.  Because to assume either of those things means that there’s nothing for you to do, which means you are consenting.