The Weakness Question

There is a leadership question I have never liked, even though I understand why it it continues to be asked: Tell me about a weakness.

I have been asked some version of it in interviews, development conversations, talent reviews, reference requests, coaching settings, and the occasional networking conversation where someone wants to skip the pleasantries and signal that we are now in “serious territory”.

Usually, the question arrives with a certain familiar tone, almost as if everyone involved already knows what kind of answer is supposed to come next. And yet, every time, some version of the same reaction rises in me.

Ugh.

Or, if you prefer a more descriptive word: resistance.

I get the ick, not because I think I am above development, nor because I lack flaws (far from it). And most assuredly not because I believe self-awareness is optional. What I resist is the question itself.

The question sounds rigorous and like the sort of thing leaders and thoughtful interviewers are supposed to ask. But the more I’ve examined it and the resultant answers over time, the more I believe that asking for one weakness is less evidence of developmental rigor than people assume.

The question often assumes, or at least steers the conversation toward the assumption, that strengths and weaknesses are discrete, portable traits.

In other words, the question implies that a person can reach into themselves, pull out one cleanly bounded deficiency, label it accurately, and hand it over as evidence of self-knowledge. Maybe sometimes people can do something close to that. More often, however, I suspect that they are producing a socially acceptable answer to a familiar script.

I don’t believe that people have neatly isolated strengths over here and neatly isolated weaknesses over there, all sitting outside of context waiting to be cataloged. I believe people have behavioral tendencies. They have recurring instincts, preferred ways of operating, familiar patterns under pressure, and certain moves they reach for faster than others. And those tendencies can create enormous value in one context and inhibit — sometimes destroy — value in another.

I.e., the same reflex that makes someone effective with one team under one set of conditions can make them distinctly less effective elsewhere, for example:

• A person may be decisive in a crisis and bulldozing in a collaborative process.

• A person may be deeply reflective in strategy work and frustratingly slow in fast-moving execution.

• A person may be empathic and trust-building in one environment, then conflict-avoidant and too indirect in another.

• A person’s high standards can look like excellence (detail-oriented) in one moment and like exhaustion (micromanagement) in the next.

• A person can naturally display confidence, which can create steadiness here and, under a different setting, hubris there.

And so on…

So when someone asks me to name one weakness, my instinct is almost always to ask a different question back: Under what context?

I wrote about this many years ago and then covered it in more depth in my first book, Big Things Fast, as “strengths and shadows”.

The shadow side of a strength is what shows up when a useful tendency gets overused, misapplied, or carried too far into the wrong environment. The problem is not always the tendency itself. The problem is often its rigidity, its overextension, or its lack of fit.

This is why I am skeptical of the traditional strengths-versus-weaknesses framing. It may be a convenient shorthand, but it often flattens a more useful perspective: that much of what gets labeled a weakness is actually an overused strength, a context-misaligned tendency, or an adaptive behavior that no longer fits the moment.

That strikes me as a much better place to start versus a tidy — and often contrived — pseudo-confession.

It is also why the “one weakness” question can create a false sense of developmental rigor. It rewards people who can narrate themselves neatly and privileges clean self-description over pattern recognition. It sounds like rigor while reducing the person into something more compartmentalized than they really are. What gets praised in those moments is not actual self-awareness so much as the ability to package self-awareness.

Again, I am not arguing for softer development. If anything, I am arguing for development that is harder, more accurate, and less satisfied with reduction.

Real self-awareness is not the ability to name a flaw on command. It is the ability to recognize your own recurring patterns, understand the contexts in which they serve you well, notice when they begin to cast a shadow, and adjust accordingly.

Net, if the “weakness” question is not especially useful on its own, the more important question becomes what should replace it. That is, what should leaders, interviewers, mentors, coaches, and reflective professionals ask instead if they actually want a more accurate picture of development?

Equally important, how would you answer the question? Would you answer it differently in a different context?

See what I did there?