The data conversation trap

The most common failure mode when managers bring data to performance conversations is leading with the data as a verdict: "Your focus score is X, which is below the team average." This immediately puts the employee on defence. The data becomes evidence in a trial rather than a shared problem-solving tool. The employee spends the rest of the meeting justifying or deflecting rather than reflecting and improving.

The opening that works

The most effective opening for a data-rich conversation is curiosity rather than finding. "I noticed from this week's data that your coding time was lower than usual and your communication tool time was higher. I'm curious what was going on this week — anything I should know about?" This invites the employee to provide context, which usually explains the data and opens a genuine coaching conversation.

When the data and the narrative diverge

Sometimes an employee's account of their week and the data diverge significantly. This requires careful navigation. The data is objective but incomplete — it does not capture phone calls, whiteboard sessions, thinking time, or offline work. The employee's account may be self-serving but contains real context. The right move is to name the gap without accusing: "The data shows something different from what you're describing — can you help me understand what I might be missing?"

Closing with action, not judgment

The best data-based conversations end with a shared action: a change the manager will make (protecting focus time, removing a blocker), a change the employee will try (batching communication to twice daily), or a follow-up conversation at a specific time. They do not end with a warning or a lecture. Data reveals patterns. Conversations create change. The goal is the change.