Fair Team Meeting Scheduling
Fair Team Meeting Scheduling is a one-hour workshop from the Atlassian Team Playbook in which a distributed team writes its own rules for when meetings may and may not be scheduled. The team maps where time zones and personal boundaries collide, then agrees how the cost of awkward hours is shared instead of always landing on the same people. It ends with owned commitments and a date to revisit them.
Facilitation script
- 1
Welcome the group, restate the purpose from the pre-work note and agree the ground rules. Ask whether anyone needs a rule added before starting.
5 min - 2
Silent writing on the board: one note per pain point, clash or idea for sharing off-hours meetings. No talking, cameras optional.
10 min - 3
Read the notes aloud, cluster them and discuss the current state. Ask who carries the awkward slots today and which meetings cause most of the trouble.
10 min - 4
Draft the norms section by section: calendar visibility, off-hours meetings and rotation, handling unavoidable conflicts, and how success will be judged. Check each draft norm with the people it costs the most.
20 min - 5
Build the action plan: who changes which recurring meeting, who updates calendars and team documentation, and by when.
10 min - 6
Close by reading the norms back, confirming the review trigger and thanking people for naming their boundaries.
5 min
Tips
Bring the data into the room: a simple grid of each person's working hours in one reference time zone makes the imbalance visible without anyone having to complain.
Ask the people in the majority time zone to speak last during the discussion, because they usually experience the current schedule as normal.
Write each norm so it can be checked in a calendar, such as a named rotation or a protected window, rather than as a statement of good intent.
Common pitfalls
Running the workshop itself at a time that suits only the majority time zone, which tells the rest of the team how seriously the topic is taken before a word is said
Agreeing principles such as 'be mindful of time zones' without a concrete rotation or protected window, so nothing changes in the calendar the following week
Letting the discussion turn into a debate about whose personal commitments are legitimate; people then stop disclosing boundaries and the norms are built on incomplete information
Leaving the recurring meetings untouched after the session, so the old invitations quietly overrule the new norms
Never revisiting the norms when the team changes, which leaves a newcomer in a new time zone bound by an agreement they had no part in
Variations
For a team of more than ten, collect the sticky notes asynchronously beforehand and use the live hour for norms and the action plan only. A team in one time zone can run the same agenda around caregiving hours, part-time schedules and focus time instead of time zones. The resulting norms can be added as a section of an existing working agreement rather than kept as a separate document.
Where it fits
When to use it
The same people join the 7 am or 9 pm call every week and have started to mention it, or have stopped attending
A new team member or office in a different time zone has just joined and the existing recurring meetings were set before they arrived
Meetings are regularly booked over school runs, religious observance, public holidays in other countries or part-time days because nobody can see those boundaries
The team is forming and wants to settle scheduling rules before recurring meetings harden into habit
People decline or skip meetings silently and decisions are being made without them
When not to use it
The team needs agreements about communication, decision-making and conflict as a whole; run Working Agreements and treat scheduling as one section of it
The real problem is too many meetings rather than badly timed ones; first cut and redesign them, for example with a Silent Meeting or Live Doc Meeting format
The meeting times are set by a client or another department and the team has no authority to move them; take the map of pain points to whoever owns the calendar instead
Only one person is affected and the fix is obvious; a direct conversation and a calendar change are faster than a workshop
Related methods
Frequently asked questions
What is Fair Team Meeting Scheduling?▾
It is a workshop from the Atlassian Team Playbook in which a distributed team agrees its own rules for when meetings can be scheduled. The team surfaces time-zone pain points and personal boundaries, writes norms for calendars and off-hours meetings, and assigns owners for the changes.
How long does the workshop take?▾
About 60 minutes for the session, plus roughly five minutes to schedule it and send the pre-work. The longest block, around 20 minutes, goes to drafting the norms.
How many people should take part?▾
The play is designed for one team of roughly three to ten people. Everyone affected by the schedule should be present, because norms agreed without the people in the minority time zones tend to repeat the existing imbalance.
What kind of norms come out of it?▾
Typical results are a rotation for meetings that fall outside someone's working hours, an agreed overlap window in which shared meetings are booked, a rule that working hours and blocked time are visible in calendars, and a default for what happens when someone cannot attend, such as a recording and written notes.
How is this different from a working agreement?▾
A working agreement covers how the team collaborates in general. Fair Team Meeting Scheduling deals only with meeting times and availability, which makes it short enough to rerun whenever the team's membership or time zones change. Many teams file the result as one section of their working agreement.
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Fair Team Meeting Scheduling into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Atlassian Team Playbook.