How to Assign Tasks Fairly at Work with a Random Picker

Why fairness at work is hard

Every team has tasks nobody wants: taking minutes, covering the late shift, updating the shared spreadsheet, testing the boring edge cases, organising the leaving party. When a manager assigns them, people quietly track who got what. Over time, small imbalances turn into resentment, especially if the same reliable people keep getting landed with extra work. Volunteering doesn't fix it either: the same generous people step up while others hang back.

A random picker offers a neutral way to share certain types of work. It doesn't replace good management, but for the right tasks it removes the suspicion of favouritism and saves time.

What should be random

Chance works best for tasks that are roughly equal in effort, don't require specialist skills and simply need someone to do them. Good candidates include meeting roles (host, note-taker, timekeeper), rotating support or on-call duties within a qualified pool, code review or document review assignments, office chores such as restocking or plants, and choosing who presents at a weekly demo.

Tasks that depend on expertise, development goals or workload should be assigned deliberately. Randomly giving a complex client project to a new starter, or adding a big task to someone already overloaded, isn't fair just because a wheel chose it. A good rule is to use judgement to decide who is eligible, then chance to choose among eligible people.

Build an eligible pool

Before spinning, agree who's in the pool for each task. For on-call, that might be everyone trained on the system. For meeting notes, everyone who attends. Hide people who are on leave or temporarily unavailable rather than deleting them, so their history is preserved. Being explicit about eligibility prevents arguments later. "Why was I picked when I'm on holiday next week?" shouldn't happen if availability was checked.

Balance load over time

A single random pick is fair, but a series of picks can be lumpy. Someone might draw the minutes three times in a month. That's normal randomness, but it doesn't feel fair. Turn on Fair Rotation so people who haven't been picked recently have a better chance and recent picks have less. Add a cooldown for tasks people really dislike, such as a minimum of four weeks before anyone covers the weekend shift again.

For tasks with strict equality requirements, such as rotating holiday cover, use elimination over a full cycle: everyone takes one turn in random order before the cycle resets.

Be transparent

Run the spin where the team can see it, at the start of a meeting or on a shared screen. Explain the rules: who's eligible, whether Fair Rotation is on and how often the list resets. Visibility turns the wheel from "the manager's tool" into a shared team process. Many teams find that complaints drop sharply once people can see the method.

If someone asks why they've been picked, the history panel shows when each person was last selected. You can export it to a spreadsheet for longer-term review.

Keep a record

Records protect both the team and the manager. Export the history monthly or keep the saved wheel running across weeks so its history builds up. For duties that affect pay, such as overtime or on-call allowances, a clear record of how assignments were made is especially useful. If your organisation needs a formal audit trail, download receipts for important draws. They record the pool and the result with a fingerprint that shows nothing was changed later.

Respect availability and constraints

Random doesn't mean rigid. People have caring responsibilities, part-time schedules, religious observances, medical appointments and time-zone differences. Collect constraints in advance and build them into the pool. If a randomly assigned person has a genuine conflict, let them swap with a willing colleague rather than re-spinning, which can feel like gaming the system. Note the swap in the record.

For distributed teams, consider separate pools by time zone for tasks that must happen at a particular hour, such as live support. Fairness includes not making someone in Asia take notes at 3 a.m. for a meeting scheduled for Europe.

Combine chance with recognition

Some teams pair the wheel with a small recognition system. Anyone who takes on an unpopular random task earns a point. Points can be used to skip a future spin or to get first pick of desirable work like a conference place. This acknowledges that some tasks cost more than others and gives people a sense of control. Keep the rules simple and visible.

Desirable tasks deserve fairness too

Fairness isn't only about chores. Interesting opportunities, such as presenting to leadership, attending an event or leading a pilot project, are often given to the same visible people. Where several team members are equally qualified, a random draw from the eligible pool can open opportunities to people who are quieter or newer. Pair it with a clear statement of the criteria for eligibility so it doesn't look arbitrary.

Introducing a random picker to your team

Start with a low-stakes task, such as choosing the stand-up order or the weekly note-taker. Explain why you're trying it: to share work fairly and save time on decisions. Ask for feedback after a month. Most teams quickly come to like the neutrality. If people raise concerns, take them seriously; they often point to tasks that shouldn't be random or to eligibility rules that need adjusting.

Common pitfalls

Using chance for tasks that need skills. Forgetting to hide people on leave. Re-spinning when the manager dislikes the result, which undermines the whole idea. Running spins in private. Never resetting cycles, so people who joined later feel penalised. Each of these is avoidable with a little planning and openness.

Talking about it with your team

Introduce the change in a team meeting rather than by email. Explain the problem you're solving, show the wheel and its settings, and ask the team which tasks they think should and shouldn't be random. People support systems they've helped design. Agree a review date, such as after six weeks, and stick to it. If the team asks for changes, like a longer cooldown or a different pool, make them openly and note the date so the history makes sense later.

A sample setup

Create one saved wheel per recurring task: minutes, demo presenter and on-call. Add the eligible people to each. Turn on Fair Rotation and a cooldown for on-call. Spin at the Monday team meeting on a shared screen. Allow swaps, and log them in the meeting notes. Export the history at the end of each month and review it at a retrospective once a quarter. With this simple system, work is shared visibly and fairly, and decisions that used to take a conversation take a few seconds.

Try it now

Put these ideas into practice with the Task Assignment Wheel, Meeting Host Picker, Balanced Team Rotations, or open the main spin the wheel tool.