How to Run Performance Reviews at a 10-Person Company Without HR

At a 10-person company, performance reviews usually fail for one of three reasons:

1. nobody owns the process,
2. the team overcomplicates it before it starts, or
3. the manager avoids the conversation until the moment has already passed.

The problem is usually not a lack of good intentions. It is that a small team needs a process one person can actually finish.

If you are the founder, team lead, or manager, you do not need to invent an HR department. You need a lightweight review cycle with a clear owner, a short timeline, and language that is specific enough to be useful.

Here is a version that works for a 10-person company without turning into a quarter-long project.

What a small-team review process should actually produce

Keep the output narrow.

A good review cycle for a team this size should end with:

• one clear written review per person
• a short conversation between manager and employee
• one or two strengths worth reinforcing
• one main growth area
• concrete expectations before the next review

That is enough.

If your process requires forms nobody wants to fill out, committee review, or a stack of calibration meetings, you have already built something too heavy for a 10-person company.

Decide these four things before you send anything

Before you ask anyone for feedback, make four decisions on one page.

1. Who is being reviewed?

Do not review the whole company at once unless you have to. If this is your first cycle, start with one team or one layer of managers and direct reports.

2. Who gives input?

For most small teams:

• the manager writes the review
• 2 to 4 peers give structured input when they work closely with the person
• the founder reviews the managers, or writes those reviews directly

You do not need everyone reviewing everyone.

3. What is the final output?

Choose one format before collecting feedback. The simplest structure is:

• strengths to keep using
• growth area to improve
• expectations before the next review

4. Who owns the schedule?

One person owns the cycle. On a small team, that is often the founder, ops lead, or the manager running the team.

If ownership is fuzzy, the process dies in the middle.

A two-week review calendar that a 10-person company can finish

This is the version to run when you want structure without a full HR project.

Day 1: announce the process

Tell the team exactly what is happening, who is involved, and what the output will be.

Use plain language:

We are running a lightweight performance review cycle over the next two weeks. Each manager will gather a few structured inputs, write one review per direct report, and then meet 1:1 to talk through it. The goal is clarity, not paperwork.

That message matters because uncertainty creates avoidance.

Days 2-5: collect input

Ask the manager and a small set of relevant peers for written input. Keep the questions focused and behavior-based.

If you need a starting point, use a short question set like:

• what work is this person consistently reliable at?
• where did they have the biggest positive impact?
• where do they create drag, confusion, or rework?
• what is one change that would most improve their results?

For a complete copy-and-paste version, use these 10 performance review questions for small teams.

The point is not to gather every opinion. The point is to collect enough signal to see patterns.

Days 6-8: write the review

The manager should now turn the input into one document that can actually be said out loud.

A useful review is usually short. In most cases, one page is enough.

Use this structure:

1. strengths to keep using
2. one main growth area
3. expectations before the next review

If a comment is too vague to say in person, it is too vague to include in writing.

Days 9-10: hold the conversation

The written review is not the finish line. The conversation is.

A simple 30-minute agenda works:

1. start with what is working
2. move to the main growth area
3. explain why it matters to the team and the role
4. agree on what better looks like
5. close with next steps and support

Do not turn the meeting into a surprise. The document should help the conversation feel clearer, not more defensive.

Be honest about privacy on a tiny team

This is where small-team reviews go sideways.

If four people work closely together, they can usually guess who said what. So do not promise anonymity you cannot actually provide.

A better approach is:

• tell people their input is private to the manager
• summarize patterns instead of forwarding raw comments
• avoid verbatim quotes unless the person giving feedback is comfortable being identified
• remove details that make the source obvious when they are not necessary to the point

The trust rule is simple: never describe the process as safer than it really is.

That honesty matters more than polished HR language.

How to write feedback that does not collapse into vagueness

Most weak reviews fail in one of two ways:

• they are too soft to be useful, or
• they sound harsher on paper than the manager would ever say in person

You want a middle ground: specific, behavioral, and fair.

Instead of this:

Communication needs improvement.

Write this:

Project updates often come after deadlines move, which leaves the team reacting late. By the next review cycle, I want blockers and timeline changes raised earlier so the team can adjust before work slips.

That kind of sentence does three things:

• names the behavior
• shows the impact
• makes the next expectation visible

If you cannot connect feedback to real work, it probably belongs in a draft note, not the final review.

What to do when the employee disagrees

Some disagreement is normal.

When it happens:

• listen before defending the writeup
• separate disagreement about tone from disagreement about facts
• ask for missing context or examples
• update wording if it is inaccurate
• do not abandon the core point just because the conversation is uncomfortable

The goal is not to win an argument. The goal is to leave with a shared understanding of what should continue and what should change.

What not to build yet

A 10-person company usually does not need:

• a year-round performance management platform
• a complicated rating system
• cross-company calibration rituals
• a giant competency framework
• a new process for every edge case

You need a review cycle the team will actually repeat.

If this process works once, run it again in six months with lighter setup the second time.

If you want the lightest useful version

Own the cycle, keep the input structured, write reviews in plain language, and tell the truth about privacy.

That is enough to run a real performance review process at a 10-person company.

If you want help collecting the inputs and turning them into a manager-owned written review, that is what I built Teemzo for. It is $49 per person reviewed, no subscription, so you can run the process when you need it without paying for a year-round HR platform.