Read a sample: 1. The Fairness Challenge
Maya has been supervising her team for a few weeks when two employees ask for the same Friday off. Both submitted their requests before the team’s scheduling deadline. Their work overlaps, and Maya believes she can approve only one request without leaving the shift short.
Elena submitted her request first. Jordan has been flexible about covering unpopular shifts in the past. Both have plans they would rather not change.
Before becoming a supervisor, Maya might have offered an opinion and left the decision to someone else. Now the calendar is hers to manage, and both employees are waiting for her answer.
Her first impulse is to approve Elena’s request because it arrived first. That feels objective, and it would be easy to explain. Then she remembers Jordan’s past flexibility. If she uses first come, first served, does that make Jordan’s contributions irrelevant? If she favors Jordan, is she changing the rules after seeing who made the requests?
Maya considers asking each employee to explain why the day matters. Perhaps the person with the more compelling reason should get it. But she hesitates. She does not want the team to think time off depends on whose private life makes the strongest case to a supervisor.
This is a scheduling problem, but it is also a leadership problem. Maya must decide what matters, find out what she needs to know, make a choice within her authority, and explain it without turning either employee’s personal circumstances into team business.
She cannot guarantee that both people will like the result. She can give both a process they have reason to respect.
When requests compete for something limited, an outcome can be disappointing without being unfair. One employee may receive the preferred day off while another must change plans. One person may attend a training course while a colleague waits. A team may need to share equipment that everyone would prefer to have available all the time.
The test is not whether disappointment disappears. It is whether the decision was made for reasons relevant to the choice, with reasonable attention to the people affected.
A fair process generally has several recognizable features. The supervisor understands the decision before making it. The criteria fit the situation and are applied consistently. People have a reasonable chance to provide relevant information. The supervisor considers constraints rather than treating assumptions as facts. The explanation matches the actual reasoning, and a meaningful mistake can be revisited.
Those features do not produce a perfect answer every time. People can reasonably disagree about how much weight a factor deserves, and a decision can be procedurally sound yet still cause hardship. Fairness requires attention to both the process and its effects, even when a supervisor cannot remove every burden.
It also requires more than treating every request as though it were identical. Suppose two people ask for the same day off, but one request falls within an established approval process while the other concerns a situation that an applicable policy handles separately. The difference may matter. Maya should check the relevant process and seek guidance if needed, rather than either ignoring the distinction or improvising a new rule around it.
Consistency means using the same relevant standards in comparable situations. It does not mean refusing to recognize a meaningful difference.
A request for a preferred shift can sound routine. The employee asks, the supervisor checks the schedule, and someone receives an answer. Yet even a small decision can carry a larger message about how the team works.
Employees may be watching to see whether the supervisor remembers previous commitments, whether a vocal colleague gets more attention than a quiet one, or whether opportunities seem to circulate among the same few people. They may wonder whether a decision was made before they had a chance to speak.
As a new supervisor, you may also be navigating relationships that have recently changed. Coworkers who once shared frustrations with you may now bring requests to you. You may know details about their lives that have nothing to do with the decision. You may feel pressure to demonstrate that you are still approachable, or to prove your authority by making a quick call.
Neither impulse is a dependable guide. Being approachable does not require saying yes, and exercising authority does not require deciding without input. Your role is to make the best-supported choice available within the limits of the situation.
The stakes differ from request to request. A minor change to a shared calendar does not call for the same examination as a decision that affects access to important training. Still, even a brief decision benefits from a clear reason. The explanation can be proportionate to the choice.
A useful question is: If the people affected understood how I reached this decision, would the reasoning make sense even to someone who disagreed with it?
That question does not mean every employee is entitled to every detail you considered. Privacy, confidentiality, and organizational rules may limit what you can share. It means the part you can explain should be truthful, relevant, and consistent with what you actually did.
Maya’s first challenge is to define the scheduling decision before comparing Elena and Jordan.
She needs to know exactly which shift is affected, what coverage is required, and whether another workable arrangement exists. She also needs to confirm that she has authority to approve the requests and check whether a…