General

Welcome, Atlantic Readers

If you’ve just landed from my piece on “microtransit” at the Atlantic, welcome!  Here are a few key things that will help you understand where that piece was coming from:

And for the big picture of what I’m about, try the introduction to my book!

Job: Come Work for us! Transit Analyst Position. Apply before Nov 15!

You get to draw cool visualizations, and invent new ones!


Our firm has a fulltime opening for a transit analyst.  (Also, watch this space for a senior planner and project manager position to be posted soon!)

Here are the details:

Jarrett Walker and Associates is a consulting firm that helps communities think about public transit planning issues, especially the design and redesign of bus networks. The firm was initially built around Jarrett Walker’s book Human Transit and his 25 years of experience in the field. Today, our professional staff of nine leads planning projects across North America, with an overseas practice including Europe, Russia, and Australia / New Zealand.

You can learn about us at our website (jarrettwalker.com) and at Jarrett’s blog (HumanTransit.org). For a sense of our basic approach to transit planning, see the introduction to Jarrett’s book Human Transit, which is available online. For a typical report of ours, showing some of the analysis we do, see here.

We are seeking a transit analyst based in Portland, Oregon, or Arlington (Crystal City), Virginia.  The position offers the potential to grow a career in transit planning. As a small firm, we can promote staff in response to skill and achievement, without waiting for a more senior position to become vacant.  Everyone pitches in at many different levels, and there are many opportunities to learn on the job.

Duties include a wide range of data analysis and mapping tasks associated with public transit planning.

Required Skills and Experience

For this position, the following are requirements. Please respond only if you offer all of the following:

  • At least two years of professional experience using the skills listed in this section, OR formal training in these skills (such as at a college or university). Directly-applicable coursework is valuable but not essential.
  • Fluency in spoken English and proficiency at writing in English. In particular, an ability to explain analytic ideas clearly.
  • Understanding of basic statistics and experience with analysis and visualization of quantitative and statistical information.
  • Experience in spatial data analysis (GIS).
  • Experience working in Adobe Illustrator.
  • Experience in cartography, evidenced in at least one mapping sample that is clear, accurate, and visually appealing.
  • Availability to start full-time work in Portland or Arlington on before the first week of January, 2019, at least 32 hours per week.
  • Legal ability to work in the US.

Other Desired Skills and Experience

The following are desirable but not essential.  Candidates with the required skills listed above but none or few of these desired skills are still encouraged to apply.

If you have any of the following skills, please describe them in your application

  • Experience with public transit issues.
  • Experience using analysis programming languages (such as R).
  • Experience with qGIS, Remix or InDesign software.
  • Experience in advanced database analysis. (Postgres/PostGIS, MySQL, etc)
  • Expertise with transit-focused routing software, such as OpenTripPlanner.
  • Experience describing issues from multiple points of view, including the perspectives of different types of people, and different professions.
  • Graduate degree in urban planning, transportation, or a related field.
  • Foreign language ability. Spanish is especially useful but other language skills are valued as well.
  • Experience working with minority and disadvantaged communities.
  • Experience managing small teams.
  • Experience and comfort in public speaking.

Compensation, Benefits and Place of Work

Compensation will depend on skills, but will start in the range of $25-32/hour depending on skills and experience.  Raises of over 10% in the first year are typical for excellent work.  Our benefits program includes medical, dental, and disability insurance; a 401(k) program; subsidized transit passes; paid sick leave; and paid time off.

This position will require working out of either our Portland, Oregon, office or our Arlington, Virginia, office. JWA does allow employees to set work schedules that include working from home or other locations.  This position requires travel, to work with clients directly, at least a few times per year.

How to Apply

To apply, please send the following materials to [email protected] .

  • 1-page cover letter, explaining your interest in the position.
  • 1- or 2-page resume, describing your relevant experience and skills.
  • Links or electronic files for up to three (3) samples of your work. If possible, please include a map, a piece of writing, and a demonstration ofa spatial analysis. (A single sample may satisfy more than one of these requests.)
  • Contact information for 1 to 3 references who can attest to your experience with the skills listed above.
  • Please do not include any information about your prior compensation.

We will be redacting from your materials any explicit information about your name, race, gender, or sex.

Diversity and Inclusion

JWA follows an equal opportunity employment policy and employs personnel without regard to race, creed, color, ethnicity, national origin, religion, sex, sexual orientation, gender expression, age, physical or mental ability, veteran status, military obligations, and marital status.

This policy also applies to management of staff with regards to internal promotions, training, opportunities for advancement, and terminations. It also applies to our interactions with outside vendors, subcontractors and the general public. 

Timeline

The deadline for applying is 11:00 pm Pacific Standard Time on Thursday, November 15th. Submitting earlier is advantageous as we will review applications as we receive them.

We will ask a select group of applicants to perform a simple analysis and mapmaking test on their own, and then to join us for an interview. The test will be assigned on November 20 and due on November 27. We wish to hold interviews (in person or by phone/web) on November 29 or 30.

Thank you for reviewing this listing. Please share it with others you know who might be interested. We look forward to hearing from you.

 

Come Work With Us! Apply by Nov 15.

You get to draw cool images like these, and invent other kinds that nobody has thought of yet.


Our firm has a fulltime opening for a transit analyst.  (Also, watch this space for a senior planner and project manager position to be posted soon!)

Here are the details:

Jarrett Walker and Associates is a consulting firm that helps communities think about public transit planning issues, especially the design and redesign of bus networks. The firm was initially built around Jarrett Walker’s book Human Transit and his 25 years of experience in the field. Today, our professional staff of nine leads planning projects across North America, with an overseas practice including Europe, Russia, and Australia / New Zealand.

You can learn about us at our website (jarrettwalker.com) and at Jarrett’s blog (HumanTransit.org). For a sense of our basic approach to transit planning, see the introduction to Jarrett’s book Human Transit, which is available online. For a typical report of ours, showing some of the analysis we do, see here.

We are seeking a transit analyst based in Portland, Oregon, or Arlington (Crystal City), Virginia.  The position offers the potential to grow a career in transit planning. As a small firm, we can promote staff in response to skill and achievement, without waiting for a more senior position to become vacant.  Everyone pitches in at many different levels, and there are many opportunities to learn on the job.

Duties include a wide range of data analysis and mapping tasks associated with public transit planning.

Required Skills and Experience

For this position, the following are requirements. Please respond only if you offer all of the following:

  • At least two years of professional experience using the skills listed in this section, OR formal training in these skills (such as at a college or university). Directly-applicable coursework is valuable but not essential.
  • Fluency in spoken English and proficiency at writing in English. In particular, an ability to explain analytic ideas clearly.
  • Understanding of basic statistics and experience with analysis and visualization of quantitative and statistical information.
  • Experience in spatial data analysis (GIS).
  • Experience working in Adobe Illustrator.
  • Experience in cartography, evidenced in at least one mapping sample that is clear, accurate, and visually appealing.
  • Availability to start full-time work in Portland or Arlington on before the first week of January, 2019, at least 32 hours per week.
  • Legal ability to work in the US.

Other Desired Skills and Experience

The following are desirable but not essential.  Candidates with the required skills listed above but none or few of these desired skills are still encouraged to apply.

If you have any of the following skills, please describe them in your application

  • Experience with public transit issues.
  • Experience using analysis programming languages (such as R).
  • Experience with qGIS, Remix or InDesign software.
  • Experience in advanced database analysis. (Postgres/PostGIS, MySQL, etc)
  • Expertise with transit-focused routing software, such as OpenTripPlanner.
  • Experience describing issues from multiple points of view, including the perspectives of different types of people, and different professions.
  • Graduate degree in urban planning, transportation, or a related field.
  • Foreign language ability. Spanish is especially useful but other language skills are valued as well.
  • Experience working with minority and disadvantaged communities.
  • Experience managing small teams.
  • Experience and comfort in public speaking.

Compensation, Benefits and Place of Work

Compensation will depend on skills, but will start in the range of $25-32/hour depending on skills and experience.  Raises of over 10% in the first year are typical for excellent work.  Our benefits program includes medical, dental, and disability insurance; a 401(k) program; subsidized transit passes; paid sick leave; and paid time off.

This position will require working out of either our Portland, Oregon, office or our Arlington, Virginia, office. JWA does allow employees to set work schedules that include working from home or other locations.  This position requires travel, to work with clients directly, at least a few times per year.

How to Apply

To apply, please send the following materials to [email protected] .

  • 1-page cover letter, explaining your interest in the position.
  • 1- or 2-page resume, describing your relevant experience and skills.
  • Links or electronic files for up to three (3) samples of your work. If possible, please include a map, a piece of writing, and a demonstration ofa spatial analysis. (A single sample may satisfy more than one of these requests.)
  • Contact information for 1 to 3 references who can attest to your experience with the skills listed above.
  • Please do not include any information about your prior compensation.

We will be redacting from your materials any explicit information about your name, race, gender, or sex.

Diversity and Inclusion

JWA follows an equal opportunity employment policy and employs personnel without regard to race, creed, color, ethnicity, national origin, religion, sex, sexual orientation, gender expression, age, physical or mental ability, veteran status, military obligations, and marital status.

This policy also applies to management of staff with regards to internal promotions, training, opportunities for advancement, and terminations. It also applies to our interactions with outside vendors, subcontractors and the general public. 

Timeline

The deadline for applying is 11:00 pm Pacific Standard Time on Thursday, November 15th. Submitting earlier is advantageous as we will review applications as we receive them.

We will ask a select group of applicants to perform a simple analysis and mapmaking test on their own, and then to join us for an interview. The test will be assigned on November 20 and due on November 27. We wish to hold interviews (in person or by phone/web) on November 29 or 30.

Thank you for reviewing this listing. Please share it with others you know who might be interested. We look forward to hearing from you.

 

Early Positive News from Richmond, Virginia Redesign

by Scudder Wagg

It’s been nearly three months since the launch of the Pulse Bus Rapid Transit line, and the bus network we helped design, for the City of Richmond and its transit agency.

The early news looks positive for ridership. For some context, the redesigned network was intended to shift the balance of the network from about 50% ridership focus to about 70% ridership focus.

Prior to the launch of the new network, weekly ridership was averaging about 141,000. The first week of the new network saw huge ridership, 226,000 for the week, but that was driven by free rides. Immediately after the launch, ridership remained near or above the pre-launch ridership levels (if you ignore the July 4 holiday week). And since August, ridership has climbed to about 157,000 per week, an 11% gain.

Any gain at this point is good news.  It’s normal for there to be a slight dip in ridership just after implementation, as people take time to adjust to the new network, and for ridership to then grow gradually over two to three years.

Some of this gain is attributable to the new partnership with Virginia Commonwealth University (VCU). VCU has partnered with the transit agency by investing $1.2 million per year in exchange for transit passes for all students, faculty, and staff. VCU was drawn to this partnership in part by the obvious value that the new BRT and Route 5 (part of our network design) provided to the University. And its willingness to invest in the service is a good sign of the renewed confidence that many have in the usefulness of transit service in Richmond.

That confidence is reinforced by the expansion of service that happened this past weekend in adjacent Henrico County. The County decided this past spring to add evening and weekend service on three routes and extend service to Short Pump, the largest suburban retail and jobs center in the region. That expansion launched on September 16.

More time and data will help make clear how much ridership growth is attributable to network design and how much is attributable to other factors. But the early signs are positive, and we hope they continue in that direction and spur additional improvements in transit for Richmond.

 

Scudder Wagg, who played a central role in the Richmond project, manages the US East Coast practice for Jarrett Walker + Associates.

What is a Spine?

A spine is a really powerful network design idea that takes a moment to explain.  This is how a spine works, in an example from the Dublin bus network redesign proposal.

[That diagram is by Dublin-based graphic designer Kevin Carter, and uses a style common in the UK.  The National Transport Authority has hired Kevin to complete these diagrams for the other six spines.   If you’re on Twitter, follow him at @yascaoimhin.]

A spine is several bus lines designed to share a common segment, with the buses evenly spaced on that segment to deliver a very high frequency.  In this case, each spine branch runs every 15 minutes all day, so the common segment is every 3.75 minutes on average.

If you are in the inner city, where all the spines are running on their common segment, you just say “take any bus whose number starts with A”.  The result is a high-frequency network map that’s easy to draw a map of, and to learn, remember, and explain.

(That image is ours, from the summary report.)

In the case of the A spine, all four branches are every 15 minutes all day so the common segment is a little better than every 4 minutes all day.

The National Transport Authority also did an animation, here.

Many, many cities have a geography where this structure makes sense.  As you move out from the centre, the area to be covered gets wider but the frequency need gets lower, so you branch.  But you make it legible.   The inner city needs an extremely frequent line that’s easy to learn and remember, so we just explain that the A-spine is made of all the buses whose numbers start with A.  Presto.  You have a simple network of inner-city lines where the bus is always coming soon, exactly what people moving around in the core need.

Once you understand it, it’s simple.  But it takes a moment to learn, and different people learn it differently.

Do We Need a New Theory and Name for “Bike Lanes”?

Important: I’m thinking out loud here!  The title is a question because I don’t have answers and am not proposing anything.

Now that we have scooters sharing bike lanes, I wonder if we’ll need to think more clearly about the different kinds of lane on a street and what their real defining features are.  This could lead to different words.

We separate traffic types for two reasons:

  • Speed, so that faster vehicles aren’t often stuck behind slower ones,
  • Width, so that we use less space to serve the needs of narrower vehicles, thus using scarce space more efficiently overall.

Sarah Iannarone and I were chatting about this on the bus this morning, and after that she went straight to the whiteboard and drew this:

The idea here is that a street with a speed limit over 30 km/hr will need to separate these three kinds of traffic, because they differ in both speed and width.  At lower speeds you can mix them more.

Where speed and width come apart, however, speed has to be the defining feature.  You can’t ride a motorbike at 30 km/hr down a “bike” lane, even though it may be narrow enough.  You have to ride it in the traffic lane, even though that’s a waste of space.

All this came up because I was trying to think of the correct new term for “bike lane” as we proliferate more vehicle types that run more or less at the speed and width of bicycles but are clearly not bicycles, such as electric scooters.  The two logical terms seem to be narrow lane or midspeed lane.  One way or another the two concepts will need to track with each other.

I wonder if this kind of language can make our sense of the role of these lanes more flexible, and thus less divisive.

There is a lot of room for individual choice here about which lane to use.  Cyclists, for example, already choose between midspeed “bike” lanes and full-speed traffic lanes, depending on their preferred balance of speed and safety.  Meanwhile, an 8-year-old learning to ride a bike should probably be on the sidewalk.  Another reason that “cycle lane” may be a misnomer.

This isn’t easy.  The things that might go in a midspeed lane have very different acceleration and stopping characteristics, all of which will cause friction.  When I raised this thought on Twitter, I got lots of responses expressing concern about different kinds of vehicles sharing a lane.  But even with just the few lane types that we already have, it’s hard to make them all fit.   We’ll never have a separate lane for every type of vehicle that needs a slightly different speed, acceleration, or stopping distance.  So again, I’m asking a question, not answering it.

Finally, Sarah assigns transit to the full-speed, widest lanes, but of course that leaves open the question of transit priority within that territory.  Where there’s demand and room for a bus lane, it should be automatic in my view.  It doesn’t even need to be “constructed” necessarily.  Just paint the lane red.

 

Why We’re Used to Some Outrage at Network Redesigns

Here are some things that happen whenever a big bus network redesign is first proposed to the public. They are happening in the Dublin network redesign process right now, but to some degree they’ve happened on every project I’ve done over my 25-year career.

  • People assume that the plan is more final than it is, so they feel they need to gather forces in angry meetings and attack us, when in fact we want their detailed comments so we can address them.
  • We consult the public about the plan and they tell us, as we’re consulting them, that we’re not consulting them. (This is an understandable consequence of the previous point; people assume they’re being told when in fact they’re being asked.)
  • People say that while we’ve consulted some people, we haven’t consulted everyone in the right way.  (This is an understandable complaint, and often a valid one, but we will always get it no matter how much consultation is done. People rely on so many different information sources, and need things explained in so many different ways, that reaching everyone the right way is a potentially infinite task.)
  • Some people hear only that “there won’t be a Route 54” and begin holding rallies to “Save the 54,” without knowing or caring what service is proposed to replace the 54.  (Sometimes we’re just changing the number!)
  • Media headlines often inflame this confusion, with headlines about bus lines being “scrapped”.
  • People attack the whole plan because one local detail isn’t right.  (Many of the details that people are outraged about in Dublin are fixable, now that we have heard about them.  That’s why we’re consulting you about it now, to help us get the details right!)
  • Unions representing bus drivers, understandably seen as experts in some circles, will often put out their own messages tied to their own interests.
  • People attack the consultant.  (It’s not the first time my tiny 10-person firm has been called “corporate.”)
  • Some sympathetic person explains to me that people in their city or country are just crazy in some way, and I assure them that no, this is what happens everywhere, from Russia to the US to New Zealand, when a proposed network redesign comes out.  Because what everyone is doing is completely understandable in their situation.

Here, for example, is a deep dive into a current network redesign in Canberra, Australia (which I helped lay the groundwork for years ago).  You will see all of the themes I’ve listed.

What’s happened next, in all my projects, is that we collected the comments and fixed what was fixable, which turned out to include most of the details that had most inflamed people.  In most cases that addressed enough concerns that the plan moved forward and was a success.  It solved the problems it was meant to solve, and once people got used to it many of them discovered that it wasn’t as bad as they thought.

That doesn’t always happen, though. Sometimes elected leaders panic at this point and stop the plan, leaving all of the existing problems in place.

For me, there’s a reason to be happy about all the controversy:  It means people care.  The least controversial projects I’ve done were in very car-oriented places where few people (and no powerful people) cared what the buses did.  I would much rather be dealing with controversy.

The key thing is not to panic when we hear outrage at this stage of the process.  While was it was especially inflamed by misinformation in Dublin’s case, it’s a normal phase in the conversation.

And again, that doesn’t mean we’re not listening. The whole point is that we are listening, so we can make the plan better.

[Note: I will be mostly away from the internet, until the 20th August.]

Dublin: We Need Your Comments!

 

The proposed Dublin bus network redesign has been out for public comment for about a month. It’s very important that Dubliners learn about the plan (there are many ways to do this) and then to comment on it before the end of September.

Sadly, a great deal of false or misleading information is out there.  Falsehoods appeared on social media within minutes after the report was posted, long before anyone could have read it.  Then, a major bus drivers’ union distributed a table that claims to describe the plan, but whose real effect is to cause needless confusion and panic.  For example, it describes existing route 140 as “gone” even though every segment of that route continues to be served, mostly at higher frequencies, in the new plan.

We’ve put out more accurate information, including a detailed route-by-route table and interactive maps that help you see how an existing route would be replaced, and how the network expands where you could go on public transport.

But of all the falsehoods being spread, the biggest is that NTA has “decided” to implement the plan.  Many people are outraged because NTA “decided on” the plan without consulting them.

The answer is:  NTA is consulting you now.  That is what the draft plan is for, to put ideas out there for people to respond to.  Nothing has been decided.  What you tell us now will guide what happens next.

So again:

  1. Read my overview of the plan here.
  2. Explore the plan here (busconnects.ie), or at one of the meetings (check back for more to come).
  3. If you have a specific objection to the plan, use the survey to explain that objection.
  4. There’s no need to attack the whole plan unless you hate the whole plan.  We may have gotten something wrong in your neighborhood, but that doesn’t mean the whole plan is a bad idea.

Again big ideas of the whole plan are:

  • a much simpler, more frequent network on which more people can get to more places sooner …
  • which requires a few people to interchange where they now have a direct bus …
  • and which sometimes requires a little more walking, though almost never over 400m.

If you hate these ideas, you should definitely oppose the whole plan.   (Look at Chapter 5 of our report if you want to understand why these things are connected. )

But meanwhile, we need everyone’s detailed feedback and comments, so that we can make the plan better.  Start here.

Is Ride-Hailing to Blame for Rising Congestion?

Throughout the past few years, the explosive growth of ride-hailing services such as Uber and Lyft have changed the landscape of urban transportation.  Proponents of ride-hailing have long argued that these services benefit cities by reducing the need for people to own their own cars and by encourage them to use other transportation options, ultimately reducing the total vehicle miles driven in cities.

Last week, a new report by Bruce Schaller suggests that these ride hailing services are in fact, adding to overall traffic on city streets, and risk making urban cores less desirable places to live. Notably, Schaller’s report finds that:

  • TNCs added 5.7 billion miles of driving in the nation’s nine largest metro areas at the same time that car ownership grew more rapidly than the population.
  • About 60 percent of TNC users in large, dense cities would have taken public transportation, walked, biked or not made the trip if TNCs had not been available for the trip, while 40 percent would have used their own car or a taxi.
  • TNCs are not generally competitive with personal autos on the core mode-choice drivers of speed, convenience or comfort. TNCs are used instead of personal autos mainly when parking is expensive or difficult to find and to avoid drinking and driving

Schaller points out that on balance, even shared rides, offered by Lyft Line and Uber Pool, add to traffic congestion.

Shared rides add to traffic because most users switch from non-auto modes. In addition, there is added mileage between trips as drivers wait for the next dispatch and then drive to a pickup location. Finally, even in a shared ride, some of the trip involves just one passenger (e.g., between the first and second pickup).

To many readers, Schaller’s report implies that Uber and Lyft are primarily to blame for the increasing traffic congestion and declining transit ridership in many US cities.  Citylab published a rebuttal to Schaller’s report, titled “If Your Car Is Stuck in Traffic, It’s Not Uber and Lyft’s Fault”.  The author, Robin Chase, founder of Zipcar, disputes the scale of ride-hailing’s impacts on traffic congestion in cities.  Chase writes:

[In major urban areas], taxis plus ride-hailing plus carsharing account for just 1.7 percent of miles travelled by urban dwellers, while travel by personal cars account for 86 percent.

Chase contends that traffic congestion is not a new problem in cities and that ride-hailing is no more responsible for it than the personal automobiles that still make up the majority of trips.

Special taxes, fees, and caps on ride-hailing vehicles are not the answer. My strong recommendation for cities is to make walking, biking and all shared modes of transit better and more attractive than driving alone—irrespective of the vehicle (personal car, taxi, or autonomous vehicle). Reallocate street space to reflect these goals. And start charging all vehicles for their contribution to emissions, congestion, and use of curbs.

On taxing or limiting all vehicles — called (de)congestion pricing — Chase is right on the theory and Schaller’s report doesn’t disagree.  From Schaller’s report:

Some analysts argue for a more holistic approach that includes charges on all vehicle travel including personal autos, TNCs, trucks and so forth, paired with large investments to improve public transit.  This is certainly an attractive vision for the future of cities and should continue to be pursued. But cordon pricing on the model of London and Stockholm has never gone very far in American cities. Vehicle mile charges have been tested in several states, but implementation seems even further from reach.

Yes, ideally, we would aim to charge every vehicle for precisely the space it takes up, for the noise it creates, and for the pollution it emits, and to vary all that by location and time-of-day. However, we have to start with what’s possible.

Ultimately, the most scarce resource in cities is physical space, so when we allow spatially-inefficient ride-hailing services to excessively grow in our densest, most urban streets, we risk strangling spatially efficient public transit and fueling a cycle of decline.  If we are to defend the ability to move in cities, we have to defend transit, and that means enacting achievable, tactical policies even as we work on building the coalitions needed for bigger change.  Reasonable taxes or limitations on TNCs are one such step.

Finally, these interventions should really be locally-focused, because like all urban transportation problems, this one is extremely localized.  Lyft wants us to think of them as feeders to transit, which is a fine idea.  But what is actually profitable to TNCs is to swarm in the densest parts of cities, increasing congestion and competing with good transit, and that’s where they do net harm.  Lyft and Uber knows where every car is at every moment, so it would be perfectly possible to develop cordon-based surcharges to focus any interventions on the actual problem.  Otherwise, it will be easy to say that by restricting TNCs in Manhattan we’re keeping someone in outer Queens from getting to the subway, which is not the point at all.

Christopher Yuen and Jarrett Walker

Dublin: How Much Could the Draft Network Change?

While our Dublin network redesign is open for public comment, I’ll be posting some frequently asked questions here.

How much change could we make to the plan in response to public comment?

In a July 18 article in the Irish daily The Independent, Paul Melia wrote that “Only minor changes can be made to a radical restructuring of the Dublin Bus network unveiled last week or it will “fall apart”.  The headline is “Only ‘minor changes’ can be made to radical plan for Dublin Bus.”

“Minor” is the reporter’s word, not mine.  I did say that if you change more than about 15% of the network it will fall apart.  But 15% is not minor.  While the plan is a dramatic change, at least half of it consists of service on streets served now, doing something much like what it does now.  So compared to the amount of the network we’re actually changing, 15% is very substantial.

Under the plan, 77% more people can get to DCU in 45 minutes, and someone living near there can get to 44% more jobs in that time. (You can find these for many point around Dublin at busconnects.ie)  But this isn’t the result of certain routes. It’s the result of a whole network of connections involving many possible routes you could use.

Why is there a limit to how much we could change the network?

The defining feature of a network the interdependence of its parts.  We did not just design a set of routes.  We designed a pattern of connections.  The connections, as much as the routes, governs how much of Dublin people can get to in a reasonable amount of time.  So we will resist changing a route in a way that destroys or damages a connection, because the connections — the ease of getting off this bus and onto that one so that you can get to more places — are the essence of how the plan achieves its benefits.

Having said that, we will make changes.  Quite possibly lots of them.  But we will be mindful of this principle when we do.