top of page

Surviving the Self Review


A short field guide for people who do real work

Every year, intelligent adults are asked to describe themselves in a few small text boxes.

It’s an unusual moment. Briefly, you are your own historian, your own communications team, and your own legal counsel.

The trick is to be understood.


In large organizations, your self-review rarely travels alone. It’s read alongside calibration notes, scorecards, budget constraints, and people who have never met you but control outcomes that affect your mortgage. So write for that room.


Start with what changed: The organization deals in scale and only outcomes are visible, effort rarely is.

So list your projects that shipped, the risks you helped reduce. If you're in sales or Customer Success talk about the Customers you retained or acquired.



Apply the so what? filter

As you write, apply one simple test: would this change how someone judges my contribution?


If the answer is no, rewrite it. Attending meetings, Being visible, Collaborating endlessly aren't impact. You readers want to see you write about what moved because you were there.


When your work feels subtle, name it anyway.

Remember large systems depend on invisible labour: preventing poor decisions, absorbing ambiguity, translating strategy into something operational, keeping fragile projects upright, helping tense people think clearly again are the lubricants that help the organization run smoothly. And if you don’t document this, the organization will assume it didn’t exist. Let them know the qualitative side of who you are too


Use other people’s words when you can.

A short line from a client. A stakeholder’s email. A message that begins with “thank you for…”

This isn’t boasting. It’s evidence.


Numbers help. Not because they’re perfect, but because they are broadly understood and they are quantitative (the bias in almost every organization)

Time saved.

Revenue influenced.

Incidents avoided.

Volume handled.

Backlog reduced.

Even approximate signals beat vague adjectives.


When you reach the development section, stay professional.

Strong organizations don’t reward self-flagellation. They reward trajectory.

Choose edges you are already working on. Show awareness. Show where you are learning. Show momentum.


Write about the future with specificity. Not “I want to grow.” Rather what you want to own. What problems you are ready to take responsibility for. What skills you are deliberately building.


Finally

Before you submit, imagine someone you’ve never met reading it during a long afternoon of calibration.


If they conclude: “This person delivers.” or “This person is low-drama.” and especially “This person makes things work.”


You’ve done your job.

 
 
 

Recent Posts

See All
a kind of shorthand

I’ve been noticing something I use all the time, and I think we all do. An idea that is technically wrong…but psychologically helpful. And that turns out to matter more than we like to admit. Take t

 
 
 
You Have to Give to Get

A few years ago, I built a playlist for my sister called The Soundtrack of Your Life . It wasn’t a neat Spotify list of greatest hits. It was more like a small museum: obscure recordings, half-forgott

 
 
 

Comments


bottom of page