Clarity draft

What, So What, Now What.

Clarity means the resident never has to guess. Not what a notification meant. Not where their package is. Not why the elevator is offline. Not what happens next.

The principle

Every message from the building answers three questions: What happened? What does it mean for you? What should you do? A message that fails any of these three creates confusion, not communication.

Clarity is not about volume. A building that sends fifteen notifications a day has not achieved clarity — it has achieved noise. Clarity is about precision: the right information, to the right person, at the right time, in language they do not need to decode.

Across the six domains

Access × Clarity — when entry fails, the resident knows why and what to do. No silent denials. No ambiguous error states. The reason is communicated immediately at the point of failure.

Deliveries × Clarity — the resident knows what arrived, when, and where it is. Every status change in the item's lifecycle is communicated. No item sits in the building without the resident knowing.

Spaces × Clarity — the resident knows what is available, what the rules are, and what happens if conditions change. Closures and policy changes are communicated with adequate lead time.

Support × Clarity — the resident knows the status of their request without asking. Every state change — received, in progress, resolved — is communicated. The resident is never left wondering whether anyone is working on their problem.

Lifecycle × Clarity — every charge is explained, every document is accessible, and every deadline is communicated. The resident never wonders what they owe, what applies to them, or what happens next.

Environment × Clarity — the building communicates infrastructure events — outages, maintenance, environmental changes — before or as they occur. The resident understands what is happening to the building around them.

Why it depends on Reliability

Clarity requires something to be clear about. If the underlying system does not work reliably — if requests are lost, deliveries unrecorded, entries intermittent — then no amount of communication can compensate. You cannot clearly explain the status of something the system has no record of.

Clarity sits at the usability layer, one level above the foundation. It assumes the building works. Then it makes sure the resident knows what is happening.