You ask the team in standup if anyone is overloaded. Nobody says yes. Later a deadline slips, and the person who owned it says they saw it coming for weeks. This guide is for team leads who want to hear about workload while there’s still time to move something. It covers why the topic stays quiet, what a tested weekly check-in looked like, a six-step format built on two words, Enough and Rest, and ten questions to use with or without the deck.
Why “Is anyone overloaded?” gets silence
A yes to that question costs the person who says it. In interviews with 40 employees, Milliken, Morrison and Hewlin found that most had been concerned about an issue at work and not raised it with a supervisor. The reason mentioned most often was the fear of being seen or labeled negatively, and of damaging relationships that mattered to them (Milliken et al. 2003). Saying “I can’t take this on” can sound, to the speaker, like “I’m not good enough for this job.”
The team’s habits add to it. In a nine-month field study of a software engineering team, Leslie Perlow described a “time famine”: a feeling of having too much to do and not enough time to do it. The engineers kept interrupting each other, and a crisis mentality and rewards for individual heroics kept the pattern going (Perlow 1999). On a team like that, the person working late can look committed, and the person asking for less can look weak. A single open question in standup doesn’t change that. A fixed format with its own slot can.
What a weekly check-in did at one consulting firm
Leslie Perlow and Jessica Porter ran experiments with consulting teams at the Boston Consulting Group over four years. Each person had a scheduled day or night off every week, and each team held a weekly check-in about how it was going (Perlow and Porter 2009). The check-in had three parts:
- Calendar: did everyone take their time off last week, and can they take it next week.
- Pulse check: each person rated and talked about four questions, including “Is the current operating model sustainable for you throughout the project?”
- Concerns: items people had sent in advance, without their names, about anything that made them uncomfortable.
The authors report that the check-ins led to talks with the whole team about priorities, expectations and problems. In teams outside the experiment, consultants usually started talking about problems only once they were already overstressed. One project manager estimated that the team now spent about 30% of meeting time on how the work was done, where a typical meeting spent about 5%. The authors also give a reason the format worked: the talk started on a narrow, concrete topic, so a person could raise a small issue, see how it landed, and then decide whether to say more.
That last point is the design rule for the format below. Start narrow, make the first answer small, and let people go further only if they choose.
The format: six steps
The steps below fit a weekly team meeting. Run them at the start, before the agenda, so the answers can change what the meeting covers.
- Give it a fixed slot. Put it on the same meeting every week, with a fixed time box. A check-in that runs only when things look bad tells the team that things look bad.
- Agree on passing. The Thesis rules include this line: “Before you start, agree together how passing works.” Say out loud that anyone can pass with no reason given, and that a pass gets no follow-up.
- Run the Enough round. Each person says where their week sits against enough: under it, at it or over it. One sentence is a full answer. You go first, and you keep yours short.
- Run the Rest round. Each person names when they last stopped work with nothing pending, or when they plan to. This is the calendar part from the BCG check-ins in one question.
- Pick one thing that moves. If someone is over enough, the group names one task that moves, gets dropped or gets a later date. The decision is about the work, never about the person.
- Close on time. Thank people for their answers in one line and start the agenda. Anything longer goes to a one-on-one the same week.
Step 5 is the one that’s easy to skip. A check-in where people say “over” and nothing changes can teach them to say “at” next week. Perlow and Porter describe the same move in their calendar review: when someone hadn’t taken their time off, the team asked what was going wrong and how to fix it.
Two cards for the check-in
Enough and Rest are two of the 50 words in Thesis. Each card has an idea on one side and an everyday thing on the other, and the thing side gives a lighter way in for anyone who’d rather not talk about their own load that week.
Enough has Photograph on its back. On a team, Enough reads as capacity: how much work fits in a week, and what counts as done for this sprint. The word lets people describe their load without a number of hours or a list of tasks. The Photograph side works for a person who’d rather stay off workload today. They can describe a picture on their desk or their phone and still give a full answer.
Rest has Clock on its back. Rest at work can mean a lunch break away from the screen, a weekend with notifications off, or a project that’s finally off someone’s desk. The Clock side turns to time itself: a deadline, a time zone, the hour someone stops answering messages.
Balance has Watch on its back. It suits a monthly version of the check-in, when the team looks back over several weeks. Someone might say the month was out of balance in the first half and fine in the second. Someone else might take the watch and talk about how they track the day.
Questions for a workload conversation
The questions below work in the Enough and Rest rounds or on their own. Each one can take a one-sentence answer:
- Is this week under, at or over enough for you?
- What would make next week enough?
- What’s one task you’d hand off if you could?
- Which task is taking more time than anyone planned?
- When did you last stop work with nothing pending?
- When is your next stretch of time with no meetings?
- What does done look like for you this week?
- Which request came in this week that nobody planned for?
- What could the team stop doing without anyone noticing?
- What would make it easier to say no to a request?
Running it as a card round
With the deck or the online table, the round follows the Thesis rules. Draw a card, choose 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.” For a workload check-in, lay Enough and Rest face up instead of drawing, and let each person pick one. The others can ask one short question. The rule card gives three examples: What did that feel like? Who else was there? Has it always meant that to you?
Before your next team meeting, add one line to the invite: “We’ll start with a short workload check-in. Passing is fine.” Then write down one task you could move if someone says “over.” The words have their own pages: Enough, Rest and Balance. For openers on other topics, see check-in questions for team meetings. For more on running it at work, see Thesis for teams and classes. For the studies behind the deck, see the research page. See the rules and the box.