Equal Workloads Are Not Always Fair Workloads

A team can divide tasks evenly while distributing uncertainty, interruption and responsibility very unevenly.

The count can hide the burden

A manager can assign the same number of tasks to two people and still create an unequal working arrangement. One list may contain familiar work with clear inputs. The other may require repeated clarification, difficult coordination and responsibility for consequences outside the worker's control. Equality in the count does not establish fairness in the commitment.

This essay offers an editorial framework rather than a new empirical finding about workplace behaviour. The practical question is how to discuss workload without relying exclusively on visible units. Fairness becomes more examinable when the team can describe what a task actually requires, which uncertainties it carries and how much room the person has to decide how it is completed.

Separate volume from complexity

A routine task and an ambiguous assignment can look identical on a planning board. Both may be represented by one card. The second can consume more attention because its definition changes as the work proceeds. A useful workload conversation should therefore examine the nature of the assignment, not simply the number attached to its owner.

Consider a hypothetical team preparing several client documents. One person updates an established format using complete information. Another must coordinate conflicting contributions and resolve missing decisions. Dividing the documents equally does not divide the effort equally. The point is not to discover a perfect universal weighting. It is to make the relevant differences visible before the allocation is described as self-evidently fair.

Include the cost of interruption

Some roles absorb questions, approvals and emergencies generated by the rest of the team. That work may not appear on the person's original list, although it repeatedly reduces the time available for it. An assessment based only on planned deliverables can misinterpret the resulting delay as poor personal organisation.

Track a representative period and ask which interruptions required this person's attention, which could have been resolved elsewhere and which reflect unclear authority. The purpose is to improve the arrangement, not to account for every minute indefinitely. A modest record can reveal that a team has assigned someone both a full production load and an unacknowledged coordination role, then judged them as if only the first existed.

Responsibility should be matched with influence

An employee can be held accountable for an outcome while lacking control over the inputs or decisions that determine it. This produces a different burden from a task whose owner can change the method, negotiate scope or stop unsuitable work. Fairness should include that relationship between responsibility and authority.

A fictional project coordinator may be expected to guarantee a deadline while other teams can delay their contributions without an agreed escalation route. The coordinator's workload includes managing that contradiction. A clearer arrangement identifies dependencies and gives the owner a way to raise a decision before failure becomes inevitable. Repeating the instruction to take ownership does not create authority that the organisation has withheld.

Make invisible support discussable

Helping a colleague, documenting a process and answering recurring questions can support the team's output without generating an individual deliverable that is easy to display. If these contributions are never considered, the people performing them may face an unattractive choice between supporting the group and protecting their own visible performance.

A workload review should ask who maintains the conditions under which everyone else works. Some support may belong within an ordinary role; some may have accumulated accidentally. Making the work visible does not automatically settle how it should be rewarded or distributed. It creates the basis for a more honest decision than assuming that work absent from the project list has no cost.

Explain an unequal allocation

Fairness does not always require assigning the same work. Experience, development needs and temporary circumstances can justify different responsibilities. The explanation matters because an unexplained exception can be interpreted as favouritism even when a defensible reason exists.

State the purpose and review point of a different arrangement without exposing private information unnecessarily. A temporary reduction to support a specific transition differs from an indefinite expectation that others will absorb extra work without discussion. The team needs enough clarity to understand how the allocation serves its responsibilities and when it will be reconsidered. Transparency should support coordination while respecting the boundaries of information others do not need.

Keep development work visible

Training someone can temporarily increase another colleague’s workload even while it improves the team’s future capacity. A fair allocation recognises both parts of that exchange. Identify the time needed for instruction, review and correction, and avoid treating the trainer as if the additional responsibility were costless. At the same time, specify the capability the learner is expected to acquire. This makes the arrangement a deliberate investment rather than an indefinite transfer of work hidden inside a general expectation that experienced people will always help.

Test the arrangement through delivery

After changing an allocation, examine whether work has become more reliable or the burden has merely moved to someone less visible. A cleaner dashboard is not sufficient evidence of improvement. Ask whether dependencies are clearer, interruptions are manageable and people can complete the work for which they remain accountable.

My conclusion is that fairness requires a more accurate description of work. Equal counts can be one useful reference, but they should not end the discussion. A team works with greater clarity when it can distinguish volume, complexity, support and responsibility. That vocabulary makes disagreement easier to resolve because the conversation can examine the arrangement rather than treating every concern as a contest over who is willing to work harder.

Gabriel Nicolaev — CyGuru

Editorial photograph for illustration.

FOLLOW THE CONNECTION

Another angle on this subject

Continue through related ideas, decisions and consequences.

The CyGuru Column

Finishing Quietly Can Restore the Meaning of the Work

A completed task does not always need a public performance of completion. Some results deserve to be lived before they are displayed.

Human Behaviour

Confidence Is Not the Same as a Good Decision

A convincing account of an outcome can hide weak reasoning, while a careful choice can still end badly.

Culture & Ideas

Translation Preserves Meaning When It Makes Difficult Choices Visible

A fluent translation can conceal uncertainty about tone, context and concepts that do not fit neatly into the receiving language.