Read a sample: 1. What a Fair Workload Really Means
On Monday morning, Maya looks at her team’s assignment board and feels reasonably confident. The work appears to be spread across three people. Each person owns several items, and no one has raised an urgent objection.
By Wednesday, that picture has changed.
A customer has asked for an accelerated delivery. Priya, the team’s most experienced specialist, is answering questions from two colleagues while trying to finish a difficult analysis. Luis is leading a visible presentation that could help his development, but he is also handling routine requests that arrive throughout the day. Erin has fewer items on the board than either colleague, yet one assignment depends on information from several departments, and she spends much of her time chasing decisions that nobody else can make for her.
Maya’s first impulse is to move an item from Priya’s column to Erin’s. The board suggests Erin has room. A short conversation reveals that the move would give Erin another dependency-heavy project just as she is trying to resolve the first one. Luis offers to take it, but he would need guidance from Priya, who has little uninterrupted time available.
There is no obvious villain here. Maya is not careless, and the team members are not unwilling to help. The difficulty is that the visible assignment count is only a partial account of the work. Even with a fuller picture, Maya still has to make choices: whether to meet the accelerated request, which work can wait, who should receive a development opportunity, and how much support the team can provide while deadlines are close.
That is the central challenge of fair workload leadership. Fairness is not a number that can be calculated once and announced. It is a continuing effort to understand the work, make defensible choices, and adjust when the reality changes.
Equal distribution can be useful when tasks are genuinely similar, team members have comparable capacity, and the work carries similar consequences. If everyone is taking turns monitoring the same inbox under the same conditions, a roughly equal rotation may be a sensible starting point.
Most teams do not have only one kind of work. One assignment may take a focused afternoon; another may occupy someone’s attention for weeks because it requires repeated follow-up. A task that is straightforward for an experienced employee may be a valuable but demanding learning opportunity for someone else. A routine responsibility may be easy to complete yet difficult to schedule around because it can arrive at any moment.
Counting assignments as if they were interchangeable hides these differences. It can also reward the wrong behavior. A person who divides work into small visible tasks may appear busier than a colleague carrying a single, complicated responsibility. Someone who quietly prevents problems may look available precisely because those problems never reach the assignment board.
Fairness asks a broader question: Given the work, the people, and the constraints, is this a reasonable distribution—and can we explain and revisit it?
A reasonable distribution will not always feel equal on a particular day. One person may carry more urgent work during a launch while another prepares for the next phase. A specialist may temporarily handle a difficult issue that others cannot yet resolve independently. A colleague may take on a larger share for a short period while someone else is unavailable. These arrangements can be fair, but the word temporary needs substance. Leaders should be able to say what is expected, what support is available, when the arrangement will be reviewed, and what will happen if it continues.
The opposite is also true: an equal-looking distribution can be unfair. If everyone receives the same number of assignments but one person handles the hardest problems, trains new colleagues, and absorbs the interruptions, the symmetry is cosmetic.
A workload is not simply a list. It is a combination of demands that compete for time, attention, judgment, and flexibility. As you assess whether a load is reasonable, look beyond the title of each assignment.
Urgency changes the shape of work. A task due soon may require someone to set aside planned work, respond quickly to questions, or remain available for decisions. Two assignments of similar scope can feel very different when one has a flexible deadline and the other is tied to an approaching commitment. Repeated urgent requests also create a burden that may not be obvious from any one request.
Ask whether urgency is real, assumed, or inherited. A colleague may say, “We need this immediately,” when what they need immediately is an answer about when the work can begin. Clarifying that distinction does not make the request unimportant. It gives the team a chance to make an informed commitment.
Difficulty is more than technical complexity. Difficult work can involve unfamiliar subject matter, ambiguous instructions, sensitive conversations, competing stakeholders, or decisions with consequences that are hard to reverse. A task may be demanding because the person doing it must continually decide what to do next, not because it appears large on a plan.
Difficulty also depends on the person’s experience and available support. An experienced analyst may know where to find an answer that a newer analyst must learn how to locate. That does not make the newer analyst less capable or the assignment inherently inappropriate. It means the leader should account for learning time, access to guidance, and the effect on other commitments.
Coordination is work, even when it produces few…