A team leader's load isn't just the actual work
On the shop floor, a team leader often ends up with all of this:
- Their own regular work
- Putting into words roles that management never defined
- Juggling priorities and deadlines
- Improving processes and writing the standard procedure documents
- Training new hires
- Keeping tabs on everyone's progress
- Maintaining a workplace where people feel safe speaking up
- Putting out fires when mistakes and delays pile up
- Reworking slides and reports for the people above them
That's not one job. It's four rolled into one: the person doing the work, the trainer, the one who designs how work gets done, and an unofficial manager.
Managers are supposed to set the purpose, the roles, the priorities, the resources, the time budget for training, the decision-making authority and the criteria for evaluation. Leaders then handle day-to-day operations inside that frame. But when a manager pushes the design work down and only grades the results from above, responsibility and authority come apart.
Hands-off and micromanaging can go together
Micromanagement isn't only about giving detailed orders from the start.
Hand it over vaguely at first
→ The person thinks it through and builds something
→ The manager fixes the details afterward
→ It gets redone again and again
→ Right before the deadline, the manager or a mid-level employee takes it over
With this pattern, the boss tends to feel they're "respecting people's initiative." In reality, they never showed where the decision boundaries were, and they've kept the option to step in at any moment.
From the employee's side, it looks like freedom but isn't. You're on the hook for the outcome, yet you have no right to define what the right answer is.
Psychological safety can't rest on one person's good nature
When they have slack, people can be patient and kind with newcomers. But once regular work, questions, reviews and firefighting stack up, you start hearing things like this:
I already explained that. I'd like you to think for yourself more. I'm busy right now, so can it wait?
If the company explains this away as a personality problem, it just piles more onto that person: "communication training," "active listening," "psychological safety." The actual workload doesn't go anywhere.
According to the Job Demands-Resources model, high job demands are linked to exhaustion, and a shortage of resources is linked to withdrawal and cynicism. [1] Resources like autonomy, feedback and support can cushion the link between overload and burnout. [2] A meta-analysis that pooled 203 samples and more than 180,000 people also found links among job demands and resources, burnout, engagement and safety outcomes. [8]
So psychological safety isn't "the ability to stay kind no matter how busy you are." It's an operating design that includes enough people, time, standards and authority to actually handle the questions.
What a superhuman can do isn't a standard
The ideal leader is often expected to have all of these abilities at once:
- Knows the work inside out
- Teaches well
- Can keep track of everyone's progress
- Can explain things differently to each person
- Never gets emotional
- Can improve processes too
- Can put together materials for upper management
- Meets their own deadlines
Some people can do all that, alone. But a system should be judged by whether an ordinary successor could take over.
A standard that assumes a superhuman isn't a standard.
When a strong performer soaks up the gaps, the manager sees "things are running fine." Nothing gets fixed, the work keeps piling onto that one person, and the whole thing collapses the moment they quit, transfer or go on leave.
Pushing management work down gets called "leadership"
Making your subordinates figure out their own role, guess what your own boss expects from a report, or leave training methods and training time up to the floor doesn't necessarily build initiative.
What a person should think through is how to carry out the role they've been given. What the manager should define is what needs to be achieved, what the person may decide, what they aren't responsible for, what comes first and how they'll be evaluated.
If you make someone submit a blank-slate version of their role and then keep correcting it afterward, the subordinate ends up doing the manager's work of putting things into words, in a "redo game."
When managers focus upward, nobody designs downward
Managers can spend much of their time on meetings, briefings for their superiors, back-and-forth edits to slides, and tweaking wording to get approval. Some of that is necessary work. But it's a problem if the following get neglected as a result:
- Where each role begins and ends on the floor
- Priorities
- Spare capacity for training
- Flaws in the process
- Decisions for when something goes wrong
- Decisions to reduce the workload
When explaining things upward becomes the manager's main job and the downward design gets passed to the leader, the leader turns into "the person who covers the work of the people above."
The cycle that drains mid-level staff
The manager doesn't design it
→ Mid-level staff fill in the ambiguity
→ Training newcomers and firefighting land on them too
→ Mid-level staff run out of slack
→ Newcomers find it hard to ask questions
→ Mistakes and delays increase
→ Mid-level staff take on even more
→ Newcomers or mid-level staff quit
→ The load concentrates on those who remain
Mid-level employees tend to have both the experience to see what's wrong with the organization and the market value to leave for somewhere else. That's why the ones who go first aren't the people who can't put up with it, but the ones who can see the flaws and have the ability to walk out.
