Skip to content
She Inc.By She Inc., helping 250,000+ women learn and grow.
Performance

Annual review: writing a self-review that doesn't undersell you

A 6-section template, the wording fixes most women miss, and what to do with feedback you disagree with. Half a day of work that compounds.

Share:LinkedInWhatsAppEmail
By Matt DelacFounder, She Inc.8 min read

The self-review is the highest-leverage document you write each year. It anchors your manager's review, it shapes calibration, and (at most companies) it's quoted verbatim in your performance write-up. Most people undersell themselves on it. Here's the structure that doesn't.

The six sections

  1. Headline — one paragraph, what you'd want said about you in calibration.
  2. Wins — 5–8 outcomes from the year, each quantified.
  3. Scope growth — how your surface area changed vs. last year.
  4. Leadership / multiplier — what you did beyond your own work.
  5. Areas you're working on — what you're getting better at.
  6. What you want next year — explicit, ambitious, and the help you need.

Headline: write the line that gets repeated

Calibration committees skim 20 reviews. The headline is what survives. Make it punchy and specific — and write it in the voice of someone advocating for you.

Weak headline

I've had a strong year, contributing to several team initiatives and growing in my role.

Strong headline

Owned the largest revenue line on the team ($14M ARR) end-to-end this year. Doubled activation in Q3 and led the cross-functional team that shipped the Asia launch — three months ahead of plan.

Wins: outcomes, not activities

Two failure modes. The first is hedging verbs — "helped", "supported", "contributed to". The second is listing activities instead of outcomes. Replace both.

  • Bad: "Helped the team launch onboarding v2."
  • Better: "Led onboarding v2 launch — increased D7 activation from 38% to 52%."
  • Bad: "Worked on improving documentation."
  • Better: "Rebuilt the docs system; cut sales onboarding from 3 weeks to 8 days."

Scope growth: name what's bigger now

Scope is the easiest thing to lose track of and the most-promoted-on metric. Spell out, year over year, what you own now that you didn't.

  • Headcount touched — direct, dotted, partner.
  • Surface area — products, regions, customer segments.
  • $ moved — revenue, budget, cost saved.
  • Decisions made unilaterally — sign-offs you didn't have last year.

Leadership / multiplier: invisible work, made visible

Mentoring, hiring, cross-functional unblocking, fixing process — this is the work that disproportionately falls to women and gets undercredited. Name it explicitly.

Examples

Onboarded 3 new PMs (each productive in 6 weeks vs. previous 12). Ran the sprint-planning template that the rest of the org adopted. Sat on the hiring loop for 14 senior interviews this year.

Areas you're working on

This is where most people accidentally tank their review. "Working on confidence" or "public speaking" sounds like an admission of weakness. Reframe as growth in service of bigger scope.

Weak

I'm working on being more confident in big meetings.

Strong

Sharpening my exec-comms — moved from briefing my manager pre-meeting to presenting in QBR directly. Next: own the Q4 board narrative for our area.

What you want next year

End the review by stating what you want and what you need. This is not the place to be modest. If you don't put it in writing, no one is responsible for it.

Closing paragraph

What I want next year: promotion to [level], ownership of [area], and to lead one company-level initiative. What I need from you: air-cover on [X] and an introduction to [Y]. Let's make it happen.

What to do if the review you receive is unfair

If your manager's write-up undersells you or contradicts the calibration outcome you wanted, don't let it sit. Don't fight it in the moment. Send a written response within 5 days that does three things:

  1. Acknowledges what you agree with — specifically, not generically.
  2. Names what you disagree with, with examples.
  3. Asks for a written addendum to the file.

Keep reading