Performance Review Guide & Conversation Flow

A practical, development-focused guide to prepare for and run performance conversations that combine concrete evidence, appreciative coaching, fair calibration, measurable development plans, and reliable follow-up.

Purpose and primary hunger

Performance conversations should turn evaluations into meaningful development and clearer expectations. This guide helps managers and contributors prepare, structure, and follow up on reviews so they increase capability, reduce defensiveness, and produce measurable progress rather than only ratings.

Why this matters

When reviews emphasize evidence, appreciation, and concrete development commitments, they reduce demotivation, improve retention, and produce observable performance improvement. Poor reviews (rating-only, vague, or punitive) create confusion, resentment, and turnover.

Quick overview of the conversation flow

  1. Set the tone with appreciation and purpose
  2. Review observable evidence and examples
  3. Explore strengths, gaps, and root causes
  4. Create a measurable development plan (SMART commitments)
  5. Agree on accountability, check-ins, and measures

Preparation checklist (for managers)

  • Collect recent, specific examples (dates, situation, behaviour, impact).
  • Ask the employee to provide their self-assessment and examples in advance.
  • Review role expectations, goals, and prior development commitments.
  • Identify calibration context: how similar roles were evaluated and why.
  • Prepare two or three concrete development options aligned to business priorities.
  • Plan 45–60 minutes: uninterrupted, private, with notes and next-step placeholders.

Preparation checklist (for employees)

  • Collect your evidence of outcomes and examples of learning or obstacles.
  • Reflect on strengths and one or two development priorities.
  • Bring suggestions for support, resources, or role adjustments that will help you succeed.

Evidence capture template (use during prep and in conversation)

Capture specific examples using this short structure for each item you mention:

  • Situation/Task: Where and when (brief).
  • Behavior: What the person did or said (observable, not inferred).
  • Impact: What happened because of it (data, customer effect, team result).
  • Desired change or repeat pattern: What should happen next time?

Example: "On 6/12 during the client call, you summarized next steps clearly (behavior) which helped the client agree to a timeline (impact). Continue that approach and invite one extra clarifying question each call (desired repeat)."

Conversation roadmap with sample prompts

Open with appreciation and shared purpose (5 minutes)

Start with a short genuine appreciation. Set the intent: learning and alignment.

Sample: "I want to start by thanking you for how you handled X. My goal today is to understand what’s working, where we can grow, and agree on a plan you can succeed with."

Review evidence (10–15 minutes)

Share concrete examples using the evidence capture template. Invite the employee’s view.

Sample: "Here’s what I observed and why it mattered. What’s your perspective?"

Explore strengths, barriers, and root causes (10–15 minutes)

Ask diagnostic and coaching questions to discover capability gaps, resource needs, or systemic obstacles.

  • "What helped you achieve X?"
  • "What got in the way of Y?"
  • "What would you change if you could redo that project?"

Co-create the development plan (15 minutes)

Translate findings into 1–3 focused, SMART (Specific, Measurable, Achievable, Relevant, Time-bound) commitments. Assign ownership, supports, and measures.

Template for each commitment:

  • Goal: Brief, outcome-focused.
  • Success measures: How we’ll know it worked (numbers, examples, behaviors).
  • Actions & timeline: What the employee will do and by when.
  • Support: What the manager or org will provide (training, time, shadowing).
  • Check-in cadence: When we’ll review progress.

Sample goal: "Improve sprint delivery predictability: increase on-time delivery from 65% to 85% within three months, measured by sprint reports. Actions: pair planning sessions weekly, update backlog grooming process. Manager support: attend first two plannings and provide feedback."

Calibration and fairness (10 minutes or separate calibration meeting)

Ensure consistency across roles and remove bias by comparing evidence to role expectations and calibrated examples. Use shared rubrics or examples to justify ratings and avoid last-month bias.

Calibration checklist:

  • Compare examples against agreed role standards.
  • Document why a rating was chosen with 2–3 supporting examples.
  • Avoid mixing coaching feedback with administrative actions—separate performance development from disciplinary processes when possible.

Commitments and closing (5 minutes)

Clearly state the agreed commitments, next steps, and the timing of the first check-in. End on a note of confidence and partnership.

Sample close: "We’ll try this plan for 8 weeks and meet on [date] to review the measures. I’ll support by doing X, and I’m confident we’ll see improvement in Y."

Follow-up plan and tracking

  • Document the commitments in writing within 48 hours (manager responsibility).
  • Set recurring check-ins (e.g., 2–4 weeks) with a short agenda: progress, obstacles, next actions.
  • Use simple measures (quantitative where possible) and one short qualitative check per interval ("what’s changed?").
  • Keep a running evidence log for successes and challenges; use it in the next review cycle.

Common pitfalls and quick tips

  • Don’t surprise the employee—share evidence and invite self-assessment in advance.
  • Focus on behaviors and impact rather than personality judgments.
  • Avoid overloading with too many development goals—limit to 1–3 priorities.
  • Be specific about manager support and remove administrative friction for agreed actions.
  • Document decisions to avoid confusion and support fair calibration later.

Next steps and adaptation

This guide is a practical template you can adapt to different roles, seniority levels, and organizational norms. For teams that want to scale best practices, consider converting the evidence template and development-plan fields into a short interactive form so conversations are consistently documented and tracked.

Where to start now

  • Use the evidence capture structure to prepare two or three discussion points for your next review.
  • Draft one SMART development commitment with measures and a first check-in date.
  • Agree on how you’ll document the conversation so both parties have a clear record.

End of guide — adapt, test, and refine this flow with your team so reviews become predictable, useful, and empowering.


Discussion

Comments and conversation will live here.