← Back to the chapter · Previous detail · Next detail →

Technical detail · Empathize and Define

Translate findings into product states

3.3.4 Findings to System Constraints

Research findings become useful when they map to system constraints. “Technicians check the local display before opening the app” can become a requirement for device-side status, readable labels, offline diagnostics, and local acknowledgement. “Residents worry about who sees leak data” can become role-based access, retention limits, and a clear sharing model.

Translate each insight into actors, states, events, and measurements. Actors may include device, gateway, user, installer, automation rule, support agent, and external service. States may include unpaired, provisioning, normal, pending, offline, stale, faulted, acknowledged, overridden, and recovered. Events need timestamps, source, confidence, freshness, and ownership so later prototypes can test the real workflow.

The output should be a small constraint set that links user need to technical behavior. Commissioning is the setup process that connects and prepares a device for use; for example, BLE provisioning should recover after a failed QR scan, and Matter commissioning should explain what failed. A device shadow or twin is a software record of a device’s intended and reported state; it should show the difference between the two. An alert rule should avoid paging the wrong role, and a support console should show firmware, battery, last heartbeat, and recent command outcomes.

← Back to the chapter · Previous detail · Next detail →