How to Write a Performance Review for Your Team When You Have No Idea What to Say

At Sumizeit, we built a book summary app for people who need the idea inside a book, fast, without clearing a free weekend to go get it. This one's for every manager staring at a review deadline with no idea where to start.

If you manage people, you know the feeling. It's November. Review season landed in your calendar like a brick, and you're staring at a blank text box with a cursor blinking at you, waiting for wisdom you don't have yet. You know this person's work. You just don't know how to turn a year of Slack messages and half remembered one on ones into three paragraphs that sound like you actually paid attention.

Here's the good news. You don't need to write a performance review from a cold start. Some of the best management books ever written are basically review templates in disguise, and you can pull their frameworks straight into your draft tonight. This guide walks through exactly how to write a performance review for your team using five ideas borrowed from books that are faster to skim than most HR portals are to log into.

TL;DR

Writing performance reviews for your team gets easier once you stop trying to invent language from scratch. Borrow a strengths first structure from a book like First, Break All the Rules, use a clear feedback framework from something like Crucial Conversations to handle the hard parts honestly, and give quiet, steady performers the same specific attention you'd naturally give your most vocal one. Batch the writing in one sitting instead of spreading it across a miserable week, and when you barely know someone's work, say that plainly and build the review around what you can verify. None of this requires reading a 300 page management book this month. You need the ideas, not the page count, and that's exactly what Sumizeit is built for.

Why writing reviews feels so much harder than giving feedback out loud

Talking to someone about their work is easy compared to writing it down. Speech disappears. Writing sits in a file forever, gets read by HR, sometimes gets read by a lawyer, and follows the person into their next promotion conversation. That permanence is why so many managers freeze, then default to vague filler like "continues to be a strong team player," which helps nobody and tells the employee nothing they didn't already know.

The fix isn't trying harder. It's borrowing structure from people who've already solved this problem. Management writers have spent decades studying what makes feedback land and what makes it bounce off, and their frameworks turn a blank page into a fill in the blank exercise. That's the whole point of this post.

Borrow a strengths first structure before you write a word

Start with the research behind First, Break All the Rules, which found that the best managers build reviews around a person's strengths and manage around their weaknesses, rather than trying to fix every gap evenly. Before you write a single sentence of criticism, write down the two or three things this person is genuinely good at, in specific terms tied to real work, not personality traits. Not "great attitude." Instead, "ran the migration rollout with zero surprises and kept three other teams informed the whole way."

Once the strengths section is done, your tone for the rest of the review changes. You're not writing a report card anymore. You're writing an honest account of someone you've actually watched work, and that comes through on the page even when the feedback that follows is tough.

If you manage a team you're still getting to know, pair this with the ideas in how to prepare for a performance review in 11 practical moves, written from the other side of the table. Reading it as a manager is useful too, because it shows you exactly what your own reports are hoping to hear back from you.

Use the feedback cube to say the hard part without wrecking the relationship

Every review has one paragraph that's harder to write than the rest, the one where you have to name a real problem without torching the relationship. This is where Crucial Conversations earns its keep. The core idea is simple and it works on paper just as well as it works out loud. Separate the fact from your story about the fact. "Missed the deadline three times" is a fact. "Doesn't care about the team" is a story you built on top of it, and it's probably wrong or at least incomplete.

Write the fact first. Then write the impact, specifically and without exaggeration. Then write what you'd like to see change, in behavior you can actually observe next quarter, not in vague character terms. That's three short sentences instead of one defensive paragraph, and it reads as fair instead of personal.

Extreme Ownership adds a useful gut check here too. Before you write that someone failed at something, ask what you, as their manager, could have made clearer earlier in the year. Sometimes the honest answer changes the whole paragraph. Sometimes it doesn't, and that's fine, but asking the question keeps your reviews from reading like you're grading from the sidelines.

Write for the quiet performer, not just the loud one

Here's a pattern that shows up in almost every management book on team dynamics, including Good Boss, Bad Boss. Managers write their best, most specific reviews for the people who talk to them the most, and their vaguest reviews for the quiet, steady performers who just do the work without narrating it. That's backwards, and it's worth catching in yourself before you hit submit.

If someone on your team hasn't been pinging you with updates all quarter, that's not a review gap, it's a tracking gap on your part. Pull up your project tracker, your calendar, or whatever system holds the actual record of what shipped. You'll usually find more specific material than your memory gave you credit for, and the review gets fairer for it.

A 45 minute process for writing performance reviews for your whole team

Most managers write reviews the slow, painful way. They open a doc, stare, write a paragraph, close the laptop feeling bad, then repeat the next night for a week. Try batching it instead.

Block one 45 minute window. Before you open a single doc, spend ten minutes refreshing yourself on two or three management ideas you want to apply across the board, whether that's the strengths first approach above or a feedback structure you like. This is exactly the kind of prep that works well on a commute or over coffee, since a ten minute summary of a book's core argument is enough to borrow the framework without reading the whole thing. If you want a running list of what to feed into that ten minutes, this reading list for new managers is a solid starting point.

Then write every review in one sitting, using the same structure each time. Two to three specific strengths, one or two areas for growth stated as fact plus impact plus desired change, and a closing line about what you're hoping to see from them next quarter. Keeping the structure identical across your whole team also makes the reviews easier to compare fairly against each other, which matters more than most managers realize when calibration conversations roll around.

What to do when you barely know this person's work

Sometimes you inherited a direct report mid year, or they're on a different time zone, or they quietly do their job well enough that you've genuinely never had to dig into the details. Don't fake familiarity you don't have. It reads as worse than admitting the gap, because employees can tell the difference between specific praise and a template with their name swapped in.

Say what you do know plainly, pull concrete examples from tickets, docs, or commits rather than memory, and be honest in the one on one that follows that you want to understand their work better next quarter. Most people respect that far more than a review full of confident sounding nothing. If you want more on applying a book's idea to a specific moment like this one instead of just reading for the sake of reading, this piece on walking into your next meeting with one good idea from a book covers the same instinct applied to meetings instead of reviews.

None of this requires a free weekend and a stack of management books. You need the ideas inside them, fast, in a form you can actually use before Friday. That's what Sumizeit does. It turns books like the ones above into text, audio, and video summaries you can get through on a lunch break, so the next time review season lands in your calendar, you're not starting from a blank page. Head to sumizeit.com and pull up a few leadership summaries before your next round of reviews is due.