The Team Leader Who Protects Their Team From Bad Tools

On a Monday morning a team leader opens the weekly meeting by asking who has updated the shared tracker. Nobody has. The tracker is the third system the team is expected to keep current, alongside the ticketing tool and a spreadsheet a different department insists on. The team leader knows all three are partly duplicated. She also knows that if she raises it upstairs, she will be told the tools were chosen for good reasons. So she does what many team leaders do: she quietly absorbs the friction herself.

This piece looks at that role, the person who stands between a team and tools the team did not choose. It explores why the work is mostly invisible, what it costs the leader, and what a business can do so that protecting a team from bad tools does not depend on one person's private effort. It is a hypothesis drawn from general research on workload and support, not a finding about a particular South African employer.

What protecting a team looks like

Shielding a team from bad tools takes many forms, and most of them go unrecorded. A team leader might:

re-key information from one system into another so that the team only has to enter it once;
send a summary of the tracker to people who ask for it, so the team does not have to answer repeated questions;
run a short stand-up and update the system afterwards, so the meeting is about the work and not the form;
translate vague requests from other departments into something the team can act on;
negotiate quietly with the system owner for one small fix, instead of filing a formal request.

None of this appears in a job description. It is also not trivial. Each act removes some friction from the team and puts it on the leader.

The human tax: autonomy and energy

The cost to the team leader is energy. The Gallup research on employee burnout identifies unmanageable workload, unclear expectations and lack of manager support among its leading causes. A team leader who is absorbing the friction of several tools is carrying an extra workload that nobody has agreed to, and often has no one to turn to for support. The article on why nobody trains for the job of being human middleware describes what it feels like to be the connection between systems that do not talk to each other.

The cost to the leader's autonomy is subtler. A leader who cannot change the tools, cannot remove the duplicate reporting and cannot say no to a new system has limited say over how their own team works. The UK Health and Safety Executive's management standards for work-related stress treat control as a core condition of a healthy workplace, and they pair it with support: from managers, from colleagues and from the organisation. The leader who shields others often has the least of both.

The World Health Organization's guidance on mental health at work also names low job control and limited support as risks. The people most likely to experience both are often the ones who hold the team together.

An illustrative case

Consider an illustrative example, not a real case: a Johannesburg logistics firm whose customer service team of nine uses a ticketing system, a shared spreadsheet for urgent shipments and a messaging group for daily changes. The team leader, whom we will call Naledi in this example, joined the company four years ago and has watched each system arrive.

Each Friday she spends about two hours copying urgent items from the messaging group into the spreadsheet and from the spreadsheet into the ticketing system, because management reads only the ticketing reports. She does it in the evening so that the team's working hours stay free. She has told no one how long it takes. When her manager asks why she looks tired, she says it has been a busy quarter.

The team is productive and has low turnover, and part of the reason is Naledi. The business has no idea that its reporting depends on two hours of her Friday evenings, or that she is considering moving to a company with simpler tools.

Why this is hard to see

A shield works only if it is invisible. If the team notices the friction, it has not been shielded. If management sees the effort, it may decide the problem is handled. So the better a leader does the job, the less evidence there is that a job is being done.

The same invisibility makes it hard to bring up. A leader who says "our tools are costing us" may be heard as complaining about the tools, or about the people who chose them. The piece on why teams stop suggesting improvements describes how that silence sets in, and the ten open tabs and five logins shows the day-to-day cost for the people on the team.

What could realistically change

The aim is not to remove the team leader's protective instinct. It is to make the cost visible and share it.

Count it. For two weeks, the leader keeps a short note of every workaround done on the team's behalf and how long it took. A list of hours is harder to dismiss than a general complaint.
Bring a pattern, not a grievance. Present the list with a specific suggestion, such as one integration or one fewer report. The guide on how to separate urgent systems problems from merely annoying ones helps frame the case.
Ask before the next tool arrives. The questions in before you buy another tool, ask these questions can be put to any proposed system, including those from other departments.
Give the leader a voice in the decision. Team leaders see the cost of tools first. Involving them before purchase is cheaper than repairing the damage afterwards.
Share the load. If workarounds are needed in the meantime, rotate them or make them explicit tasks with time allocated, rather than leaving them to one person.

The business outcome

Making the hidden effort visible allows the business to decide whether it wants to keep paying for it. Often it will not. A single integration or the retirement of a duplicate report can return hours every week and reduce dependence on one person's goodwill. Retaining a good team leader is also worth more than most tool licences. In a labour market where experienced supervisors are not easy to replace, the leader who quietly holds a team together is a risk that is easy to overlook until she leaves.

There is a further benefit to the team. When the leader no longer needs to filter, the team sees the tools as they are and can contribute to fixing them. Improvement can then begin with those who use the tools most.

The human dividend

The dividend is autonomy: the ability of a team, and its leader, to shape how the work is done without having to work around the tools. For a team leader like Naledi, that would mean a Friday evening that belongs to her, and a team that can see the real state of the work. It does not require perfect systems. It requires a say in which systems stay, which go and which are never bought.

The trade-offs

Visibility has a price. Once the hidden work is shown, the business may expect the leader to fix it too.
Change takes time. Integrations and consolidations are not instant, and a leader may need to keep shielding in the meantime.
Tools often exist for a reason. A system that frustrates one team may serve another, such as finance or compliance, and the trade-off may be legitimate.
Not every cost is measurable. Some friction is real but hard to put a number on, which makes it easier to dismiss.
Shielding can go too far. A team that never sees the constraints may find it harder to understand why decisions are made.

Why it matters

Behind many functioning teams is a person absorbing the cost of tools that do not fit. The arrangement works until she tires, moves on or is promoted. A business that notices the work, counts it and gives its team leaders a voice in how tools are chosen turns a private act of protection into an ordinary part of how the business is run.

Sources and further reading

Employee Burnout, Part 1: The 5 Main Causes (last verified 10 October 2026)
Management Standards - Support - HSE (last verified 10 October 2026)
Mental health at work (last verified 10 October 2026)
Management Standards - Control - HSE (last verified 10 October 2026)