A team can finish a Thursday with every meeting attended and still be unable to name the piece of work that moved. The calendar was full. The inbox was cleared. The note a customer or a colleague was waiting on is where they left it on Monday. A session sold into that week will feel like a success if it only teaches people to move faster inside the same interruptions.
The booking that earns its cost changes the pattern of those interruptions. It leaves a manager with a way to see, a fortnight later, whether the work got clearer or merely quicker. A completion row will record that people sat through the tips. It will not show whether a shorter email was shorter because it was better, or because the person had to get it off the desk before the next ping.
The speed that hides the cost
Gloria Mark, an informatics researcher at the University of California, Irvine, ran a laboratory study of this compensation with Daniela Gudith and Ulrich Klocke of Humboldt University Berlin. Their paper, The cost of interrupted work, was presented at the CHI conference in 2008. Forty-eight people answered a simulated human resources inbox. They were told to be quick, correct and polite, and they had a fact sheet to work from. The point of reading it, if you are about to pay for a workshop, is the split between a faster finish and a worse experience.
Each person worked three blocks, with the order rotated so the sequence itself was not the result. One block had no interruptions. One was interrupted with questions in the same context as the inbox. One was interrupted with questions on another topic. Half the people took those questions by telephone and half by instant message. The interruption arrived every two minutes, a rate the authors set from their earlier observations of office work and from a pilot. They subtracted the time spent on the interruption, so a long call could not inflate the score.
People took longest when nobody interrupted them. The mean for that block was 22.77 minutes. Same-context interruptions came in at 20.31 minutes, and different-context interruptions at 20.60. The gap between the two kinds of interruption was not significant, and neither was the gap between telephone and instant message. Errors did not rise. A politeness score, built from greetings and from words such as please and thank you, did not fall. The messages got shorter. Uninterrupted emails averaged 31.49 words. Same-context emails averaged 29.17.
What the hour is for
The authors measured the strain on a scale from 1 to 20. Stress sat at 6.92 with no interruptions, at 9.46 when the interruption shared the task, and at 9.13 when it did not. Frustration, time pressure, effort and mental workload moved with it. After 20 minutes of interrupted work, people reported significantly higher stress, frustration, workload, effort and pressure. Mark and her colleagues read the speed as compensation. People who expect to be interrupted work faster and write less, so the clock looks kinder while the experience gets worse. They are plain that a short laboratory task cannot say whether that strain would ease or keep climbing across a real month. Eighty-one percent were German university students, with a mean age of 26.
An interruption about the work in front of you did not spare the person. In this experiment it carried the same time pattern as an interruption about something else, and both raised the strain. A proposal that calls some pings harmless because they are on-topic is offering a distinction the study did not find. Changing the channel did not spare them either. The pattern held when the question moved from a phone to a message window.
What a tips session cannot see
A proposal can teach a morning ritual, a cleaner list and a promise to touch each message once, and never ask what is allowed to break the work. If you score that day by tasks finished, you will congratulate the compensation. The person got faster. The note got thinner. The strain went up. A smile sheet does not ask which of those three you bought.
Ask what the people in the room will stop, and who has the authority to stop it. A personal pledge to check mail less often dies the hour a senior person expects an instant answer. In the study the interruption was a supervisor with a question. In a company the supervisor is often the meeting, the channel and the person who can put work on a plate without asking. A room that never includes that person will train everyone else to absorb the cost more politely.
The useful hour is slower than a tips reel, because the team has to name a real interruption and decide what happens to it. A status meeting can become a note. A question in the middle of a draft can wait until the draft has a reader. Those sentences are awkward when the person who calls the meeting can hear them. That awkwardness is the practice. A facilitator who smooths it away, so the hour stays pleasant, has removed the part that would show up on Monday.
Habits you can actually keep
A provider will often bring a tidy exercise about a fictional week. The inbox is invented. The meetings are invented. Nobody in the room has to disappoint a real senior person. That exercise can teach the vocabulary of focus. It cannot teach the rule, because the rule only bites when the interruption has a name and a rank. Ask whose week will be on the table. If the answer is a sample, you are rehearsing a story. The study used a simulated inbox because it was a laboratory. The day you are buying is not a laboratory. The cost you need to see shows up on work the team already owes.
Put the reviewer in the session for the part where the rules are read back. A reviewer who arrives a fortnight later, and meets the rules for the first time, will score the work against the old expectations. The tally will look like a failure of discipline when it is a failure of agreement. Name that person in the proposal, and have them hear the delay accepted out loud.
What to count before the day
Before you book, pick two samples from the week the team just lived. One is a piece of work that was interrupted and still went out: an email, a brief, a decision note. One is a piece that stalled because the interruptions won. For each, write what the interruption was, who caused it, how long the work sat open, and whether the version that left was thinner than the author would have stood behind on a quiet morning. You need a baseline a reviewer can hold next to the work a fortnight later. Without it, the debrief becomes a debate about how busy everyone felt.
On the day, use those samples. Look at whether the team can name the interruption without blaming a tool, and whether they can change the rule that produced it. A rule is a sentence a manager can repeat. This kind of question waits. This meeting becomes a note. This stretch of the day stays closed unless the work is actually stuck. If the only output is a list of personal hacks, the system that created the interruptions has not been touched. Change the exercise before you treat the day as finished.
What a fortnight should show
Two weeks later, do not rerun the tips and call the memory a result. Ask each person to bring one piece of work done since the session, with the interruptions still visible. The reviewer, named before you booked, marks three things. Did the agreed rule hold, or did the old ping win. Did the work go out at a standard the person will stand behind. Did they finish by rushing, or did the rush ease because the interruption had somewhere else to go. A team that can show those three on a new task has changed its week. A team that can only describe the session has not.
Keep a short tally. How many of the sampled tasks kept the rule. How many went out thinner than the author wanted. How many were interrupted by someone who had agreed to stop. If the tally is worse than the baseline, change the rule rather than book a second tour of the same tips. If the work is faster and the standard is worse, you have the laboratory pattern in your own building. The next conversation is about what you are willing to protect, not about another ritual for the morning.
The rule a senior person must keep
Name the team, the two samples and the reviewer before you book. Name one rule that will inconvenience a senior person, and get that person to say it back. If every rule in the proposal falls on the people who already answer fastest, the day will teach coping. The students in the lab were already good at coping. They got quicker, they wrote less, and they felt worse. An organisation does not need a quicker version of that week.
Read the rules aloud before anyone leaves, including the ones that slow a response down. A page written the next morning, by the person who liked the tips, will drift back toward individual heroics. If the group cannot hear a senior person accept a delay, the session is not finished. The delay is the point. It is how the work gets thick enough to send.
Collective Campus is building high-performance culture and teams for the AI world. The productivity workshop is for a team that can already point at the interruptions in its week, and wants a rhythm a reviewer can still see a fortnight later. Why a notes pack fades is in the notes nobody used. A calendar full of ceremonies that do not move the work is in agile without the theatre. Habits that have to survive the first busy week are in turning bad habits into good ones.
What to bring
Bring the two samples and the name of the person whose meetings and messages create the interruptions. If that person will not be in the room, and will not read the rules afterwards, you do not have a decision to practise. You have a lecture waiting for a calendar slot.
