Every team has duties that appear in no job description. Someone books the room, writes the notes, answers the client who emails on Sunday, and reminds everyone about the release freeze. When that person goes on vacation, the team finds out how much they carried. This guide shows a team lead how to run one conversation that lists those duties, hears what each person feels they owe the team, and ends with a name next to each one. It fits one team meeting and works with a word written on a sticky note.
Why shared duties drift to one person
A duty that belongs to everyone can end up with whoever notices first. Steven Karau and Kipling Williams reviewed 78 studies of social loafing, the tendency to put in less effort on a shared task than on a solo one. The effect held across tasks and populations. Among the moderators with the strongest influence were whether individual effort could be evaluated, what people expected from their co-workers, how meaningful the task was, and culture (Karau and Williams 1993). The studies measured effort, not who ends up holding a chore. Still, the scene above can play out on a team: a shared task with no owner gets picked up by one person, and it becomes theirs without anyone deciding so.
The person who picked it up may never raise it in a status meeting. They may describe it as part of the job, or say they owe it to the team. That’s why a conversation about duty can reach what a task audit misses. A task list shows what gets done. Talk about duty shows why someone keeps doing it, and what they’d hand over if they could.
Why the lead speaks first
A junior colleague may stay quiet about who carries what, because the answer could point at someone senior. Ingrid Nembhard and Amy Edmondson studied this in 23 neonatal intensive care units. They found that leader inclusiveness, meaning a leader’s words and actions that invite and value others’ contributions, predicted psychological safety. They also found that professional status shaped how strongly inclusiveness and psychological safety were linked (Nembhard and Edmondson 2006). It was a survey of hospital teams, so it’s a lead for an office team and not a promise. It still suggests one move: the lead names a duty they’ve dropped or handed off before asking anyone else.
A duty conversation in five steps
The session below fits a regular team meeting with one person running it.
- Say what the session is for. One sentence is enough: “We’re going to list the work that keeps this team running and isn’t in anyone’s role, and decide who holds it.” Say that the goal is a list, and that nobody’s past effort is being graded. If some duties are fixed by contract or on-call rules, say so now.
- List the unwritten duties. Everyone writes three duties on sticky notes, one per note, without names. Prompts help: what happens before every release, who people message when something breaks, what gets done after hours. Read the notes out and group the repeats. A duty that shows up on several notes is a good place to start.
- Play one round with the word. Put the word Duty on the table. Each person says a few sentences about it from any angle: a duty they took on as a kid, a team where they felt they owed something, a duty they dropped. The lead goes first and keeps it to two or three sentences. This round is where people explain why they keep certain work.
- Put a name next to each duty. Go through the grouped notes. For each one, the team writes who holds it now. Then the holder says whether to keep it, share it or hand it over. A duty with no name gets a name or gets dropped on purpose.
- Set a date to check. Write the list where the team can see it, next to the sprint board or in the team channel. Pick a date three or four weeks out to see whether the new names stuck.
When duty and boundaries collide
Some duties keep running because someone feels they can’t say no. The colleague who answers Sunday emails may do it out of loyalty to a client, or because a former manager praised it once. The conversation lets that person say what the duty costs them without asking permission to stop. If a duty turns out to belong to nobody, the team can decide it doesn’t need doing. For the other half of this conversation, see boundaries at work.
Three cards that fit the round
Each Thesis card has an idea on one side and an everyday thing on the other. For a team, the thing side gives anyone a way in that stays away from private life.
Duty has Ticket on its back. On a team, Duty can bring up early lessons about obligation: walking a younger sibling to school, a first job where closing the shop was yours. The Ticket side suits a work round too. Someone can talk about a support ticket they kept because nobody else picked it up, or a train ticket for a trip they took out of duty.
Loyalty has Camera on its back. It opens the question of who someone feels a duty toward: the team, the client, a manager, a craft. Those answers can point in different directions, and hearing them helps a team see why two people hold the same task for different reasons. The Camera side gives a lighter way in, through a photo someone kept from a team they once belonged to.
Work has Stone on its back. It lets people talk about the heavy, steady part of a job, the part that may not show up in a review. Someone might take the Stone side and describe something they carried for a long time before putting it down.
Questions for the round
The questions below can replace the card round or follow it. Each one works at any depth:
- What’s a duty you took on as a kid that you still remember?
- What do you do on this team that isn’t in your role?
- What duty would you hand over first if you could?
- Who taught you what it means to owe something to a team?
- When does a duty start to feel like a favor?
- What’s a duty you dropped, and what happened next?
- What would break first if you were away for two weeks?
- What duty do you like having?
Running it as a card round
With the deck or the online table, each turn follows the same steps. Draw a card, pick the idea or the thing, roll the die and look at the word from that side. The die has six plain words: MEMORIES · BODY · PEOPLE · VALUES · CHILDHOOD · FUTURE. The only instruction is “Look at the word from that side.” The rules say: “Say as much or as little as you like. The others ask, gently.” The others can ask one short question, such as What did that feel like? Who else was there? Has it always meant that to you?
Two rule lines matter at work. “Before you start, decide together how passing works.” On a team, the lead can propose that a pass costs nothing and needs no reason, and the group agrees. “What is said at the table stays there.” Agree before the first turn that the round stays in the room, and only the duty list goes on the board.
Before your next team meeting, write three unwritten duties of your own on sticky notes and bring them as the first examples. The cards above have their own pages: Duty, Loyalty and Work. For more on running it at work, see Thesis for teams and classes. For the studies behind the deck, see the research. See the rules and the box.