Performance Review: A Practical Guide for Small Business
Performance reviews for small business: types, process, how to write them, examples, and a practical playbook without enterprise overhead.
Performance Review
A practical guide for small businesses, demystified
The first performance review I ever ran ended with the employee in tears and me apologizing for things I should have said six months earlier. She was not a weak performer. She was not unreasonable. She was just hearing, for the first time in a 14-month tenure, that her communication style had been frustrating the team. I had noticed it in month two. I had said nothing. I had let it accumulate until the formal review forced me to bring it up. By that point, no amount of careful framing could undo the fact that she had spent over a year doing things I considered problems without anyone telling her.
Most small business owners I talk to have a version of that story. Performance reviews feel like enterprise overhead, so they get scheduled once a year, written the morning of the conversation, and delivered with all the accumulated avoidance of the previous twelve months. The employee leaves the conversation either bewildered (why did no one say this earlier?) or vindicated (I knew this was coming, and you confirmed why I have been looking elsewhere). Neither outcome is what the review was supposed to produce.
This guide explains what a performance review actually is, how to run one well, the types that matter for small businesses, and the practical playbook for doing this without an HR department. I built FirstHR for small businesses, and most of what follows comes from running and mis-running performance reviews myself. One disclosure up front: FirstHR does not currently include a performance review module, so nothing below is a pitch for one.
What a Performance Review Actually Is
Three things a performance review is not, despite frequent confusion. First, it is not the entire performance management practice. The review is one event; the practice is the year of conversations and feedback that lead up to it.
Second, a review is not a surprise event. Anything an employee hears for the first time at a review represents a manager who avoided the conversation when it would have been useful. Third, it is not a paperwork compliance exercise. The forms support the practice; they are not the practice itself.
The simplest framing: a performance review is the formal moment where the manager and the employee agree, in writing, on how the past period went. It is the documentation that protects the company legally, anchors compensation decisions, and creates continuity from one cycle to the next. Done well, it produces alignment on what comes next. Done badly, it produces defensiveness, recency bias, and surprise resignations.
Appraisal vs Assessment vs Evaluation
These are the same event under different labels, and the differences are about emphasis rather than substance. Appraisal is the older and more formal word, and it usually implies a rating attached to a pay decision. Assessment implies measurement against a defined standard. Evaluation is the neutral catch-all most US companies use in practice.
| Term | What it emphasizes | Where you usually see it |
|---|---|---|
| Performance appraisal | A rated judgment of the period, most often tied to a pay or promotion decision | Formal HR policy, public sector and union settings, academic writing |
| Performance assessment | Measurement against a defined standard or competency framework | Skills matrices, probation decisions, licensed and certification-heavy roles |
| Performance evaluation | The general act of judging how the period went | Most small business forms and templates |
| Performance review | The conversation and the written record together | Everyday use in most US companies |
| Employee evaluation, staff appraisal, work evaluation | The same event phrased around the person rather than the period | Handbooks, older forms, and job postings |
The practical implication is to stop shopping for the right word and pick one. Use it in the calendar invite, the template, the handbook, and the conversation itself. When each manager uses a different label, the team reads it as different standards, and that impression is the real problem rather than the vocabulary.
Performance Review vs Performance Management
Performance management is the entire ongoing practice: setting expectations, monitoring work, giving regular feedback, supporting development, and reviewing performance at a defined cadence. The performance review is just one event within that practice. Treating the two as synonyms produces the "annual review with no real management between reviews" pattern that dominates most small businesses.
| Dimension | Performance Review | Performance Management |
|---|---|---|
| Time scope | A defined event (annual, quarterly, etc.) | Continuous, year-round |
| Output | A documented record | Behavior change, development, engagement |
| Frequency | 1-4 times per year | Daily and weekly |
| Primary purpose | Document for decisions | Help employees do their best work |
| What fails without it | Compliance, fairness, legal defensibility | Engagement, retention, development |
Put simply, the review is the formal checkpoint that closes one cycle, and management is everything that happens between checkpoints. A review without management is paperwork without practice; management without reviews is conversation without documentation. You need both.
Why Performance Reviews Matter
The honest case for performance reviews comes down to three failure modes that show up reliably when they are absent or poorly run. These failures are not theoretical; they are the predictable outcomes of running a business without a real review practice.
The first failure is unfair compensation decisions. Without a documented review, raises and bonuses get decided based on recency bias, personal relationships, and whoever happened to be most visible to leadership in the weeks before the decision. The team eventually notices. Trust erodes.
The second failure is surprise resignations. Top performers who never hear they are appreciated assume the silence means their work goes unnoticed; they take a recruiter call and leave.
The third failure is the unfireable underperformer: the manager has noticed issues for months but has no documented record, so the eventual termination decision either drags on or creates legal risk. Real reviews prevent all three.
Types of Performance Reviews
Six main types dominate the field, each with different strengths and use cases. Most small businesses use a combination, not a single type exclusively. Below is a practical breakdown of when each works and when it does not.
Choosing the Right Mix
The instinct most small business owners have is to pick one type and run it religiously. Resist the instinct. No single type gives you real-time feedback, documentation frequent enough to catch issues, and the formal annual record that compensation and HR files depend on.
The practical mix that works for most small businesses combines several types: weekly 1-on-1s as the foundation (continuous feedback), quarterly written check-ins (formal documented reviews on a fast cadence), an annual summary (the longer view tied to compensation), and a 90-day review for every new hire (the probationary documentation). Together they cover all three jobs.
| Company stage | Recommended cadence | What to skip |
|---|---|---|
| Founder-led small business, no managers yet | Weekly 1-on-1s + annual summary | Quarterly formal reviews (overhead), 360-degree (too political) |
| Small business, first managers | Weekly 1-on-1s + quarterly written + annual summary + 90-day for new hires | 360-degree formal reviews, dedicated software |
| Small business, several teams | Above + lightweight 360 for senior roles only | Calibration committees, 9-box grids, forced ranking |
| Growing into mid-size | Above + structured calibration across managers | Forced bell curves, full enterprise review software |
| Mid-size and enterprise | Full structured system with calibration, talent reviews, integrated software | Continuing to operate informally |
The pattern across all sizes: more frequent informal feedback beats less frequent formal reviews. The annual review remains the legal documentation standard, but on its own, it is not performance management. The companies that get the most value from reviews are the ones that combine formal cadence with continuous feedback throughout the period.
Performance Appraisal Methods
Appraisal methods are the mechanics of how the assessment gets made, which is a separate question from how often you run reviews. The methods below cover almost everything you will encounter in practice, and most small businesses end up combining two or three of them without ever naming them.
| Method | How it works | Where it fits |
|---|---|---|
| Graphic rating scale | The manager scores a fixed list of competencies on a numbered scale, usually 1 to 5 | Fast and familiar. Compresses nuance into a digit and invites everyone-gets-a-3 scoring |
| Behaviorally anchored rating scale | Each point on the scale is anchored to a written description of observable behavior | The most consistent method across managers, and the most expensive to build for every role |
| Management by objectives | Performance is judged against goals agreed at the start of the period | Strong where output is measurable. Unfair when priorities changed in month four and the goals did not |
| Critical incident method | The manager logs specific events, good and bad, through the period and writes the review from the log | The highest-value method for small teams. It is the running document, and it is what kills recency bias |
| Narrative assessment | A written assessment built on specific examples, with no scores attached | The default for small businesses. Rich signal, hard to compare across managers without shared criteria |
| 360-degree feedback | Structured input from peers, reports, and cross-functional partners feeds the assessment | Useful for development. Risky for pay decisions, where it turns political fast |
| Forced ranking or forced distribution | Employees are ranked against each other and slotted into fixed buckets | Built for organizations with thousands of employees. On a team of twelve it manufactures losers |
For a company without an HR department, the working combination is a critical incident log kept through the period, goals agreed at the start of it, and a narrative writeup at the end. Add a rating scale only where the number feeds a real decision. Skip behaviorally anchored scales and forced ranking until someone else runs the process for you.
The Performance Review Process
The review process has four phases: preparation, the conversation itself, documentation, and follow-up. Most failures happen in preparation. A review that is well-prepared mostly runs itself; a review that is written the morning of the conversation produces all the predictable problems of recency bias and missed context.
Preparation: The Two-Week Lead Time
Schedule the review at least two weeks in advance. Send a calendar invite with the date, the duration (60-90 minutes for an annual; 45-60 for a quarterly), and the self-assessment template. Ask the employee to complete the self-assessment before the meeting. Two weeks gives both sides time to think. Last-minute reviews produce defensive employees and unprepared managers.
During the lead time, the manager writes the review using the running document of notes from weekly 1-on-1s throughout the period. If the running document exists, the review writes itself in 30-45 minutes. If it does not, the review will be heavily biased toward the last two weeks of the period, which is the most common quality problem of all. Write your review before reading the self-assessment; reading it first anchors your perception.
The Conversation
The review meeting itself runs best with a consistent structure. Open with the period's goals and the actual outcomes, with concrete examples. Move to observations on behaviors and contributions, both positive and corrective.
The gap between the self-assessment and the manager assessment comes next, and it is often the most useful part of the conversation. End with development priorities for the next period and confirmation of next-period goals. Reserve the last 10 minutes for the employee to ask questions or raise concerns; these often surface the most important context.
When a Performance Discussion Goes Sideways
A performance discussion goes sideways in two ways: the employee disputes what you wrote, or the room gets emotional and neither of you can think straight. The instinct in both cases is to soften the feedback until the discomfort passes, which is the same avoidance that created the problem in the first place.
When the dispute is about facts, ask what they are working from. If they name a contribution you did not know about, say so and change the document. A review that moves because new evidence arrived is a stronger record than one defended out of pride.
Disagreement about interpretation is different. Record both views in the document and keep going; you are not required to converge in the meeting. When the conversation turns emotional, stop it and offer to pick it up in two days. The feedback does not expire, and most people hear it far better after a gap.
Documentation and Follow-Up
After the conversation, update the review document with notes from the discussion: any commitments, development plans, decisions, or concerns raised. Both parties acknowledge in writing that the conversation happened. Schedule the next quarterly check-in or 1-on-1. The review is not over until the documentation is complete and the next cycle is scheduled.
Across a team, the failure is rarely one bad review. It is three reviews that happened, two that slipped, and one employee who quietly never got one, which is both a fairness problem and a documentation problem. Track the cycle itself on one sheet so you can see at a glance who is still owed a conversation and which comp discussions are still sitting too close to the review.
| A | B | C | D | E | F | G | H | I | J | K | L | M | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Employee | Manager | Review type | Period covered | Review scheduled for | Self-assessment sent | Self-assessment returned | Manager review written | Conversation held | Acknowledged in writing | Comp conversation held | Next check-in scheduled | Notes |
| 2 | Replace this row with your first employee | Quarterly, annual, or 90-day | At least two weeks after the invite goes out | With the calendar invite | At least three days before the conversation | Written before the self-assessment is read | Both parties, on the document itself | Weeks after the review, not the same meeting | An empty row in this sheet is the fairness problem, not a formatting one | ||||
| 3 | |||||||||||||
| 4 | |||||||||||||
| 5 | |||||||||||||
| 6 | |||||||||||||
| 7 | |||||||||||||
| 8 | |||||||||||||
| 9 | |||||||||||||
| 10 | |||||||||||||
| 11 | |||||||||||||
| 12 | |||||||||||||
| 13 |
How to Write a Performance Review
The writing itself is where most reviews succeed or fail. A good performance review is specific, evidence-based, and free of surprises. The structure below is what works for most small businesses.
- A summary of the period’s goals and the actual outcomes, with specific examples
- Observations on key behaviors and contributions, with concrete situations the employee will recognize
- Honest assessment of areas of growth, framed as forward-looking development priorities
- The employee’s self-assessment summarized and the gap between self and manager view discussed
- Documented development priorities for the next period
- A clear connection (if applicable) to compensation, promotion, or other decisions
- Both parties’ acknowledgment that the conversation happened and the content was discussed
- Vague language (“great teammate,” “could improve communication”) with no specifics
- Recency bias: only the last two weeks of the period appear
- First-time feedback that the employee has never heard before
- Praise inflation that makes the next time you give honest feedback feel disproportionate
- Mixing the development conversation with the compensation conversation
- Numeric ratings without supporting narrative explanation
The Specificity Standard
The single most important quality of a good review is specificity. "Sarah is a great teammate" is filler. "Sarah's handling of the customer escalation in March, where she stayed late to coordinate with engineering and shipped a workaround within 48 hours, is the kind of ownership we want more of" is a review. The first version produces no behavior change and damages credibility. The second produces a clear signal about what the company values and reinforces the specific behavior that demonstrated it.
The same standard applies to corrective feedback. "Could be more proactive" is not feedback; it is filler. "In the May roadmap meeting, when the customer feedback came up, you waited for me to summarize the implications instead of leading the conversation; I would like you to take the lead on the customer-facing summary in the next meeting" is feedback. The specificity makes it actionable; the lack of specificity makes it vague enough to be either ignored or interpreted as personal.
Examples and Phrases for Performance Reviews
Examples and phrases are where many managers start when a performance review is due, and most published collections are generic enough to be useless. The pattern that works: phrases that name a specific behavior, ground it in a situation, and connect it to a future expectation. Below are examples in that pattern across common review categories.
Strong Performance Examples
| Category | Example phrasing |
|---|---|
| Quality of work | “The customer onboarding documentation you produced in Q3 is now used by the entire support team. Specifically the troubleshooting flowchart cut average ticket resolution from 4 hours to 90 minutes.” |
| Initiative | “You identified the data inconsistency in the billing system before any customer reported it and led the cross-functional fix without being asked. That is the level of ownership we expect at the next level.” |
| Collaboration | “In the cross-team launch in October, you were the connective tissue between engineering and marketing. The launch went on schedule because you held the timeline together when it was slipping.” |
| Communication | “Your weekly project updates have become the model the rest of the team copies. The structure (decisions made, blockers, next checkpoint) is what the company needs more of.” |
| Customer focus | “The way you handled the angry customer in March, calmly walking through the issue and following up daily for a week, retained an account we were about to lose. That account is now our largest reference.” |
Areas of Growth Examples
Growth feedback, printed on most forms as opportunities for improvement, fails when it stays abstract. Each example below names the situation, states the cost of the current behavior, and sets one specific change for the next period. That third part is what separates a growth area from a complaint.
| Category | Example phrasing |
|---|---|
| Delegation | “I noticed you took back the design work from the contractor twice in Q2 because the output was not exactly how you would have done it. The trade-off is your time. Next quarter, the goal is to coach the contractor through one revision rather than redoing the work.” |
| Communication timing | “The Q2 customer churn issue surfaced to me through Slack three days after you knew about it. Going forward, raise issues of that magnitude within 24 hours so we can address them together.” |
| Strategic thinking | “Your tactical execution is consistently strong. The growth area is connecting tactical decisions to longer-term implications. Next quarter, I would like you to write a one-page strategy memo for each major initiative before kickoff.” |
| Feedback delivery | “You give honest feedback in private 1-on-1s. The growth area is giving the same level of feedback in real time during meetings, when the rest of the team can also benefit. I will model this in the next planning session and ask you to do the same.” |
| Boundary setting | “You are answering Slack messages on weekends consistently. The team copies what they see; if you are working weekends, others feel they should too. Next quarter, I want to see weekend Slack volume drop by half.” |
Notice the pattern across all of these: specific situation, specific behavior, specific expected change. This is the structure that makes feedback actionable. Generic phrase lists ("exceeds expectations," "meets expectations," "needs improvement") without this structure are filler that produces no behavior change.
Phrases by Performance Level
Most managers need help with the language for honest feedback at different performance levels. The phrases below are starting points, not scripts; the specificity test still applies. Adapt each to a real situation the employee will recognize.
| Level | Example phrasing |
|---|---|
| Top performer | “You consistently deliver beyond what the role requires. The Q3 customer migration is a good example: you scoped the work yourself, identified risks I had not seen, and shipped on time without escalation. This is the level we want to reward and to use as a model for the rest of the team.” |
| Meets expectations | “You reliably deliver what the role requires. The Q3 product release shipped on time at the quality we expected. The growth area for next quarter is taking on one stretch responsibility: leading the cross-functional planning meeting, owning a customer escalation end-to-end, or scoping a small initiative independently.” |
| Mixed performance | “Your technical work is consistently strong. The growth area is communication: in three of the last four cross-team projects, the engineering team learned about timeline slips after they had already happened. The expectation for next quarter is raising risks within 24 hours of identifying them, in the team channel, not in private DMs.” |
| Underperforming | “The work this quarter has not met the bar for the role. Two specific examples: the Q3 deliverable shipped 6 weeks late with quality issues that required follow-up work from the rest of the team, and the customer-facing communication in the August incident was not at the standard we need. We will discuss a structured improvement plan in our next 1-on-1.” |
| New hire (90-day) | “The first 90 days have been a strong start. You have ramped up faster than expected on the technical side and have begun contributing to architecture conversations. The growth area for the next quarter is owning a customer-facing project end-to-end, with me available for support but not driving.” |
What Not to Say
Some phrases do active damage. They are clichés that signal lack of thought, or they encode subjective judgments that read as personal rather than performance-based. Avoid the categories below.
- “Not a culture fit” (subjective; often mask for unconscious bias; weak documentation in legal contexts)
- “Lacks executive presence” (vague; not tied to specific behavior; unfair to people whose communication style differs from leadership’s)
- “Just needs to be more proactive” (vague; gives no specific behavior to practice)
- “Has potential” (without specifics, sounds like “not delivering yet” with no path forward)
- Generic phrase-list language copied from a vendor template (the team can tell)
- Praise inflation: calling everyone a “rockstar” or “A-player” when the actual performance does not warrant it (devalues the words for the people who actually earn them)
Performance Review Tips That Matter
Below are the tips that consistently make the biggest difference in review quality, drawn from running and watching reviews across many small businesses. These are not the only useful tips; they are the ones that compound the most.
- Write the review before reading the self-assessment, not after; reading the self-assessment first anchors your perception
- Open the conversation with a specific recent contribution; do not lead with criticism even when criticism is the bulk of the review
- Use the 80/20 ratio: spend most of the conversation on what the person should keep doing and grow, not on what they should stop doing
- When delivering hard feedback, name the behavior, the situation, and the expected change; avoid making it about the person
- Pause for the employee to react; resist the urge to fill silence with more feedback or qualifiers
- End with a clear ask: what specifically will be different next quarter, and what support will you provide to make it possible
- Send the self-assessment with the calendar invite and ask for it back at least three days before the conversation, so the employee has time to reflect rather than react
- Tell the employee up front that a gap between their self-assessment and your view is expected, and that it will be discussed openly rather than held against them
- Invite them to ask for the specific situation behind any point that feels unfair, and have that example ready before you walk in
- Encourage them to take notes during the conversation, and send your own written summary afterward; emotional moments make memory unreliable
- Do not push for agreement on the document in the meeting; give them a few days to digest it and add a written response to the file if they want to
- End by asking what one specific commitment from you (more support, clearer expectations, removal of a blocker) would make the next quarter easier, and write it down
Performance Reviews for Small Business
Most published material on performance reviews assumes the reader works at a Fortune 500 with a dedicated HR team and review software. The frameworks are designed for organizations where consistency across thousands of managers is the central problem. None of these assumptions hold at small business scale, where the manager is usually the founder or the operations lead, the team is small enough to know each other, and review software is overhead the company cannot afford and does not need.
The version that works for small businesses is much simpler. The full system fits in a shared document per employee, plus a calendar reminder for weekly 1-on-1s, plus a quarterly review template. No software, no calibration committees, no 9-box grids (the enterprise chart that plots each person's performance against their potential).
The Small Business Review Stack
| Component | Tool | Time investment |
|---|---|---|
| Weekly 1-on-1 notes | Shared Google Doc per employee | 5-10 min after each 1-on-1 |
| Quarterly review template | Google Doc or Notion template | 30-45 min per employee per quarter |
| Annual review summary | Separate document, references quarterly check-ins | 60-90 min per employee per year |
| 90-day review for new hires | Separate template specific to probationary period | 60 min per new hire |
| Self-assessment template | Same template structure for consistency | 30 min for the employee to complete |
The total time investment for the manager is roughly 6-12 hours per employee per year, spread across the year. Most of it goes into the few minutes of notes after each weekly 1-on-1, and that time buys the highest-return HR practice the company can run.
The One-Page Quarterly Template
The quarterly review document fits on one page. Two pages maximum. The template structure that works:
- Header: employee name, role, period, manager
- Goals from last quarter and actual outcomes (with specifics)
- Top 2-3 strengths demonstrated this quarter (with specific examples)
- Top 1-2 areas of growth (with specific examples and forward-looking framing)
- Self-assessment summary and notable gaps with manager assessment
- Goals and development priorities for next quarter
- Both parties’ acknowledgment that the conversation happened
The discipline of fitting on one page forces specificity. Long reviews drift into corporate language and filler; short reviews force the manager to pick the points that actually matter. The team also reads short reviews; long reviews get filed and forgotten.
Reviewing Remote and Hybrid Employees
A performance review for remote employees uses the same structure as any other review, with one adjustment: the evidence has to come from output and written record rather than from what you happened to witness. Managers who skip that adjustment rate the people they see in person higher, and the whole team notices the pattern before the manager does.
Three habits make it work. Write the expectations for a remote role in terms of deliverables and response commitments rather than hours online. Keep the running document somewhere both of you can open, so the review is never one person's recollection of a year of video calls. Send the self-assessment earlier than you would in an office, because the hallway context that fills the gaps in an office does not exist.
Run the conversation on video with cameras on, never over chat and never on a call where either side is walking somewhere. Send the written review a day ahead so a remote employee can read it without an audience. That is the one structural advantage remote reviews have over the office version, and most managers waste it by reading the document aloud instead.
Running Performance Reviews Without an HR Department
Most small businesses do not have a dedicated HR department. The founder or operations lead plays both roles: designing the review framework and running it with their direct reports. This has trade-offs in both directions. The advantage: there is no friction between framework and practice; the same person owns both. The disadvantage: the framework gets built quickly, often without the legal and consistency considerations a dedicated HR person would catch.
The practical recommendation for a small business without HR: start from a simple template that already exists, such as the one-page version above or one of the performance review forms published by the Society for Human Resource Management (SHRM), rather than inventing your own. Spend the time you save on the actual practice, which is where the real value comes from.
The Owner-as-Reviewer Risk
The single biggest risk in running reviews without HR is the owner-as-reviewer problem: the founder reviews everyone, which means the founder's biases, blind spots, and personal preferences become institutional. There is no calibration check. Employees who happen to align with the founder's working style get strong reviews; employees who do not, even if they are equally productive, get weaker ones. Over time, this homogenizes the team in ways that hurt long-term performance.
The mitigation: write down review criteria before writing reviews. List the behaviors and outcomes the role is responsible for, in order. Score against those criteria, not against general impression. Ask one trusted senior team member to read the review draft before delivery and flag anywhere the language sounds personal rather than performance-based. This adds 15 minutes to the process and catches the most common bias problems.
Reviewing the Managers on Your Team
A manager performance review evaluates a different job than an individual review does, so the criteria have to change with it. What you are assessing is not the manager's personal output. It is what happened to the people and the work they were responsible for, which is a slower and more indirect signal.
| What to evaluate in a manager | Evidence to look for |
|---|---|
| Team outcomes | Whether the team hit its goals, and whether the manager saw the misses coming or was surprised by them |
| Retention | Who left, what they said on the way out, and whether the manager knew the risk before the resignation landed |
| Hiring judgment | How the people they hired in the last year are performing, and how quickly they acted on a hire that was not working |
| Development of reports | Name the specific people who took on more scope this period and what the manager did to make that possible |
| Feedback discipline | Whether their reviews are written from notes or from memory, delivered on time, and free of surprises for the employee |
| Upward and peer input | What their reports and peers say about how decisions get made and how conflict gets handled |
Most of that evidence lives with the manager's team rather than with the manager, so a management appraisal that never asks their reports anything is an opinion piece. A short set of the same questions to each report, asked at the same point in every cycle, is enough at small scale. Full 360 machinery is not required to get the signal.
Performance Rating Scales, Calibration, and Bias
A performance rating scale is a fixed set of levels a reviewer assigns to summarize the period, most often five points running from poor to excellent. Use one only where the number drives a real decision: a raise, a bonus pool, a promotion slate. A rating with no decision attached is a digit that upsets people for no return.
What separates a useful scale from a demoralizing one is not the number of points. It is whether each point has a written definition a manager can apply without guessing, and whether those definitions describe observable work instead of attitude. Write the definitions before anyone starts filling in forms.
| Rating | Label | What it has to mean before you assign it |
|---|---|---|
| 5 | Outstanding | Delivered well beyond the scope of the role, with at least two specific results the company would not otherwise have had. Rare by definition. If a third of the team is a 5, the scale is broken |
| 4 | Exceeds expectations | Met everything the role requires and took on real scope beyond it: a project nobody assigned, a problem nobody escalated, a teammate who is better because of them |
| 3 | Meets expectations | Did the job the company hired them to do, at the quality expected, on the timelines agreed. This is a good rating, and saying that out loud is most of the work of keeping a scale alive |
| 2 | Needs improvement | Fell short on a specific, documented part of the role. You should be able to point to feedback already given during the period and to what changes next quarter |
| 1 | Unsatisfactory | Did not perform the core duties of the role. This should never be the first time the employee hears it, and it normally precedes a written improvement plan |
Running a Calibration Meeting
A calibration meeting is a working session where managers put their draft ratings side by side before anything is delivered and defend each one against the same standard. The purpose is not to force a distribution. It is to catch the manager who rates everyone a 4 and the manager who has never given anything above a 3.
It becomes worth the hour once more than one person is writing reviews, which for most small businesses arrives with the first layer of managers. While the founder is still the only reviewer, the criteria-first habit described above does the same job that calibration does at larger scale.
- Every manager brings draft ratings plus one piece of written evidence per rating, circulated before the meeting rather than read out in it
- Outliers go first: every 5 and every 1, with the evidence behind them, because that is where the disagreement lives
- The group asks one question of each rating: would this survive if the same work had been done by someone on another team?
- A rating moves only when the evidence moves. A rating changed to fit a curve is the exact failure this meeting exists to prevent
- One person records what changed and why, because that record is the defense if a pay or promotion decision is challenged later
- Reviews are delivered only after calibration, which means the draft has to exist about a week before the conversation
The Biases That Distort Performance Ratings
Appraisal bias is any pattern that moves a rating for reasons other than the work. Most of it is not prejudice in the obvious sense. It is the set of predictable shortcuts memory takes when one person summarizes twelve months of another person's work from recall, under time pressure, the week it is due.
| Bias | How it shows up in a review | The practical counter |
|---|---|---|
| Recency | The last six weeks dominate the period, so a strong year with a rough December reads as a weak year | Write from the running document instead of from memory |
| Halo and horns | One standout strength, or one visible failure, colors every other category on the form | Rate each category against its own evidence and make yourself name an exception |
| Leniency and severity | One manager’s 4 is another manager’s 3, consistently, across an entire team | Calibration, plus written definitions for every level of the scale |
| Central tendency | Everyone lands on a 3 because the middle is the least uncomfortable number to defend | Require a written justification for every rating, not only for the extremes |
| Similar-to-me | People who work, communicate, and plan the way the reviewer does score higher than people who do not | Ask it directly while drafting: am I rating the role’s requirements or my own working style? |
| Proximity | The person in the office is described in more detail, and rated more generously, than the person on the other end of a video call | Judge documented output and commitments rather than visibility |
None of these are cured by good intentions. They are cured by mechanics: notes taken through the period, definitions written before the ratings, and a second person reading the draft. A bias someone can name in a meeting is a bias that has mostly stopped changing the outcome.
The Annual Review
The annual review is the most common performance review type and the most criticized. It earns both labels. As the only formal review a company runs, the annual is wildly insufficient: it surfaces feedback months too late, suffers from severe recency bias, and turns into a ritual everyone dreads. As the capstone of a year of weekly 1-on-1s and quarterly check-ins, it works exactly as intended: a documented summary of conversations that already happened, tied to compensation and longer-term planning.
The mistake is treating the annual review as the entire performance practice. The fix is to keep the annual review (it is the legal documentation standard at most companies) but pair it with quarterly check-ins and weekly 1-on-1s that do the actual work of feedback and development throughout the year.
Annual Review Structure
The annual review covers the same elements as the quarterly review but at a longer time horizon and with the addition of compensation and longer-term planning. Standard structure: summary of the year's goals and outcomes, review of the four quarterly check-ins (referenced as documented evidence), longer-term development trajectory, compensation discussion (or reference to a separate comp conversation), and goals for the year ahead. Length: 2-3 pages, conversation 60-90 minutes.
The honest test for whether your annual review is working: at the end of the conversation, does the employee say anything that surprises you? If yes, the quarterly check-ins are not real; they should have surfaced the surprise earlier. If no, the cycle is working.
Using the Review to Decide Advancement
Employees should be evaluated for advancement on evidence that they are already doing parts of the bigger job, not on how well they performed the current one. Strong performance in the current role is the entry ticket. It is not the case for promotion, and confusing the two produces the person who was excellent at the job they had and underwater in the job you gave them.
- Two or three documented examples of the person already operating at the next level, from different quarters rather than one memorable month
- A written description of what the next role is actually responsible for, so both of you are agreeing to the same job
- An honest list of the parts of that role they have not done yet, with a plan for those, because no internal candidate arrives complete
- Confirmation that the current role can be backfilled or absorbed, which is a business constraint and not a judgment about the person
- The same written standard applied to everyone at that level, set before anyone was under consideration, so the decision holds up if it is questioned
- A direct conversation about whether they want the next job at all. Management is a different job, not a prize for doing this one well
The annual review is where that evidence gets collected, but the promotion is not announced in the review meeting, for the same reason compensation is not. Let the review conversation be about the work. Come back within a few weeks with the decision, the new scope, and the number attached to it.
The Employee Self-Assessment
The self-assessment is the most underused tool in performance reviews. Done well, it improves review quality dramatically: the employee's perspective surfaces before the manager has anchored the conversation, and the gap between the two views becomes the center of the discussion. Done badly (or skipped), it produces a one-sided review where the manager talks and the employee receives.
The Self-Assessment Template
- What did you accomplish this period? Top 3-5 contributions, with specifics
- What did you struggle with this period? What would you do differently?
- Where do you want to grow in the next period? Specific skills or scope
- What feedback do you have for your manager?
- What feedback do you have for the team or company more broadly?
- Anything else you want to discuss in the review conversation?
The self-assessment is sent to the employee with the calendar invite for the review and is expected back at least three days before the conversation. The manager reads it after writing their own review, not before. The order matters: reading the self-assessment first anchors the manager's perception and reduces the value of comparing the two perspectives.
Reading the Gap
The gap between the self-assessment and the manager assessment is the most useful part of the review. If the employee underrates their performance and the manager rates them higher, the conversation surfaces hidden contributions and addresses imposter syndrome. If the employee overrates their performance and the manager rates them lower, the conversation surfaces the calibration gap that needs addressing. Either way, the gap is the substance; the matching parts are confirmations.
Performance Review Questions That Matter
The questions you ask in a review shape what gets discussed. Most published lists of review questions are too generic to draw out anything specific; the questions below are built for a real conversation that produces useful information rather than ritual answers. Adapt them to the specific employee and situation.
- What are you proudest of from this period? Walk me through the specific situation.
- What is one thing you tried that did not work, and what did you learn from it?
- Where do you feel most stretched right now? Most under-utilized?
- What is the single biggest blocker to you doing your best work?
- If you had my role for a week, what would you change about how the team operates?
- What is one piece of feedback for me as a manager that I have not heard yet?
- What do you want to be doing 12 months from now? What needs to happen between now and then to make that real?
- If this person resigned tomorrow, what would I genuinely miss? Would the company be measurably worse off in specific ways?
- What feedback have I been holding back that I should have given months ago?
- Am I evaluating against the role’s actual requirements, or against my personal preferences and working style?
- What did this person do that I did not see coming? What does that tell me about their potential?
- Where am I being too generous because I like the person? Where am I being too critical because their style differs from mine?
- If I had to defend this review in court tomorrow, would the documentation hold up?
The third question on the manager list (am I evaluating against the role's requirements or against my personal preferences) catches the most common bias of all. Founders and operators often promote people who work the way they themselves work, and unconsciously penalize people whose style differs even when the outcomes are equally strong.
The question is uncomfortable because the honest answer is often "I am penalizing this person for not working like me." Catching that pattern at the writing stage prevents the review from becoming a vehicle for unconscious bias.
Legal and Compliance Considerations
Performance reviews are legal records. Inconsistent or absent documentation creates risk in termination cases, discrimination complaints, and audits. Three compliance areas matter for any company with 15 or more employees, the threshold for most federal anti-discrimination laws.
Equal and Consistent Application
Review practices must be applied consistently across all employees. Selectively running reviews for some employees but not others, or applying different standards to different demographics, can become evidence in discrimination complaints. The fix is to document the practice clearly and apply it consistently.
The Equal Employment Opportunity Commission (EEOC) tells small employers to apply performance standards consistently and to make sure no employee is held to a higher standard, or given a worse evaluation, because of a protected characteristic.
Documentation as Legal Record
Review documents become legal records in employment disputes. The standard for documentation: the assessment is based on observable performance, applied consistently, and tied to job-related criteria. Subjective judgments ("not a culture fit," "does not have leadership presence") are weak documentation; specific behavioral evidence ("missed three of four quarterly goals; received negative feedback from two team members in documented 1-on-1s") is strong documentation. The SHRM guidance on conducting great performance reviews makes the same point: describe observed behavior, not vague judgment.
Retention of the record matters as much as its quality. According to the EEOC recordkeeping requirements, employers must keep all personnel and employment records for one year, and records that explain a wage differential between employees of opposite sexes, job evaluations included, must be kept for at least two years under the Equal Pay Act. A review that fed a raise decision can explain exactly that kind of differential, so the version you file should be the version you delivered.
Performance Improvement Plans
When a review surfaces serious underperformance, the standard practice is to put the employee on a Performance Improvement Plan (PIP): a written document specifying the gaps, expected improvements, timeline, and consequences if improvement does not occur.
PIPs serve two purposes: giving the employee a real chance to improve, and creating the documented record needed if the employment relationship eventually ends. PIPs done badly (vague, punitive, set up to fail) create legal risk. PIPs done well give a fair shot and document the process honestly.
The length of the plan matters as much as its content. According to SHRM (July 2025), a PIP needs to run for at least 30 days, and 60 or 90 days is more customary. A two-week plan reads as a formality rather than a real chance to improve.
Common Performance Review Mistakes
The mistakes below are patterns I have seen repeated across dozens of small businesses. None of them are unfixable. All of them are avoidable if you know what to watch for.
The meta-pattern across all eight mistakes: treating the review as the entire performance practice rather than as the documentation of an ongoing practice. The annual review becomes a high-pressure event because it has to do all the work the year of conversations should have done. The fix is not to write better annual reviews; it is to run real performance management throughout the year so the review becomes a low-pressure summary.
Tools and Templates
Software vendors heavily oversell the tooling side of performance reviews. The honest answer at small business scale: you do not need dedicated review software. A shared Google Doc or Notion template per employee is enough. As a company grows into mid-size and reviews spread across several managers, dedicated software starts to add value (calibration across managers, integration with compensation, historical tracking).
| Stage | Recommended tooling | Why |
|---|---|---|
| Founder-led small business | Google Doc or Notion template per employee | Founder runs everything; software is overhead |
| Small business, several managers | Structured templates with consistent format across managers | Need consistency across teams but not yet at scale that justifies dedicated software |
| Growing into mid-size | Lightweight performance review software OR structured template system | Multiple managers need consistent practice; an HR person typically joins the team at this stage |
| Mid-size and enterprise | Full performance management platform integrated with an HRIS (human resources information system) | Multiple teams need calibration, executive visibility, integration with compensation |
The mistake to avoid: buying performance review software in the hope that the software will create the practice. It will not. Tools amplify habits; they do not create them. Build the habit with a simple template, then upgrade only when manual tracking becomes the bottleneck.
Where FirstHR Fits (Honest Disclosure)
FirstHR does not currently include a performance review module. The platform handles employee onboarding, employee profiles, document management, training modules, org charts, and the operational HR foundations that small businesses need. Performance reviews themselves run in your shared docs or your wiki. FirstHR's role is to handle the surrounding infrastructure: clear employee records (so the review has a basis in documented role expectations), onboarding flows that set the right standard from day one, and the organizational data that informs reviews.
FirstHR is built for small businesses, with flat, predictable pricing, so that the founder can focus on the higher-leverage work like running real 1-on-1s and writing genuine reviews rather than wrestling with HR infrastructure.
Where Performance Reviews Are Going
The field is shifting in three observable directions, and a small business can usually start with where it is heading rather than where it has been.
The first shift is from annual to continuous. According to Harvard Business Review (Cappelli and Tavis, October 2016), traditional performance appraisals have already been abandoned by more than a third of US companies. What replaces them is almost always some form of shorter, more frequent check-in. The reason is simple: feedback close in time to the work produces behavior change; feedback delivered six months after the event produces defensiveness.
The second shift is from numeric ratings to narrative assessment. Large employers have been publishing their own reasoning for a decade: Deloitte wrote in Harvard Business Review (April 2015) that its system for evaluating people, then training, promoting, and paying them on the result, had grown out of step with its objectives.
The case against ratings runs the same way each time: they consume management time on calibration debates that produce poor differentiation, and they discourage the honest feedback that drives improvement. The trend is toward narrative assessment instead: what specifically this person did, with examples.
The third shift is from HR-owned to manager-owned. The traditional model placed HR at the center; the emerging model places the manager at the center, with HR providing tools and frameworks. This shift requires investing in manager development, which is why leadership development has become central to healthy review practice at scale.
The federal government shows how uneven these shifts are. An OPM final rule effective August 6, 2026 requires a supervisory critical element for every supervisor it covers, so managers are rated on how they manage. The same rule removes the prohibition on a forced, or standardized, distribution of rating levels. A small business can borrow the first idea and leave the second.
The Long View on Performance Reviews
The honest case for performance reviews at any company size is not that they are magic. They are not. They are a structured way to do something most managers should do anyway: assess how the past period went, document the assessment, and use it to inform what comes next. Done well, reviews make this rhythm visible and shared. Done badly, they bury the rhythm under bureaucratic theater that signals process compliance without producing real outcomes.
The teams that get the most value from reviews are the ones that run a simple version consistently for years. After several cycles, the review becomes the natural capstone to the year of conversations rather than a high-pressure event. Surprises disappear. Compensation conversations become anchored in evidence. Top performers feel seen; underperformers receive the structured feedback they need to improve or move on. None of this is achievable through a single annual review; it is achievable through the year of practice that the review documents.
The place to start is the running document. Open one this week for each person you manage, and add a few lines after every conversation about their work. By the time the next review comes around, it will mostly write itself.
Frequently Asked Questions
What is a performance review?
A performance review is a formal, written assessment of an employee’s work over a set period, most often a quarter or a year. It looks at results against the goals agreed for that period, the behaviors the manager observed, what the person added to the team, and where they need to grow, and it often feeds decisions about pay and development. The review is the checkpoint that closes one cycle of performance management and starts the next. When no feedback has happened between checkpoints, the review is usually a weak one.
How do you write a good performance review?
Write it from evidence, make every point specific, and include nothing the employee has not already heard. For most small businesses, the order that works starts with what the period’s goals were and what actually happened, backed by concrete examples. Then describe the behaviors and contributions you observed, tied to moments the employee will remember. Be honest about growth areas, using examples you already raised in 1-on-1s, and close with development priorities for the coming period. Three traps to avoid: vague labels such as “great teammate,” recency bias that lets the last two weeks stand in for the whole period, and any feedback the employee is hearing for the first time.
What are the main types of performance reviews?
There are six main types. The annual review happens once a year and is the most common. The quarterly review runs every three months and is the strongest cadence for small businesses. Continuous feedback is ongoing and forms the foundation that formal reviews sit on. A 360-degree review gathers input from the manager, peers, and direct reports. A project-based review is triggered when a project ends rather than by the calendar. The probationary or 90-day review applies to new hires. Most companies combine several; a small business usually does best with quarterly written check-ins, one annual review, and a 90-day review for each new hire.
What is the difference between a performance review and performance management?
Performance management is the whole ongoing practice, while a performance review is one formal event inside it. The practice covers everything a manager does all year: setting expectations, giving feedback, coaching, and reviewing. The review happens on a set schedule, such as annually or quarterly, and is the point where performance is formally assessed and linked to decisions on compensation, promotion, or development. Without the management, a review is just paperwork; without the review, management leaves no written record. A company needs both, and a review only means something when real management surrounds it.
How often should performance reviews happen?
Hold a formal written review at least once a quarter, with an annual summary on top and weekly 1-on-1s underneath. The small-business cadence that works combines several layers: weekly 1-on-1s (real-time feedback), monthly written notes (documented progress), quarterly formal check-ins (full review of goals and development), and an annual summary (compensation and longer-term trajectory). New hires get one extra checkpoint, the 90-day review at the end of the probationary period. Companies that only review annually tend to produce surprised employees, weak documentation, and avoidable turnover, because the feedback arrives months after the work it describes. Pairing weekly conversations with quarterly written check-ins keeps every formal review a summary of feedback the employee has already heard.
What should you say in a performance review?
A performance review should say four things: (1) specific accomplishments tied to the period’s goals, with concrete examples; (2) observations on behaviors and contributions, both positive and corrective, with situations the employee will recognize; (3) honest discussion of areas of growth, ideally framed as forward-looking development priorities rather than backward-looking criticism; (4) clear next-period priorities both parties have agreed on. Avoid filler praise, vague concerns, and any feedback the employee is hearing for the first time. Leave out subjective labels such as “not a culture fit” or “lacks executive presence,” which name no behavior and make weak documentation if a decision is ever challenged. A quick test for every line: could the employee turn it into a specific action to take or stop taking? If not, rewrite it or cut it.
What is a 90-day performance review?
A 90-day performance review is the formal evaluation at the end of a new hire’s probationary period. It looks at what the person has learned, what they have contributed so far, and the manager’s own observations, and it records the formal decision on whether the employment relationship continues, which is often called “passing probation.” No review in an employee’s tenure carries more weight than the 90-day review, because it sets the precedent every later review follows. A good one establishes a clear standard for ongoing performance conversations; a careless one teaches the new hire that reviews are a formality. At small business scale it needs its own template rather than the quarterly one, and about an hour of manager time per new hire.
Can small businesses run performance reviews without an HR department?
Yes. The practical version of performance reviews for a small business without dedicated HR: a one-page review document per employee, run quarterly, with a longer annual summary. The founder, owner, or operations lead writes the review based on a running document of notes from weekly 1-on-1s. Reviews without HR are not lower quality; they are often higher quality because the manager is closer to the actual work. The risk is inconsistency across managers, which gets larger as the team grows and more than one person starts writing reviews.
What is a self-assessment in a performance review?
A self-assessment is a written evaluation that the employee completes about their own performance, usually before the manager’s review. It typically covers what they accomplished, what they struggled with, where they want to grow, and feedback for the manager. Self-assessments improve review quality because they surface the employee’s perspective before the manager has anchored the conversation. They also reveal gaps between how the employee sees themselves and how the manager sees them, which is often the most useful part of the review conversation.
What is a 360-degree performance review?
A 360-degree review collects feedback from multiple sources: the employee’s manager, peers, direct reports (if applicable), and sometimes customers or cross-functional collaborators. The goal is to give a multi-perspective view of performance rather than relying solely on the manager’s view. 360-degree reviews are powerful for development conversations because they surface blind spots. They are risky for compensation decisions because the input can become political. The safer practice is to use 360 reviews for development only, kept separate from compensation. In a small business, a formal 360 process is usually too political to run well while the founder or the first managers do all the reviewing. Once there are several teams, a lightweight 360 for senior roles only is enough, and when the person being reviewed is a manager, the same short set of questions put to each of their reports gets most of the signal without the full machinery.
What is a performance improvement plan (PIP)?
A performance improvement plan is a structured written document for an employee who is underperforming. It names the gaps, the improvement expected, the timeline, the support the manager will give, and what happens if the improvement does not come. On timing, SHRM guidance says a PIP needs to run for at least 30 days, and 60 or 90 days is more customary. A PIP does two jobs at once: it gives the employee a genuine opportunity to turn things around, and it builds the written record the company will need if the employment relationship eventually ends. A vague or punitive plan designed to fail creates legal exposure and damages trust, while a fair one gives the person a real shot and keeps an honest record of the process.
How do performance reviews affect compensation?
In most small businesses, performance reviews feed straight into compensation decisions such as raises, bonuses, and equity refreshes. The honest approach links the two without holding them in the same meeting. Keep the review itself about performance and development. Hold the compensation conversation afterward, ideally weeks later, and treat the review as one input alongside market data, company financials, and how the role has evolved. When both happen in one sitting, the employee spends the review angling for a raise, and the pay discussion drifts toward vague talk about potential instead of specific evidence.
Make HR the easy part of running your business
Onboarding, e-signatures, training and core HR in one place. Up and running in 5 minutes.
- 7-day free trial
- No credit card required
- Cancel anytime