Workload is the amount of work that falls on a person or a team in a given period, measured against the time they have available. The key word is measured. Forty hours of work in a week is too much for someone working part time, and may be fine for someone with nothing else on their plate.
That is why you can’t determine workload from the number of tasks. Two people with five open tasks each can be in completely different situations.
Workload and capacity
The two concepts belong together, but they are not the same.
Capacity is the time a person actually has available for work. Meetings, time off, routine admin and anything that never makes it into the task manager all come off the top.
Workload is the work that falls into that time.
If workload is consistently higher than capacity, something will slip. If it is consistently much lower, that is a signal too, just one we notice less often.
Why task count is misleading
Task count is a convenient metric because it is easy to count. It gives a distorted picture for several reasons.
Tasks vary in size. “Call the supplier” and “prepare the quarterly report” are both one task. The effort behind them can differ tenfold.
Waiting tasks don’t add load. If someone has six tasks but four are waiting on something else, they can actually work on two. Blocked tasks inflate the list without adding work.
Invisible work gets left out. Answering questions, helping colleagues, urgent things that come up. These often never enter the system, yet they take time.
Timing matters. Ten tasks spread over three months are a very different load from ten tasks due the same week.
What to look at instead
Exact measurement is rarely possible. A good approximation is.
Estimated effort. Once tasks have a rough number of hours attached, workload becomes comparable. It doesn’t need to be precise. It already helps to know whether someone is carrying two hour tasks or two day tasks. The article on estimating project duration gives some pointers.
How deadlines are distributed. What matters is not the total amount of work but how much falls into the next week or two.
Active versus waiting tasks. Look separately at what someone can work on right now and what is waiting on others.
A buffer for unplanned work. If all capacity is planned, the first unexpected issue causes a delay.
In MyPro Sync, estimated effort can be recorded on tasks in hours, and the manager overview lets you filter all of the team’s tasks by assignee. That puts everyone’s tasks in one place to review. The manager draws the conclusions. The system provides the picture.
How to recognize overload
Overload rarely announces itself. Most people don’t speak up as long as they can cope. Some signs are still telling.
- The same person’s deadlines keep slipping while the quality of their work stays good.
- One person’s name shows up at the critical point of almost every project.
- Their tasks get started but stay in progress for a long time.
- They ask for extensions or help more often than they used to.
None of these is proof. But each is reason enough for a manager to ask.
Why workload is a management question
Team members see their own workload, rarely everyone else’s. Uneven distribution is therefore usually something the manager is in a position to notice and to fix.
That doesn’t require asking everyone every day. It is enough if tasks, owners and estimated effort are recorded, so the picture can be put together from them. That is what transparency without micromanagement is about.
As a first step, look at your team’s next two weeks. Don’t count tasks. Ask how many hours of work each person has in that period. If nobody knows, start by adding estimated effort to tasks.