Performance Support & PIP Review

Template Overview

Managing engineering underperformance requires rigorous empathy, precise expectations, and legally defensible documentation. The Performance Support & PIP Review template helps engineering managers outline specific performance gaps, provide concrete coaching resources, and maintain an objective progress log in plain Markdown.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Performance Support Sync: [[Manager]] & [[Team Member]]"
date: [YYYY-MM-DD]
manager: "[[Engineering Manager Name]]"
employee: "[[Employee Name]]"
hr_partner: "[[People Partner Name]]"
support_cycle: "[Week X of 4 / 60-Day Plan]"
status: "[Active Coaching / Formal PIP]"
tags: [1-on-1, performance-support, hr, coaching, management]
---

# Performance Support & Expectations Review — [YYYY-MM-DD]

## 1. Concrete Expectations & Objective Standards
- **Core Performance Gap:** Explicit description of observed gaps (e.g., missed sprint commitments, code quality regressions, lack of architectural communication).
- **Objective Standard Expected:** Clear, measurable benchmark of what meeting expectations looks like.

## 2. Progress Evaluation Since Previous Check-In
| Target Deliverable / Competency | Agreed Goal | Observed Outcome | Evaluation |
|---|---|---|---|
| Sprint Feature Delivery | Ship [[Module X]] by [Date] | Shipped on time with full test coverage | Met Expectation |
| Code Review Responsiveness | Respond to reviews within 24h | Average turnaround: 48h | Needs Improvement |
| Technical Communication | Proactively flag blockers in standup | Blockers communicated promptly | Met Expectation |

## 3. Support & Enablement Provided by Management
- **Pairing Opportunities:** Assigned Staff mentor [[Mentor Name]] for 2 hours weekly.
- **Scope Clarification:** Explicit prioritization of tasks to eliminate context switching.
- **Training Resources:** Allocated time for systems debugging coursework.

## 4. Mutual Commitments for Next Review
- [ ] [[Employee Name]] Submit PR for [[Feature Refactor]] by Thursday 17:00.
- [ ] [[Manager Name]] Complete mid-cycle HR check-in with [[People Partner]].
- [ ] Next progress evaluation scheduled for [YYYY-MM-DD].

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Performance Support Sync: Week 3 Review"
date: 2026-10-10
manager: "[[Devin Zhao]]"
employee: "[[Alex Morgan]]"
hr_partner: "[[Sarah Jenkins]]"
support_cycle: "Week 3 of 4-Week Coaching Plan"
status: "Active Coaching Plan"
tags: [1-on-1, performance-support, hr, coaching, management]
---

# Performance Support & Expectations Review — Week 3

## 1. Observed Progress
Devin Zhao noted that Alex successfully delivered the database migration script on Tuesday with 100% unit test pass rate. This directly addresses the deliverable commitment established in Week 2.

## 2. Areas for Continued Focus
Alex still needs to improve proactive communication when encountering unexpected third-party library errors. Rather than waiting for the bi-weekly 1-on-1, blockers should be surfaced in the team Slack channel within 4 hours.

## 3. Management Actions
Devin confirmed that if the current trajectory continues through Week 4, Alex will successfully conclude the coaching plan and return to regular quarterly review status.

When to Use and When to Avoid

When to Use

• Use during structured performance improvement plans (PIP) or proactive coaching support cycles.
• Use to establish measurable, objective performance targets with clear timeline expectations.
• Use to document manager enablement efforts, mentoring allocations, and weekly evaluation results.

When to Avoid

• Avoid for general exploratory career goal brainstorms (use the Career Growth template).
• Avoid for casual social coffee chats.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the performance review discussion recording:
1. Summarize specific performance gaps and objective benchmarks discussed.
2. Outline employee responses, progress updates, and identified blockers.
3. Extract manager enablement commitments, mutual expectations, and next review dates.
Output in clean, structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.