A performance-review conversation addressing variability needs a different structure than one addressing a fixed skill gap — it should center on the gap between an employee’s own best and typical output, not just their average score, and frame the discussion around regulation support rather than skill correction, since the skill is often already demonstrably present.
Why Leading With the Average Score Misses the Point
A review conversation built around an average score treats the issue as a single number needing to rise, which doesn’t fit a variability problem well — the average may be entirely acceptable while the underlying inconsistency, visible in the spread between best and worst outcomes, is the actual issue worth discussing.
Why Showing the Employee’s Own Best Work Changes the Conversation
Opening with concrete examples of an employee’s own strongest performance reframes the conversation away from “you need to develop this skill” and toward “you clearly have this capability — what’s getting in the way of accessing it consistently,” which is both more accurate and less likely to be experienced as a skill-based criticism that doesn’t match the employee’s own sense of their ability.
Why This Reframing Reduces Defensiveness
An employee told they lack a skill they know they possess — because they’ve demonstrated it repeatedly — reasonably experiences that feedback as inaccurate or unfair, which tends to produce defensiveness. Framing the conversation around consistency and access to existing skill, rather than skill itself, tends to land as a more accurate and more collaboratively solvable framing.
What a Variability-Focused Review Conversation Actually Covers
Reviewing the specific pattern — when the dips occur, what they correlate with, whether they cluster by time, task type, or workload — together with the employee, and discussing what recovery or regulation support might address the pattern, replaces a generic “improve your performance” directive with a specific, collaborative diagnostic conversation.
Frequently Asked Questions
Does this mean skill development should never be part of the conversation?
Not necessarily — some employees have both a genuine skill gap and a variability pattern, and the conversation should address whichever is actually supported by the data.
How can a manager show variability data without it feeling like surveillance?
Framing the data collaboratively — as a shared tool for understanding the pattern together, rather than evidence being presented against the employee — supports a more constructive conversation.
How does ORS™ inform variability-focused review conversations?
ORS™ (Operational Regulation Systems) provides the pattern data — best-case vs. typical performance, correlation with specific conditions — that supports a regulation-focused rather than skill-focused review conversation.
Related Reading
Read more on how a manager should respond differently to a mediocre vs. a variable performer and why you should measure performance variability instead of just averages. ORS™ (Operational Regulation Systems) was built by Matthew F. Stevens.