Ask a team leader what they would like to do more of, and many will say the same thing: talk to their people. Ask what fills their week, and the answer is reports. Weekly summaries for the director, monthly packs for finance, status updates for a client, a dashboard to refresh before Monday. None of it is pointless. But the hours add up, and the conversations that never happen are not on any report.
This piece looks at how reporting crowds out the time managers have for their teams, what that costs, and how a business can make room. It is a hypothesis drawn from general research on management and working conditions, not a finding about any particular South African employer.
How reporting takes over a week
Reporting grows in a particular way. Every report starts with a good reason: someone needs to know how things are going. Then another person needs a slightly different view, and another asks for the same figures with a new cut. The first report is rarely retired when the second arrives. A manager who once produced one summary now produces five, each assembled from the same sources by hand.
The work is also hard to push back on. A report has a named reader and a deadline. A conversation with a team member has neither. When both compete for Thursday afternoon, the report wins, because the cost of missing it is visible and the cost of missing the conversation is not.
Three patterns usually sit underneath:
- Manual assembly. Figures live in several places and are gathered by copying and checking, so the time goes on collection, not on thinking.
- Duplicate requests. Different audiences ask for overlapping reports, and nobody compares them.
- Reporting as proof of work. A full report is a visible sign of effort, and a quiet word with an anxious employee is not.
What the research says about support
The UK Health and Safety Executive's management standards for work-related stress include a standard on support, which covers the encouragement, sponsorship and resources provided by the organisation, line management and colleagues. A related standard on relationships covers how conflict and unacceptable behaviour are handled. Both depend on managers being available, since a manager who is always at the screen cannot give encouragement, notice a problem or settle a small dispute before it grows.
The World Health Organization's guidance on mental health at work names poor communication and weak management practices among the working conditions that can harm wellbeing, and points to training for managers in recognising and responding to stress as one of the ways to protect people. Neither suggests that managers should abandon reporting. Both point to the time needed for the human side of the role.
The piece on when monitoring replaces trust in the reporting line describes a related risk: when numbers replace conversation as the way a manager knows their team, the numbers can say less than the manager believes.
An illustrative case
Consider an illustrative example, not a real case: a Gqeberha call-centre team leader responsible for fourteen agents. Each Monday she builds a performance summary for the operations manager from three exports. On Wednesdays she prepares a client-facing service report, and on the last working day of the month she compiles a pack for finance. Together these take about a day and a half a week.
Her one-to-ones with agents were meant to happen every fortnight. They have slipped to once a month, then to whenever someone looks upset. A new agent who is struggling with difficult callers goes six weeks without a proper conversation. When the agent resigns, the exit comment is that nobody seemed to have time. The team leader is surprised, and a little hurt, since she had been working through lunch to keep up.
The human tax: presence and time
The first cost is presence. A manager can be in the room and still be absent, with eyes on a screen and attention on the next number. People notice. They learn that bringing a problem to the manager means interrupting something more important, and they stop doing it.
The second cost is time, and it falls on both sides. The manager spends hours assembling figures. The team spends weeks waiting for feedback, guidance or approval that could have been given in a ten-minute conversation. Problems that would have been small become larger because nobody had room to catch them.
The cost is also unevenly spread. New staff, those who are quiet and those who find it hard to ask for help are least likely to push for attention, so they are the ones who lose most when attention is scarce. The loudest voices still get heard. The quiet ones become the ones who leave.
What could realistically change
Few businesses can stop reporting. They can, however, reduce the cost of producing it and be more deliberate about which reports are really read. The discovery piece on teams that cannot tell which reports are actually used describes how often that question has no answer. The note on what changes when status updates stop being a chore shows what becomes possible when the updates take care of themselves.
Where data is gathered by hand from several systems, a connected source can often replace the copying. Microsoft's documentation on scheduled refresh in Power BI is one example of how a report can update on a timetable rather than by someone's Monday morning effort. It is only one route, and it is only worthwhile if the numbers behind it are trustworthy.
Practical next actions
- List every report you produce. For each, write down who reads it, how long it takes to produce, and what decision it supports. Many managers find reports that nobody has asked about for months.
- Ask the readers. Show recipients the report and ask what they would miss if it stopped. Merge duplicates, shorten the long ones and retire what nobody uses.
- Automate the collection, not the conversation. Where figures are copied between systems, set up a scheduled or connected feed so that the manager reviews the numbers instead of building them.
- Block the people time first. Put one-to-ones and a weekly walk-around in the diary before the reporting deadlines, and treat them as seriously as a client meeting.
- Track the human side. Keep a simple note of when each team member was last properly spoken to. If a name has not appeared for a month, that is the next conversation.
The business outcome
A manager with time for their team spots problems earlier, gives clearer direction and keeps good people longer. Reports become shorter and better, because they are written by someone who knows what is happening on the floor and not just what the figures say. Turnover is expensive, and a business that loses staff because nobody had time to talk should count that cost against the supposed efficiency of full reporting.
The human dividend
The dividend is presence and time: a manager who is actually there when a team member needs a word, and team members who can expect an answer in the same week. For the manager, it is also relief from the sense of being always behind on the part of the role they value. What each person does with a good conversation, whether it is a decision, a career step or simply feeling heard, is for them to decide.
The trade-offs
- Less reporting means less visibility. Senior leaders may feel they are managing blind unless the remaining reports are clear and reliable.
- Not every manager wants more conversations. Some are better at analysis than at people work, and they may need training or a different split of duties.
- Automation can hide errors. A report that updates itself still needs someone to check that the numbers are right.
- Conversations can become another form. A one-to-one run as a box-ticking exercise adds to the load without adding presence.
Why it matters
A team is held together by the small, unrecorded exchanges between a manager and the people they manage. Reports are necessary, but when they eat the week they take the connection with them. A business that protects the time for talking, and trims the reporting to pay for it, gets better numbers and a team that is still there to produce them.
Sources and further reading
- Management Standards - Support - HSE (last verified 10 October 2026)
- Mental health at work (last verified 10 October 2026)
- Configure scheduled refresh - Power BI (last verified 10 October 2026)
Related Mellorca reading
- When Remote Work Means Missing the Quiet Conversations
- The Team That Only Talks When Something Breaks
- When Screens Sit Between Colleagues Who Sit Together