Performance reviews for small teams

A review is a categorization, not a document

Without an HR team, reviews either never happen or happen in a rush: the founder, a manager and a memory of the last three months, written up as an essay the night before. It does not have to be either. You are not scoring twenty competencies. You are answering one question against a role that was written down before you asked it.

Four categories are enough for every people decision a small company makes: who is ready for more, who is carrying the role as it stands, who needs support, and who is in the wrong role. Rating more than that is what turns ten minutes into an afternoon — and what makes two managers disagree about the same person.

The four categories

Four letters, defined once by you and then the same for the whole company.

• A — above the role: the person delivers more than the role asks for today, and the evidence is there. An A says the role can grow, not that a promotion is owed.
• B — the role, delivered: the work matches what the role owns. Most of a healthy team sits here, and B is a good answer, not a consolation prize.
• C — partly there: parts of the role are not met yet. The answer is support, a narrower scope or a clearer boundary — not a warning.
• D — not this role: even with support, the work does not match what the role needs. That is a statement about the fit between person and role, and it ends in an honest conversation about a different one.

What the categorization needs

• A role that was written down first — what the person owns, where it ends and what success looked like. Review the person against that, not against a general idea of a good employee.
• The evidence, next to the person. A short note after a project or a one-to-one is enough; it only has to exist before the review starts, not the week before it.
• Your definitions of A, B, C and D — what each letter means and which action it allows. You set that once; no tool hardcodes it for you.
• The letter and the next action, written down with a date, so the next review starts from the last agreement instead of from memory.

One person, one letter: a worked example

Take a Customer Success Lead in a company of forty people. The role as written in January: hold renewals above 85 percent, own the escalation path for the top ten accounts, decide credits up to one month without asking, and hand anything that changes price to the founder.

Three short notes from the quarter are the whole evidence base: renewals closed at 90 and 92 percent, two escalations closed inside a week, and one credit decision that belonged to the founder.

• Deliverables above the bar, one boundary crossed. That is a B, not an A: the role is delivered, it is not outperformed.
• The next action follows from the letter: repeat the boundary back in the next one-to-one instead of treating it as a fault.
• Ten minutes, one letter, one decision — written down on the day, and still explainable a year later.

Why the four categories have to be written down

The categorization is only simple while everyone reads it the same way. When each manager carries a private idea of a good employee, the same person comes out A in one review and C in the next, and the conversation becomes an argument about perception.

• Defined once, four letters make "she is a B, he is an A" mean the same thing in every room.
• Nobody re-opens the rating, because the definitions were agreed before the case was on the table.
• The decision lands in the meeting instead of being postponed to the next one.
• It stays defensible: the role and the evidence were there before the letter was.