Opening Day

I remember a few years back, Sports Illustrated or ESPN had a list of the Best Baseball Cities. They ranked St. Louis the best. And it is a good baseball town - lots of fan support, and everybody dresses in Cardinal red at home games. But I remember being somewhat offended on behalf of Cincinnati and my Reds. Opening Day is essentially a city holiday in Cincinnati. Businesses close. I've heard school is let out. There is a parade right through downtown. Nobody does Opening Day better than Cincinnati. And I think that is a measure of how much Cincinnati loves the Reds.

This year, the Reds defeated the Cubs in convincing fashion, winning 5-1. The general consensus is that this will be a rough year for the Reds. It's been a rough few years for the Reds, actually. And I concede, this probably won't be much different. Sportswriters often comment on the Hope of Opening Day - every team is still undefeated, still in the race, this could be The Year. I don't hold out a lot of hope for this season - but I am excited because I love baseball, and my team is on the field. That is enough. Go Reds!

Language

We had a meeting today at work. This should come as no surprise - unless you're one of the folks who actually makes something for a living, you probably spend a lot of time at work in meetings, too. And, like most meeting attendees, I hate meetings. Most meetings aren't really that productive, or get monopolized by a few people that waste everyone else's time, or worse still just spawn more meetings. The meeting spawn are the worst. We say "let's take that issue offline" and then hold a "splinter session." Splinter - it always makes me think of sailing ship battles, where the cannonballs would smash the wooden bulkheads, and the splinters would fly like shrapnel, causing more harm than the ball itself.

But as I said, I am already predisposed to dislike meetings. I once was selected and directed for special training in Meeting Facilitation, and it was great. Basically, they said

• Have an Agenda
• Control who is talking
• Keep it under 30 minutes

That right there will put you a long way towards having a good meeting. On the program I'm working right now we break all those rules, all the time.

This particular meeting was interesting, because it highlights something I always enjoy. The perversion of language. That is to say, when we play games with language to avoid unpleasant consequences or get what we want. Bear with me while I explain what happened.

The meeting, which was scheduled some time ago, was a "90% Milestone Review." This means it was a session to review technical issues when a particular portion of the project was 90% complete. This particular portion or zone was unusual, in that we are only having one milestone review - most zones have 3, at 50%, 70%, and 90%. This is because this particular zone is very plain, with very little to design and review.

When we (the Government and it's representatives) received the design, we began our review and quickly concluded the design was not 90% complete. The exact phrase is it did "not meet the 90% Entrance Criteria." Fair enough. But, because of bureaucratic momentum, we still held the "90% Milestone Review," even though ALL parties, Government, designer, contractor, etc., agree that it is not 90% ready. This is where the language issue comes up.

If we call the meeting a "90% Zone Design Review" and review this design we have in our hands, we have to fail the design. That gets reported up to the Big Boss, and is a Bad Metric. Bad Metrics eventually get projects canceled. So, we're in a bind - we've got too much momentum to cancel the meeting, but if we hold the meeting it hurts the program. The solution? We rename the meeting. The 90% Milestone Review became a Government Comment Review Session. That way there's no report, no bad metrics, just a schedule slip as the "real" 90% meeting "slips to the right" to a date to be determined. That is a bad metric, too, but it is easier to hide in the recent tide of schedule slips.

This is just my personal example of the perversions of language. "Tax increase" vs. "expiring tax cuts" and "estate tax" vs. "death tax" are two famous examples. My friend Chris in Japan told me another, more grisly euphemism, "human accident" for suicide-by-subway in Tokyo. Euphemisms, misdirection, obfuscation... all just games with language. Kind of fun, if you can step back from it. I'm still too close, I think - I still have to set up and run the "real" meeting in a few weeks, probably. It will be funnier after that.

Executive Decision

A personal parallel to the presidency.

When asked his reason for refusing to allow his aides to testify under oath, the President has invoked "executive privilege." The idea that his aides can't speak freely if they think they'll be forced to testify about their advice and discussions. This idea is often ridiculed. It isn't mentioned in the Constitution, but many Presidents have insisted it is a necessity to maintain a coequal branch of government.

I've always thought if had the whiff of BS about it. Why would you want to keep something a secret if it was legal, or part of a reasonable discussion of how to govern? Sunlight is the greatest disinfectant and all that - opacity only benefits the corrupt. Transparent government will always be just, and rule best.

In a happy coincidence, though, a very similar situation has developed at work. I cannot go into too much detail, but I can generalize some. We are the government's agent, acting in the interest of the Navy. In this role, we pursue the Navy's interests dealing with the shipyards. We review the detail designs provided by the yard at a series of milestones, sending comments back to the yards. At a recent informal, collaborative review session, one of our Navy team members said "this model is crap, it is not adequate for this 90% Complete Milestone." Or words to that effect.

This Navy team member got written up. His comments percolated back to the shipyard, and up to some VP-type, Inner-inner Circle Executive. And his comments were not well recieved, apparently. So now we've recieved direction that our informal, collaborative meetings will be GOVERNMENT ONLY so this kind of thing won't happen again.

This annoys and disappoints me in a few different ways. First, and not to be self-aggrandizing, I invented these meetings. I suggested them, I came up with the scheduling and the basic format. It bugs me that now the folks On High are telling me how to run something I run and is entirely my creation. More importanly, it betrays one of the basic guidelines for this process. These reviews were supposed to be a collaborative process, where the government, contractors, and shipbuilders worked together to improve the design and make the best possible ship for the price, for the schedule, and for the mission. Now we have to begin cutting some people off our invite list, to avoid saying the wrong thing in front of them. That means less eyes on the design, acting as a team. It promotes the kind of antagonism that seems to poison so many contracts. It means the shipyard is now our enemy, instead of our partner.

All of this leads me to a few conclusions. First, I see more clearly why an Administration would fight for Executive Privilege. Not just to cover up illegal or unscrupulous acts (though that may be a major factor) or to win a intragovernmental pissing match. But to actually keep doing the job. If we don't restrict the working sessions to the Navy personnel, they won't happen, and that hurts the quality of the work. And if the Administration was completely transparent, they couldn't say some things without stepping on some political toes. It may not be that the ideas are illegal or immoral - they would just piss off powerful representatives and senators, bogging down debate and snarling the already molasses-slow process of democratic government. Second, though, this reaffirms my belief that everyone's job - on this program, in government, maybe everyhere - would be easier if we could just check our egos at the door. The engineer who got written up hadn't done anything - he merely stated an opinion. How is that a problem for the yard? I'm convinced the VP-type was just offended personally, when the engineer was just offering a (bluntly phrased) assesment of the design from the yard. If you train people not to give their honest assessment and rubber-stamp things, you get spectacular engineering failures (Tacoma Narrows, Challenger, Kansas City Hyatt, etc).

For a great book on those incidents and the subject of failure due to lack of good advice and analysis, see To Err is Human by Henry Petroski.

AEF

This morning, I read about the passing of one of the last 6 American veterans of the Great War at age 109. A long, hearty life. It is an interesting time, as the last firsthand witnesses to a great historical event leave us, and we are left only with artifacts and records. This is a loss, but may also herald a new era of scholarship on the subject. I, for one, welcome that. In all of my formal education, I was never taught about World War I. I was told that it happened, the approximate dates. Of course, my history classes covered World War II, and World War I would be mentioned as part of the prologue. Name-checked, with the Treaty of Versailles occasionally cited as a cause of the second great conflict.

In my own reading, I've come to recognize this as a terrible oversight. The world was changed so profoundly by World War I. It sounded the death knell of the Victorian Age, sped the decline of the British Empire, gave rise to the Soviet Union. So many changes that shaped the century to come. I've ranted before about how each historical event is informed by those that came before, so there's little point in ranking them or prioritizing them. And I maintain that arguing about the ranking of events is foolish and pointless. That is not to say that some historical eras and events aren't particularly important and demand study. The Great War is one that, in my education at least, fell through the cracks. Perhaps it's passage from Living History to only recorded history will promote study and education.

I don't want to come off as overly didactic, stuffy, or preachy. I've always felt at ease tackling historical topics, absorbing facts and forming opinions, sometimes even learning the historical lessons. And that is not the case for everyone, and you can get along fine without being familiar with the causes of the War of 1812. I know there are topics I want to learn about, but still struggle with. Probably the foremost was also brought home to me today: philosophy. Slate ran a piece on Sartre, so in the spirit of exploration, I decided to tackle existentialism... on my coffee break. It was like clawing at meringue - I simply could not get any purchase on it. Which was frustrating, since I have no difficulty with the closely related moral and ethical theories. It just seemed so pointless, so much ivory tower-building and foam.

But I'm going to stick at it. I was talking with Sarah this morning, with regards to her rowing crew again. It sounds like she is doing quite well, though she said "my muscles doth protesteth." I replied "if it was easy, everyone would do it." The difficulty is what makes it worthwhile. I'm going to follow my own prescription, then - my mind doth protesteth, but I'll keep trying. If it were easy, everyone would do it.

Perdicaris Alive or Raisuli Dead

In the newspaper today I read about the US Navy's exercises in the Persian Gulf. Military exercises like that, in a areas where tensions are already high, is historically dangerous. Students of the Cold War will recall ABLE ARCHER 83, when the Soviet Union mistook a particularly large NATO exercise for the prelude to a nuclear first strike. Playing war games in troubled regions is playing with fire.

Of course, the exercises seem to be a response to the recent arrest/kidnapping of British sailors by Iranian forces. This incident recalls two historical parallels: the Perdicaris Incident and the Japanese kidnappings by North Korea. Neither are perfect parallels - Perdicaris was kidnapped by a Moroccan rebel in an attempt to blackmail concessions from the Sultan. And while the North Korean kidnappings were state-sponsored, they did not involve members of the military. But there are enough similarities that some lessons can be learned.

It appears that the UK is applying a solution along the lines of Teddy Roosevelt's. Some saber rattling, some increasingly tough talk. But behind the scenes, the senior partners in the alliance (Britain and France then, the US now) applies pressure for a more diplomatic solution. At least, I hope that parallel is valid. It is popular for many wags and pundits to speculate that the Bush Administration is spoiling for war with Iran, and this is a gift-wrapped excuse. I sincerely hope that is just that, speculation. One of the few ways to worsen the state of affairs, with one war stalled and another rapidly spiraling downwards, would be to add a third. Though I guess it would geographically unify our trouble spots - turn 3 medium wars into one big war! It's always smart to buy wholesale instead of retail.

To be honest, I am somewhat surprised by the restrained response to the abductions. In days past, capturing sailors of the Royal Navy during peacetime would have met with swift, direct reprisal. Remember the cover of Newsweek in 1982, as the Falklands War was beginning. Granted, that was an invasion, not a merely abductions, but the pugnacity of it, the real feeling in Britain that "this will not stand, and we will fight." I don't get that sense, possibly because most everyone understands the precariousness of the situation. Another Iranian hostage crisis, but now Iran is nearly nuclear; with wars to the East and West. It's just a hot bottle of trouble. Perhaps the Blair government can do what the Carter Administration did during the last hostage crisis. "Do a diplomatic deal with us while you can, because the guy taking over in a few weeks is crazy, and will bomb you into the stone age without hesitation. It's Morning in America!"

A more (darkly) humorous take on the incident here.

Corridor

I've written about this before, but it is still striking. I had occasion to take a walk down M Street today, going to the Navy Yard. This was the exact same walk I once took daily 6 summers ago, when I was an intern at NAVSEA. I've remarked before on how much this part of DC has changed. Once, it was nothing but abandoned row houses, muffler shops, and empty lots. But since NAVSEA moved in, office towers have been springing up. There's a hotel and condos now. An excellent website, Near Southeast, catalogs these developments.

Probably most symbolic of the changes is the new ballpark. I can see it going up from my office window. Just last week, a new portion of the upper deck blocked off my view of Coast Guard Headquarters forever. There is a lot of talk of how the stadium will anchor development, a "ballpark village." I'm not so sure - I think it will be fairly lively... 81 days a year. Down the street, the Nationals' owner is putting up an office tower, which is where the webcamera that took the above picture is installed. On the roof, the national ensign is flanked by the District flag and a banner bearing the curled W of the Nationals. It is distracting - right outside my window, flapping in the breeze, reminding me that baseball season is so close.

I think that office tower, and all the others like it, will have more impact on the neighborhood. Probably the biggest change to the area, after NAVSEA, is the new Department of Transportation Headquarters. Seven thousand people are moving in soon, and they will be here 5 days a week. That means more food services, more traffic, crowded Metro trains, more everything. The District is creating a second downtown.

Washington is surrounded by the infamous Beltway, but it is divided by the less well known Southeast Expressway. This highway runs from the old Long Bridge Potomac crossing near the Pentagon, then east across the city, just south of Capital Hill, terminating at Pennsylvania Avenue where it crosses the Anacostia. Almost the entireity of SE and SW Washington are walled off from the rest of the city by a raised expressway, similar to the erstwhile Central Artery in Boston. The central business district of the District is K Street. But for a number of reasons, another is slowly growing here in Southeast. In a few years, everything that exists in Downtown will exist here on M Street SE, in miniature. Numerous office and condominium high-rises, cultural centers, major federal headquarters, etc. It is a novel experience, watching as a new neighborhood is created, essentially from whole cloth.

I have to wonder if there is a better way, though. Not that there is anything glaringly wrong with the new Southeast, or even the existing Downtown. But it is being done in a fairly piecemeal fashion, each owner developing their plot as they see fit. Though I don't necessarily think a centrally plan would be any better, a scheme, a guide, an aesthetic, might be helpful. DC is more than just its monumental core. In addition to it's massive public spaces and institutions, it must have all the parts of a modern, working city. But with so much space given over to government facilities, the Mall, Rock Creek Park, the Smithsonian (all on prime, central real estate), and prohibited from building skywards, the city must be especially efficient with its design and use of space. Otherwise, more people will move out to Rockville and Manassas, and work in Bethesda or Tyson's Corner. The challenge is to grow as a livable, working city without losing the character that makes Washington completely unique. And with its heightened pace of change, the M Street Corridor exemplifies that struggle. I think it would be wise for citizens of other growing cities to watch what happens in DC very carefully.

If Washingtonians want to look for an example to follow, I don't think they need look much farther than across the river. Arlington has been very successful in creating a core around the corridor from Rosslyn to Ballston, along the Orange Line. Towers rose near the metro stations, surrounded by restaurants, shops, and services, trailing off into the residential single family homes. I think M street from the Waterfront to the Navy Yard has similar potential, and the District should move now to encourage that, regulating enough to maintain a "sloping" neighborhood from towers to townhouses.

I can't say why I find this interesting - I don't actually live in DC, and once this assignment is over, I won't work here either. But complete makeovers of entire sections of major American cities are unusual events - the only larger recent occurrences I'm aware of are the Big Dig, the reclamation of Stapleton Airport in Denver, and Ground Zero. Each has taken a different approach, so the comparison should be valuable to the next generation of city planners. But its value to me, and most readers, will be as an intellectual exercise. How do you redesign a city?

Dirty Trick Bomb

The above "ad" has been making the virtual rounds via YouTube and the like recently. Leaving aside the merits of the ad itself, I'd like to take a look at the response. Specifically, the quote at the end of this article.

"It's not perfect," Sifry said. "It would be better if the person who made this was open about who they are so we can judge fully whether it is genuinely a piece of voter-generated content or a dirty trick."

I find that distinction very interesting. Why is the ad more important if it is "voter-generated" vice a dirty trick? The ad, in its fashion, articulates an argument. Where the argument originates doesn't affect the validity of the argument. This is a classic case of confusing the message with the medium. Like refusing to buy Volkswagens because the original was a product of Nazi engineers. The cars have value, regardless of their designers.

It is conventional wisdom that partisan dirty tricks are undesirable. Now, depending on your definition of dirty tricks, you may agree or disagree with that position. But every idea can be evaluated on its own merits. If you inform yourself, most dirty tricks are quite transparent. Nevertheless, what if a "trick" contains a valid point? Is it invalidated simply because it was articulated by a partisan source? I submit that it would not.

A²+B²=C²

Is just as valid whether it was first posited by the enlightened Pythagoras or one history's worst villains. The Illiad and The Odyssey are great works, whether they were truly written by a blind man named Homer or are actually the accumulated work of generations of poets. And this little film can have a argument with merit, regardless of who made it. We should give all ideas the same benefit.

By the same token, we must take care not to conflate people we like with their bad ideas. That is to say, hold everyone accountable for their ideas, but don't give the idea credence just because you have a positive impression of the person. Ideas, especially debated ideas, need to be evaluated dispassionately. If an argument is sound, it will hold up to scrutiny, no matter who makes it.