Purpose
Produce a quarter-ready OKR set for a customer experience organization that spans support, enablement, and client success — each objective laddered to a business outcome (gross/net revenue retention, NPS, or time-to-value) and each key result expressed with a baseline, target, and owner so the plan is operational on day one. Solves the common CX planning failure where teams set activity goals (tickets closed, calls made) that never connect to retention or expansion.
When to Use
Invoke this skill when the user asks to:
- Build quarterly OKRs for a CX, support, or customer success team
- Translate a retention or NPS target into team-level goals
- Align support, enablement, and client success on shared outcomes for the next quarter
- Replace activity-based metrics with outcome-based key results
- Prepare a CX goal-setting document for a leadership or board review
- Cascade a company-level retention or NRR target down to function-level objectives
Inputs Required
Before starting, collect:
- Quarter and fiscal context: Which quarter (e.g., Q3 FY25) and any company-wide theme or strategic priority for the period
- CX team structure: Which functions exist — support, enablement/onboarding, client success, plus approximate headcount per function
- Current performance baselines: Existing numbers for GRR/NRR, NPS or CSAT, time-to-value, CSAT/response times, churn rate — whatever is tracked
- Business outcome targets: The company-level goals CX must support this quarter (e.g., NRR target, logo retention, expansion %)
- Known problem areas: Where CX is underperforming or where leadership has expressed concern
- Strategic initiatives in flight: Any active projects (new onboarding flow, self-serve launch, QBR program) the OKRs should reinforce
- Tooling/data limits: Which metrics can actually be measured and reported on this quarter
If baselines are missing for any metric, set the key result as a "establish baseline + improve from baseline" structure and flag it as a measurement-readiness risk.
Instructions
Step 1: Map CX Functions to Business Outcomes
Before writing objectives, establish the outcome ladder. Each CX function rolls up to one or two business outcomes:
- Client Success → Net Revenue Retention, expansion, logo retention: Owns account health, renewals, expansion identification
- Enablement/Onboarding → Time-to-Value, early-stage retention: Owns activation, first-value milestones, onboarding completion
- Support → CSAT/NPS, deflection, GRR contribution: Owns resolution quality, response speed, escalation reduction Confirm which company outcome each function is on the hook for this quarter. State the ladder explicitly in the output so every objective traces upward.
Step 2: Draft 3-5 Objectives (Qualitative, Inspirational, Outcome-Anchored)
Write one objective per major focus area. A strong CX objective is:
- Qualitative and directional — describes the desired end state, not a number ("Make first-value moments fast and reliable for new accounts")
- Tied to a single business outcome named in Step 1
- Achievable within the quarter, ambitious but not fantasy Recommended objective spread for a full CX org:
- One client-success/retention objective (anchored to NRR or logo retention)
- One enablement/time-to-value objective (anchored to activation/TTV)
- One support-quality objective (anchored to NPS/CSAT)
- One cross-functional or operational objective (e.g., health scoring, voice-of-customer program)
- Optional: one team/capability objective if the user flagged a people or process gap
Step 3: Write 3-4 Key Results per Objective
Each key result must be measurable and follow this structure:
- Metric — the specific number being moved
- Baseline → Target — from where to where (use the inputs; if no baseline, structure as "establish baseline, then move X")
- Owner — the function or role accountable
- Cadence — how often it's measured this quarter
Apply these rules:
- At least 70% of key results must be outcome or output metrics (retention %, NPS, TTV days, ARR retained), not activity metrics (tickets handled, QBRs scheduled)
- Activity metrics are allowed only as leading indicators and must be paired with the outcome they predict
- Targets should be a meaningful delta from baseline — typically a 10-25% improvement for mature metrics, larger for new programs
- Avoid more than one "vanity" metric per objective set
Step 4: Add Leading-Indicator Health Metrics
For each retention-linked objective, identify 1-2 leading indicators the team can watch weekly (e.g., product adoption depth, onboarding milestone completion rate, at-risk account count). These aren't key results — they're the early-warning signals that tell the team whether the KR is trending toward target before the quarter ends.
Step 5: Flag Dependencies and Risks
List the cross-functional dependencies (Product, Sales, Data/RevOps) and measurement risks that could block a key result. Each flagged risk gets a one-line mitigation.
Step 6: Build the Scorecard Format
Render the full set as a scannable scorecard: objective → key results table → leading indicators → dependencies. Include a confidence note per objective (High / Medium / Stretch).
Output Format
- Structure: Outcome-ladder summary, then one block per objective; each block has a key-results table (Metric / Baseline → Target / Owner / Cadence), leading indicators, and a confidence rating; closing dependencies-and-risks section
- Length: 1,000–1,400 words
- Format: Structured document with tables for key results; prose only for the outcome ladder and risk mitigations
- Sections: Outcome Ladder → Objective 1–5 (each with KR table) → Leading Indicators → Dependencies & Risks → Quarter Confidence Summary
- Tone: CX director planning for a leadership review — pragmatic, numbers-forward, no fluff; assumes the reader will defend these in a board or exec meeting
Quality Checklist
Before delivering output, verify:
- [ ] Every objective traces to exactly one named business outcome (NRR, NPS, TTV, or retention)
- [ ] Each objective has 3-4 key results, and the total set has 3-5 objectives
- [ ] At least 70% of key results are outcome/output metrics, not activity counts
- [ ] Every key result has a baseline-to-target framing and a named owner
- [ ] No key result is a placeholder — all targets use the provided numbers or an explicit "establish baseline" structure
- [ ] The dependencies section names specific teams and one mitigation per risk
Notes
- The most common failure in CX OKRs is goal-setting around volume (tickets, calls, QBRs) instead of outcomes (retention, value realization) — push every activity metric to justify itself as a leading indicator of a real outcome
- If the company has a single overriding outcome this quarter (e.g., defend NRR during a downturn), weight the objective set toward it rather than spreading evenly across functions
- Time-to-value is the most underused CX metric and the strongest predictor of early-stage retention — if the team isn't measuring it, the enablement objective should include establishing the baseline
- Stretch key results are healthy, but no more than one per objective should be a true stretch — otherwise the whole set reads as unachievable to leadership
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills