On this page we model each break as a miniature project: a duration, a trigger, a way to come back, and a line in the shared log. We do not describe anyone’s private health; the stories are anonymised shapes we have seen in education, logistics, and software teams. If you need a registered health professional, that sits outside this informational site.
These sit between dense tasks when the next action is already known but the hands and eyes need a different surface. People often pair them with water, a stretch that does not require a mat, or a look out a real window instead of a second screen. The benefit we document is procedural: the calendar shows a tiny gap that used to collapse into the next meeting. We do not measure heart rate or stress chemistry; that is outside this public copy.
Here the medium changes: you leave the building, you walk without a destination, or you talk to a colleague without an agenda line. The goal is distance from the problem statement, not from your team. We keep examples anonymous so you can borrow the shape without importing someone else’s story into your stand-up.
Some organisations can block a half-day to replan a quarter or to clean a backlog column. We only care, in this document, how the calendar line is labelled and who approved it; we do not ask what people do in their private time after they have left the office network. HR and policy teams have their own vocabulary; we stay in the lane of “how the shared schedule looks.”
Parallel work can use a channel mute and a single wrap message at the end. The practice is the agreement, not the outcome: some days the code still fails, but the room does not feel like a notification fire. Friction often comes from unclear end times, so we recommend a visible clock or a shared alarm everyone can hear.
No. A whiteboard or a shared document is enough to start. Apps can help with reminders, but the label on the calendar is the contract your team sees most often.
Start with a pilot that includes their manager or a sponsor who can say no to late drops. A break policy that lives only in an email footer will not hold; the visible signal in the room matters more than the PDF.
Clarity pages talk about light, lists, and how meetings open. Breaks give the empty space those techniques need. Jump to Clarity for the companion ideas, then return here if you are still sorting calendar shapes.
Use the contact form with a work address if you act for a company. We answer in New Zealand business hours first, then line up async time if your message needs it.
We do not link any break length to a measurable outcome in your body or mind. We do not name syndromes, suggest treatments, or use fear to sell a schedule. The value proposition we stand behind is narrower: clearer hand-offs between pieces of work, and a calendar that matches what the team said it would do.
When you are ready to map a rhythm to policy text, send a note from Lambton Quay’s digital front door with your sector, time zones, and the tools you already pay for—so we do not invent process you cannot keep.