Practical guide
Shared Pomodoro timer: a practical group protocol
A shared timer succeeds when the group agrees on behavior before the clock starts.
The short answer
Name one host, one outcome per participant, one emergency channel, and a finish time. Keep the work interval quiet and use the break for short coordination.
Make four agreements
Decide who controls the clock, what can interrupt it, whether breaks are social, and how many cycles you will run. These choices prevent the timer itself from becoming a source of negotiation.
- 1. Name the host.
- 2. State individual deliverables.
- 3. Mute ordinary channels.
- 4. Stop at the agreed time.
Pick a duration by task
Use 25 minutes when starting is difficult or work is fragmented. Try 40 to 50 minutes for writing and code once the workspace is ready. A duration is useful when it fits a meaningful unit of work, not because it is universally optimal.
Handle interruptions explicitly
Put non-urgent requests on an after-block list. If the group must stop, the host pauses for everyone and says why. Repeated exceptions usually indicate that the chosen time or task is unsuitable.
Close the session
Each person reports the result, obstacle, and next action in one minute. Evaluate output, interruption count, and remaining energy rather than rewarding the largest number of cycles.
Research cited
These sources support only the specific mechanisms discussed above. Their methods, populations, and limits do not establish that one timer routine works for everyone.