My Dad learned how to water ski when he was very young. Every year for the past 60+ years, he’s made water skiing a part of his summer vacations. He has taught many family members and friends how to ski. One of his favorite sayings we heard repeatedly as we were growing up was “If you don’t fall, you’re not trying.” Considering how many times he went to the hospital due to his deep passion to get better at things, my sisters and I rephrased it as “If you don’t bleed, you’re not trying.”
I think we’ve all heard that you learn more from your mistakes than your successes. A piano player repeatedly playing a perfect “Happy Birthday” will never suddenly have the ability to play Chopin flawlessly. Our ability to do hard things only comes from failure. To play Chopin flawlessly, you must first play it terribly and learn from your mistakes.
That which does not kill us, makes us stronger — Nietzsche
Success is dangerous to learning
The early days of our professional careers are filled with mistakes and learning. “Can you explain that? I’m new here” is a pretty easy statement to make when you were hired 3 weeks ago. Those first weeks and months stretch our ability to perform, and we drastically improve our productivity as we enter each situation with an open mind.
Then we have a success or two. Someone compliments us on a presentation, or a particularly insightful bit of code. Success is awesome. It feels great. We love the confidence it gives us when we hit something out of the park. When we have success at work, it gives personal satisfaction. It gives potential career growth. It gives us security in our position. It also can be self-defeating.
I’ve seen this pattern a number of times. An employee gets comfortable with their current tasks. They confidently resolve similar tasks at a consistent rate over time. They know how to do these types of tasks. They are reliable at those tasks. However, they don’t pick up harder tasks. They don’t pick up new technology. They don’t try new ways of doing things. They want to play the exact same song, forever.
In interviews, I always give time for questions at the end. I’ve regularly had experienced engineers ask “Which coding language will I be using?” This might be related to their curiosity about which technology their area of Amazon is using. I’ve also had it asked with the added context of “I only know how to code in Java, so I want to make certain I’m going to be using Java in this job.”
When you have been seduced by success into wanting only success from now on, you’ve tied an anchor around your own neck. Unless your job allows you to mechanically execute the exact same thing for the remainder of your career, growth and failure is required to succeed and thrive.
This post is for subscribers only
Sign up now to read the post and get access to the full library of posts for subscribers only.