Published November 17, 2026.
A team can look evenly staffed on paper while the work is distributed very unevenly in practice. One person closes the difficult cases, another trains every new hire, and a third quietly absorbs the overflow. None of this appears in a headcount chart. A roster review makes the invisible load visible before it turns into burnout or an exit.
Start with the work the team actually does
List the work in categories rather than job titles. Separate core production from support work, rework, and coordination. Support work includes training, scheduling, and answering questions that never appear in a queue. A category list shows where the real time goes.
Ask each person to estimate the share of their week in each category. Use a simple check-in rather than a detailed time study. The estimates do not need to be precise to reveal a pattern. Compare the estimates with the team's own view of who is busy.
Include the work that arrives through side channels. A colleague who is the default person for a difficult customer carries a load that a ticketing system may not record. Ask what people handle outside the formal queue. The answer often explains a quiet frustration.
Count demand and capacity together
Compare the volume of work with the time available to do it. A roster with equal headcount can still be unequal when one area needs more cover. Look at the peak hours and the handoff points. The person on duty during the peak may carry more than the weekly average suggests.
Look at waiting time as well as completed work. A queue that is cleared by one person at the end of every shift hides a capacity gap. The wait shows where the team is short, even when the output eventually looks fine. Waiting time is often the earliest signal of imbalance.
Add the time spent switching between tasks. A person who covers three functions in one shift loses time to context changes. That loss is real even when no single task looks heavy. Count the switches rather than only the finished items.
Look for informal roles that never rotate
Name the informal roles the team relies on, such as the person who trains new hires or fixes the printer. Ask whether those roles rotate or sit with one person by default. A role that never rotates becomes invisible until the person is absent. The absence then reveals how much the team depended on them.
Check who answers questions from other teams. A single point of contact can be efficient, but it can also become an unpaid second job. Look at the volume and timing of those requests. If they cluster around one person, the team has a hidden dependency.
Review who handles exceptions and escalations. Exception work is often more tiring than routine work because it requires judgment and emotional effort. Count it separately from standard tasks. A fair roster accounts for the weight of the exception, not just its frequency.
Use a short observation rather than a survey alone
Spend time watching how work arrives and who picks it up. A survey captures what people remember, while observation captures what happens. Watch for the person who is interrupted most often. Interruption is a form of load that rarely shows in output counts.
Ask people what they would drop if they had one less hour in the day. The answer reveals the work that feels optional but still consumes time. Compare the answers across the team. A pattern of dropped recovery time is a warning sign.
Check the end-of-shift behavior. The person who stays late every day may be covering a structural gap rather than choosing to work longer. Ask whether the late work is scheduled or absorbed. A recurring late finish deserves a roster change, not a reminder to leave on time.
Share the findings without ranking people
Present the pattern at the team level rather than as a list of who does the most. A ranking invites defensiveness and misses the structural cause. Use categories and shares to show where the load sits. The conversation should be about the work, not about who is winning.
Explain what the review can and cannot show. Estimates are approximate, and some work is hard to count. Say that the goal is a better distribution rather than a perfect measurement. Honesty about the limits makes the findings easier to accept.
Invite corrections before any change is made. The people doing the work will spot a missing category or a misread task. Their corrections improve the picture and give them ownership of the fix. A review that ignores the team's knowledge will not last.
Test one change at a time
Choose one imbalance and one change that can be observed. Rotate the training role for a month, or move one recurring report to a shared queue. A single change is easier to evaluate than a broad redesign. It also limits the disruption if the change does not work.
Set a date to review the effect and a measure that the team accepts. The measure might be the number of late finishes or the share of interruptions during peak hours. Avoid a measure that only counts output, because output can rise while strain also rises. Use a measure that reflects both work and recovery.
Ask the team whether the change made the load fairer. Their answer is the main test, supported by the measure. If the change did not help, say so and try another. A failed experiment is useful information when it is reviewed honestly.
Build the review into the normal schedule
Put the roster review on a quarterly calendar rather than waiting for a resignation. A regular check catches drift before it becomes a crisis. Keep the format short so it does not compete with daily work. A recurring review is more valuable than a perfect one that happens once.
Assign an owner who can change the schedule and the task allocation. A review that ends with a report but no authority will not lead to action. Give the owner the team's findings and a date to respond. The response can be a change, a trial, or a reasoned decision to keep the current pattern.
Record the changes and the reasons in the team's operating notes. A future manager can then see why the roster looks the way it does. The record also prevents an old imbalance from returning unnoticed. Over time, the notes become a practical history of how the team learned to share the work.
Watch for the cost of invisible work
Invisible work often falls to people who are conscientious and less likely to complain. That combination makes the imbalance hard to see and costly to lose. Check whether the same person is always the helper, the note-taker, or the trainer. If so, rotate the role or recognize it in the workload count.
Ask whether the person carrying the invisible work has time for their own development. A helper who never gets to practice a new skill may leave for a role that offers growth. The roster review should include the opportunity side of work, not only the burden. Fairness includes access to the interesting tasks.
Review the distribution again after any team change. A departure or a new hire can shift the load in ways that nobody planned. A short check after the change catches a new imbalance early. The goal is a team that can adjust without waiting for someone to break.
