You owe your reports a better performance review
|Jul 18||Public post|| 1|
Ever since my first piece of writing after leaving Airbnb, I’ve been wanting to do a deep dive into performance reviews. IMHO, they are the secret weapon of the best managers. Done well, they improve performance, align expectations and accelerate your report's career. Don't poorly, they accelerate their departure. I’ve been fortunate to have amazing managers, like Vlad, who showed me how powerful performance reviews can be, and so when the First Round Review reached out about doing a guest post, this felt like the perfect opportunity to share these learnings. Below is an excerpt from the full article — enjoy!
FOLLOW THIS THREE-STEP PERFORMANCE REVIEW SYSTEM
The system I’ve come to rely on is made up of three equally important parts:
This template forms the foundation of the system, and we’ll walk through each section in detail below. Here’s the Google Doc version of the template for your own easy use.
STEP 1: PREPARE, PREPARE, PREPARE
This is where the bulk of your time should be spent, as it sets up the steps that follow. Start by gathering data on how your direct report did, both by seeking input from your report’s peers and a self-assessment from the individual directly. You want to get as much signal as possible at this stage, ideally as early on in the process as you can (I typically start at least a month before a scheduled performance chat, since it often takes a while to get everyone’s responses). There are many ways to do this, and most companies have their own system for gathering feedback, but you can always take a lightweight approach over email.
First, work with your direct report to identify five to eight people who’d be able to provide input. Then fire off emails (bcc’ing everyone) asking three simple questions:
In an effort to help Jane level up in her career, I’m gathering peer feedback from people she works most closely with. I would really love your input. If you can find 5-10 minutes in the next few days to answer these questions, I would truly appreciate it (and so will Jane):
1. What are 2-3 things Jane should start doing? Why?
2. What are 2-3 things Jane should continue doing? Why?
3. What are 2-3 things Jane should stop doing? Why?
I will keep your answers anonymous, unless you tell me otherwise. Please be honest and candid, as that’s what’ll help me give Jane the best support in her career. And, if there’s anything else you’d like to share, good or bad, I’d love to hear it.
In parallel, ask your report to do self-review, with an email such as:
Ahead of our upcoming performance conversation, I would love to get your perspective on how things went. Could you please answer these three questions, along with anything else you’d like to share, and get back to me by X/X?
1. What were your top five accomplishments in this cycle?
2. What 2-3 areas do you want to focus on developmenting over the next cycle?
3. What are your goals for your career over the next two years?
While you’re waiting for the feedback, I strongly recommend you start crystalizing your opinion on how your report performed. What did they do well? What is keeping them back? What are the one or two most critical development areas for them to focus on over the next cycle? This is a key step to reducing bias and avoiding being completely swayed by what peers say.
As you begin to gather your thinking, and as peer feedback begins to roll in, start to flesh out the template referenced above, which you’ll eventually share with your report. Let’s walk through each section:
Accomplishments: Detail the person’s accomplishments over the course of the period. Collect these from the report’s self-review, peer feedback, and your own notes that you’ve been keeping throughout the year. Each item here should be significant and meaty. For example, write “Hit team’s goals” and “Shipped project X on time and under budget," not “Held a great meeting” or “Went to three conferences." In this same section, I also like to include a sampling of the best positive peer feedback I’ve collected, ideally three to five of the best quotes about the person (anonymized of course).
Superpower: Most performance reviews over-index on development areas. The reality is that an individual will have just as much impact (if not more) on an organization if they flex what they are really good at, instead of just trying to improve on the areas they’re struggling with. Here, you have a chance to highlight that. Describe their biggest superpower, and how they can flex it further. A few examples of superpowers that I’ve highlighted in the past include a special knack for storytelling, execution, or galvanizing a team. There’s a lot of research that shows focusing on strengths is much more effective than obsessing over weaknesses. Note that it’s important to watch for bias here, since many of us unconsciously describe the same behavior by men as a strength and as a weakness by a woman. (You can read more on this topic here, here, and here).
High level feedback: Next, I take a step back and summarize the report’s performance in a short narrative, about four to six sentences. I try to make a simple story arc, starting by describing how far they’ve come, then a sentence or two about how they did this cycle, and ending on a high-level overview of what they need to focus on next.
Identify one to two development areas to focus on for the next cycle, and put them in the middle column (see the screenshot below). This part is core to the performance review, so selecting these with care is absolutely critical. A few specific suggestions for how to nail these down:
What is most holding the person back from the next level? If your company has a leveling system, leverage it to explain your thinking.
Do any clear themes emerge from the peer feedback or self-review?
If your company does calibration, is there a key issue you’re hearing from other managers? Even if it’s not something you agree with, it’s something you’ll need to address.
Make sure you still identify important development areas for even the highest of performers. No matter how amazing someone is, there’s almost always something they can focus on to get to the next level.
A few examples of potential development areas include reliable execution, increasing code quality, and more succinct verbal communication. Don’t worry so much about making the descriptions super comprehensive here, as the details will be filled into the next column. A common mistake here is including too many development areas (more than two makes it very hard to make meaningful progress on any), or not making the development opportunities concrete enough (where your direct reports are left guessing at what you really mean).