Most performance reviews are dreaded by both sides of the table. The manager scrambles to remember what happened nine months ago. The team member braces for feedback they've never heard before. Neither party leaves with a clear picture of what changes next. The industry doesn't matter — this pattern plays out in restaurants, logistics companies, retail stores, and everything in between.
The fix isn't a longer form or a more sophisticated rating scale. It's a consistent process that starts well before anyone sits down.
Step 1: Gather the data before the conversation
A performance review is only as fair as the evidence it's built on. If your preparation is reading last month's emails and trying to recall standout moments, you're not running a review. You're running a memory test, and memory is unreliable, biased toward recent events, and influenced by how much you like the person.
Data gathering means pulling together, for the period in question:
- Actual output against agreed targets (jobs completed, sales figures, service scores, whatever is measurable for that role)
- Any formal feedback received — from clients, colleagues, or your own observations logged at the time
- Tasks assigned and completed
- Any events noted during the period (positive or negative)
A restaurant manager doing this well has a log of covers managed, customer complaints by server, and any incidents from the past six months. A delivery company manager has on-time rates, damage reports, and customer interaction scores per driver. A retail store manager has units per transaction, conversion rates, and any service feedback attributed to individuals.
If you don't have data, you don't have a review. You have a conversation about feelings dressed up as an assessment. That's not fair to the person being reviewed, and it won't hold up if the decision is ever challenged.
The data doesn't have to be comprehensive. It has to be real, consistent, and gathered throughout the period — not reconstructed the week before the review.
Step 2: Structure the conversation
The review conversation has four components, in this order. Skipping any of them turns the review into something else.
Opening: State the purpose. This is a structured look at the past period and a plan for the next one. Not a judgment. Not a surprise. A shared review of what the data says.
Performance against targets: Walk through the metrics together. Not your interpretation first — show the numbers, ask what they think. A delivery driver who knows their on-time rate dropped from 94% to 87% in Q3 will often explain the cause before you have to ask. That explanation is data too.
Qualitative feedback: This is where behavioural observations go — reliability, communication, how they handled pressure, feedback from colleagues or clients. This section needs to be grounded in specific examples, not general impressions. "You've been hard to reach when things go wrong" is not feedback. "On three occasions in October you didn't respond to dispatch calls within the expected window" is.
Looking forward: Agree what the next period looks like. What stays the same. What needs to change. What support or resources are needed. This is the part most managers rush. It's actually the most important — without an agreed plan, the review has no consequence.
Step 3: Document what was agreed
The conversation needs a written record. Not a transcript — a brief summary of what was covered and, specifically, what was agreed for the next period.
This serves two functions. The obvious one is that it creates accountability on both sides. If you agreed the team member would hit a 90% on-time rate by the end of the quarter, the next review starts from that commitment. The less obvious function is that it protects both parties if the relationship deteriorates. A documented, consistent review process is the difference between a difficult performance conversation and a legally defensible one.
The document doesn't need to be long. One page. What the data showed. What was discussed. What was agreed. Both parties sign or acknowledge it.
Step 4: Follow up before the next review
A performance review with no follow-up is a conversation with no consequence. The agreed targets need to be visible to both parties between review cycles. Check-ins should happen — brief ones, data-led, not formal reviews — at least monthly.
A retail store manager who agrees a conversion rate target in a January review and doesn't revisit it until July has essentially wasted the January conversation. The team member has had no signal about whether they're on track. The manager has no basis for the July conversation beyond what they can recall.
The check-in doesn't require a meeting. It requires a shared view of the numbers. "Here's where you are against the target we agreed" is enough. The team member sees it. The manager sees it. The review in July has context.
KaiHub is built around this cadence. Performance data is logged throughout the period, tracked against targets set per role, and surfaced in a view that makes the review preparation genuinely fast. When the review conversation arrives, the data is already there — no reconstruction required.
Walk into every performance review with the data already prepared
KaiHub tracks KPIs, events, and progress throughout the year so your reviews are built on facts, not memory.
See pricing →Run the same four-step process for a chef, a driver, and a sales rep. The metrics will differ. The process won't. That's what makes it fair.