First Round Review

First Round Review's deep dive is one of the most practical reads in the set because it gives a repeatable system for preparing, delivering, and following up on a performance review. The core argument is that good reviews do not come from filling out forms. They come from doing real narrative prep before the meeting and real coaching after it.

The strongest part is the structure around development areas. Instead of naming a weakness and moving on, the framework asks you to describe the opportunity clearly, ground it in examples, suggest concrete ways to improve, and keep revisiting it after the formal review ends. This level of specificity is what separates a review that changes behavior from one that gets filed away and forgotten.

The framework recommends that managers write a narrative summary of each person's performance before the review conversation. This is not the same as filling out a rating form. It means sitting down and writing, in your own words, what this person has done well, where they have fallen short, and what you want them to focus on next. The writing process itself is valuable because it forces you to move past vague impressions and commit to specific observations. Many managers discover that their sense of someone's performance shifts once they have to ground it in actual examples rather than general feelings.

For strengths, the authors advise going beyond "great job" and explaining why the person's contribution mattered. What did their work make possible for the team or the business? What skill or behavior should they keep investing in? This kind of specific recognition is motivating in a way that generic praise is not, because it tells the person exactly what to keep doing and why it matters.

For development areas, the framework is even more detailed. The framework suggests naming the gap, providing two or three concrete examples, explaining the consequences of the gap for the person's growth and for the team, and then offering specific suggestions for improvement. Crucially, the suggestion should be actionable within the next review cycle. Telling someone to "be more strategic" is not useful. Telling someone to "bring a recommendation with tradeoffs to the next three project kickoffs instead of waiting to be asked" gives them something they can practice immediately.

The authors also emphasize that the performance review is not the finish line. It is the starting line for a coaching conversation that continues through regular one-on-ones, informal check-ins, and real-time feedback. A review that names a development area but never follows up teaches the person that the feedback was not serious. A review followed by consistent coaching teaches them that growth is expected and supported. The difference between these two outcomes is not the quality of the review document. It is the quality of what happens after.

Key ideas to carry into practice

• The review itself should not be the first time you are organizing your thinking about performance. Write a narrative summary in advance.
• Development areas need examples, implications, and concrete suggestions, not vague encouragement.
• When recognizing strengths, explain why the contribution mattered and what skill the person should keep investing in.
• Make development suggestions actionable within the next review cycle. Abstract advice does not change behavior.
• The conversation gets stronger when you balance recognition, developmental feedback, and forward-looking expectations.
• Follow-up matters as much as delivery. Ongoing coaching is what turns a review into actual growth.

Common questions

Q: How do I handle a performance review when someone is doing many things well but has one serious issue?

A: Use the structure from the article. Name their strengths clearly, then spend most of the conversation on one or two development areas with concrete examples, why they matter, and what improvement would look like. That keeps the review balanced without burying the main issue.

Q: What should I say at the end of the conversation?

A: End with a follow-up plan, not just a summary. For example: "The main development area we are focusing on is handoff discipline. Over the next month, I want us to check in weekly on deadlines and risk flags so we can see the change in real time."