Book Review: Overcoming Imposter Syndrome

I was quick to read “Overcoming Imposter Syndrome,” the new electronic book by one of my favorite bloggers, Elizabeth Harrin, as soon as it became available in Kindle format.  If you’re not familiar with the term, Elizabeth quotes Judith Beck: “It’s that sense that you don’t fully know what you’re doing and that you have fooled other people into believing that you are more competent and talented than you really are.”  Of course, it isn’t really a medical condition, and Elizabeth hastens to explain that she isn’t a trained medical professional.  But the phenomenon is real enough, and Elizabeth lists five symptoms, as well as a self-assessment checklist by Geoff Crane, another blogger I follow.  She also references research by Drs. Pauline Clance and Suzanne Imes into self-esteem, and lists four behavioral characteristics that seem to contribute to feelings of Imposter Syndrome.

Then Elizabeth lists ten strategies for overcoming Imposter Syndrome.  Some of them, such as reading widely, networking, and publishing your writing, are all excellent strategies for improving your knowledge base, capabilities, and resume.   Other strategies address self-esteem: understand what motivates you, challenge yourself, have confidence, accept that there is always someone better than you, and remember that other people don’t notice.  But at this point, I started asking, “What if I haven’t tried to fool other people?  Why should I feel guilty for being who I am?”  As Geoff puts it, “Remember that you’re not a fraud until you do something fraudulent.”  Her last two strategies consider both sides of that question: fake it, and recognize when you should feel like a fraud.  Note that she’s not advocating we misrepresent ourselves; she’s merely advocating for confident behavior, without crossing any ethical lines.

In one way or another, these strategies all attempt to de-legitimize the feelings of inadequacy and guilt, based on the idea that Imposter Syndrome might have some basis in objective reality.  And I think that’s the concern I have with this approach: it seems to accept the notion that we need to be at the upper end of the Bell curve.  In truth, half of us are below average, at least in a normal distribution.  Shall we assume that those folks should feel inadequate?  Wealth is not the only measure of personal success, and neither should knowledge and demonstrated competence on the job be our only driver of self-esteem.  I’d add a few strategies: find your sources of joy and cultivate them, try to understand what people like about you, and change something about your appearance that will make you feel good.  And address your “soft” skills: work at improving your ability to influence others, to be a better listener, and to be a calming influence.  There are a lot of ways to add value, in and out of the workplace.

Of course, I’m not a trained medical professional, either.  But after four decades in the work force, I’ve come to understand that competence and talent isn’t everything.  And the smartest guy in the room isn’t always someone I want to emulate.

New PM Articles for the Week of January 2 – 8

New project management articles published on the web during the week of January 2 through 8, 2012.  We read all of this stuff so you don’t have to!  Recommended:

  • Ty Kiisel shares some memories of getting commitment from his team.
  • Andy Jordan shares his vision of self-selected project teams.  No, seriously!
  • Elizabeth Harrin interviews Josh Nankivel on “what a coach does.”
  • Jorge Valdés Garciatorres says we need to manage stakeholders by developing relationships with them.
  • Patrick Richard is still skeptical after reading the special report on Agile in the latest issue of PM Network.  “I’m not saying it doesn’t work; I’m saying prove it works.”
  • Mike Griffiths shares his presentation on Smart Agile Metrics, along with a great quote from Einstein on what can be counted, and what counts.
  • Peter Saddington reports on research by Fergal Glynn, who found evidence that software developers write their worst and most buggy code between October and November.
  • Shim Marom applies lessons from Daniel Kahneman’s recent book, “Thinking, Fast and Slow” to project management.  Specifically, when is “professional intuition” a valid tool?
  • Paul Bruno draws some interesting project management lessons from the Battle of Gettysburg.
  • Girish Despande expounds on the Three Sisters of Project Management: knowledge, experience, and people skills.  My initial reaction: corn, beans, and squash?
  • Bruce McGraw considers when to ask for help.
  • Johanna Rothman explodes Management Myth #1: 100% utilization.
  • Glen Alleman explains, once again, what earned value is about.
  • Craig Brown shares a story about a project that began by visualizing a workflow, and essentially reached their goals while collaborating over the diagram.
  • Kerry Wills argues for “living documents,” as opposed to simply storing a series of updates.
  • Derek Huether tells us how to claim PDU’s toward renewing your PMP credential, if you’ve let your membership in PMI lapse.
  • Bas de Baar on Sensemaking: “When Columbus set out to discover America, he didn’t have a map that had America on it. That was the whole point of discovering it.”  Whoa …
  • Bruce Benson says, “Project management consists of change management and risk management.  Everything else is an application of these two concepts.”  Whoa …

Enjoy!

Living and Working With My Inner Eighth Grade English Teacher

I don’t have an inner child.  In point of fact, I am a child; I just happen to have a lot of seniority.  But I do have an inner eighth grade English teacher.  And lately, he’s not amused.  He sees the way English speakers abuse the language when they write, and he wants to hand out lousy grades.  Or at least, he wants to correct their grammar and spelling.  But what drives him to distraction is the way otherwise intelligent people write simple declarative sentences padded with colloquialisms that add no value, or word combinations that “sound like” the words which they should use.

“I’m going to try and quit smoking.”  No, you’re going to quit smoking.  Or you’re going to try to quit smoking.  But not both!  Search for “try and” and replace with “try to.”  You can safely “replace all,” because there is no circumstance in which “try and” is correct!

“In the event of failure, get ahold of the support desk.”  Get ahold?  Get a grip!  You should contact technical support.  I thought this was a “Texas thang” until I saw it written by an author from Boston.

“You should of contacted the system administrator.”  No, you should have contacted the system administrator.  If you decide to use the contraction “should’ve,” I’ll look the other way.  But there is no “should of,” “would of,” or “could of.”

“When I went to open a new application, the system froze.”  No, you didn’t go anywhere.  You attempted to open a new application.  I manage to ignore this sort of thing when people say it in a conversation, but there are limits to my tolerance.

“We plan to keep on using Microsoft Project.”  No, you plan to continue using MS Project.  That old blues song lyric, “I’m gonna keep on keepin’ on” is only effective because it’s wrong.

It’s difficult sharing my otherwise easy-going personality with a strong-willed alter ego.  Medication hasn’t helped.  Scotch seems to work fairly well, but it’s difficult to justify four fingers of single-malt when I’m reviewing a draft project document.  Consequently, I’ve had to find ways to channel my inner eighth grade English teacher’s energies.  I let him find ways to focus the narrative; some descriptions are improved just by changing the order of the sentences.  Sometimes, I give him a chance to improve a list of bullet points by putting them in a common structure.  Other times, I let him re-write a painfully worded paragraph.  It keeps him from outright rebellion, without annoying my colleagues and clients.

And now, if you’ll excuse me, I’m going to redline The Lord’s Prayer …