A 1:1 is the highest-bandwidth channel a manager has, and most of them start from memory: "how's the week going?" Meanwhile the honest answer, where the week actually went, is sitting in your activity dashboard: focus time, idle stretches, app mix. The question is how to bring that data into the room without turning the conversation into an audit.
The distinction matters more than any dashboard feature. Data used as a conversation starter builds trust and surfaces problems early. The same data used as a gotcha ends the conversation permanently. People don't argue with surveillance, they just route around it.
The data is a prompt, not a verdict
Activity data tells you what happened, never why. A cratered focus-time week could be a struggling employee, or three fire drills, a broken build, and a calendar full of meetings they didn't ask for. If you walk in with a conclusion, the data becomes an accusation wearing a chart.
Walk in with a question instead. "I noticed your focus blocks got shorter after the reorg, what's eating them?" invites the person to explain their own week. Nine times out of ten the explanation points at something you can actually fix: meeting load, unclear priorities, a noisy on-call rotation.
Three signals worth bringing into the room
- Focus-time trend. Not one week's number, the direction over a month. A steady decline is a leading indicator of overload or disengagement long before it shows up in output.
- Context-switching. When someone's day fragments across ten apps in five-minute slices, the problem is rarely the person. It's how work reaches them.
- Idle-time patterns. A cluster of idle periods at the same time every day usually maps to something structural: a recurring meeting that shouldn't exist, or a dependency that blocks them every afternoon.
Notice what's not on the list: screenshots, individual app tallies, or anything at minute-level granularity. That resolution belongs to work verification (invoicing, compliance), not to coaching conversations.
Anti-patterns to refuse: opening a 1:1 with a screenshot, reading idle minutes as laziness, ranking teammates against each other's activity scores, or quoting the data back as a gotcha when someone says the week was rough. Each one teaches your team to perform activity instead of doing work, and once that starts, your data is worthless too.
Openers that work
The framing that works is consistent: name the pattern, own your interpretation as a guess, and hand over the microphone.
- "Your focus time doubled since we moved standup, is the new slot working for you?" Reinforce a win.
- "I see a lot of context-switching on Tuesdays. What's landing on you that day?" Diagnose fragmentation.
- "The dashboard shows a lot of after-hours activity these past two weeks. I'd rather fix the cause than have you burn out, what's driving it?" Catch overwork early.
Close the loop or don't bother
The fastest way to make people resent activity data is to discuss it and change nothing. Every data-informed 1:1 should end with one concrete adjustment (a meeting declined, a priority clarified, a blocker escalated) and next week's 1:1 should check whether it moved the needle. That is also the honest test of whether you're using the data for management or just for monitoring: if the numbers only ever produce scrutiny and never produce change, your team will notice before you do.
Used this way, the dashboard stops being something done to your team and becomes something done for them. Same data, opposite meaning, and the difference is entirely in how you open the conversation.