← The Journal

Application

·4 May 2026·3 min read

The performance review you wrote for yourself

A self-evaluation is often the written record a manager works from in conversations you’re not part of. Attribution and specificity matter more than volume.

By Casey Bawden , Creator of Neutral Authority Method

A performance self-evaluation is read by someone deciding, in part, what to recommend for you: what level to assess, whether a promotion or raise conversation is warranted, what to say in a room you won’t be in.

Most people approach it as a reporting exercise: document what happened, list the projects, note the outcomes. What can get lost is that the way an outcome is attributed also carries information. “The project was delivered” and “I led the delivery of the project” describe the same event with a different amount of visible agency.

Patterns that show up in self-evaluation writing

Passive attribution. “The client retention initiative was delivered on time and within budget” describes an outcome without naming who caused it. “I designed and led the client retention initiative, which delivered on time and within budget” contains the same facts with the professional named as the agent. Whether that distinction matters to a given reader can’t be guaranteed, but it does change what information is on the page.

Hedged claims. “I think I contributed positively to team morale” is a qualified opinion. “Team communication improved after I introduced the weekly briefing format” is a specific, checkable statement. Neither is automatically correct, the second should only be written if it’s actually true and demonstrable, but where it is true, hedging it adds uncertainty the writer doesn’t actually have.

Collective attribution. “We achieved” and “the team delivered” are accurate when the work genuinely was collective. They become a problem only when individual contribution is consistently folded into group language, leaving no record of what a specific person did. There’s a real difference between acknowledging collaboration and erasing an individual’s part in it.

What the reader is trying to establish

A manager reading a self-evaluation is usually asking what, specifically, this person did, what it produced, and whether that supports a particular case. Language that is specific, active and clearly attributed gives them something to work with. A summary of general activity leaves more for the manager to infer, and the inference they make will not necessarily be generous.

7 Emails, free

Seven ordinary professional emails, with the original, one possible revision and the reasoning behind it.

The PDF arrives by email. You can unsubscribe at any time. See the Privacy Policy.

A more specific way to write it

The correction here isn’t to overclaim or to take credit for work that was genuinely shared, those are separate problems. It’s to write in a way that reflects what actually happened: who decided, who led, what changed, and what caused it.

Common version

The negotiation process was restructured.

One possible revision

I restructured the negotiation process after identifying that the previous format was creating delays at the agreement stage.

Common version

Client satisfaction scores improved.

One possible revision

Client satisfaction scores increased by 18% in Q3, following the revised onboarding framework I implemented in May.

A useful check: read each sentence and ask whether a reader could identify, from that sentence alone, what you specifically did. If the subject of the sentence is the project or the team rather than you, and the work genuinely was yours, it may be worth rewriting with yourself as the agent of the outcome.

A disappointing review outcome isn’t always a performance problem. Sometimes the work isn’t in question at all, and what’s missing is simply an accurate written account of who did what.

Related: the promotion conversation that didn’t land.

7 Emails

7 Emails I Would Write Differently Now