How to Talk About Weaknesses in a Performance Review

Almost every performance review asks about weaknesses or areas for improvement, and it's the section people most dread. Handled badly, it either dodges the question or hands your manager a liability. Handled well, it actually strengthens your case by demonstrating self-awareness and growth. Here's how to do it right.

Why the weakness question matters

Managers ask about weaknesses to gauge self-awareness, not to collect ammunition. Someone who can honestly name a development area and show they're addressing it reads as mature and coachable. Someone who claims to have no weaknesses, or who names a fake one ("I work too hard"), reads as either oblivious or evasive. The goal is to show genuine self-awareness paired with action.

The framing that works: weakness as forward motion

The key move is to frame any development area as something you're *already addressing*, not a static flaw. The structure:

1. Name something genuine (but not catastrophic).
2. Show you're aware of its impact.
3. Describe the concrete steps you're already taking.
4. Point to early progress if you have it.

This turns "here's something I'm bad at" into "here's how I'm growing" — which is exactly what the question is really asking for.

Examples

Strategic influence:

"An area I'm developing is broader strategic influence across the org. I've tended to focus on execution within my team. To grow, I started by leading the cross-team migration working group this quarter, and I'm now looking to drive a larger initiative."

Delegation:

"I've historically taken on too much myself rather than delegating. I realized it was limiting both my scope and my team's growth, so I've started handing off recurring work to newer teammates and coaching them through it. Two tasks are fully delegated now."

Data fluency:

"I want to be able to make faster independent decisions without waiting on the data team. I've started owning my own reporting and building my analysis skills, and I'm already less dependent on others for routine questions."

How to choose which weakness to name

Pick something that is:

• Genuine — fake weaknesses are obvious and damage trust.
• Not disqualifying for your role — don't name a weakness in the core competency the job depends on.
• Improvable — something you can show progress on.
• Already in progress — ideally something you've started addressing.

What to avoid

• The humble-brag ("I'm too much of a perfectionist") — transparent and irritating.
• Claiming no weaknesses — reads as a lack of self-awareness.
• Naming a fatal flaw — don't volunteer a weakness in your role's central skill.
• Naming a weakness with no plan — the plan is the whole point.
• Over-confessing — one or two genuine areas, handled well, is plenty.

The bottom line

The weakness section is an opportunity to demonstrate growth, and growth is best shown with evidence — the specific steps you've taken and the early results. The easiest way to have that evidence ready is to track your development efforts alongside your wins, so you can point to concrete progress rather than vague intentions. That ongoing record is what [CareerRise](/) is built for.

---