Aotearoa · interval craft

Design the pause so the return feels obvious

We work with the idea that small breaks, named clearly, make heavy calendars easier to read. This is not a story about your health; it is a set of team-facing habits: how a room closes a meeting, how a list stays short, and how consent and privacy stay visible when you write to us from overseas.

Explore break patterns Clarity and attention
3 layout tiles for sorting breaks in workshops
~7 content refreshes to clarity per quarter, typical
1 Wellington address for in-person by appointment
4 policy layers: cookie, privacy, terms, return

These principles sit under every public page. They are written so that compliance, rhythm, and modest documentation reinforce each other instead of trading off.

Data care first

Forms, logs, and consent take a careful view of the GDPR, and we reference Dutch DPA material when a client wants an external anchor. Nothing here is legal advice; it is how we like to work.

Intervals as design

Breaks are not prizes; they are structural gaps in the calendar. The label matters more than the app that records it, because tools change and words stay in minutes.

Group tempo

When two people both guard the same open window, the week stops oscillating. We describe the choreography, not who should feel guilty about their pace.

Plain documents

We would rather a dated paragraph in a log than a glossy promise. Auditors and future you both benefit from boring sentences.

Return curves

After a break, a one-line re-entry plan reduces thrash. The line names the next block of work, not a personality trait in the room.

Border-aware

When your team spans time zones, we think about which privacy rules attach to the mailbox you use, not only where the server sits on a map.

Abstract illustration of light through a window

Let the last meeting end with a visible hand-off

When a call finishes, a physical cue you can all see—laptop half closed, a chair rolled back, a different playlist, the lights raised slightly—gives the group a line to walk across before the next context loads. The pattern is borrowed from different studios; we are not saying it is universal, only that teams who tried it found the transition easier to describe in retros.

Art direction here is deliberately lightweight: a single brand palette means fewer bytes on mobile networks, and the illustration stays at arm’s length from any idea of “wellness” as a product category.

SVG, fixed dimensions, and descriptive alternative text keep the page honest for assistive technology.

Five beats we draw on a whiteboard before we trust software

Put the number of minutes in one place the whole team checks.

Agree a colour or sound for “we are in the hush”.

Re-enter with one sentence: what the next block is for.

Review once a month; change a single variable only.

Archive a short note in the run log, same format every time.

Geometric blocks suggesting balance and intervals

Blocks, not a ladder of notifications

We borrow masonry language on purpose: weight below, air above, a joint where the next block can slide in without wobble. A chain of calendar alarms, by contrast, trains people to ignore soft pings, because the number of pings does not line up with the number of real decisions the day contains.

If you are mapping an increment, bring the constraints, not a promise of outcome. A slower cadence can still miss a market window; the claim we defend is that the meeting of minds about time becomes less noisy, not that velocity increases for every crew.

Ask us to look at a season with you
Pauses that stay legible in the calendar outlast the app that nudged them. Name the break for the team, not the scoreboard.

Next increment, calmer debriefs

Whether you are shipping a release or a policy, interval craft keeps the room from running hot on opinion alone. Send us a note with the shape of the calendar and the time zones in play, and we will suggest a pattern boring enough to survive the next tool migration.

Open the contact form

Walk-in, by plan

We keep one telephone number in the footer of every page so you never hunt for a different line. In-person time at 233–237 Lambton Quay is by appointment; email often arrives first, especially if you need a person to join from Europe or the Pacific on the same week.

Information practices on this static site are described in the legal pages, which draw on New Zealand’s Privacy Act, the GDPR where it applies, and the Dutch reading of layered consent for cookies. None of that replaces your own counsel, but it should read clearly enough for a first review.

233–237 Lambton Quay, Wellington Central, Wellington 6011, New Zealand

We avoid collecting what we do not need; contact threads stay inside the policy retention windows unless law says otherwise.