Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Loma Prieta, 20 years later

Freshness Warning
This blog post is over 14 years old. It's possible that the information you read below isn't current and the links no longer work.

The San Jose Mercury News is running a look back at the 1989 Bay Area earthquake. A California native, I was living on the east coast at the time, watching on TV as my beloved Giants prepared to play a World Series game.

Mark Purdy describes the stadium in the minutes after the quake.

And the cheering started. Lusty roars. Loud. The vibe was: "Hey, it’s a Bay Area series and this is cool!" But then reports reached the ballpark about the bridge and the fire. The scoreboard flickered out. Power was gone. Things grew quiet. I hiked down to the field and interviewed players, who were plucking their families out of the stands. A cop with a megaphone told fans to evacuate. The A’s team bus returned to Oakland via San Jose because the bridges were all closed.

And those bridges? Twenty years after the quake, they’re still undergoing work to make them safe for the next quake.

Debates about project design, location and aesthetics slowed the east span planning, adding to the cost. State officials initially figured they could fix the entire bridge in place, but later decided they had to replace the east span.

Political squabbles added to delays. When he was the San Francisco mayor, Willie Brown held up the east span between 1998 and 2000 as he objected that the Caltrans design for it would harm his city’s redevelopment ambitions for Treasure Island.

Twenty years and counting for the retrofit. I’d imagine there’s people who’s entire careers have been spent working on the bridges.

Recently Written

Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.