Performance Management

Performance management is the part of the job most managers learn by getting it wrong. It is the system through which a team's people get better — or stop getting better — over time. Done well, it is mostly invisible: people grow, the bar rises, weak signals get corrected before they become problems. Done badly, it shows up as a single dreaded review meeting once a year where nobody learns anything.

The mental shift that makes the rest of this section make sense: performance management is a growth system, not an evaluation event. Evaluation is one output of it. If the only time you think about someone's performance is when HR asks for a rating, you do not have performance management — you have performance archaeology.

What It Actually Is

Performance management is the set of recurring conversations and decisions through which you:

• Set expectations — what good looks like at this person's level, on this team, this quarter.
• Observe reality — what they are actually doing, with enough signal to be fair.
• Close the gap — feedback, coaching, delegation, and structure that move reality toward the expectation.
• Record and reward — reviews, ratings, promotions, and recognition that make the loop legible and worth running.

Most of the work is in the middle two. The first and last are the ones orgs over-invest in because they are the visible, calendared ones.

Growth vs. Evaluation

These two framings pull in opposite directions, and most of the dysfunction in performance management comes from confusing them.

You need both. But you cannot run them in the same conversation with the same person and expect honesty. The 1:1 where someone admits they are out of their depth cannot also be the meeting that determines their bonus. Keep growth conversations frequent, low-stakes, and forward-looking. Concentrate evaluation into clearly-marked, predictable cycles. When the two blur, people optimize for the evaluation and stop telling you the truth.

How The Pieces Fit

The pages in this section are not five separate topics — they are one loop running at different cadences:

• 1:1s are the weekly heartbeat. This is where you observe, coach, and catch problems early. Almost everything else either feeds into 1:1s or follows up from them.
• Feedback and recognition is the continuous layer. Real-time, specific, given in days not quarters. If 1:1s are the scheduled check-in, feedback is the always-on signal.
• Performance reviews are the periodic consolidation. They should contain zero surprises if the first two are working — a review is a summary, not a reveal.
• Career frameworks are the map. They define what "next level" means so that growth conversations and reviews point somewhere concrete instead of into a fog.
• Delegation is the primary tool for growth. You grow people mostly by handing them work that stretches them and supporting them through it — not by talking to them about growth.

A useful way to hold it: feedback and 1:1s are the high-frequency loop, reviews and promotions are the low-frequency loop, and the career framework and delegation are the substrate both run on.

Daily/weekly:   feedback ── 1:1s ── delegation
                   │          │          │
                   └──────────┴──────────┘
                              │
Quarterly/annual:        reviews ── promotions
                              │
                       career framework (the map underneath)

The Manager's Real Job Here

A few principles that hold across teams and that the detail pages build on:

• No surprises. Nobody on your team should learn how they are doing for the first time in a formal review. If they do, that is a failure of the weekly system, not the annual one.
• Specific beats sincere. "Great work this quarter" feels good and changes nothing. "The way you broke the migration into reversible steps is exactly the judgment we want at senior" tells someone what to keep doing.
• You manage outcomes and behaviors, not hours. For engineers especially, time-in-seat is noise. Manage what they ship, the quality of their decisions, and how they affect others.
• Fairness is a system property, not an intention. You will have favorites and blind spots. The defense is structure — written expectations, calibration, multiple inputs — not trying harder to be unbiased.
• The goal is to need yourself less. Good performance management raises the floor of what people can do unsupervised. If your team gets more dependent on you over time, the system is running backward.

Common Anti-Patterns

These show up everywhere. Naming them is half the battle.

The annual ambush

The only performance conversation happens once a year, is mostly backward-looking, and frequently contains news. People spend the week before it anxious and the week after it demoralized. The fix is not a better review template — it is moving the actual management into the weeks in between.

Recency bias

The review reflects the last six weeks because that is what you remember. The person who shipped a heroic Q1 and coasted in Q4 looks the same as the person who did the reverse. The fix is to write things down as they happen — a running note per person beats memory every time.

The halo and horns

One strong trait (great communicator, ships fast) inflates everything; one weak trait drags everything down. Calibration with peers exists largely to catch this.

Feedback hoarding

Saving up feedback to "deliver it properly" in the review. By then it is stale, the moment to act on it has passed, and it lands as a list of grievances. Feedback has a short shelf life; give it close to the event.

Conflict avoidance

The hardest one. A manager who cannot say "this is not good enough" lets weak performance persist, which is unfair to everyone carrying it. Niceness that prevents honesty is not kindness — it is abdication that you have dressed up as empathy.

Ratings as the point

Treating the number or label as the deliverable. The rating is a lossy compression of a year; the value was supposed to be in the conversation and the development, not the bucket someone got sorted into.

Cloning the framework onto people

Treating the career ladder as a checklist that every person must complete in the same order. Levels describe a center of mass, not a gate sequence. People are spiky; useful management works with the spikes.

Where To Start

If you are setting this up from scratch on a team, the order that works:

1. Get 1:1s running reliably first — they are the foundation everything else attaches to.
2. Build the habit of continuous feedback so reviews stop being surprising.
3. Make sure a career framework exists, even a borrowed one, so conversations have a destination.
4. Use delegation deliberately as your main growth lever.
5. Run reviews and promotions as the consolidation layer on top, not the main event.

The rest of this section goes deep on each. Start with 1:1s.