Team Workload: How to See Who's Overloaded Without Asking

To see team workload, and who on your team is overloaded, stop asking and count. Take the task list your team already keeps, filter it to work that isn't done, and chart it by owner with one bar per person. The bar that's twice as tall as the others is the person to talk to, and you'll know before the missed deadline tells you.

Asking doesn't work because everyone answers it the same way. "I'm fine" is the polite answer, the safe answer and, for the person who's actually underwater, the answer that takes the least time. A count of open work doesn't have any of those reasons to be polite.

TL;DR: Keep one task list with an owner and a Done box on every row. Filter it to open work, group it by owner and count the rows. Compare bars, not totals: the chart of every task your team has ever had usually looks even, and the chart of open work often doesn't. Then open the conversation with the chart ("your bar is twice everyone else's, what should come off it?") rather than with a question about how someone is coping.

Why "is anyone overloaded?" always gets the same answer

Most managers of small teams have asked it in a standup or a one-to-one. It sounds considerate, and it almost never produces a yes.

Part of the reason is that nobody on a team can see anyone else's list. Someone with nine open tasks has nothing to hold nine up against. It might be a heavy week, or it might be what everyone has. Without a comparison, "fine" is an honest answer.

The other part is that the person with the most reason to say yes has the most reasons not to. Saying you're overloaded can sound like saying you're falling behind. It invites a conversation about your performance at exactly the moment you have the least time for one. And the busiest person on the team is the one least likely to stop and raise it at all.

One commenter put it plainly on Hacker News, in a thread about burnout: "We're siloed into different projects so I never realized I was doing 5x the work rather than 20% extra until a new reporting tool visible to each other was used." Not even the person doing five times the work could see it until the work was laid out side by side.

So the question gets the same answer every time it's asked, and the first honest signal is a slipped date or someone quietly working weekends.

What to count: open work, per person

The measure that answers "who is overloaded" is simple: how many unfinished tasks each person owns right now.

Two parts of that matter.

Unfinished. Counting every task a person has ever been assigned tells you who has been on the team longest, not who is busiest today. Finished work has to come out of the count, and the easiest way to make that possible is a Done checkbox (or a status) on every task.

One owner. A task owned by "the team" or by two people at once can't be counted against anyone. Give each task exactly one owner. If two people genuinely share it, split it into two tasks.

Here's the smallest table that supports this:

Task	Owner	Done
Send the Q4 proposal to Northwind	Henry	☐
Fix the invoice export	Sarah	☑
Draft the onboarding checklist	Henry	☐
Review the new pricing page	Fatima	☐

Nothing about it is special. Most teams already have something like it on a board, in a spreadsheet or in a project tool. What matters is that the owner and the done-ness are columns, rather than a name mentioned somewhere in a task's description.

Isn't a task count too crude?

A count treats "reply to an email" and "rebuild the billing page" as the same. That's a fair objection, and it matters less than it sounds. You aren't using the chart to grade anyone. You're using it to find the one bar that's out of line with the rest, and a difference of two to one tends to survive the noise of tasks being different sizes.

If your tasks vary wildly, add a size or an estimate column (a number of hours or points) and sum that instead of counting rows. Start with the count, though. It needs no extra discipline from anyone, and a measure that's kept up beats a better one that isn't.

Chart team workload: one bar per person

A list of forty tasks doesn't show you workload, even filtered. You'd still have to count names down the column. A bar chart does the counting and puts the answer where you can see it at a glance: one bar per owner, the height being the number of open tasks.

The filter is where the insight is. In the demo workspace we used to build this, the team's task list has 42 rows across five people. Charted with every task included, the bars read 9, 9, 9, 8 and 7, as even as a team could look. Filtered to work that isn't done, the same five bars read 8, 4, 4, 4 and 3.

Nothing about the team changed between those two charts. Everyone was assigned about the same amount of work. Four people have closed four or five of their tasks. One has closed one of nine, and now has twice as much open as anyone else. That's the thing a self-report hides and a filtered count shows. It's also why "everyone has about the same number of tasks" isn't reassuring on its own: the question is how much each person still has in front of them.

A few habits keep the chart honest:

Keep it next to the task list, not in a report. A chart exported once a month is out of date the day after. A chart that reads the same rows the team updates every day is always current.
Share one version. If each manager builds their own, they'll disagree about the numbers. Save the chart so everyone who opens it sees the same filter and the same bars.
Look at it on a schedule. Once a week, before a planning meeting or a round of one-to-ones, is enough. The value is in noticing a bar that's grown since last week.

What to do with the tall bar

The chart doesn't make the conversation easier. It changes who has to start it.

Without the chart, the overloaded person has to raise it, which is the thing they have every reason not to do. With the chart, the manager can open with something like:

"Your bar is twice everyone else's. What should come off it?"

That's a question about the work, and questions about the work are much easier to answer honestly than questions about how someone is coping. It usually leads somewhere concrete: a task that can move to Sarah, one that can wait until next month, one that was never really needed.

Three things to avoid:

Don't treat the short bar as the slacker. A short bar can mean someone finishes quickly, or that they're working on one big task. Ask before assuming.
Don't turn it into a leaderboard. The moment people think the chart grades them, they'll close tasks early or stop creating them. Use it to move work, never to rank people.
Don't leave the tall bar tall. Looking at the chart and changing nothing teaches the team the chart doesn't matter. Something should move by the end of the conversation.

This is the same idea behind running async standups and tracking postmortem action items in one table: swap a question people have reasons to answer politely for something anyone on the team can look at.

Setting it up in LumifyHub

In LumifyHub the task list is a database, and a chart is one of the ways a database can be shown, alongside a table and a board. The chart is a view of the same rows, so it's never a copy you have to keep up to date.

Open your task database. It needs an Owner select with one option per person and a Done checkbox.
Add a Chart view. Click the + beside the view tabs, choose Chart, and create it.
Group by Owner and count rows. Under Axes, set Group by to Owner and Aggregation to Count all. You get one bar per person, and the caption above the chart reads "Count all by Owner".
Filter out finished work. Add a filter on the chart view itself: Done, is not checked. Filters belong to each view, so a filter on your table doesn't carry over to the chart.
Save for everyone. The filter and axes are saved on the view, so a teammate opening it sees the same bars.

If your tasks have a number column such as hours or points, pick Sum as the aggregation and choose that column as the Value, and the bars show the total size of each person's open work instead of the count. It's one kind of chart, a vertical bar chart, which is the kind this question needs.

The full walkthrough, with a screenshot for each step, is in the guide See who's overloaded, and every option on the chart is covered in the database views docs.

If your tasks are currently spread across a few tools, our all-in-one workspace guide covers what it takes to keep the work, and the view of it, in one place.

Frequently Asked Questions

How do I know if someone on my team is overloaded?

Count the open tasks each person owns and compare them. Someone carrying roughly twice what their teammates carry is overloaded, whatever they say when asked. Missed deadlines, slow replies and people working late are also signs, but they show up after the fact. A count of open work shows it while there's still time to move something.

Why don't employees say they're overloaded?

Saying so can sound like admitting you're falling behind, it invites a conversation at a moment when you have no time for one, and without seeing anyone else's workload most people can't tell whether theirs is unusual. The result is that "I'm fine" is the answer to "is anyone overloaded?" whether or not it's true.

What's the best way to visualise team workload?

A bar chart of unfinished tasks, one bar per person. It's simple enough to read in a second, and the difference between one bar and the rest is the whole point. Filter out finished work first, or the chart shows who has been on the team longest rather than who is busy now.

Should I count tasks or hours?

Start with tasks. Counting rows needs nothing extra from anyone and is usually enough to spot a two-to-one imbalance. If your tasks vary a lot in size, add an estimate column and sum that instead.

How often should I check team workload?

Weekly is enough for most small teams, ideally before a planning meeting or a round of one-to-ones, so that anything the chart shows can be acted on in the same week.

Can I chart workload in LumifyHub for free?

LumifyHub's Free plan is for one person, and a team workload chart needs the team in the workspace. Paid plans are $10 per member per month, or $7 per member per month billed yearly. See pricing.