Most sales managers have the same problem and rarely say it out loud. Their people are out — at meetings, in cars, at a client's office, working from home on a Thursday — and the manager genuinely does not know how the week is going until someone tells them.
So they ask. And asking is slow, it interrupts, and it carries a faint accusation no matter how warmly it is phrased. Ask twice in a week and you are checking up. Ask nobody and you find out in month three that a deal died in month one.
The obvious fix is to watch more. It is also the fix that quietly destroys the thing you are managing.
Visibility and surveillance are not the same thing
They get confused because they use the same data. The difference is what the data is for.
Visibility is about the work. Which deals are moving. Where the pipeline is thin. Which client has heard nothing for a month. It is information about the state of the business, and any adult on the team would agree the manager should have it.
Surveillance is about the person. When they logged in. How many calls they made before lunch. Whether they were at their desk at nine. It is information about compliance with a routine, and it tells you almost nothing about whether the work is any good.
The test is simple. Would you be comfortable if the person could see exactly what you can see about them? If the honest answer is no, you have crossed over. Not because the data is secret, but because you already know they would experience it as being watched rather than being supported.
What a manager genuinely needs
Strip out everything that is merely interesting and the real list is short. Four things:
- ✓Who is stuck. A deal sitting at the same stage for six weeks. Not a judgement about the person — a fact about a deal that needs a second pair of eyes.
- ✓Who has gone quiet. Not the salesperson. The client. A relationship with no contact for a month is drifting, and nobody notices from inside their own week.
- ✓What was promised. A proposal due Tuesday that has not gone out. Commitments to clients are the business's problem, not a private matter.
- ✓Where the pipeline actually is. Enough at the top, enough near the close, and an honest view rather than an optimistic one.
Every item on that list is about a deal, a client or a commitment. None of them is about a human being's hour-by-hour behaviour. That is not a coincidence — it is the whole design principle. Point the system at the work and it stays useful. Point it at the person and it turns into something else.
What a manager merely wants
The wanted list is longer, more satisfying, and mostly worthless. Calls made. Meetings booked. Time in the system. Notes written. Login and logout. Activity per day, ranked.
These are attractive because they arrive as neat numbers, and neat numbers feel like control. They spike when a manager feels anxious, which is the tell: the demand for activity data usually goes up when results go down, and it is a way of doing something rather than a way of knowing something.
Fifty calls could be fifty voicemails. Twelve meetings could be twelve coffees with people who will never buy. A quiet week could be someone doing the deep work on the one deal that makes the quarter. Activity is the easiest thing to count and the least informative thing you can know.
The uncomfortable part
Here is the bit that gets left out of most articles on this, because it is inconvenient for anyone selling a dashboard.
Measuring activity changes behaviour, and usually for the worse. The moment a number goes on a board, it stops being a description of the work and becomes a target. People are not stupid. They will hit the target — and the cheapest route to the target is almost never the same as doing the job well.
You can watch it happen, and it is always the same shapes:
- ✓Call counts go up and call quality goes down. Short calls to easy contacts beat hard calls to real prospects, because the number does not know the difference.
- ✓Notes get longer and less true. Someone writing to be seen writes differently from someone writing to remember.
- ✓Deals get logged optimistically, because an empty pipeline looks worse than a fictional one, and the reckoning is always next month.
- ✓Meetings get booked that nobody needed, with people who were never going to buy, because a meeting counts and a judgement call does not.
None of that is dishonesty. It is a rational response to being measured on the wrong thing. The manager gets exactly what they asked for and none of what they wanted.
There is a second uncomfortable thing, pointing the other way. Some teams genuinely do need closer management, and that is not a moral failing. A new joiner three weeks in needs someone looking closely, because they do not yet know what good looks like. A team that has missed target four quarters running has earned a harder conversation than a monthly catch-up. Someone who has stopped doing the job needs to be managed, not trusted from a distance.
Trust is not a policy you apply evenly. It is something you extend at the level someone has demonstrated. The mistake is not managing closely — it is managing everyone closely because of one person, and calling it a system.
Coaching from the record, not interrogating from memory
Most one-to-ones are an act of recall. The manager asks what happened with an account, the salesperson reconstructs it from memory, and the meeting is spent rebuilding a picture that already existed somewhere. Half the time is spent on retrieval and the rest is spent on whatever came to mind first.
The alternative is that both people arrive with the same record already in front of them.
The difference in the room is immediate. Instead of "how is that account going?" — a question that invites a summary, and summaries are where optimism lives — the conversation starts at "this one has not moved in five weeks, and the last note says they were waiting on their finance team. What do you want to do?"
That is a better question in three ways. It is specific. It is about the deal rather than the person. And it does not put anyone in the position of defending their week.
Notice what makes it possible: the record has to be good, and the record only gets good if writing to it is worth the salesperson's time. Which loops back to the same principle that governs everything else here. A system that only feeds the manager will be fed badly. A system that gives the salesperson their own morning back gets fed properly, and the manager gets accurate visibility as a by-product rather than as a demand.
A rhythm that replaces the asking
Most of the temptation to monitor comes from not having a routine. If nothing is scheduled, the only way to find out is to interrupt someone, so managers interrupt.
A rhythm removes the need. It does not have to be elaborate:
- ✓Daily, on your own. Two minutes on exceptions only — deals that stalled, promises that came due, clients who have gone silent. You are looking at a short list of things that changed, not a report on everyone.
- ✓Weekly, with each person. Twenty minutes on three or four specific deals, chosen from the record before the meeting rather than remembered during it. Their agenda first, yours second.
- ✓Monthly, on the shape. Is there enough at the top of the pipeline to make next quarter, and is the mix realistic. This is the only one that is genuinely about numbers.
The point of writing it down is that a rhythm is predictable, and predictable attention does not feel like being checked on. An unscheduled question about a deal lands as suspicion. The same question at the same time every week lands as the job.
Be honest about what is visible
Whatever you decide to see, tell the team you can see it.
This is the cheapest thing in the article and the most often skipped. Quiet monitoring that later surfaces in a meeting — "I noticed you did not log in on Friday" — does more damage in one sentence than the monitoring itself ever did. The problem is not that you knew. It is that they did not know you knew.
Say it plainly, at the start, in ordinary words: here is what the system shows me, here is what I look at, here is what I do not. Then do exactly that. If you find yourself wanting to look at something you did not mention, that reluctance is information — it usually means you already know it is over the line.
As a general principle, people at work do expect their employer to have a reasonable view of the work itself, and they equally expect not to be tracked as individuals without being told. Most of the trouble in this area comes not from what was collected but from it being collected quietly and used for something other than what people assumed. Openness costs nothing and removes almost all of the resentment.
The short version
You will never see a field sales team the way you can see an office. Trying to solve that with more monitoring solves the wrong problem, because the thing you cannot see is not effort. It is judgement, and judgement does not show up in a login record.
Watch the work, not the worker. Keep the list of what you look at short enough to say out loud. Say it out loud. And accept that a manager who needs to know what everyone is doing at eleven on a Tuesday has a hiring problem or a trust problem, and neither one is fixed by a dashboard.
Common questions
Ask whether you would be comfortable showing the person everything you can see about them, and whether you could explain why you need it in one sentence about the work. If the reason is about a deal, a client or a commitment, you are fine. If the reason is really about whether someone is working hard enough, you are measuring the person, and they will feel it before you say anything.
Broadly, people accept that work done on company systems is visible to the company, and they do not accept being individually tracked without being told. The safe general principle is to collect what you actually need for the work, tell people what it is, and use it only for that. Most of the resentment in this area comes from surprise rather than from the monitoring itself, so being upfront removes almost all of it.
Yes, but for a specific person and a specific reason rather than as a permanent scoreboard. Activity is genuinely useful when you are diagnosing something — a new joiner learning the ropes, or a good performer who has suddenly gone flat. It stops being useful the moment it becomes a standing target, because then people optimise for the number instead of the outcome.
Not their activity — the shape of their pipeline. Look at how long deals sit at each stage, how many are genuinely near a decision, and how many are the same names as three months ago. Busy with nothing closing usually means too much time on deals that were never going to happen, and that is a qualification problem you can coach rather than an effort problem you can chase.
It is fairer than the alternative. Someone in their first month and someone in their eighth year need different amounts of oversight, and pretending otherwise underserves one and irritates the other. What is not fair is applying tight oversight to everyone because of one person's problem, or never explaining why one person is getting more attention.
Make the record something the team uses for themselves rather than something they file for you. If opening a client gives a salesperson the last conversation in four lines and a reminder of what they promised, they will keep it accurate out of self-interest. Accurate management reporting is a by-product of a system the team actually wants to use, and it is very hard to get any other way.
We build websites and run SEO & AEO for Singapore businesses. HeyAda is a Singapore web studio — design, copywriting, code and SEO, handled end to end. We write these guides to share what actually works, in plain English. If your site isn't getting found, say hi.
Not sure what you should be able to see?
It is usually a shorter list than people expect, and writing it down is half the work. Tell me how your team is set up and what you are currently guessing at, and I will tell you which of it is worth building a view for — and which of it you are better off not knowing.