How to run performance reviews in a small business

Most small businesses do not skip performance reviews on purpose. There is no HR team to put them in the calendar, and the last one turned into a conversation about how the manager felt about the previous three weeks rather than about the work that was actually delivered.

This is the method we use ourselves, and the one we recommend to any founder-led team: five steps, roughly thirty minutes per person, and one written outcome you can still point to a year later.

Why reviews break between ten and a hundred and fifty people

Up to about twenty people the founder can hold the whole picture in their head: who is carrying the quarter, who is overloaded, who is ready for more. Once the first managers join, that picture splits. Each manager remembers a different part of the work, and the founder remembers the part they were personally in the room for.

Three symptoms show up in almost every company we talk to:

• The loudest project wins. The review becomes a verdict on whatever happened last month.
• Nine months judged on three weeks. Someone who quietly kept an unglamorous part of the business running gets no credit for it.
• Postponement. The conversation is uncomfortable without a shared standard, so it slips a quarter, and then another.

None of these are attitude problems. They are record problems: there is no written role and no evidence, so everyone argues from memory.

The five steps

1. Write the role down before you look at the person

Review the person against what the role owns — the outcomes, the decisions they can make alone, and where the role stops — not against a general idea of a good employee. This has to happen before the review, not during it, so that the standard existed while the work was being done.

2. Collect evidence as the work happens

One short note after a project, a launch or a one-to-one is enough. Four or five lines per person per quarter beat a four-page form written the night before the review. What matters is that the note exists before you know how you feel about the outcome.

3. Prepare the comparison before the meeting

Lay the evidence next to the role and write two or three plain statements: where the work landed, where it fell short, and what you are proposing. If you cannot write the proposal in three sentences, you are not ready to have the conversation.

4. Run one conversation, about thirty minutes

A structure that works: five minutes reading the role and the evidence together, fifteen minutes on what the person saw from their side, five minutes on the decision, five minutes on what happens next. The point of doing it in one sitting is that the manager decides in the room instead of scheduling a follow-up that never happens.

5. Record the decision, with a date

What was agreed, who decided, and when. This is the step everyone skips and the one that saves you later: an unrecorded promise is the most reliable way to end up telling two different stories about the same decision.

How to evaluate employee performance: a worked example

Take a Customer Success Lead in a forty-person software company. 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.

The evidence is three short notes from the quarter rather than a survey: renewals closed at 90 and 92 percent, two escalations closed inside a week, and one credit granted that should have gone to the founder first.

The comparison writes itself. The deliverables landed above the bar; one decision crossed a boundary that was written down in advance. The proposed outcome: the limit moves up to two months, and the boundary is repeated back in the next one-to-one instead of being treated as a fault.

That is a review where nobody has to argue about perception. There is a role, there is evidence, there is one decision, and there is a date attached to it.

What to do when the answer is "not yet"

Four outcomes are honest and useful, and every review should end in one of them:

• A clearer role — the scope was fuzzy, so the fix is the definition, not the person.
• More support — training, a second pair of hands, or a manager who stops moving the priorities weekly.
• A different scope — the person is strong, the seat is wrong.
• An honest fit conversation — kinder in month six than in month twenty.

The mistakes we see most

• Rating people against a job description that lists tasks. Everyone ticks every box, which tells you nothing about how the role was carried.
• One annual cycle. In a small team the work changes every few months, so the standard has to move with it.
• Skipping the record. A decision that lives only in the founder's head is not a decision your managers can follow.

Where software actually helps

The two hard parts of reviews are not judgement, they are memory and structure: keeping the role current, keeping the notes, and putting the comparison in front of the manager at the right moment. That is the part employee performance review software can carry for you, and the part we built Team Inflection around — the role, the running history and the outcome in one record, so the next review starts from the last agreement instead of from a blank page.

The condensed version lives on our guide page: performance reviews for small teams. The same cycle, run across the whole team twice a year, is a talent audit for small businesses.