The Performance Review Review

👔 Tales from the W2

May 11, 2026

I’ve spent years being reviewed at work.

Performance reviews. Development plans. Calibration cycles. Growth conversations.

The usual corporate bullshit.

This year, I decided to review the review itself.

Not emotionally. Not as revenge. Just curiosity.

Interesting thing about corporate feedback: it reveals as much about the organization as it does about the employee.

The language. The incentives. The abstractions. The careful balance between motivation and ambiguity.

Once you’ve been through enough cycles, you start noticing the patterns underneath the phrasing.

So I figured I’d annotate mine.

Achievements

Manager’s Answer

Over the past six months, Zaddy acted as a primary support liaison for a major onboarding initiative, helping resolve several long-standing production blockers and improving reliability across critical systems.

He also contributed heavily during a broader production stability effort, leveraging AI-assisted analysis to identify root causes, surface meaningful metrics, and improve leadership visibility during high-pressure operational periods.

Zaddy’s Notes

Translation: the system caught fire and everyone suddenly discovered “cross-functional urgency.”

The AI part mattered more than they realize. Not because it replaced engineering, but because it compressed investigation time. Leadership mostly experiences engineering through visibility and stability. If you reduce chaos faster than everyone else, people start assigning you leverage whether they understand the technical details or not.

Challenges

Manager’s Answer

A large-scale production stability initiative created significant disruption across the team, reducing routine predictability and shifting priorities frequently. Post-initiative alignment and support structures were still evolving, creating additional ambiguity around ownership and long-term direction.

Zaddy’s Notes

Interesting thing about management during unstable periods:

Specific feedback becomes harder to pin down.

Not because leadership lacks awareness, but because ambiguity preserves optionality. Priorities can move faster when nothing is overly committed or clearly defined.

Priorities

Manager’s Answer

I am aligned with Zaddy’s development goals and encourage him to continue positioning himself as a driver of positive change within the team, particularly through technical leadership and mentorship as he progresses toward stronger senior-level influence.

Zaddy’s Notes

Corporate development feedback is usually designed to be universally applicable.

“Drive change.”
“Increase influence.”
“Show leadership.”

You could hand the same phrases to almost any employee in the building and it would still sound correct.

That’s the point.

The language stays broad enough to motivate, while abstract enough to avoid committing to anything concrete.

Career Interests

Manager’s Answer

Zaddy should continue deepening his impact within his current role while partnering closely with leadership to prepare for future growth opportunities and broader organizational influence.

Zaddy’s Notes

For promotions, you’re not just competing against performance.

You’re competing against organizational geometry.

Sometimes there simply isn’t another layer available above you yet.

Associate Development

Manager’s Answer

Zaddy has already begun demonstrating an “AI-first” mindset that aligns closely with the future direction of software engineering. I encourage him to continue leaning into that strength and use it as a differentiator as he works toward his long-term goals.

Zaddy’s Notes

Interesting shift happening right now.

A few years ago, engineering prestige came from memorization and raw technical recall. Now the leverage is shifting toward orchestration, synthesis, and reducing cognitive load faster than everyone else.

The engineers treating AI like autocomplete are probably missing the point.

Most of my code was AI slop anyway.