When we build our career in technology, knowing the right answer gets rewarded.
But we start not knowing the right answer.
We find ourselves in stressful situations where we need something to work. We struggle through testing, reading, asking, and troubleshooting. Eventually it works. Hopefully in time.
While we try to avoid those high stress, high profile failures, tech gives us a lot of challenges to learn from. Over time, we develop the sense of knowing where to look, what to ask, and what’s happening. We embrace the craft of technology.
Our experience informs us. When asked, we know the right answer.
Then something interesting happens.
The more we get known for knowing the right answer, the more people look to us to offer the right answer. It feels good for us, and it works for them. We offer what we know, while inadvertently hiding what it took to figure it out.
I’ve noticed that for a lot of people, knowing the right answer becomes part of our identity.
The downside of identifying as the person who knows the right answer is the silent fear of not knowing. We figure that not knowing, or worse, admitting we don’t know, somehow comes across as weak. We don’t want to let people down.
So someone asks a question, expecting us to know. We don’t immediately know, but then we don’t want to look like an idiot, either. Because we base their trust in us on knowing the right answer.
The voice in our head reminds us we know how to figure it out, if only we had more time. We’re still willing to work through what we don’t know. We just don’t want anyone else to know we’re figuring it out.
We didn’t start by knowing the right answer. We earned that ability by being willing to find out.
When did not knowing become something we needed to hide?