IoT Interaction Review
IoT Interaction Review
Try It Now
Choose one IoT interaction and write a one-row review:
| Field | Your answer |
|---|---|
| User task | What the person is trying to do, not the feature name. |
| System state | Current, pending, stale, uncertain, rejected, offline, or fallback state that changes the task. |
| Feedback channel | Device indicator, app message, haptic cue, sound, notification, dashboard, or support surface. |
| Recovery path | Undo, retry, cancel, override, escalate, local fallback, or support handoff. |
| Trust boundary | Permission, consent, privacy, shared role, accessibility, or support visibility issue. |
Micro-Exercise: State Truth
For each interface phrase, rewrite it so the user can see what the system really knows:
“Door unlocked” when the command has only been queued. “Room available” when the gateway is offline and the last motion event is stale. “Pump fault urgent” when sensor confidence is low and no maintenance role is currently assigned.
Rehearse Recovery at the Pump
Put an operator beside the noisy pump with gloves on and ask them to acknowledge a maintenance alert. Record what they see on the local indicator, what the dashboard reports, and whether the acknowledgement reaches the device. Then disconnect the gateway during the task. The interface should identify the pending command, mark the last confirmed state, and offer a repeatable route to check the pump before another command is sent. Treat an apparent success message as a defect until the device confirms it.