Over-fine permission granularity adds friction to daily life

What it is

Technically, smart homes can enforce extremely fine permissions: per device, per action, per time window. But every fine-grained gate is a potential stop on a daily path — turning on the heating requires approval, entering the guest room means re-requesting access. Over-fine access control turns the home into an office: office permission models are designed for low-trust, high-turnover, role-separated organizations, while a home is high-trust, low-turnover, shared life — importing that model presses governance cost onto every single operation.

The friction is not the permission system failing; it is the permission system working correctly — every properly enforced stop is an interruption of life together.

Why it happens

The account of fine-grained friction compounds by frequency. A two-second confirmation met fifty times a day is an hour of compliance per month — arithmetic invisible at design time (per-instance) that surfaces only in long use (cumulative). Permission systems are evaluated per stop; users live the running total; the two timescales don't meet.

Heavier still is the social cost: requesting permission from an intimate is a face-threatening act. The first request is process; the tenth is an accusation — "what, I can't turn on a light in my own home?". So households route around formal permissions: borrowing the phone verbally, sharing the PIN, pressing physically. The informal institution hollows out the formal one, the system perceives none of it, and still records "permission system operating normally" in its own ledger.

The deep reason: the household already runs on a social-norm governance system (who spoils whom, what must not be touched — tacit understandings long predate the device). Fine-grained permissions add a technical governance layer on top. The two layers must stay in sync — when the social understanding shifts, the technical configuration must follow — and sync labour has no owner, so it falls into arrears by default.

Studying it

• Preference surveys: access-control preference questionnaires find stable patterns — coarse sharing for low-risk devices (lights, sockets, TV), tolerance for fine granularity only for high-risk ones (locks, cameras, purchases). Risk-tiered granularity preferences replicate across studies.
• Deployment telemetry: in trial deployments, log denied attempts with frequency and context — a steady nonzero denial rate means the permission model is fighting daily life; the device classes where events cluster are where granularity is mis-set.
• Experience sampling: trigger a short probe at the moment of a permission stop (what just happened, how did you resolve it) to capture workarounds — direct evidence of the formal system being bypassed, which retrospective interviews smooth over with rationalized narratives.

One methodological caution: permission requests in lab scenarios carry no real relationship load — participants follow rules politely. The social dimension of friction (the awkwardness of the tenth request) appears only in real household deployments; this is the single most decisive ecological-validity requirement for the topic.

Where it stops holding

• Granularity needs scale with device risk. Locks, cameras, and payment devices justify fine control — friction is offset by security benefit. Reading "too fine adds friction" as "don't build permissions" is wrong: granularity follows risk, not a uniform coarse setting.
• Relationship type shifts the friction threshold. Between flatmates, formal permissions are often welcome (clear boundaries prevent disputes); between close family the same gate reads as offence. One scheme, two opposite receptions.
• High-conflict households may need it most. When relations are tense, "the system won't allow it" spares the confrontation — a permission gate can buffer conflict. The friction claim is strongest in harmonious households and must be discounted in conflicted ones.

Applying it

• Tier default granularity by device risk: lighting and sockets default to whole-family sharing; locks, cameras, and purchases default to restricted, opened per need. Defaults absorb 90% of granularity decisions.
• Make common upgrades one-shot temporary grants: "allow today" rather than role changes — lowering social cost while keeping the boundary.
• After launch, audit high-frequency stop points: the top device/member pairs by denied events are where granularity is too fine — check each against intent (design error versus deliberate governance).
• How to check: weekly count of denied access events per household; approaching zero at launch then rebounding to a stable nonzero level means the default granularity fights the household's rhythm and needs recalibration.

Related

• Same group: Z4.07.1 Household members can hold unequal control over the same device · Z4.07.3 Over-coarse permissions give secondary members unexpected power · Z4.07.4 Permission changes need to notify affected members
• Nearby: Z6.01 Control conflicts · Z6.02 Permission layering
• Search terms: access control granularity · permission friction · household sharing