Case Study 02 · Quarterly Review System · 2026

Quarterly Review System: one skill, four PMs, four quarters, zero rebuilds

A working walkthrough of a quarterly performance check-in system built on top of a new corporate-wide process. Three artifacts plus one reusable AI skill turned a binary Workday status into a personalized takeaway for every direct report — without rebuilding the playbook each cycle.

Owner · Lead PM, PMO Time-to-launch · 2 weeks before Q1 cycle Scale · 4 PMs · 4 quarters · 1 skill First run · Q1 2026 · April 15

The five-stage path, at a glance

The Problem

16 reinventions

Same talk × 4 PMs × 4 quarters

The Insight

Encode the process

Skill once, run quarterly

The Build

3 artifacts + 1 skill

Guide · template · summary

The Outcome

Personalized takeaway

Beyond a binary status

The Compounding

Scales with the team

Name in → review out

The Problem · Same conversation, sixteen times

A corporate process needs a PMO adaptation

The company rolled out a new quarterly check-in rhythm in 2026. Every manager, every direct report, every quarter. But a binary Workday status didn't give PMs a takeaway — and re-running the same prep conversation four times per cycle didn't scale.

Before the system · the math of the problem

Same prep + script + summary, repeated quarterly per PM

Corporate timeline slide showing the rationale for moving from annual to quarterly reviews: Sep 2024 call-to-action, Dec 2024 research with 700+ survey responses, Jan 2025 finding the answer, Oct 2025 checked the work, today launching lightweight quarterly check-ins

Corporate rollout context · the new rhythm requires a per-manager adaptation

What the new corporate process gives you

A fixed quarterly cadence (Q2 / Q3 / Q4 + Year-End).
A binary On Track or Off Track status submitted in Workday by the 15th of the review month.
An automatic Slack validation question to the employee after the 15th.

What it does not give you

A consistent prep flow across PMs so each conversation lands at the same quality.
A shareable takeaway the PM can keep, beyond the binary Workday status.
A way to scale the process as the team grows without rebuilding it from memory each quarter.

The Insight · Run the process as a product

Encode it once. Run it every quarter.

If the conversation is the same shape every quarter, the prep should be. Build the system once as a reusable artifact — and let the AI assemble the pieces per PM per cycle.

Six-card grid summarizing the new performance approach: Feedback Every Quarter, Goals Stay Current, Agile Performance, In Your Current Flow, 3 Ratings Not 4, No Peer Reviews

The principles the new process was built on · the design constraints for any manager-level system

The design principles

Encode the process, not the output. The skill captures the how — prep, script, summary structure — not a specific PM's review.
Two scripts, one branch. On Track and Off Track use the same opening, then diverge. The skill picks based on a pre-conversation gut check.
Document before the conversation. Drafting the Workday Off Track justification before the 1:1 keeps the live message honest.

What stays manual on purpose

The PM call (Impact, Effort, On Track call). The skill never decides — it surfaces what you already know.
The judgment in the conversation itself. The skill produces the script; the manager runs it.

The Build · Three artifacts wired to one skill

Guide, template, summary — all from one source

The PMO-side build sits on top of the corporate cadence. A conversation guide drives the 1:1, a shareable template is populated per PM, and a Claude skill ties the two ends together so the manager prep stays consistent each quarter.

How the pieces connect

Conversation Guide. Pre-conversation gut check (5 questions) plus two parallel scripts (On Track 30-45 min, Off Track 45-60 min). Same opening, different middles.
Shareable Template. A neutral takeaway doc with feedback summary, goals tracker, action items, and a "running notes" section the PM fills between cycles.
Claude Skill. Encodes the prep, scripts, and template population as a reusable agent. Trigger by name + quarter; the skill produces the conversation guide and the populated summary draft.

What the system inherits from the corporate process

The cadence (Q1 / Q2 / Q3 / Q4) and the 15th-of-the-month Workday deadline.
The On Track / Off Track binary as the system-of-record status.
The post-conversation Slack validation to the employee.

Quarterly process at a glance slide showing Q2, Q3, Q4 check-ins each with align on goals, share feedback, discuss growth, share on/off track status, and Slack validation, followed by year-end reviews in November through February

The four-cycle rhythm · same shape, every quarter

Quarterly check-in detailed flow showing the April 1-15 phase with Workday submission and the conversation, followed by the April 16-20 phase with auto-released comments, employee Slack validation, and L1/L2 reporting

Per-cycle mechanics · prep and conversation by the 15th, validation and reporting after

The Outcome · From binary status to personalized takeaway

Each PM walks away with something specific

Workday gets the binary status. The PM gets a populated summary: their Q1 feedback, their goals and progress against them, the action items both sides own, and a running-notes section to bring to the next cycle. The skill assembled the draft; the manager edited it; the conversation finalized it.

On Track vs Off Track decision criteria slide showing the four conditions for each status and the requirement that ratings auto-release to employees after the 15th

The corporate-side decision · binary status into Workday

Sanitized example of a Q1 2026 quarterly summary document for PM-A showing the Manager Feedback section with three feedback points: Labs Solo Lead, Multi-Client Delivery, and Stakeholder Management Escalation as the focus for next quarter

Example only · PM-A Q1 2026 summary (names sanitized)

What goes into Workday

A single On Track or Off Track selection plus brief justification if Off Track.
Visible to the employee after the 15th of the review month.
That's the system-of-record. It's necessary, but not sufficient.

What the PM keeps

A personalized quarterly summary covering Q1 feedback, Q1 → Q2 goal tracker, short and long-term goals, and shared action items.
A running-notes section the PM fills between cycles. Brought to the next conversation as the starting point.
Anchored to specifics: project ownership, escalation patterns, stakeholder relationships, technical gaps.

The Compounding · Scales with the team, not against it

Name in. Review out. The skill carries the rest.

The skill is the durable part. Adding a new direct report doesn't require rebuilding the playbook — it requires adding a name and a start date. Every quarter, the corporate Slack loop validates the conversation happened; the skill carries the prep forward.

Skill bundle

pm-quarterly-review

📋SKILL.md

Trigger phrases, workflow, and references to the conversation scripts and template.

💬conversation-scripts.md

Pre-conversation gut check plus On Track and Off Track scripts with fill-in prompts.

📄shareable-template.md

Neutral takeaway doc structure. Populated per PM, per quarter.

🏢company-process.md

Reference: the corporate process this skill operates on top of.

Loop closure · post-conversation validation

People Team App just now

My manager completed a quarterly check-in with me?

What scales, and how

Onboarding a new PM. Add name + start date as a skill input. Next quarter runs the same way.
Cycle handoff between Q1 and Q2. The running-notes section carries forward; the skill picks up from "last quarter said X."
Off Track recovery tracking. The Off Track script's recovery checkpoints become the goal tracker rows for the next cycle.

The loop closure

The corporate Slack validation arrives after the 15th. The employee confirms the conversation happened — that's the audit trail that the system ran. The takeaway doc the PM holds is the proof of what was said.

What this case shows about how I work

The quarterly review system didn't try to replace the corporate process — it built on top of it. The corporate side handles cadence and audit. The PMO-side skill handles depth and continuity. Each direct report walks away with something they can carry forward, every quarter, every cycle.

Adapt, don't reinvent

The corporate process gave the rhythm. The PMO adaptation gave the substance. Layering beats replacing every time.

Skills as the unit of scale

A Claude skill captures process the way a doc captures content. New PM joins? Add a name. The skill handles the rest.

Document before the conversation

Drafting the Off Track justification before the 1:1 is the highest-leverage manager habit. The live message stays consistent because the written one already exists.