Performance Feedback Without Politics

Performance conversations go political when they become vague, late, or surprising.

Engineers can handle hard truth. What they cannot handle is fog: “be more proactive,” “improve communication,” “raise your impact” — with no examples, no path, and no shared definition of success.

Coaching engineers has reinforced something simple for me. Most useful feedback is not complicated. The hard part is saying the specific thing while there is still time for the person to do something with it.

Leadership work, whether Staff coaching or EM accountability, is making feedback usable.

#Specific beats clever

Good feedback points at work.

• “In the last two incident reviews, the postmortem missed the customer-facing impact.”
• “Your PRs are strong technically, but reviewers wait days because context is missing in the description.”
• “You owned the migration plan end-to-end — that is the bar for senior delivery.”

These are the kinds of conversations I want engineering teams to be able to have. Not “you need more executive presence.” Not “people have concerns.”

Name the work. Name the effect. Give the person something they can act on.

Personality labels invite defense. Observed behavior invites change.

#Timing is part of the craft

Annual reviews should never be the first time someone hears a concern.

The durable pattern is small and frequent:

• 1:1s that include growth, not only status
• review comments that teach
• praise close to the moment it was earned
• course-correction while the work is still recoverable

I have found this particularly important while onboarding engineers. The first few reviews are not gates on code so much as opportunities to explain the team’s standards — testing, documentation, conventions, integration awareness.

Done consistently, the same comment should not need to be written forever.

Late feedback is not “careful.” It is expensive.

#Separate support from consequences

People deserve clarity about three things:

1. What “good” looks like in this role.
2. What support is available to get there.
3. What happens if the gap remains after a fair window.

Politics thrives when those stay implied. Teams stabilize when they are explicit.

This is also where Staff leaders practice manager muscles before the title. You may not own formal performance decisions, but you can still coach with evidence, advocate fairly, and refuse hallway narratives.

#Write less theater, more signal

When written feedback is needed, keep it boring and true:

• Situation
• Observed behavior
• Impact
• Expected change
• Support offered

That framework is intentionally uninteresting. It forces the conversation back onto what actually happened and what should happen next.

Skip the novel. Skip the score-settling. Skip the vague adjectives that sound sophisticated and mean nothing.

#The point is a stronger team

Feedback is not a ritual for HR. It is how you protect the people carrying the work — including the person receiving the critique.

A team that cannot talk about performance cannot talk honestly about standards. And standards that cannot be discussed eventually become politics, tribal knowledge, or resentment.