Skip to main content

Overcoming Imposter Syndrome

Imposter Syndrome is a cruel partner in your professional journey.  If you're not familiar with the term, it is essentially the feeling that you do not belong in a particular profession or that you do not deserve a specific role or set of responsibilities.  (You may read more in the Wikipedia article.)  I did not hear the term myself until I participated in a mentoring group for young employees at my current job - some of the young employees said they had this, and I won't deny a bit of surprise when I read what it is.

If you feel this way, you're obviously not alone.  A good friend of mine suffers from this in no small amount in spite of the fact that she's an upper mid-level manager at her company with an organization of approximately 40 people reporting to her.  She feels this way because she never completed college, but fails to realize that her hard work and dedication to being the best that she can be is why she has been repeatedly promoted through the ranks of her company.  She constantly calls herself a hack or someone who has only been successful in avoiding being "voted off the island."

Personally, I have a very specific opinion on this subject:

  • You are not allowed to feel this way.
  • You are not inadequate.
  • You are not undeserving.
  • You are valuable.

If you doubt me, consider my earlier blog entry on Business Impact.  In that article, I said:

"...business impact is therefore the journey from the current state to the future state.  Put another way, any activity that advances the journey in the correct direction toward the desired future state is considered to have 'business impact.'"

When looked at through the lens of your current employment or your current set of responsibilities, you have to understand that you were given your current role or hired into your current job after a purposeful decision was made that was based on the perceived business impact that you would have.

In other words, you're where you are because you deserve to be there.  You have the skills, talents, and experience to succeed in your role, to move the business in some way so that it's closer to the desired future state.

Let me give you another example:

At my current company, applicants who wish to become Solutions Engineers have to pass a three part interview process: the first two parts are interviews with the hiring manager and one of their peers or key members on their team.

The final part involves executing a miniature sales cycle that lasts two weeks.  During that time, you not only have to conduct a discovery session with a fictitious CIO (via role playing) but then you have to create a fully functioning solution to the use case given to you using technology that you've had no prior exposure to and present that along with a full slide deck establishing context, business impact, and quantifiable conclusions at the end.

This is not a small task.  At the beginning of it all it is overwhelming.  But even after people succeed and are hired, they still feel like they don't deserve the job.  They ignore the amazing accomplishment that they've just completed and focus on what they feel makes them inadequate because they are comparing themselves to people who have been at the company for 5, 10 or more years.

Recently, a good friend of mine, award winning composer Chance Thomas, recently posted some thoughts on overcoming Imposter Syndrome.  I've quoted a snippet of those thoughts below, which start with a translation of a poem called The Great Yes by the poet Constantine Cavafi:

THE GREAT YES

   To every man there comes a time,
   When he must declare the Great Yes.
   He who has the Great Yes burning inside,
   Immediately reveals himself.
   And so saying…
   On he goes, to the victory.

I was struck by the idea that we human beings can develop a positive internal awareness which grows to become so radiant, so vibrant, so inescapable that everyone around us immediately recognizes our competence, without internal dissonance. Brimming with the Great Yes, such a person progresses naturally, perhaps even inevitably, to success.

This is the opposite of imposter syndrome. 

Develop that positive internal awareness by trusting in the decision to hire you, to promote you, to give you that extra project.  It wouldn't have happened if those who made the decision didn't believe in your ability to succeed.

Popular posts from this blog

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mobile applica

#FailOps

Many years ago, Oleg Vishnepolsky and I worked together at IBM's T. J. Watson Research Center on the OS/2 1.1 port of the TCP/IP protocol stack.  Recently, I had a conversation with Oleg, who is currently the CTO at The Daily Mail Online, about DevOps and how it seems companies miss the whole point of what DevOps promotes.  During our conversation (via email), it came out that he was of the opinion that DevOps is not a successful paradigm to follow and asked me for my thoughts on the matter.  I decided (with his permission) to publish the conversation because it seems that a lot of people are of a similar mind when it comes to DevOps (just as there were similar attitudes when the OGC released ITIL in the late 1980's), and while I do agree that many companies are not seeing the benefits of DevOps that it is supposed to bring to an organization, I don't believe that the problem is with the paradigm.  Hopefully, my answers to Oleg will not only clarify why DevOps is import