Are Your Managers Managing or Just Drowning in Workload
A manager can be busy all week and still do very little managing.
That is the problem. Calendars fill up. Reports go out. Approvals get cleared. Schedules get patched. Calls get answered. Escalations get handled. Everyone sees activity.
But the core work of management gets squeezed out: coaching people, fixing recurring problems, improving daily operations, and building stronger teams.
Busy is not the same as effective. Workload is not the same as management effectiveness.
Workload can hide weak management systems
Many organizations judge management by pace. A manager who answers every message, attends every call, and stays late to close reports looks committed.
That may be true. It may also reveal a broken operating model.
Look at a regional leader responsible for ten locations. Monday starts at 6:30 a.m. with route changes, time-off gaps, weekend incident notes, and customer complaints. By 8:00 a.m., the leader is building a weekly performance report.
The data already exists across workforce, finance, scheduling, customer, and operations systems. Leadership can already see most of it. Still, this regional leader spends half the day copying, cleaning, checking, and explaining the numbers.
By early afternoon, the report is done. Then come approval requests. One location needs a temporary labor adjustment. Another needs a vendor exception. A supervisor wants guidance on a disciplinary issue. A third location has a staffing shortage and asks the region to decide who moves where.
By 5:00 p.m., the regional leader has worked hard. But how much managing happened?
Not much.
No site visit. No coaching conversation with a struggling manager. No root cause review on repeat overtime. No evaluation of why one location keeps missing service levels. No time to compare practices between the strongest and weakest sites.
The issue is not personal discipline. It is system design.
When managers spend most of their time collecting information, routing permission, and absorbing escalations, the company has converted leadership capacity into administrative drag.
That has real cost. Gallup has long reported that managers play a major role in employee engagement. Lean operating systems also place strong focus on daily problem solving close to the work. Both ideas point to the same fact: managers create value when they improve people and processes, not when they act as human middleware between systems.
The difference between activity and management
Management has a job. It is not just keeping the machine moving.
At its best, management does four things well:
Sets clear priorities
Builds capable teams
Solves problems at the right level
Improves how work gets done
A loaded calendar does not prove any of that is happening.
A retail district manager may spend six hours a week in status calls and still miss the reason turnover is rising. A plant supervisor may approve schedule changes all day and never address why the schedule fails every Friday. A regional service leader may review last week’s numbers and never coach the location leader who keeps missing the same target.
The trap is that administrative work feels urgent. Coaching rarely does. Process improvement rarely screams. Better decision rights rarely show up as an emergency.
So the urgent work wins.
Here is the distinction that matters:
Workload is the volume of tasks a manager carries.
Workload shows up in email, meetings, reports, and approvals.
Workload often increases when systems are unclear.
Management effectiveness is the degree to which a manager improves people, decisions, and operating results.
Effectiveness shows up in stronger supervisors, fewer repeat issues, and better execution across locations.
Effectiveness improves when authority, information, and accountability match the role.
This is where many companies misread the problem. They see overloaded managers and add tools. Or they add analysts. Or they add another meeting to “get visibility.”
Visibility is useful. But visibility without better decisions creates more noise.
Span of control needs more than a headcount ratio
Span of control often gets discussed as a number. One manager has five direct reports. Another has twelve. A regional leader has ten sites.
The number matters. It does not tell the full story.
Ten stable, similar locations with experienced local managers may be manageable. Ten locations with high turnover, different service models, inconsistent systems, union rules in some sites, and weak frontline supervision are a different job.
A span of control assessment should look at more than structure charts.
Key questions include:
How similar are the locations or teams?
How mature are the local leaders?
How often do exceptions require regional approval?
How much travel is required?
How complete and trusted is the data?
How many recurring problems stay unresolved?
How many direct reports need active coaching?
How much decision authority sits above the work?
A broad span with clean systems can work. A narrow span with constant noise can fail.
This is where leadership capacity becomes measurable. A manager has only so many hours and only so much focused attention. Every recurring exception spends that capacity. Every avoidable report spends it. Every meeting without a decision spends it.
Companies that want better operating results need to ask a blunt question: what percentage of manager time goes to work that only a manager can do?
If the answer is low, the organization has a capacity problem even if every management role is filled.
Reporting automation helps only when the reporting work is worth doing
Reporting automation can return meaningful time to managers. It can also automate clutter.
That distinction matters.
If a regional leader spends Monday assembling a report from data the organization already owns, automation should be on the table. Leaders should not pay skilled managers to copy numbers into slides or reconcile exports by hand.
A better reporting model answers four questions:
Who needs the information?
What decision will they make with it?
How often does the data need to refresh?
What action should happen when the number changes?
If no decision follows, the report may be a habit. If the same data appears in three formats for three audiences, the process may be waste. If managers spend hours explaining numbers that no one trusts, the company may have a data governance issue, not a manager productivity issue.
Good reporting automation reduces manual work, improves consistency, and gives leaders faster access to the same version of the truth. It supports operational efficiency because it cuts the friction between data and action.
But automation alone will not solve weak management.
A dashboard will not coach a supervisor. An AI summary will not decide who has authority. A workflow tool will not fix a culture where every local decision gets escalated to the region. Automation can remove waste. Leaders still need to redesign the work.
The goal is not “more automated reports.” The goal is better management time.
Decision authority determines where problems land
Constant escalation is a sign. It may signal weak local capability. It may signal fear. It may signal unclear policy. It may signal leaders who say they want accountability but punish reasonable decisions.
Whatever the cause, escalation consumes management capacity fast.
When every staffing exception, customer concession, vendor change, and employee issue moves upward, managers stop managing their level. They become traffic controllers.
A healthy decision model makes three things clear:
What local leaders can decide on their own
What requires consultation
What must be approved at a higher level
This does not mean giving every manager unlimited discretion. It means matching authority to the work.
For example, a location manager may be allowed to approve overtime within a defined weekly threshold. A regional leader may review patterns when overtime exceeds a set level for repeated weeks. Senior leadership may approve structural staffing changes.
That model keeps exception work from swallowing the week. It also builds local judgment.
Decision authority and workforce strategy belong together. If the company wants stronger local leaders, those leaders need real decisions to make, clear boundaries, and coaching after the fact. They cannot grow if every meaningful call gets pulled upward.
Meeting discipline is a management system
Meetings are not the enemy. Bad meeting habits are.
Multi-site organizations need coordination. They need shared priorities and fast issue resolution. They also need to protect the time managers use to lead.
A meeting should earn its place on the calendar.
Use a simple test:
Is there a decision to make?
Is there a problem to solve?
Is live discussion needed?
Are the right people in the room?
Can the update be handled through a dashboard or written note?
Will the meeting end with owners and next steps?
If the answer is no, the meeting is probably consuming capacity without creating value.
Recurring meetings deserve special scrutiny. They often survive because no one wants to challenge them. A weekly call that made sense during a crisis may become permanent. A reporting review may become a ritual. A leadership sync may turn into status reading.
Status reading is not management. It is expensive narration.
For senior teams, meeting discipline sends a cultural signal. If every issue requires a meeting, the organization teaches managers to wait for group discussion. If meetings end without decisions, the organization teaches managers that time has little cost.
Set a higher bar. Fewer meetings. Better agendas. Clear decisions. Shorter invite lists. Written updates where written updates work.
Then give managers the space to act.
Measure where leadership time actually goes
Many companies measure labor hours closely. They track overtime, absence, productivity, open roles, and cost per unit.
They rarely measure how management time gets spent.
That is a mistake.
Leadership time is one of the most expensive and constrained resources in the business. It deserves the same attention as labor dollars and capital spend.
A simple time study can reveal more than another engagement survey or performance review cycle. It does not need to be complex. For two to four weeks, ask managers to classify their time into clear categories:
Coaching and talent development
Direct operational problem solving
Reporting and data preparation
Administrative work
Scheduling and staffing coverage
Meetings
Approvals
Escalations
Travel
Customer or employee issue resolution
Then compare the results by role, region, location type, and performance level.
The findings often expose the real problem.
High-performing regions may spend more time coaching and less time chasing exceptions. Struggling regions may spend more time preparing reports because data quality is poor. New managers may escalate more because decision rules are unclear. Senior leaders may discover that they created many of the approvals slowing the system down.
This kind of measurement turns complaints into evidence.
It also helps avoid lazy answers. If managers are overloaded, the answer may be automation. It may be better staffing. It may be clearer authority. It may be fewer meetings. It may be a smaller span of control. It may be stronger frontline capability.
Most often, it is a mix.
That is why the best fix starts with diagnosis, not tools.
The management capacity test
A practical management capacity review should ask five direct questions.
Are managers doing work that systems should do?
Manual reporting, duplicate entry, status compilation, and recurring file cleanup are signs that systems are not carrying their share.
Are managers making decisions at the right level?
If senior leaders approve routine exceptions, the organization has likely centralized too much control.
Are managers coaching enough to build future capacity?
If coaching time is near zero, today’s workload will become tomorrow’s talent problem.
Are meetings creating decisions or consuming attention?
Every standing meeting should have a clear purpose, owner, and useful output.
Are spans of control based on complexity?
A flat headcount ratio ignores location maturity, operational variation, turnover, travel, and data quality.
This test does not blame managers. It tests the system around them.
That matters because burned-out managers can look like low performers. In reality, they may be carrying work the organization never designed well.
Before adding another layer, another dashboard, or another initiative, look at where the time goes.
For organizations ready to examine the work behind the org chart, Data Consultants Inc. brings together workforce analysis, operations improvement, and practical AI automation. Explore DCI’s services to see how those capabilities connect.
FAQ
How can leadership tell if managers are overloaded or ineffective?
Start by measuring time use and outcomes together. If managers spend most hours on reports, approvals, meetings, and escalations, workload may be blocking effectiveness. If they have protected time but teams still miss clear expectations, capability or accountability may be the issue.
What is a healthy span of control for a regional manager?
There is no universal number. Ten locations may be reasonable if operations are stable, data is clean, and local leaders are strong. Five locations may be too many if turnover is high, decision rights are unclear, and every issue escalates.
Should companies automate management reports?
Yes, when the reports are still needed and the data is reliable. Do not automate reports that no longer support decisions. First confirm the purpose, audience, timing, and action tied to each report.
How do meetings reduce management effectiveness?
Meetings reduce effectiveness when they replace decisions, repeat information already available elsewhere, or pull managers away from coaching and problem solving. Meeting discipline protects leadership attention.
What should managers spend more time doing?
They should spend more time developing people, removing barriers, solving recurring operational issues, improving local execution, and building stronger frontline decision-making.
The real question is what management time is buying
The goal is not to make managers less busy. The goal is to make their time more valuable.
A manager who spends Monday assembling reports from available data is not failing. The system is wasting scarce leadership capacity. A regional leader who approves routine exceptions all day is not always being helpful. The organization may have failed to define decision rights. A supervisor in constant meetings may not be more aligned. They may simply have less time to lead.
Workload is visible. Management value is harder to see.
Measure it anyway. Then redesign the work so managers can manage.
Comments