On Sunday, the Seattle Times wrote up ($) SDOT’s Employer Shared Transit Stop Pilot program, which started a week prior. It’s a good writeup, although transit nerds probably won’t learn too much they didn’t already know. From SDOT’s page:
The City of Seattle and King County Metro are collaborating with Seattle Children’s Hospital and Microsoft to conduct a six-month pilot that will allow these participating organizations’ employer-provided shuttles to temporarily share a select set of public transit stops with King County Metro buses. This pilot was carefully developed over the last two years. The pilot project will test the feasibility of allowing employer-provided shuttles to use public transit stops while minimizing impacts to public transit operations.
As someone who both cares a lot about public transit, and the space given to public transit, and also someone who uses an employer shuttle occasionally (not one in this pilot), I have a few reactions.
First, I applaud SDOT and Metro for spotting a growing trend, and proactively experimenting with a pilot program to get real-world experience in managing it. Rule changes are generally easy to reverse if they don’t pan out, and I’ll take data over endless process and waffle any day.
Second, I think there will be mixed operational results from the stops chosen (you can see a full map on the SDOT page). Some, like SB 15th Ave E @ Mercer, seldom see more than a bus every ten minutes, and an additional shuttle using the stop is unlikely to cause delays for public transit riders. Others, like SB Queen Anne @ Harrison, are very heavily trafficked. That traffic includes RapidRide D*, on which SDOT and Metro have spent a lot of money in the name of speed and reliability. A noticeable level of conflict between shuttles and transit in the peak period seems inevitable, and any resulting delays will undermine the effort and money spent on the RapidRide program.
Of course, this variety of stop profiles will yield more interesting data, and may have been an intentional part of the pilot’s stop choices, although SDOT doesn’t call it out as such.
Finally, I note the dead hand of America’s great cognitive bias in street space allocation: when a new actor arises and asks for street space, the first people whose interests are traded off are all those who don’t drive and park their own car in the public right of way. Particularly depressing is the suggestion quoted in the Times article, that “if more loading zones are freed up, officials eventually could change some of those loading zones to public parking.”
Curbside parking (as distinct from loading) is, in general, the least valuable use of space, on a busy thoroughfare in a dense neighborhood. If the primary motiviation for a permanent shared stop program is to eventually add a couple of dozen parking spaces to SDOT’s street parking inventory across the entire city, then that is a fatally worthless premise. If, on the other hand, the purpose is to make each street function better overall (e.g. can we please have a bike corral by the pilot stop at Ballard & Market?), and any negative feedback on transit conflicts is taken seriously, then this program may prove meritorious.
If you have your own scaldingly hot take on this pilot program, please share it with us in the comments, and then email it to sharedstoppilot@seattle.gov.
My email Q&A with SDOT, lightly edited, is after the jump.
* UPDATE: As pointed out in the comments, the D Line skips this one stop in Uptown. Nevertheless, it’s a busy stop for all the routes coming southbound out of Queen Anne, and SDOT and Metro have spent a chunk of money on making those routes faster and better, so I think the point mostly stands.