// Performance · aggregate view

Small numbers, wide context

We keep tallies at the level of a floor or a zone, not a scoreboard for individuals. A steady line on a simple readout can mean the route to water is working; a dip after a public holiday is often a calendar effect before it is anything else. This page walks through the shapes we use in pilots, the comparisons we will not run, and the handoff we leave in your systems when the pilot pauses or ends.

What a week-one and week-two chart is for

When a second cooler lands between two dense desk banks, you often see a different shape before and after, but only if the scale on the readout is the same each week. We align weeks on the calendar, not on “whenever someone remembered to look,” and we note weather and holidays in the margin of the one-page readout you keep. The bars below are illustrations only; your hardware might record differently, and we never paste live client data into a public page.

If the shape is jagged, we ask about meeting load and door closures before we ask about anything personal. A glass box that is always full of back-to-backs can starve a nearby station without anyone “underperforming.” The fix is often furniture or schedule visibility, not a new poster.

Illustrative evenness (bars only)

Smoother does not always mean “better for every org”; it means fewer spikes that point to a structural choke.

Abstract arc suggesting gradual change over a work week

KPIs we are comfortable sharing in a room

The three cards below are labels we use in slide decks, not live calculations from your site visit. The spinning ring is a visual accent. Real math sits in a workbook you control, with a column for “weird week notes” that everyone agrees to use honestly.

Zone A

refill evenness by half-day

+1

second station, mid pilot

14

day trial window, typical

A simple comparison: what we do versus what we do not

The table is a conversation aid for steering committees. It is not a contract, and the “do not” column is there so nobody mistakes an aggregate pilot for a people analytics project.

Topic In scope for us Out of scope for us
Data grain Zone or floor totals over a time window you pick Per-person or per-desk export for HR
Reminders Shared posters and calendared facility checks Apps that ping individuals about their choices
What we sign One-page readout, filter dates, and vendor contacts Promises about specific outcomes in your org

What we will not do, said twice on purpose

We do not tie any refill tally to performance reviews, stack ranks, or “wellness” leaderboards. We do not use language in apps or posters that shames a person for their private choices, and we do not describe water habits as a substitute for advice that belongs with licensed professionals in regulated settings. If a vendor asks for that pairing, we walk away or help you find a different product lane.

Handoff is part of the work

When a pilot pauses, you should still have part numbers, the next filter month, and a short note on which door often stayed locked during a heat wave. We format that in a file your facilities lead can file next to the HVAC log, not in a system that only our team can read. If you need a second language version for a regional office, we can often mirror the layout, not auto-translate the jokes.

Where to go from here

The Hydration page has the softer side: prompts, carafes, and compost. The Contact form is the right place for a floor plate PDF, a list of what you have tried, and a sense of the quarter when you need a decision. We try to keep first replies short on purpose, with an explicit next step, even when the honest answer is “we need a second look from your GC before we can size anything.”