Summary
You have just been given a team and a dashboard. Nobody explained what the dashboard is for, and the two obvious ways to use it, checking on everyone constantly or ignoring it out of discomfort, are both wrong. This guide is for managers in their first year. It covers what monitoring data can and cannot tell you, a weekly routine that takes fifteen minutes, how to talk about the data with your team so it does not read as surveillance, and the five mistakes that new managers make with it in their first months.
E-Monitor's team dashboard is built for exactly this: team-level views by default, individual detail only when you go looking for a reason. Book a demo →
What the Dashboard Is Actually For
Monitoring data answers three questions well and one question badly. It tells you where the team's time goes, which is useful for spotting a process that eats hours. It tells you who is overloaded, because active hours and after-hours work climb before anyone complains. And it tells you when something changed, a sudden drop in someone's activity or a shift in what they work on, which is your cue to ask rather than to conclude.
The question it answers badly is "who is working hard". Activity is not effort and hours are not output. A dashboard that shows one person at ninety percent active time and another at seventy percent tells you almost nothing about which of them is doing the better job, and treating it as if it did is the first mistake most new managers make. The productivity definition guide explains why the two things come apart.
A Fifteen-Minute Weekly Routine
Look at the data once a week, at a fixed time, at team level first. Fifteen minutes is enough.
Minutes one to five: the team picture. Total active hours against last week, the split between focus time and meetings, the top applications. You are looking for changes, not levels. A jump in meeting time or a fall in focus time across the whole team points at something you did or something the organisation did.
Minutes five to ten: outliers. Anyone whose active hours or after-hours activity moved sharply in either direction. Note the name and the change. Do not draw a conclusion; write down the question you will ask.
Minutes ten to fifteen: one process. Pick one workflow the team runs and look at where its time goes. Most weeks this is where the actionable finding is: a report that takes four hours because it is assembled by hand, a tool that everyone has to leave the main system to use.
Then close the dashboard until next week. Checking it daily produces reactions to noise, and your team will notice.
Reading the Data Without Micromanaging
The line between managing and micromanaging runs through what you do with a number, not whether you looked at it. Three habits keep you on the right side of it.
Ask before you tell. "I noticed your hours were up a lot last week, is everything alright" opens a conversation. "Your idle time was high on Tuesday" ends one. The data gives you the question; the person gives you the answer.
Talk about patterns, not days. One slow afternoon is a life. Three weeks of shrinking focus time is a pattern worth raising. Nothing in the data about a single day should ever reach a one-to-one.
Use the data to change the work, not the person. If someone's focus time is poor, the first hypothesis is that their calendar is broken, the second is that their queue is badly designed, and personal habits come a distant third. The monitoring vs micromanagement guide has more on where the line sits.
What to Say to Your Team
If you inherited the monitoring, your team already has a view of it, formed under your predecessor. Reset it in your first team meeting with four sentences: what you will look at and how often, what you will not look at, that they can see their own data any time, and that you will always ask before drawing a conclusion. Then keep every one of those promises for a month, because they will be watching.
If monitoring is new to the team, the announcement belongs to the organisation, not to you, but your part is the demonstration: open your own dashboard in front of them and show what it looks like. The announcement templates have a manager script for the questions that follow.
Either way, bring the data into one-to-ones only as a shared screen, never as a printout across the desk. The one-to-one guide has the agenda slot for it.
Five Mistakes New Managers Make
1. Ranking the team by activity
The dashboard makes it easy to sort by active hours. Doing so, even privately, anchors your view of each person to a number that does not measure their work. Sort by nothing; look at changes.
2. Reacting to one day
A quiet Tuesday is not a performance issue. Managers who message someone about a single low day teach the team that the dashboard is a trap, and the team starts performing for it.
3. Using the data to win an argument
"The data says you were not working" is a sentence that ends trust permanently, even when it is accurate. If you need evidence for a formal process, HR handles that with a documented procedure; it is not a one-to-one tool.
4. Hiding that you look
New managers sometimes feel awkward about the dashboard and avoid mentioning it. The team assumes the worst. Say plainly that you look at team-level data weekly; the honesty costs nothing and removes the mystery.
5. Ignoring it entirely
The opposite failure. The overload signal in the data is real and early, and a manager who never looks will miss the person whose after-hours work has doubled. The trust guide makes the case that looking, openly and for the right reasons, is part of the job.
Questions Your Team Will Ask, and Answers That Hold
The first month brings the same handful of questions, usually in the corridor rather than the meeting. Have an honest answer ready for each. Vague answers are remembered as evasions.
"Can you see what I am typing or reading?" Answer with the actual scope: what is collected, what is not, and where the policy says so. If you do not know, say you will find out and come back by a named day. Then do.
"What happens if I have a slow week?" Nothing, on its own. Say that you look at patterns over weeks and that a single week is never a conversation. If they are worried about a specific week, that is a workload conversation, and it is better had now.
"Do you look at it every day?" Tell them your actual routine. Once a week, team level first, fifteen minutes. The specificity is what makes it believable.
"Is this because of something I did?" If you inherited the tool, say so plainly and explain that it applies to every team on the same terms. If it is new, point to the organisation's stated purpose rather than inventing your own.
"Can I see my own data?" Yes, and show them how. If the answer is genuinely no, that is a gap to raise with whoever runs the program, and you should tell the team you are raising it.
"Will this affect my review or my pay?" Answer from the policy, not from your own intentions. If monitoring data is not a review input, say so. If it is one input among several, say which, and note that they can see the same numbers you can.
One rule covers all of them: never promise something the policy does not support, and never dodge something the policy does say. The team will check both against what actually happens, and your credibility in month six depends on the answers you gave in week two.
Your First Ninety Days With the Data
Month one: look only at team-level views and learn the team's normal. Write down what a typical week looks like so that you recognise a change when you see one. Month two: start the fifteen-minute routine and raise one process finding with the team. Month three: bring the shared screen into one-to-ones, ask each person what they would like you to look at and what they would prefer you did not, and adjust.
By the end of the quarter you will have a team that knows what you look at and why, a handful of process fixes that came from the data, and probably one conversation about workload that happened before it became a resignation. That is what the dashboard is for.
Frequently Asked Questions
1. How often should a manager check monitoring data?
Once a week, at a fixed time, for about fifteen minutes, looking at team-level trends first. Daily checking produces reactions to noise and teaches the team that the dashboard is a trap.
2. Can monitoring data tell me who is working hard?
No. It shows activity and hours, not output or effort. Someone at seventy percent active time may be doing better work than someone at ninety. Use output measures for performance and use monitoring data for workload, process and change detection.
3. Should I tell my team I look at the dashboard?
Yes, plainly: what you look at, how often, what you never look at, and that they can see their own data. Hiding it makes the team assume the worst; saying it removes the mystery.
4. How do I raise something I saw in the data without micromanaging?
Ask, do not tell. Raise patterns of weeks, never single days. Start from the hypothesis that the work or the calendar is the problem, not the person, and share the screen rather than reading numbers at them.
5. What is the biggest mistake a new manager makes with monitoring?
Ranking the team by activity. It anchors your view of each person to a number that does not measure their work, and it leaks into decisions about who gets the interesting projects.
6. Is it better to ignore the monitoring data than misuse it?
No. The overload signal in the data arrives weeks before a resignation, and a manager who never looks will miss it. Look openly, weekly, at team level, and ask before concluding.
A dashboard designed for managing, not watching E-Monitor shows managers team-level trends first and gives every employee the same view of their own data. Sign up →
