The Choluteca bridge

A friend shared the story of the Choluteca bridge in the Honduras. As they went about building the bridge in the 1990s, they enlisted Japanese architects to build a state-of-the-art hurricane resistant bridge.

It was a wonderful work of engineering.

Until the next major hurricane which altered the course of the river underneath it.

Alas, the bridge had to be abandoned. All those years of effort were wasted on a bridge to nowhere.

This friend shared that her reflection from the story was about the bridges she was building in her career. She intended to reflect on whether she was simply making “good bridges” that were bridges to nowhere.

It is definitely a question worth pondering.

Another one is about the adaptability of the bridges we’re building. Change, after all, is inevitable.

Three phases of good documents

Good documents go through three phases.

The first phase is when we put down our unstructured thoughts. At this stage, we can parse the flow – but it isn’t yet ready for anyone else.

The second phase is when we structure it well enough that the core team working on it understands where we’re going.

The third phase is when we frame it in a way that anyone outside the team gets it.

There’s a chasm between the final two phases. Most docs never make it to phase three because it generally requires us to completely rewrite or reframe a doc that seems to be working just fine.

But this is what experienced writers do well. They focus on the end outcome instead of getting overly attached or comfortable with any version along the way. The end result is almost always simple – especially compared to prior versions. It is why most docs don’t make it to phase three.

Simple is hard.

Wealth, measurement, achievement

“To be rich, you don’t need to make more money; you chiefly need to better manage the money already flowing through your hands.”

“Measure your wealth not by the things you can buy but by the things that no money can buy.”

Before you are old, attend as many funerals as you can bear, and listen. Nobody talks about the departed’s achievements. They only thing people will remember is what kind of person you where while you were achieving.

I’ve been sharing collections of notes from Kevin Kelly’s book “Excellent Advice for Living.”

I loved the thread in these three notes. The first talks reframes wealth in a way that focuses on what we control.

The second reframes the purpose of attaining wealth.

And the third puts the attainment of wealth and conventionally defined success in perspective.

Agreeing with the what

As we take on more responsibility, it becomes more common to find ourselves in situations where we agree with what is being said, but don’t agree with the how.

Maturity is responding vs. reacting to the how. Often, this means ignoring the how altogether – for our own sanity.

Wisdom is the reflecting on the what and ensuring the lessons from the what are learnt.

Wenn schon, denn schon

I’ve been enjoying Arnold Schwarzenegger’s autobiography “Be Useful.” I’m especially fascinating by folks who’ve done incredibly well across a range of disciplines. And Arnold’s exploits in body building, then acting, and then politics definitely makes him a fascinating study.

Outside of his incredible positive, I love the idea of “Wenn schon, denn schon.” This German phrase roughly translates to – if you’re going to do it, do it with all your effort/go all in. In Arnold’s words, “success is whole-assing whatever you do.”

It resonated.

Dear Unknown

I was emailing with a customer service alias from apparel giant Calvin Klein recently.

Every time I heard back from a customer service representative, they addressed me as “Dear Unknown.”

After one round of this, I signed off with my name just in case my email address or name wasn’t showing up in the “from” in their system. That didn’t stop them from responding with “Dear Unknown.”

I even got a survey request at the end of that chat that started with “Dear Unknown.”

It is hard to believe someone intentionally set up the system that way. So I’m assuming I’m missing some basic system limitation and that I am an unlikely edge case.

Even so, a great reminder to be thoughtful about edge cases as we design systems. These edge cases can turn out to be… ugly.