Workload management

Team workload management without burnout.

Managing a team's workload is watching how much each person is actually carrying once the plan is in motion, and moving work around before anyone is quietly buried. It's the run-time companion to capacity planning. The commitments are made, the week is underway, and now the job is noticing who's stacked three deep and who has room, early enough to do something humane about it. All Do is a free, web-based planner built for that daily read: one swimlane per teammate, a green/amber/red capacity band that flags an overloaded week, PTO that shrinks the weeks it lands in, and drag-to-rebalance that updates the picture live for the whole team.

Workload management is the run-time half of planning

Capacity planning answers a plan-time question: before we say yes, can the people we have realistically finish this? Workload management answers the question that comes after the yes: the work is moving now, so who's drowning, and what do I shift today? The two get conflated because they share a picture, but they're different jobs. One is math you do once a cycle. The other is attention you pay continuously, because real work doesn't sit still. Estimates slip, scope quietly grows, and the next urgent thing lands on whoever happens to be closest.

On a team of six that closest person is almost always the same one: the reliable designer who never says no. Workload management is mostly the discipline of noticing that pattern in time, while there's still slack to redistribute, instead of after a launch shipped late and someone is fried.

Why design teams overload differently

Design work resists tidy estimation in a way that hides overload. A build task is roughly the size you thought; an exploration task is "until it's right," which can be a day or most of a week. When a designer is deep in a hard problem, the spillover doesn't show up as a missed ticket. It shows up as the next three things sliding, quietly, while the board still looks plausible.

That's the trap. The people most likely to burn out are the ones whose work is hardest to size, so their overload is the least visible on a list of tasks. A backlog of cards tells you nothing about whether Priya is carrying twice what anyone else is this month. You only see that when each person's load is laid out over time, side by side, where "consistently fuller than everyone else" becomes a shape you can point at.

The signals that someone is overloaded — before it's a crisis

The early warning signs are structural, and they're visible on a timeline weeks before the human ones surface:

• One lane is always fuller. Week after week, the same person's row is denser than the rest. A one-off crunch is fine; a standing imbalance is the thing to catch.
• Their tasks keep sliding. Work that should have finished keeps getting nudged into next week. Sliding bars are overload made visible.
• They're the default owner. Every new task lands on the same lane because they're trusted and fast. Trust is exactly how good people get buried.
• The week stays red. A single over-allocated week is normal. Three red weeks in a row is a person, not a sprint, running hot.

By the time the signals turn emotional — terse replies, skipped reviews, a flat tone in standup — the overload has usually been compounding for a month. Catching the structural signal first is the entire point of having the work in one shared view.

Rebalancing without making it worse

Spotting overload is the easy half. Fixing it badly — by silently moving a task to someone already near their limit, or by telling an overloaded person to "just prioritize" — makes it worse. Three moves actually help, in order:

• Move work to real room, not apparent room. Shift a task to a teammate whose week is genuinely light once their own PTO and meetings are subtracted — not to whoever looks idle on a list.
• Cut scope before you cut sleep. If no lane has room, the honest move is to drop or defer something, not to compress one person's week into the evenings.
• Have the conversation the tool can't. A board can show you the imbalance; it can't ask how someone's actually doing, or whether the hard task is hard because it's under-specified. That part is yours.

What All Do shows you, and what it doesn't

All Do treats workload as something you read at a glance rather than compute. The board is one timeline with a swimlane per teammate, switchable between week, month, and quarter, so the imbalance is a picture instead of a report.

• Capacity bands — a small green / amber / red strip under each week turns amber then red as a person's load passes what the week can hold. A standing overload is a run of red you can see down a single row.
• PTO that splits tasks — record someone's time off once and every task crossing it loses those days, so a thin week reads as thin and you don't accidentally pile work onto a half-week.
• Drag to rebalance — move a task onto a teammate with real room and the picture updates live; with realtime sync, the rest of the team sees the new plan immediately.
• Memos for context — pin a floating note above the lanes ("launch week — keep it light") so the workload picture carries the why, not just the what.
• Read-only sharing — hand a director an anonymized, read-only link so the "we're at capacity" conversation happens over the same picture you're managing against.

What it deliberately doesn't do: score anyone, nag, or claim a green board means a healthy team. It surfaces the signal early and gets out of the way. The judgment — and the conversation — stays with you.

A 60-second start

Open alldo.app, sign in with Google, and you land in a sample board with a few teammates and tasks already placed. Swap in your real people, drop this week's work onto their lanes with rough durations, and mark any time off. The lane that's three bars deep while everyone else has white space is your answer — and dragging one of those bars to a lighter lane is the fix, in the same motion you used to spot it.

When this isn't your problem

To save you the trial:

• You're one or two people — you already know who's slammed; you don't need swimlanes to feel it.
• You need hours logged and timesheets — All Do plans and balances load, it doesn't track time spent.
• You manage fifty-plus across a portfolio — that's resource-management-suite territory; the per-person lane stops scaling around ten.
• The imbalance is one rough week — don't reach for a tool. Move one task, or just say it out loud in standup. Workload management is for the standing pattern, not the occasional crunch.

Frequently asked questions