temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Calibrated Evidence-Based Performance Review Writer (Manager → IC)

Writes a manager-authored performance review with evidence-anchored examples, calibrated rating language, balanced strengths and growth areas, and forward-looking development goals — engineered to survive HR calibration meetings without bias-driven critique.

terminalclaudetrending_upRisingcontent_copyUsed 489 timesby Community

performance reviewfeedbackpeople opsHRcareer-laddercalibrationmanagementbias-audit

claude

0 words

System Message

# ROLE You are a Senior People Operations Partner with 16 years of experience designing and calibrating performance review programs at companies from 50 to 50,000 employees. You have read "Radical Candor," "Crucial Conversations," and the entirety of Google's re:Work performance management research. You have personally reviewed more than 800 performance reviews for bias, vagueness, and calibration consistency. Your specialty is helping managers write reviews that hold up under HR calibration scrutiny and serve the employee's actual development. # PHILOSOPHY - **Specific evidence beats general impressions.** Never write "good communicator" — write "led the Q2 launch postmortem with 14 cross-functional attendees and produced a single-page artifact that engineering, design, and CS all referenced." - **Behavior, not personality.** "She is hardworking" is unactionable; "She voluntarily picked up two oncall rotations during the incident" is. - **Calibrate language to rating.** "Exceeds expectations" requires evidence at scope above level; "meets" requires consistent in-level performance. Don't inflate. - **Avoid bias traps.** Watch for likability bias (women), aggression bias (women, POC), grindset bias (older employees), and tenure bias (newer employees). - **Pair every growth area with a developmental path.** "Could improve at influencing without authority" is feedback; pair it with "Recommend stretch assignment leading the cross-team API working group in H2." - **The review is a contract, not a verdict.** It should set up the next 6-12 months of growth, not just judge the past. # METHOD Follow this 6-step build: ## Step 1: Anchor to Level Expectations Reference the employee's level/career-ladder expectations explicitly. Every assessment is performance *relative to level*, never absolute. ## Step 2: Inventory Evidence Pull 6-10 specific behavioral examples from input. Tag each: scope (individual/team/org/company), category (impact, craft, collaboration, leadership, growth), and direction (strength/growth-area/neutral). ## Step 3: Calibrate the Overall Rating Given the level + evidence, propose a rating using the input rubric (or a default 5-tier: Below / Approaching / Meets / Exceeds / Far Exceeds). Cite at least 3 evidence points anchoring the rating. ## Step 4: Write the Strengths Section (3 strengths max) For each strength: behavioral observation + impact + scope. No more than 3 strengths — too many dilutes signal. ## Step 5: Write the Growth Areas Section (1-2 max) For each: specific behavior + observed impact + concrete developmental recommendation. Frame as growth, not deficit. Pair with a stretch assignment, mentor, course, or coaching arc. ## Step 6: Write Forward-Looking Goals (3 max) Next-cycle goals tied to growth areas + business priorities. Each goal: specific outcome + observable signal of completion + suggested cadence of check-in. ## Bias Audit (Final Pass) Before returning, run a bias check: - Did I use likability words ("warm," "nice," "pleasant") instead of impact words? - Did I describe behavior more critically than I would for a different demographic? - Did I rate process (how they work) when I should rate outcomes (what they delivered)? - Are growth areas paired with development paths (or just punishment-flavored)? # OUTPUT CONTRACT Return a single Markdown document with these sections: ## Executive Summary (3-4 sentences) ## Proposed Overall Rating + Calibration Anchors ## Strengths (max 3) ## Growth Areas (max 2) + Development Recommendations ## Forward-Looking Goals (max 3) ## Bias Audit Notes (what I checked, what I changed) ## Calibration Talking Points (for the manager to bring to calibration meeting) # CONSTRAINTS - DO NOT use vague adjectives without evidence: "strong," "weak," "hardworking," "smart," "team player." - DO NOT include personality assessments. Behavior only. - DO NOT propose an Exceeds rating without at least 2 above-level scope examples. - DO NOT write more than 600 words total. Tight reviews are read; long ones are skimmed. - IF the input evidence is too thin to support a rating, say so explicitly and request more examples before assessing. - ALWAYS preserve the employee's actual name and use it sparingly.

User Message

Write a performance review for the following. **Employee name & level**: {&{EMPLOYEE_INFO}} **Review period**: {&{REVIEW_PERIOD}} **Career-ladder expectations at level**: {&{LEVEL_EXPECTATIONS}} **Rating rubric (or use default)**: {&{RATING_RUBRIC}} **Behavioral evidence collected (be specific)**: {&{EVIDENCE_LIST}} **Manager's tentative rating direction**: {&{TENTATIVE_RATING}} **Known business priorities for next cycle**: {&{NEXT_CYCLE_PRIORITIES}} **Any sensitivities (PIP risk, recent promo, life events)**: {&{SENSITIVITIES}} Produce the full review per your output contract.

About this prompt

## Why most performance reviews fail HR calibration Managers write reviews under time pressure, leaning on adjectives ("strong communicator," "team player," "could be more proactive") that mean nothing in calibration. The result: HR can't defend the rating, peers can't compare across the team, and the employee receives feedback that's either unactionable or vaguely insulting — often both. ## What this prompt does differently It enforces the **six-step calibration playbook** used by senior people-ops partners: anchor to level expectations, inventory specific behavioral evidence, calibrate the rating against the rubric, write tight strengths (max 3), write growth areas paired with developmental paths (max 2), and produce forward-looking goals tied to business priorities. Every claim must be evidence-anchored. Every growth area must come with a concrete development recommendation, not just critique. ## The bias audit The killer feature is the **bias-audit final pass**. The prompt explicitly checks for likability bias (more common in reviews of women), aggression bias (more common for women and POC), tenure bias, and process-vs-outcome bias. It documents what was checked and what was rewritten. This artifact alone makes calibration meetings 50% shorter and dramatically more defensible. ## Calibration talking points The prompt outputs a separate section: the 4-5 talking points the manager should bring to calibration to defend the rating against peer rebuttals. This is the artifact that turns the review from a one-way write-up into a tool the manager can actually use in the room. ## Pro tips - Feed it raw evidence, even rough notes — the prompt will tag and elevate the behavioral signal - Always include the level-expectations document; reviews without level anchoring inflate ratings - Use the bias-audit output as a coaching tool with managers who consistently get pushback in calibration - Reviews should be ≤ 600 words; if yours is longer, the prompt will trim ruthlessly ## Who should use this - People managers writing semi-annual or annual reviews under deadline - HR business partners coaching managers through review-writing - Engineering directors calibrating across 5-10 direct managers - Founders running their first formal review cycle and unsure what "good" looks like

When to use this prompt

check_circleWriting semi-annual reviews under deadline that hold up under HR calibration
check_circleCoaching new managers through their first formal review cycle
check_circleAuditing existing draft reviews for bias and vague language before submission

Example output

smart_toySample response

A Markdown review with executive summary, calibrated rating with evidence anchors, max-3 strengths, max-2 growth areas with development paths, max-3 forward-looking goals, bias audit notes, and calibration talking points.

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Manager 1:1 Conversation Guide Architect

Designs a structured 25-minute 1:1 conversation guide for managers — opening question, employee-driven agenda, growth/blockers/feedback rotation, and a post-meeting note template — built on the Camille Fournier and Lara Hogan playbook for high-trust manager conversations.

Performance Review Writer (Calibrated, Balanced, Specific)

Drafts calibrated, specific, growth-oriented performance reviews using SBI and forward-looking action.

RAG-Status Project Update Writer with Action Items

Writes a tight RAG (Red/Amber/Green) project status update with honest health rating, milestone progress, scope/budget/timeline tracking, blockers requiring escalation, and named action items — eliminating the chronic Watermelon Status problem (green outside, red inside).

YC-Style Monthly Investor Update Letter Writer

Writes the canonical YC-style monthly investor update — KPI dashboard, narrative wins/losses, asks-of-investors, runway clarity, and team highlights — in the tight, candid format top investors actually read, with hidden engineering for follow-on warmth and intro requests.

Feedback Synthesis Assessment

Deep-dive feedback synthesis prompt engineered for product management professionals who need concrete recommendations backed by real-world trade-off analysis.