Hey Reader,
Something happened recently and I can’t stop thinking about it.
I was on a flight from NYC to LinkedIn’s studios in California to film a new course.
About 30 minutes into the flight, I tried connecting to the wifi. It didn’t work, so I:
• Toggled airplane mode on and off
• Checked my settings
• Restarted my laptop
• Tried my phone
Still nothing.
I’m sitting there CONVINCED I’m doing something wrong, that everyone else is connected and I’m dumb, when the flight attendant walks by.
The passenger in front of me flags her down first.
“The wifi isn’t working,” he says matter-of-factly.
❌ Not “I can’t figure this out.”
❌ Not “Sorry, I’m so bad with technology.”
And I realized…
I had personalized an obstacle that had nothing to do with my capability.
This may happen to you all the time:
- A project gets delayed and you think: “I could have advocated harder.”
- A stakeholder doesn’t respond and you assume: “I must have said something wrong in the email.”
- A reorg shifts priorities and you blame yourself: “I should have seen this coming.”
And in doing so, you turn every challenge into evidence of inadequacy instead of just… a challenge that exists.
Here’s what I’m working on (and what I’d invite you to try):
Before you internalize a problem, ask yourself: What am I making this mean about me that may not be true?
Sometimes the wifi just isn’t working.
And naming that — clearly, objectively, without turning it into a referendum on your competence — is one of the most underrated leadership skills there is.