Team Capacity: Who Is Carrying How Much?

Workload management: visibility of open work, WIP limits, diagnosing imbalance and capacity decisions.

The team says it is busy and management cannot see why things are late. Both may be right — because “busy” is not a measured thing, and while it stays unmeasured the discussion runs on feelings.

Three measurable things

Open work count

How many open tasks, tickets and opportunities per person? The simplest and fastest indicator.

Age of the work

How long have they been open on average? Ten new items and ten month-old items are not the same load.

Inflow versus outflow

How many items open each week, and how many close? If inflow consistently exceeds outflow, a backlog is inevitable and no amount of effort closes it.

The third is the most valuable because it describes the future. Open counts describe today; the inflow–outflow balance describes two months from now.

Why imbalance happens

  • No assignment rule: in a “whoever sees it” model, whoever finishes fastest keeps receiving new work.
  • Concentrated expertise: if only one person knows a topic, that person becomes the bottleneck. That is a redundancy problem rather than a capacity one.
  • Invisible work: unrecorded work (corridor requests, asks arriving on a personal phone) appears in no report but consumes time.
  • Stale items: records that are open but effectively dead inflate the list, making someone look loaded when they are not.

Work-in-progress limits

Capping how many items someone can work on at once is counterintuitive and effective. The reason is simple: someone who has started ten things has finished none of them. With a limit in place:

  • Work finishes faster (the number completed rises, not the number started).
  • Context-switching costs fall.
  • Bottlenecks become visible — when the limit is full, new work waits and you can see where it jams.
  • The capacity conversation becomes concrete: “my limit is full” replaces “I’m busy”.

Making a capacity decision

Looking at the data produces three different conclusions, each needing a different response:

  1. Load is unbalanced: total capacity is sufficient but distribution is wrong. The fix is the assignment rule, not hiring.
  2. Load is balanced but excessive: inflow consistently exceeds outflow. The fix is either more capacity or less inflow (automation, self-service, narrower scope).
  3. Load is normal but work is late: the problem is the process, not capacity — waiting, approvals, missing information. Adding people here does not help and often adds confusion.

The third is the most commonly misdiagnosed: delays are seen, someone is hired, delays continue.

Measurement

  • Distribution of open work per person — the distribution, not the average; the gap between the most and least loaded matters.
  • Inflow-to-outflow ratio (weekly).
  • Average completion time and its trend.
  • Concurrent open items — and how often the WIP limit is exceeded, if you use one.
  • Aged work: the share of open records older than 30 days.

Frequently asked questions

Doesn’t measuring workload feel like surveillance?

It does if used to assess individuals. Used for capacity decisions, teams tend to want it — because “I’m busy” gains a measurable equivalent.

Not all work weighs the same — isn’t a count misleading?

It is, but it gives direction. If you want weighting, a simple estimate (small/medium/large) is enough; detailed effort estimation usually goes unfilled and wastes the effort.

What should the WIP limit be?

There is no fixed number. Start slightly below your current average and watch completion time; if it shortens, the limit is pointing the right way.

Next step: to see the per-person workload view, request a demo.