Most performance review systems fail before anyone fills them in.
They’re too long. Too generic. Too disconnected from how people actually work. They ask employees to rate themselves on “communication” and “teamwork” using a 1-5 scale that means nothing because nobody defined what a 3 looks like.
I’ve seen this at every stage of startup. The system gets built, launched with fanfare, and quietly abandoned after one cycle because nobody found it useful.
Here’s how to build one that works — in a week — with AI doing most of the writing.
Day 1: Define What You’re Actually Measuring
Before you build anything, answer this question: what does strong performance look like at your company, for each function?
Most companies skip this step and go straight to the form. That’s why the form fails.
Use this prompt for each function in your company:
“We are a [stage] startup. Define what strong performance looks like for a [role/function] at our company. We need this for a performance review framework. Give me: (1) the 3-4 core competencies that matter most for this role, (2) for each competency, what outstanding, meets expectations, and below expectations looks like in concrete behavioural terms — not vague descriptors. Be specific to a fast-moving startup environment, not a corporate one.”
Run this for every function. It takes about 10 minutes per function and gives you the foundation everything else is built on.
Day 2: Build the Self-Assessment
The self-assessment has two jobs: give employees a chance to articulate their contributions, and surface information the manager doesn’t have.
Most self-assessments ask the wrong questions. “What are your strengths?” produces performative answers. These questions produce useful ones:
“Write a self-assessment questionnaire for a performance review at an early-stage startup. The questions should: surface specific contributions the employee is proud of, identify where they felt under-resourced or blocked, reveal how they think about their own development, and give honest input on what they’d change about how we work. 6 questions maximum. No rating scales — written answers only.”
Day 3: Build the Manager Assessment
The manager assessment should take 20 minutes per direct report, not 2 hours. If it takes longer, the form is too long.
“Write a manager assessment form for a performance review at an early-stage startup. It should cover: performance against goals, the 3 core competencies for this role [paste from Day 1], one specific piece of developmental feedback, and a clear rating on a 3-point scale (below expectations / meets expectations / exceeds expectations). Include guidance on what each rating means so managers use it consistently. Maximum 1 page.”
Day 4: Build the Rating Calibration Guide
The most common failure in performance reviews is rating inflation. Every manager thinks their team is above average. Without calibration, your ratings are meaningless.
“Write a rating calibration guide for a startup performance review cycle. We use a 3-point scale: below expectations, meets expectations, exceeds expectations. The guide should: define each rating with specific behavioural examples, explain common biases that inflate ratings, give managers a heuristic for how ratings should be distributed across a team, and explain how to have the calibration conversation with other managers. Make it practical and direct — not corporate HR speak.”
Day 5: Build the Review Conversation Framework
The form is not the review. The conversation is the review. Most managers have no framework for the conversation and wing it — which produces inconsistent, uncomfortable 30-minute sessions that leave employees unclear on where they stand.
“Write a performance review conversation framework for startup managers. The conversation should be 45-60 minutes and cover: employee self-reflection, manager feedback, specific examples for each point of feedback, clear development areas and what support looks like, and next steps. Include the exact questions the manager should ask to make the conversation feel like a dialogue rather than a verdict. Format as a conversation guide the manager can have open during the meeting.”
Day 6-7: Build the Templates and Launch
Pull everything together into a single document: the self-assessment form, the manager assessment form, the rating guide, and the conversation framework. Put it in Notion. Set a deadline. Send it to every manager with a 3-paragraph explanation of why you’re doing this and what you need from them.
The launch communication matters as much as the system itself. Use this:
“Write a company-wide communication launching our first performance review cycle. Audience: 30-person startup, mix of engineers, commercial, and ops. The message should: explain why we’re doing this (not corporate box-ticking but genuinely useful conversation), be honest that it’s our first cycle and we’ll improve it, give clear timelines and what’s expected of everyone, and sound like a founder wrote it — not an HR department. Under 300 words.”
The System Nobody Will Abandon
The performance review system that gets used is the one that’s simple, specific, and takes less than an hour for each person involved. Everything I’ve described above fits that criteria.
Run it every 6 months. After the first cycle, ask every manager and every employee one question: what should we change? Iterate from there.
The goal isn’t a perfect system. It’s a system that produces useful conversations and gets better each time.
Get the Full HR Prompt Library
50 prompts for hiring, performance management, ops, and more — free download.
