Thank you!

This article is by Lenny Rachitsky, a former product lead at Airbnb.

Back when I was a young PM, one of my managers altered the trajectory of my career. It was my second year at Airbnb. I was doing okay, but not great. My new manager, Vlad Loktev, had taken over, just as the project I was overseeing had gotten delayed by weeks. He wasn’t impressed. Although he helped me get it back on track, and we got it out the door, I knew that when performance review season rolled around, it was going to be rough. When the time came, I did indeed get a less-than-stellar rating. Vlad flagged a number of important development areas for me to focus on, including being more communicative about status, and getting more aggressive about prioritizing. While I could have left dejected, I instead ended that performance conversation feeling more clear, motivated, and excited than I had ever been.

Here’s why: Vlad had a simple yet powerful performance review system. The clarity of his feedback, the care in his delivery, and the simple organization of his framework all came together to create a career development experience unlike any I’d ever had before. This set me on a course that catapulted me from a newly-minted IC PM to a manager of a half-dozen PMs, tackling everything from marketplace quality to growth, most recently building out and leading a cross-functional 80-person team driving supply growth at Airbnb.

Over the years, as I transitioned into management, took on a handful of direct reports, and conducted over 50 performance reviews, I adopted and expanded his system into an end-to-end performance management framework that has enabled me to systematically grow junior ICs into star performers, to turn big trouble spots into super-strengths, and build one of the best performing teams at Airbnb.

Figuring that other managers might similarly find this system useful, below I’ll dive into why performance reviews typically suck, how we can fix them, and then walk through this framework in step-by-step detail. Whether you’re a first-time manager looking for guidance on handling your first review, an experienced manager hoping to uplevel yourself from good to kickass, or an early-stage founder trying to put a company performance review system in place, the templates, tactics and real-world examples you’ll find here are yours for the taking.


It’s rare that one meeting, once or twice a year, has such a tremendous impact on the morale, performance and trajectory of an employee. Unfortunately, performance reviews are severely underutilized, and often done badly. From the perspective of direct reports, they are more likely to spark dread than hope. On the part of managers, they’re treated more as a chore than an opportunity.

Done well, performance reviews improve performance, align expectations and accelerate your report’s career. Done poorly, they accelerate their departure.

Below are the six most common mistakes managers make with performance reviews:

If you can’t find a dozen hours to focus on your report’s career throughout the year, that generally means you have too many reports — or that you shouldn’t be a manager.


As an antidote to the common missteps from above, 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.


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:

Hi Joe,

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.

Thank you!

In parallel, ask your report to do self-review, with an email such as:

Hi Jane,

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?

Thank you!

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.

Development areas:

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:

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).

Filling in the details within each development area:

This right-hand column is where most of the content — and eventually most of the in-person conversation — goes. The goal here is to make it very clear what the development opportunity is, why it’s so important, and how to concretely improve at it. I often find myself refining this section up until the last minute.

For each development area, include:

Ambitious people want to know not just how to get better, but how to blow it out of the water. Paint that picture for your direct reports — what would “killing it” look like by the next performance review?

Timeline to next level:

Finally, leave your report with a sense of how far they are from the next “level.” Even if you don’t have official levels at your company, include a meaningful milestone for your report to be excited about reaching (such as becoming a manager, expanding scope, or a title change). There are three common archetypes of situations here:


There’s a lot more to performance reviews than simply sharing the rating, development areas, and change in comp – how it’s delivered, and the conversation that it sparks, is a vital part of making change happen. I’ve had performance reviews where I received a low rating, but I left energized and motivated. I’ve also had reviews where I got an amazing rating but left unsure about my future. That’s because people want context, clarity, and most of all, next steps.

How you message the feedback — and how your direct report feels afterwards — is often more important than the actual content itself.

Here are a few tips for prepping yourself to deliver the performance review:

With that prep work taken care of, here’s how I generally sequence the conversation in the room:

I start each conversation by lightening the mood and checking in with how the person is doing. Everyone is going to be on edge — find a way to make it feel a little less intense. Then share some context about the chat:

Share the rating:
Some sort of rating scale is generally helpful for reports to get a concrete sense of where they are, so if you don’t have this yet at your org consider introducing it by the next cycle. I try to share the person’s rating as early as possible in the conversation. This is the most immediate thing on people’s mind and I find people don’t fully pay attention until they know how they “officially” did. If it’s not an amazing rating, address that, but don’t dwell on it for too long. Instead move forward, so that you can spend time talking through the opportunities to level up. As much as possible, make sure the performance rating doesn’t come as a total surprise. Your report should generally know how they’re doing through regular chats throughout the year. If the rating is really problematic, this part takes special care and attention, and often involves working closely with HR.

Dive in:
Walk through the doc. If you sent it ahead of time, and the person read it, then just hit the big points. Pause along the way and ask if everything makes sense or if they disagree with anything. Make sure you’re watching the time, and spend at least two-thirds of the meeting on the details within the development areas. When you get to tough stuff, I’d encourage you to be open and vulnerable. When possible, share personal experiences of when you yourself worked on these very same development areas, what struggles you had, and how you overcame them. The more this feels like you are on their side and there to help them succeed (instead of judging or berating them), the more likely they’ll accept the feedback.

A few common reactions to watch out for during the conversation:

Share compensation updates (if there are any): Finally, share any compensation updates. This normally ends things on a happy note. Keep it simple, share the facts, and congratulate the person on the achievement. It’s easy for employees to take a raise for granted and not treat it as a big deal, so use it as an opportunity to remind them how much you value their great work.

Leave time for discussion: Then, open it up to any remaining questions and thoughts. Is there anything your report disagrees with? Is there anything they want to dive into further? Is there any more clarity you can give around expectations for the next cycle? Try to give this at least five minutes. That being said, I try not to linger here too long if there isn’t anything pressing, especially if things seem to be in a good place. Often folks need time to process and think about everything they’ve heard, and you can follow up on it in future 1:1s.

Follow-up action plan: Finally, turn this discussion into an action plan (you’ll find guidance on how to do this below). This will allow you to channel all of the ideas, motivation, and momentum into an ongoing structured discussion that holds both of you accountable to making change.

Outro: Find a way to wrap it up end on a positive note. Remind them how valuable they are to the company (if they are), how much you enjoy working with them (if you do), and how much potential they have at your company (if they do). And last but not least, let them know that if anything comes up until you chat next, to not hesitate to ping you.

Lenny Rachitsky


As George Bernard Shaw famously said, “The single biggest problem in communication is the illusion that it has taken place.”

We want to believe our carefully-chosen words of wisdom are interpreted correctly and seared into the minds of our reports. It’s safer to assume they aren’t.

Early in my management career, I had a report that was underperforming. I put hours into preparing for our performance chat. I identified development areas, included numerous examples, and shared tons of suggestions. I talked through it in our hour-long meeting. I felt like I made a real impact. A month later, I revisited our discussion and it felt as though it never happened. My direct report had vague memories of a few points I had mentioned, and a clear desire to improve, but 95% of the message was lost.

In that moment I learned two lessons. One, it’s my fault as a manager if my report doesn't remember what development areas to be focusing on. Two, I was treating the performance conversation as the end, when it’s really only the beginning of the performance development process.

The solution to both of these problems is simple — set aside dedicated time to check in, and hold each other accountable. Here’s how you make this happen:

Create a two-sided action plan: Building off the performance review document, at the end of your conversation (see above), ask your report to list five to seven concrete actions they want to work on over the next six months and add them into a super simple spreadsheet. Give them a week to do this, while it’s still fresh in their minds. Here’s a template you can use, and a few examples:

Alongside this list, make sure they also include what they need from you in order to be successful. It’s important that your report owns this process and chooses the items (with input from you) because they’ll need to be motivated to actually work on these things. The list should be made up of concrete suggestions you noted in their performance review, things your report personally wants to work on, and things that your report needs from you in order to be successful. Put a status color next to each item, and update it every month.

Schedule a one-hour monthly check-in: Put this meeting on the calendar immediately. I call it “Monthly Career Coaching,” to distinguish it from our weekly 1:1s. The focus of these meetings is to step back from the day-to-day and focus on career and performance development. No talk of how a project is going, upcoming deadlines, or blockers (that’s for the 1:1s). Remind your report ahead of each meeting to update their spreadsheet with a status and any new discussion items they’d like to make time for.

During the Career Coaching hour: In this meeting, you have three goals:

The meeting should be mostly you listening, asking questions, and (when really necessary) offering suggestions. Your report should lead the meeting — go through each item in the action plan, share a brief update, and align on the status color. I find most of the time my report is right-on with their assessment. If you disagree, discuss it. Throughout the discussion, instead of telling your reports exactly what to do, help them figure it out for themselves. When asked for the answer or advice, turn it around and ask “What do you think the right approach is?” or “Before I answer, what do you think?” (This book from David Rock and Julie Zhuo’s writing have taught me a lot about how to be a better manager by asking good questions.)

Between chats: Keep track of instances where your report did well, didn’t do well, or generally did something noteworthy. Share these things with your report in real-time as much as you can, or in weekly 1:1s, but also save them in a running file. For example, “July 10th - Ran an excellent meeting with senior execs,” or “Sept 3 - Put together a very strong strategy for Q3,” or even feedback from others (“Jan 4th - Spike shared with me how impressed he is with Jane’s ability to run a meeting.”) I keep a separate Google Doc for each of my reports for this purpose. In addition to Google Docs, there are neat feedback and performance management tools like Matter, Culture Amp, and TINYpulse that can help you keep tabs on performance throughout the year.


As a manager, the best feeling in the world is watching your direct reports grow. I’ll never forget a junior PM that came to our team with considerable gap in their collaboration skills. After identifying that development area, working together through the process above, and then revisiting it six months later I was thrilled to see nearly every instance of peer feedback call out that this was no longer an issue — and in fact, this report’s development area had turned into a strength. All it took was infusing performance reviews with more structure, attention, and intention.

Here’s a recap of the process:

1. Prepare

2. Deliver

3. Follow-up

Even if your company already has an established feedback or performance review process, you can easily map this system onto that process. I find that there's a lot of room for managers to have a more bespoke, personal approach that persists through cycles and organizational changes. Don't just take the forms and talking points from on high and have a perfunctory conversation. Put in the legwork. You’ll notice the impact immediately, and be on your way to becoming a better manager.

Huge shout out to Vlad Loktev for too many things to name, including his contributions to this post, and to Helen Sims, Yelena Rachitsky, Eric Ruth, and Brett Hellman for reviewing early drafts.

Photography by Bonnie Rae Mills.

First Round ReviewThe best advice in tech
Subscribe for Exclusive Access