Weakness Reframing

A VP of engineering is preparing for a promotion case to SVP. In coaching she has described her three biggest weaknesses with significant certainty: she is 'too technical to lead at the executive level,' 'not a natural communicator,' and 'too detail-oriented for strategic work.' These are stated as facts, not hypotheses. Her coach has observed that she demonstrates strategic thinking in sessions, communicates with precision and impact in written form, and has built a technically excellent organization. The self-assessment does not match the evidence, but the beliefs are treated as settled.

The tool's constraint is the entry point — two situations per weakness, not one. 'What I want to do with the weaknesses you've named is look at them more carefully — not to convince you they're actually strengths, but to see whether the story you've built around them is complete. This exercise asks you to find two specific situations where each weakness could serve a purpose. One reframe is usually manageable; the second one is where you have to look harder. That second situation is usually where the most interesting information lives.' The specificity requirement prevents the exercise from staying abstract.

Watch whether she can identify both situations for all three weaknesses, or whether one weakness resists the exercise entirely. The one that resists — where she genuinely cannot find two useful contexts — is often the one most closely tied to an identity belief rather than a behavioral pattern. Also watch the language in the situation descriptions: if she describes 'situations where this could theoretically be useful' rather than 'situations where this actually serves a purpose,' she is hedging. Push for real examples from her actual professional history, not hypothetical ones.

After completing the table, compare the situations she identified to her actual role context. 'Looking at the situations you listed where your technical orientation serves a purpose — how many of those are present in the SVP role you're preparing for?' The answer is usually 'several,' which creates a cognitive dissonance with the original 'too technical for executive leadership' belief. Then: 'What do the new facts you wrote at the bottom tell you about where each weakness actually belongs — and where it doesn't?' Move from the reframe to the practical question of fit and positioning.

A senior manager at a financial services firm has a pattern her coach has observed across multiple sessions: she opens cross-functional presentations and high-stakes conversations by disclosing what she doesn't know or can't do. 'I'm not the finance expert here, so take my numbers with a grain of salt.' 'I tend to be overly cautious, so don't take my hesitation as a signal the project is in trouble.' She believes this demonstrates humility and builds trust. Her peers and senior stakeholders read it as low confidence. The pre-emptive weakness disclosure has become a conversational habit that she cannot yet see as a liability.

The tool gives her a way to examine the pattern without directly challenging the humility rationale she holds. 'The behaviors you've named as weaknesses — caution, not being the domain expert in finance, your hesitation as a signal — let's look at those more carefully. This exercise asks: in what specific situations is each of these a genuine asset? The discipline is to find two real situations per weakness, because if two exist, then the weakness isn't a fixed liability — it's contextual. That changes how and when you disclose it.' The contextual reframe is less threatening than 'stop saying that about yourself.'

The most revealing part of this exercise for her will be the Reflections section at the bottom, particularly the prompt about whether her perceived weaknesses are liabilities or assets in her current environment. If she can identify that 'caution' is genuinely valued in her regulatory environment and her pre-emptive disclosure is unnecessary there, the disclosure habit loses its justification. Watch whether she arrives at this herself or whether she needs the question framed explicitly. The insight is more durable if it's self-generated.

After completing the exercise, focus on the fit question the post-tool prompt raises: 'Are you currently working in an environment where these qualities are liabilities? Where they're assets?' For her specific role, the likely answer is that her caution is an asset in a regulated environment. Then: 'If that's true — if caution is actually working for you in this setting — what is the disclosure doing? What are you trying to manage when you announce it at the start of a conversation?' That question surfaces the underlying anxiety the habit is serving.

A team lead at a product company describes himself as 'too stubborn' and 'too opinionated' in coaching. He has internalized these as leadership weaknesses following 360 feedback from a previous organization where consensus-driven decision-making was the norm. He now overcorrects by soliciting excessive input, delaying decisions until there is broad agreement, and softening his technical positions even when he has the clearest view. His current organization, which is faster-moving and values decisiveness, finds his decision-making style too slow. He is applying feedback from a different context as a permanent self-diagnosis.

The tool provides a way to examine what the feedback was actually describing without dismissing it. 'The feedback you received said 'too stubborn' and 'too opinionated.' This exercise doesn't dispute the feedback — it asks a different question: in what two situations is that stubbornness actually doing useful work? We're looking for where that quality belongs, not arguing that it doesn't sometimes create friction. Because if there are real situations where it's an asset, then the question becomes: when does your organization need that version of you?' This framing accepts the feedback while opening the contextual question.

Watch whether his two situations per weakness are drawn from his current organizational context or defaulted to hypothetical settings or his previous organization. Situations from his current context are more useful and more motivating — they demonstrate that the reframe is immediately applicable, not theoretical. Also watch how he responds to the constraint of finding a second situation. Some clients find the second situation quickly; others need prompting. If he is stuck on the second situation for 'too stubborn,' ask: 'Where in your current work does it matter that someone doesn't move when everyone else is ready to?'

After completing the table, move directly to the fit question in the post-tool prompt. 'Looking at the situations you listed as useful for stubbornness — how many of those come up in your current role?' Then: 'In those situations, what are you doing instead of being stubborn? Is that working better or worse than the stubborn version would?' The comparison between what he currently does and what the 'weakness' would produce is often where the overcorrection becomes visible. Then the question becomes: what does appropriate stubbornness look like in this context, not no stubbornness.