← Back to the chapter · Next detail →
Technical detail · Human-Centred Design for IoT
IoT design evidence has technical shape
2.6 IoT Design Evidence Has Technical Shape
IoT design evidence is not only interview notes. It can include radio survey results, battery discharge curves, calibration drift observations, packet-loss logs, broker message traces, OTA update outcomes, and support-ticket patterns. Those artifacts matter because the user experience is distributed across hardware, firmware, network, cloud service, interface, and operations.
The method therefore needs technical checkpoints. Sampling rate affects whether the product can detect the event. Link margin means the extra radio signal strength available above the minimum needed for a reliable connection; it and gateway placement affect whether the user sees the alert. Credential rotation means replacing device passwords or keys on a planned schedule, which helps limit harm if one is exposed. Device identity and access control also affect safe support. Data retention and deletion rules affect whether collecting a signal is acceptable at all. Those checkpoints are design constraints, not late engineering cleanup.
Under the hood, design thinking turns vague risk into testable state. A connected pump controller should model normal, scheduled, manual override, dry-run lockout, offline, firmware-update, and fault states before the interface is drawn. A BLE medication cap should distinguish opened, missed, duplicate-open, low-battery, clock-drift, phone-not-nearby, caregiver-notified, and privacy-paused states. If the team only sketches the happy path, the first field trial will discover recovery behavior by accident, often after trust has already been damaged.