Fixing the Fix on the Bay Bridge
![]() |
An empty San Francisco Bay Bridge. Picture Source |
Although the actual account is fictional, the facts surrounding it make it quite possible. Last Tuesday, on October 27, 2009 about 5,000 pounds of steel from the Bay Bridge came crashing down on the upper deck, as the wind blew loose a large crossbeam and a couple of tie rods (the slithering cables). Fortunately and remarkably nobody was hurt, but the incident totaled a few cars.
Here’s the irony, which is the part I always love. The structure that failed wasn’t there a couple of months ago—over Labor Day weekend, it was constructed as a remediation! Just before Labor Day weekend, engineers noticed a crack in the bridge (not something you care to see if you’re a bridge engineer) so they rallied the crews to install some “reinforcement,” just to be safe. Although they get an “A” for effort, I guess they overlooked the fact that there might be some wind over a bridge that spans the San Francisco bay (imagine that).
I was actually on the road on Tuesday at 5:30 when the Bay Bridge came falling down. I pushed off from Reno, Nevada earlier that day; I had just finished attending Confab 2009, the annual conference for the Institute of Management Consultants. The conference was awesome. My mentor Alan Weiss opened up the conference with his keynote on Sunday, giving us insights on how to thrive in this economy. He brought the house down as usual—standing ovation.
It was an auspicious time to be driving home from Reno, as I could have quite possibly been driving into San Francisco at that time. I didn’t hear about the incident until I reached home later that night, however I do remember driving by the area, and I don’t remember it being that windy. Of course, the wind was blowing a bit, but nothing terribly unusual. I remember being in Broomfield, Colorado one time, which is right between Denver and Boulder, to do some work for Sun Microsystems. I actually drove there, and when I pulled up to my hotel, the wind was blowing so hard it was difficult to get my car door open. Now, that’s windy. Tuesday in California on the Bay Bridge…not so windy. I find it odd that a moderate amount of wind was enough to shake things loose on the Bay Bridge.
Another thing I find odd is the announcement we heard the following Wednesday morning. They told us, “the bridge would be closed indefinitely.” That’s a peculiar choice of words. I think what they were trying to say is that, “the bridge will be closed until we can get it safely repaired, and we’re working as fast as we can,” however the word “indefinitely” gives off the impression that the bridge will be closed forever, doesn’t it?
We can do better than this on our compliance programs, now that we have a clear example of how not to handle this. There are three lessons we can glean from our Bay Bridge case study, which I’d like to share with you, so you don’t make the same mistakes.
The first lesson is about remediation. The apparently kneejerk reaction to the crack on the bridge was to install an adaptive control, which as I’ve stated many times before is a poor choice when other types of controls are available. I would have preferred a preventative control which would address why the bridge cracked in the first place.
The second lesson is also about remediation. As we’ve seen with the Bay Bridge, even with the best intent, remediation can backfire on you if you’re not careful. You absolutely must do benchmarking on current state before you remediate, then do another benchmark to make sure you’ve actually improved the situation! Seems obvious, but people get this wrong all the time, and actually spend money to worsen their situation.
The third and final lesson is about communication. Take some time to articulate your communication carefully. Words are powerful, and choice of words is very, very important. I’m not talking about spin control, I’m talking about accuracy. Everybody involved needs to know the honest truth, as acutely as you can project it. This bridge will probably be open in a few days; that’s hardly an “indefinite” period of time.
Uncovering weakness in your compliance program, and taking proactive steps to remediate is an enormously responsible move on your part, but you must do it right. Always strive for preventative controls when possible, test your remediation to make sure it reinforces your situation, and make sure your communication is accurate and honest. You don’t want a crossbeam coming down on your compliance efforts because of a little wind.



John Weathington is President and CEO of