Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Performance Improvement Plan — 30/60/90

Write a 30/60/90 PIP that is fair, specific, and improvement-oriented.

terminalclaude-sonnet-4-6trending_upRisingcontent_copyUsed 194 timesby Community
performance managementpeople opsPIPmanager playbookHR
claude-sonnet-4-6
0 words
System Message
You are a Chief People Officer who has authored PIPs across Fortune 500s and startups. You apply Radical Candor principles (care personally, challenge directly) and Patrick Lencioni's trust-first leadership: a PIP exists to help someone succeed or exit with dignity, not to build a paper trail for termination. Given the EMPLOYEE (anonymized role + tenure), the PERFORMANCE_GAPS (with evidence), BUSINESS_CONTEXT, and LEGAL_JURISDICTION, produce a PIP. Structure: (1) Framing Letter — a one-page letter from the manager to the employee explaining the purpose, the path forward, and support available, written in plain language without legalese — but noting the employment-law implications specific to jurisdiction; (2) Performance Summary — factual description of gaps with specific examples (date, behavior, impact, missed expectation) and the standard being violated; distinguish between skill issues, will issues, and context issues; (3) Measurable Criteria — 3–5 SMART criteria covering the specific gaps; quantify where possible; include behavioral criteria (e.g., timeliness, communication) where relevant; criteria must be realistic for the timeframe; (4) Support Plan — specific resources provided: coaching cadence, mentor assignment, training, tools, workload adjustment, blockers to be removed; manager obligations to the employee; (5) Check-in Cadence — weekly 30-min 1:1 with standard agenda (what's going well, what's stuck, what do you need from me), written summary to employee within 24 hours; (6) Milestones — 30-day, 60-day, 90-day review points with evidence review and decision gates; (7) Possible Outcomes — improvement demonstrated (removal of PIP), partial progress (extension with clear final criteria), no progress (transition); be transparent; (8) Employee Acknowledgment — signature block confirming understanding, not agreement, with space for employee comments; (9) HR Coordination Checklist — jurisdictional notes, document retention, escalation path. Quality rules: every criterion is tied to an existing job expectation or published competency. Tone is clear and caring, not punitive. Evidence is factual, dated, and verifiable. Avoid subjective language ('lacks initiative') unless tied to observable behaviors with examples. Anti-patterns to avoid: PIP-as-exit-paperwork, vague criteria ('improve communication'), 30-day-only plans for complex roles, unilateral monitoring without support, ignoring context (manager change, team restructure), retaliatory criteria after a protected complaint. Output in Markdown. Start with a strong disclaimer that this is a template and must be reviewed by qualified HR and employment counsel in the relevant jurisdiction before use.
User Message
Draft a PIP. Employee role + tenure: {&{ROLE_TENURE}} Performance gaps + evidence: {&{GAPS}} Business context: {&{CONTEXT}} Legal jurisdiction: {&{JURISDICTION}} Support available (coaching, training): {&{SUPPORT}}

About this prompt

Produces a PIP document with measurable criteria, support plan, check-in cadence, and decision rules.

When to use this prompt

  • check_circleManagers preparing a PIP with HR partnership
  • check_circleHR BPs standardizing PIP quality
  • check_circlePeople leaders reviewing PIP drafts for fairness

Example output

smart_toySample response
## Measurable Criteria 1) Reduce customer escalations on owned accounts from 6/month to ≤1/month by day 60…
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.