Intermediate Team 8 min read

How to Run Performance Reviews

A practical guide to running quarterly performance reviews at an early-stage startup—without the overhead that makes traditional annual reviews useless.

Published March 16, 2026

Why Annual Reviews Fail at Startups

The average large company runs performance reviews once a year. For a startup, that cadence is essentially useless.

In a company that doubles its team size every 12–18 months, a lot can go wrong in a year. Skills that mattered when someone was hired may be table stakes six months later. A person who was thriving in a 10-person team may be struggling in a 40-person organization. Waiting 12 months to surface these realities costs the company in productivity, costs the employee in career growth, and often leads to surprise terminations that damage culture.

Quarterly reviews solve this. They are short enough to stay current, frequent enough to intervene early, and structured enough to protect both parties.


Step 1: Define Expectations Before the Review Period

Performance reviews are only as good as the goals set at the start of the period. Without pre-set, agreed-upon goals, every review becomes a negotiation about what “good” means—and the manager usually wins that negotiation by default.

Goal-setting framework (start of each quarter):

Each employee should have 3–5 goals that are:

  • Tied to team OKRs: the individual’s work should connect to something the company cares about measuring
  • Outcome-oriented, not activity-oriented: “reduce customer churn from 5% to 3% by EOQ” not “work on retention”
  • Differentiated by performance level: define what “meets expectations” and “exceeds expectations” look like in advance—do not wait until review time

Goal calibration: after setting goals with your direct report, share them with your own manager. This catches cases where goals are too easy, too hard, or misaligned with company priorities.


Step 2: Send the Self-Assessment Form

One week before the review meeting, send a short self-assessment questionnaire. This does several things: it gives the employee time to reflect rather than react, it reduces the manager’s information asymmetry, and it makes the review conversation two-way rather than a lecture.

Self-assessment questions (keep it to 5–6)

  1. Rate yourself against each of your Q[N] goals (1–4 scale). What is your evidence?
  2. What is the single biggest impact you made this quarter?
  3. What would you do differently if you could repeat this quarter?
  4. What is one skill or capability you want to develop next quarter?
  5. What support do you need from me to be more effective?
  6. Is there anything you want me to know that might not be visible in your day-to-day work?

Don’t skip this step. Managers who go into reviews without a self-assessment often dominate the conversation and miss things the employee knows that they don’t.


Step 3: Complete the Manager Assessment Independently

Before you sit down with the employee, write out your own assessment. For each goal:

  • Rating: 1 (did not meet), 2 (partially met), 3 (met), 4 (exceeded)
  • Evidence: at least one specific example per rating that is not 3
  • Overall performance level: Below / Meeting / Exceeding expectations

Avoiding common assessment biases

BiasDescriptionFix
Recency biasRating based on last 2 weeks, not the full quarterReview Slack messages, PRs, or notes from the full period
Halo effectOne great project colors all ratingsScore each competency independently
Leniency biasRating everyone as “meets” to avoid conflictForce-rank: calibrate against peers
Similarity biasRating people who work like you more favorablyAnchor to outcomes, not work style

Step 4: Run the Review Conversation

Duration: 45–60 minutes. Do not rush it.

Structure:

  1. Open (5 min): “I want this to be a two-way conversation. I’ll share your self-assessment highlights first, then my assessment. I want to understand your perspective before we discuss development focuses.”
  2. Self-assessment review (10 min): let the employee walk through their ratings
  3. Manager assessment (20 min): share your ratings with evidence; for every disagreement, present the specific example and listen to theirs
  4. Development focus (15 min): agree on 1–3 things to prioritize next quarter—keep it short or nothing gets acted on
  5. Close (5 min): confirm what is in writing, confirm when comp discussion happens

Delivering difficult feedback

Use the SBI model (Situation → Behavior → Impact):

  • Situation: “In the April product launch…”
  • Behavior: “…you shared the go-live date with the sales team before engineering had signed off…”
  • Impact: “…which created a commitment we couldn’t keep and damaged trust with two enterprise prospects.”

Follow with a clear expectation: “Going forward, I need launch dates to be confirmed in writing with the eng lead before they go to any external team.”

Do not cushion difficult feedback so heavily that the employee misses the message. One of the most common manager mistakes is rating someone as “meets expectations” in a review and then firing them two months later for performance—the employee had no idea anything was wrong.


Step 5: Calibrate Across Your Team

If you manage multiple people, hold a calibration session with your co-founders, HR (if you have it), or peer managers before delivering any reviews.

Calibration catches:

  • Grade inflation: one manager has rated everyone as “exceeding,” making their team look uniformly excellent
  • Inconsistency: two people doing equivalent work are rated differently for non-performance reasons
  • Blind spots: a manager misses something about a direct report that another manager noticed in cross-team interactions

Calibration format (30 minutes, 4–8 reports):

  1. Each manager shares ratings for their reports (no justification yet)
  2. Flag anyone rated at the extremes (1 or 4) for discussion
  3. Compare anyone rated 3 in one team against anyone rated 3 in another team doing similar work
  4. Adjust ratings where evidence doesn’t support the score

Step 6: Connect to Compensation and Document

Compensation timing: deliver the performance conversation, then wait 1–2 weeks before sharing any comp changes. This prevents the review from becoming a salary negotiation and ensures the feedback itself lands.

Compensation framework (simple version for early stage):

Performance levelTypical comp action
Significantly below expectationsPIP initiated; no increase
Below expectationsNo increase; reassess next quarter
Meets expectationsCost-of-living adjustment (2–4%)
Exceeds expectationsMerit increase (5–10%) or equity refresh
Significantly exceedsSignificant increase + promotion discussion

Documentation minimum:

  • Goals agreed at start of quarter (written)
  • Ratings and evidence from manager assessment (written)
  • Development focuses agreed in meeting (written, shared with employee)
  • Compensation decision with rationale (written)

A Google Doc per employee, with a new section each quarter, is enough for a sub-50-person team. Use a proper HRIS (Rippling, Lattice, Leapsome) when you hit 30+ employees.


What to Do When Performance Is Persistently Below Expectations

If an employee has been below expectations for two consecutive quarters, a Performance Improvement Plan (PIP) is appropriate.

A PIP is not a pre-termination document—it is a structured, good-faith effort to give clear guidance and a defined path to success. It also creates the documentation you need to protect the company legally if termination follows.

PIP structure:

  1. Specific, measurable performance gaps (not vague)
  2. Clear expectations for the next 30–60 days
  3. Support the company will provide (additional training, manager coaching, clearer scope)
  4. Check-in frequency (weekly is typical)
  5. Consequences if expectations are not met

Key Takeaway

Performance reviews at a startup are not a bureaucratic formality—they are one of the highest-leverage management tools you have. Quarterly cadence, goal-based assessment, independent scoring, structured feedback, calibration, and comp tied to performance: this system takes less than three hours per employee per quarter and prevents the two most expensive people problems in early-stage companies—surprise terminations and quiet quitting.

Frequently Asked Questions

How often should startups run performance reviews?
Quarterly reviews are the right cadence for most early-stage startups. Annual reviews are too infrequent—problems fester for months before they are addressed, and employees feel blindsided. Quarterly cycles keep feedback timely, allow compensation to track growth faster, and create a documented record that protects the company if a termination is ever contested.
What is the difference between a performance review and a 1-on-1?
A 1-on-1 is a weekly or biweekly check-in focused on day-to-day progress, blockers, and relationship building. A performance review is a structured, documented assessment of performance against defined goals over a specific period—typically a quarter. Reviews feed into compensation decisions; 1-on-1s should not. Mixing the two makes both less effective.
How do you deliver difficult feedback in a performance review?
Be direct and evidence-based. Name the specific behavior or output, describe the impact, and give the person a chance to respond before you move to expectations. Avoid softening difficult feedback with excessive praise—the SBI model (Situation, Behavior, Impact) works well: 'In the Q3 launch (situation), you pushed the release without completing the QA checklist (behavior), which caused three production incidents in the first week (impact).' End with a clear, written improvement expectation and a timeline.
Should performance reviews be tied to compensation?
Yes, with a deliberate lag. Conduct the performance conversation first, without mentioning numbers, so the employee engages with the feedback rather than anchoring on the comp outcome. Then follow up with the compensation decision 1–2 weeks later. This prevents reviews from becoming purely transactional and ensures the feedback itself is heard.
What should a startup do when an employee's performance is consistently below expectations?
Put the employee on a formal Performance Improvement Plan (PIP) within one review cycle of identifying the problem. A PIP should define specific, measurable improvements, a 30–60 day timeline, check-in frequency, and consequences if improvements are not met. A PIP is not a termination notice—it is a documented, good-faith effort to give the person a clear path to success. It also protects the company legally if termination follows.

Share with your team

Create an account to track your progress across all lessons.

Comments

Log in to join the conversation.

Loading comments...