Posts about Bureaucracy
Public Spaces
HSEMA rule prevents K Street Feet in the Street
DDOT will not be holding a Feet in the Street walking and cycling event on K Street because DC's Homeland Security and Emergency Management Agency won't allow a special event with any cross traffic.
Cities around the world, from Bogotá to Paris, New York, San Francisco, Seattle, Baltimore, Miami, Portland, Chicago, Kansas City and Las Cruces, New Mexico, have held similar events, variously called Ciclovia, Summer Streets, Sunday Streets, Sunday Parkways, and more.All involve closing a lengthy segment of a street to traffic, except at major intersections, for walkers, runners, rollerbladers, cyclists and more to enjoy the outdoors, get exercise, and have fun in a way that's often not possible in cities where most public space is dedicated to motor vehicles most of the time. Often "stations" along the way provide exercise classes, bicycle seminars, health information, and more.
Last year, DDOT tried one in Fort Dupont Park to great acclaim from surrounding neighborhoods, but the true spirit of the event involves closing a street through numerous neighborhoods as opposed to using a park drive. In April, DDOT decided to try hosting the event on K Street from 7th Street to Georgetown and the Capital Crescent Trail. 7th, 14th and 17th Streets would have remained open so that cars, trucks and buses could travel between the areas north and south of the route, and the route would have run under Washington Circle allowing traffic to cross there as well.
Unfortunately, they ran into a virtual concrete bollard in the form of DC's Homeland Security and Emergency Management Agency (HSEMA). According to DDOT's Anna McLaughlin, HSEMA does not allow any areas open to traffic inside an area closed off for a special event, and DDOT did not want to create an enormous barrier across the entire city. MPD and FEMS, which participate in planning for special events through a special task force, were unwilling to budge. It's not clear if this is an official written policy or just general practice at the agency.
This policy makes no sense. This has been done in exactly this way in cities everywhere. Even Arlington allowed cross traffic at some signalized intersections for Bike DC. We have trails which act as roads closed to motor vehicles, but which periodically cross regular streets with (or sometimes without) traffic signals.
Pedestrians, cyclists, and motor vehicles interact all the time at intersections every day. We even have special electrical light-based devices at the corners to guide the orderly interaction of traffic in the various directions. If it were really dangerous for cars to take turns with pedestrians, then every intersection in the city would require concrete barriers walling off the sidewalks from the roads and skybridges or tunnels to cross. It's crazy.
Sure, complete separation greatly reduces the possibility of anything happening. Some have speculated that this rule stems from an incident a few years ago where a driver on drugs drove through a barrier into a special event and killed people. However, it's not possible to completely reduce every risk. Bicycling down a street with no cars and only two signalized intersections with cross traffic is surely safer than bicycling down a regular street with cars and cross traffic at every intersection, and people do that every day, almost always safely.
This brings to mind DDOT's response to the folks trying to organize Park(ing) Day, which turns parking spaces into temporary parks for a few hours. In other cities, organizers have done this simply by placing some temporary turf and a bench on a parking space, often with permission. Here, DDOT public space officials wanted concrete barriers on all three sides, barrels and flags at the corners, 2-foot empty spaces inside the barriers, 22-foot clear zones on either side along the curbs.In other words, to separate people sitting in the park from cars, they required enormous barricades and empty spaces, even though people come far nearer cars every day when sitting at a bus stop and have no such protections. But these security decisions aren't about reason, they're about the approving official eliminating every possible risk no matter how ridiculous and regardless of everyday practice.
If HSEMA, MPD, and FEMS hold firm to this rule, there can't ever be a Summer Streets outside a park. They should try visiting another city to see how workable this really is, or perhaps just try visiting a street corner to see that those work as well. Meanwhile, DDOT will again hold this year's Summer Streets in Fort Dupont.
Parking
"Emergency no parking" permits now online
DDOT is replacing the system of getting "emergency no parking" signs at police stations with a formal, online permit system.
The permit system lets people apply for permits, such as those to reserve curbside space for moving trucks or mobile storage units. Those performing construction can also get permits for construction areas or manhole access.Formerly, there were two conflicting ways to receive permits. Officially, residents had to go to the permit center on North Capitol Street with a formal application. That process was time-consuming, complex, and carried many restrictions along with some fees. If you needed to reserve metered spaces instead of just residential spaces, you needed several days to get in touch with the right people at DDOT.
Instead, most people simply went to the local police station. They would issue signs that you could hand-write. These signs were convenient, but carried plenty of problems for parkers. It wasn't clear where they specifically applied, or sometimes over which dates, and have no contact information or even evidence they're real. In fact, some people were buying signs at the local hardware store.
Recently, MPD stopped providing these signs and started referring people to the new online system. Currently, users have to pick up the signs using kiosks at the North Capitol Street permit center, but the site says they will soon add kiosks at the police stations as well. The site now automatically knows if there are parking meters on the block you are requesting.
Permits cost $34. If someone is moving and needs two separate locations, they have to pay twice, As they refine the system, DDOT might want to consider letting people reserve two spots each for half a day for a similar price as one spot for a whole day.
It also restricts people to reserving four parking spaces. When I moved, I needed more spaces as there were two trucks, one very long; I also was denied more by the permit center, but could easily reserve more using the police station's signs. Since few people used the old regulations, DDOT may need to tweak the rules as everyone starts following them to ensure they don't restrict people unnecessarily.
Budget
Innovation resistance at Metro, part 3: Missing the forest for the trees
Unlike many other transit agencies, Metro has resisted encouraging third party applications that help riders, partly because they perceive technology from a top-down point of view, and from unrealistic expectations because Google is big and rich. But this obsession with control and getting revenue is causing Metro staff to lose sight of the bigger picture.
Greater Greater Father-In-Law told me a story about his days consulting for health care companies. One large nonprofit hospital with a budget around a billion dollars a year decided to make some forays into establishing a for-profit arm. They created a pharmacy where patients could buy medicines and supplies. This pharmacy did pretty well, and started turning a profit. Executives spent a very large percentage of their time reviewing the performance and exploring ways to improve it.However, the pharmacy only netted about $60,000 a year. That was less than the cost of one employee. Yet this project was eating up much more of the executives' time than monitoring the operations of the actual hospital. If they could have found a way to serve the same patients with even one fewer staff member, they would have netted as much money for the hospital as the entire pharmacy project. That doesn't mean that it was a bad project, but context is more important.
There's nothing wrong with Metro looking into the possibility of getting some money. But they want to spend $500,000 to investigate this. And we have some strong evidence that $0 is the most they'll get. Even if that's not true, there's no way it's anywhere near $500,000. If Google had offered, say, $50,000 a year for 10 years, would Metro have jumped with joy? But they could make that much just by not spending $500,000 in the first place.
The biggest danger is that once they've sunk $500,000 into this, it'll be all the more difficult to then agree to release the data gratis. Right now, the debate is about doing something that costs Metro nothing, and getting a benefit to riders. After $500,000 goes down the drain, it'll psychologically shift the debate into one about whether it's right to do something that doesn't recoup the investment, despite the benefit to riders.
At last week's Board meeting, Metro's Sarah Wilson repeated another one of staff's arguments against this project: that it might cut into the money Metro gets from ads on wmata.com. But Metro only gets $70,000 a year from ad revenue on the site, out of a total budget of about $1.5 billion. That's four-thousandths of a percent of the budget, and probably less than Sarah Wilson makes.
Sure, every little bit helps, but if the $70,000 in ad revenue is such a concern, why is $500,000 acceptable for a contract just to find out about the possibility of making money? There's no way that working with Google Transit is going to reduce all of that revenue. Let's say it reduces it by $10,000 a year. Just to recoup the $500,000 would take 50 years.
Zimmerman also noted that better and more accessible trip planners could bring in more riders at off-peak times. Many buses and most trains are full at rush hour, but the commuters don't need a site to tell them how to get to work. The people who would use it are tourists visiting the area, and people riding to unfamiliar locations. A lot of that is off-peak. And every rider who takes up an empty seat on a bus is pure profit for Metro.
Anyway, Metro's real business is transportation. The ad revenue is a nice sideshow, but it shouldn't trump convenience to riders. Wilson was arguing that Metro should not help riders in order to force them to use the Web site against their will, all to protect this tiny sliver of revenue. Why not charge for the trip planner entirely? Should Metro promulgate a new policy that every train will pause for 15 seconds after it reaches a station and before the door opens, in order to force riders to look at the ads on the walls? What's the difference?
Of course, the difference is that the ad revenue is a line item on the IT department's balance sheet. If Metro gets more money in bus fares from riders who use the system because of Google Transit, they get no credit. But if ad revenue goes down, even a tiny bit, that might hit their budget and deprive them of the opportunity to hire more staff. It's a common attitude in bureaucracies and large companies alike.
The IT department clearly isn't going to see the big picture. It's the General Manager's job to do so, or if he can't, the Board of Directors. One of them has to stand up and say that it's more important to help riders and try to increase ridership on services with extra capacity than to zealously guard a tiny bit of ad revenue on wmata.com and obsess over a departmental P&L.
Next: Why Metro IT might be moving so slowly.
Government
Innovation resistance at Metro, part 1: The value of "bottom-up"
Yesterday, you saw the exchanges between Metro Directors Chris Zimmerman of Arlington and Gordon Linton of Maryland on open APIs and Google Transit. Linton wants to lock down all licensing issues before allowing new applications that use the bus position data (as NextBus does) or schedule data (like Google Transit), while Zimmerman advocated for "seeding" innovation and worrying about revenue later.
To recap, there are two issues here. First, should Metro release its data generally to developers? They've released schedule data but under an unnecessarily restrictive license, and haven't released the bus position data at all. Second, should Metro try harder to work out a deal with Google to include Washington area transit directions in Google Maps, as every other large U.S. transit agency has done?
The Zimmerman-Linton exchange very clearly illustrates the dichotomy between the "open-source" philosophy and one of centralized control, or a "bottom-up" verus "top-down" attitude toward innovation. Writer and computer scientist Tim Lee discusses this issue frequently on his blog, Bottom-up. He explains, "The last couple of decades have brought us the dominance of the open Internet, the increasing success of free software," largely in Silicon Valley, "a place with extremely low barriers to entry, a culture of liberal information sharing, and a respect for the power of individual entrepreneurs." Because anyone can just make a Web site, write software for Windows, or sell a neat electronic gizmo (unless you want to connect it to a mobile phone network), we've had enormous innovation in these areas. It's precisely the absence of a gatekeeper who approves everything ahead of time that has enabled innovation to flourish.
Bottom-up thinking upset the established order when it hit the software industry in the form of open source software, and it's even more revolutionary in an agency like Metro, which tends to approach issues from a top-down point of view. Need some new railcars? Bid out a contract. Want to create an online system to track bus locations? Bid out a contract. For railcar procurement, there's nothing wrong with this strategy. But for consumer information technology, where you don't need only one type of railcar, this approach fails to stimulate innovation.
Opening up data allows both large companies and small "garage" developers to build applications. The policies of an organization affect both, but the economic forces affecting these are very different. If a larger company is going to work with Metro, they'll probably only do it if there's some money in it, which means they're willing to spend some lawyer time upfront to negotiate a good contract. Transaction costs aren't good, but they won't necessarily derail the project entirely.
A garage developer, on the other hand, is probably doing the project in his spare time, for fun. Even if there's the possibility of making some money, such as selling the app for $5 a pop in the iPhone app store, it's not going to be a major source of profit. Most likely, those fees won't even come close to compensating the author for his or her time. If he'd put the same amount of time into working for a tech company, he'd make way more. He might even have made more working at McDonald's than spending the equivalent amount of time on the application.
This is one fallacy in Gordon Linton's admonishment that someone out there might be "lining their pockets." Perhaps sometimes that's the case, but most of the time they're lining those pockets with enough to buy a nice lunch.
Because the money is a secondary consideration at best, the transaction cost is a huge deterrent. If the developer has to even spend one afternoon negotiating with Metro, it's a big burden. To Metro, it's no big deal to put weeks into carefully assembling a deal. To the developer, the thing could have been done already. Therefore, most people won't even bother. There are plenty of neat ideas out there that could make a good app. Why build the one that forces you to waste a lot of time not programming when you can just start coding on something else? Programmers want to be programming, not negotiating with bureaucracy.
That's why the best policy for Metro is to make it very painless to participate. The Boston MBTA, Chicago CTA, Portland TriMet and others have created developer resources pages to help developers get started. Agencies need to keep well-meaning lawyers who don't understand the real costs of their involvement away from this. The best way to do that is to create a standard license agreement anyone can sign on to, one that doesn't demand payment, indemnification, or any other cost present or future.
There's a large benefit to riders of having these apps, and a very small potential revenue source. Trying to grab the revenue just kills the projects (and wipes out the revenue as well). Linton worried about people making money off bus position data. But right now, as Zimmerman noted, nobody is building any apps, period, and nobody is making any money anyway. Nobody wins that way.
Next: But what about Google and their billions of dollars?
Public Spaces
DDOT being narrow-minded, overcautious on Park(ing) Day
People and cars operate every day in relatively close proximity. People walk on sidewalks right next to moving traffic on streets without parking. People walk along crosswalks while cars wait to turn, and cars enter and exit parking garages or alleys across the sidewalk. Sometimes this proximity results in injuries or deaths, but we don't refuse to let pedestrians go in crosswalks. And as designers like Hans Monderman discovered, often the less governments try to enforce separation, the safer streets actually are.
But if DCRA DDOT were issuing permits for streets today, they'd never allow any of this. They'd require 22 foot gaps between people and cars, concrete jersey barriers along every block, and huge planters on every corner. Those resemble some of the restrictions they're trying to palce on the organizers of Park(ing) Day. Instead of saying, "great idea," DCRA DDOT officials keep telling Justin Young, Brandon Schmittling, and Chris Loos that it sounds awfully unsafe for people to sit on benches in a parking space, even buffered by cars on each side. And they're demanding ridiculous designs, including a 22-foot "buffer zone" on either end with no parked cars, concrete barriers, planters with flags, and more.

There's no need for these restrictions. Cars in a travel lane don't suddenly swerve to the right or left; if they did, they'd be jumping the curbs on many streets all the time. And, in fact, these buffer zones may make the impromptu parks less safe; with a large car on either side, if a car did veer out of its lane, it would probably hit the car in front.
The original Park(ing) Day in San Francisco, and many of its followers, didn't apply for permits at all. They just fed the meter, unrolled some turf, and put a bench down. In some cities, the laws don't specify what you can do with a parking space if you pay for it. Unfortunately, in DC, it says the spaces have to be for vehicles, unless you get a permit. That's why the organizers have asked for a permit. Instead of getting help from the government, DCRA DDOT officials responded by throwing up every roadblock — literally — that they could think of.
According to Young, they're meeting again this afternoon with DCRA DDOT to try to persuade them to allow a more sensible design, though one that still contains extra barriers for added safety:

If DCRA DDOT doesn't allow this, residents should consider just going ahead and setting up parks in spaces anyway. People take up public space without permits all the time. Sometimes, when regulators are just being far too narrow-minded, the only option is to push the envelope anyway.
Update: The officials responsible for the policy decisions are from DDOT, not DCRA. The organizers originally approached DDOT, who sent them to the DCRA permit center, which includes public space permits. However, DCRA only acts as a conduit to DDOT public space officials who actually make the policy.
- WMATA presents options for SmarTrip negative balances
- Teens and young adults aren't mosquitoes
- You know you've arrived when...
- Combine the Circulator and Metro maps for visitors
- For state legislature in Montgomery County
- For Prince George's County offices
- Navy Yard sidewalks get sustainable stormwater systems
Latest reported issues:
- Lights out at 152 Massachusetts Ave NE
- Bicyclists endangering pedestrians at George washington memorial pkwy Mclean
- Pedestrian Safety Program at 11th St NW and Pennsylvania ave NW
- Pedestrian Safety Program at Calvert St and Cliffbourne St
- Streetlight Repair at Westmoreland Circle Washington D C D C
Smart Growth
Add jobs, retail, and housing for all income levels in walkable places like
Wisconsin Avenue, Brookland, and Minnesota-
Transit
Provide more alternatives to driving by expanding Metro capacity, building streetcar lines, and speeding up buses. Grow ridership through better maps and schedules from signs to mobile devices. Read posts »
Public Space
Our roadways are our most valuable public places. Design them to accommodate safe walking and bicycling. Locate plazas and public parks to create numerous focal points for human activity. Read posts »
Traffic
Design neighborhoods around grids instead of cul-de-sacs. Avoid building new freeways or widening existing ones which only induces further sprawl. Read posts »
Parking
Drivers create substantial traffic by circling endlessly for scarce parking. Use pricing to manage curb space and dedicate the revenue to providing alternatives to driving. Read posts »
Architecture
Preserve our row house neighborhoods and beautiful architecture that engages pedestrians visually and functionally. Eschew bad modernism that turns its back on the street and the starchitects that peddle it to "make a statement." Read posts »
Education & Safety
Make our urban areas desirable places for people and families of all ages with the highest quality education and safe neighborhoods for all. Read posts »
Greater Washington
District of Columbia

















