Short answer
A fair Customer Success review connects the rating to observable account work across the full period. Keep customers anonymous, separate activity from outcomes, and give every development point an operating change the person can take next.
Collect evidence across the portfolio
Use onboarding plans, adoption reviews, risk records, meeting notes, success plans, renewal preparation, and internal handoffs. Sample the whole period instead of choosing only a recent escalation or renewal.
Public examples and 360 feedback should use neutral references such as an account or the customer team. Do not include customer names, identifiable details, or unverified reasons.
Assess decisions, not relationship claims
A positive relationship is not enough evidence for a rating. Describe what the Customer Success professional learned, recorded, raised, changed, or coordinated, and what happened next.
Activity counts do not prove adoption or risk reduction. Connect meetings and messages to a verified customer action, internal decision, or clearer plan.
- Evidence of the customer's intended outcome or workflow
- A risk signal and when it was recorded
- The owner, decision, or next step created from the work
Use a third-person evidence shape
A manager example can read: They noticed [verified signal] in the account record and documented [risk or opportunity]. They brought [relevant role] into the plan, assigned [next action], and updated the renewal view when the evidence changed.
Keep placeholders until source notes support every claim. Do not invent adoption percentages, churn risk, customer quotes, or commercial outcomes.
Behavior instead of a trait
They recorded [risk signal], named the next owner, and updated the account plan before the next customer decision.
Align the narrative with the rating
Compare the evidence with the Function expectations for customer understanding, adoption, risk management, commercial judgment, and cross-functional work. Explain why the observed scope meets, falls short of, or exceeds the current level.
Do not raise a rating because an account was easy or lower it because a customer outcome depended on product, pricing, or another team. Assess the decisions within the person's control.
Turn development into an operating change
Name a specific pattern, such as late risk logging, unclear success criteria, incomplete renewal notes, or missing owners after customer meetings.
Add the next step and the evidence of progress. For example: They recorded risks only after escalation on [verified cases]. In the next period, they should review health signals before each account planning session, record the trigger and owner, and bring unresolved risks to the weekly portfolio review.