Design Thinking Phase Review

Design Thinking Phase Review

Empathize: Observe The Real Situation

Empathy in IoT includes more than opinions. Users interact with devices in physical spaces, routines, households, workplaces, vehicles, sites, and shared environments. Observation should capture what people do, what devices do, and what the environment makes possible or difficult.

Review:

  • Who was observed, and do they represent the intended users, operators, installers, maintainers, and support roles?
  • Where did the observation happen, and did that setting match real use?
  • Which routines, interruptions, workarounds, physical limits, access needs, and privacy expectations were visible?
  • Which devices, tools, labels, power sources, networks, and manual controls shaped behavior?
  • Where did a stated preference differ from observed behavior?
  • What evidence was missing and must not be treated as a general result?

For IoT, the field context is often the product requirement. Lighting, distance, wall material, shared access, noise, wet hands, gloves, weak connectivity, low battery, and household routines can matter as much as screen layout.

Frame Problems Before Solutions

The Define phase turns observations into a problem frame. A good frame describes a user need and why current behavior fails without assuming the answer is a new sensor, app, dashboard, automation, or cloud service.

Review:

  • Does the frame name the user, setting, goal, barrier, result, and evidence source?
  • Does the problem statement separate the need from a proposed solution?
  • Does the frame include non-goals and limits?
  • Are privacy, safety, access, support, and failure effects visible?
  • Did the team record assumptions that still need testing?
  • Did the team consider other meanings of the same observation?

Weak frame: “Users need a smart sensor app.” Stronger frame: “Residents need a low-effort way to confirm a shared room is safe to use because current status cues are distant, inconsistent, and hard to verify during busy handover periods.”

Ideate Before Choosing

Ideation is useful when it broadens the solution space. It is weak when the team starts with one favored technology and writes ideas around it.

Review:

  • Did the team create several ideas before judging them?
  • Did some ideas change the interaction, physical form, service flow, local fallback, or support path?
  • Were rejected ideas recorded with reasons?
  • Were ideas judged against user evidence rather than novelty alone?
  • Did battery, installation, consent, access, connectivity, and maintenance shape the choice?
  • Does the selected idea still fit the problem frame?

An idea set should include options that do less, options that move logic locally, options that avoid collecting data, options that improve service workflow, and options that use existing manual cues. The best IoT answer is sometimes a simpler non-connected or partly connected design.

Match Fidelity to the Question

Prototypes should answer specific questions. A polished prototype can be wasteful if the question is still about terminology, placement, or trust. A rough prototype can be dangerous if the question is about physical safety, power behavior, or failure recovery.

Review:

  • What question is the prototype meant to answer?
  • Why is its level of detail enough for that question?
  • Does it include the physical setting, not only screens?
  • Does it show setup, alerts, permissions, failures, and recovery paths?
  • Could users mistake it for the final product?
  • Does it avoid collecting real personal data that the test does not need?
  • Are claims about what can be built kept separate from user evidence?

Prototype examples:

Paper or clickable flow: test language, navigation, consent wording, setup sequence, and status labels. Cardboard or placement mockup: test size, mounting, reach, visibility, shared-space fit, and physical affordance. Wizard-of-Oz simulation: test automation expectation, trust, timing, and explanations before building intelligence. Bench prototype: test sensing, actuation, power, connectivity, latency, and failure behavior. Pilot deployment: test real context, maintenance, support, privacy, and behavior over time.

The review should ask whether the prototype teaches the next decision, not whether it looks impressive.

Test: Observe Behavior And Evidence

Testing should measure behavior against realistic tasks. Asking whether users “like” a prototype is not enough. IoT testing must include setup, physical interaction, alerts, multi-device behavior, privacy notices, degraded states, and recovery where relevant.

Review:

  • Do test tasks match real situations rather than interface labels?
  • Do participants include the roles affected by the product?
  • Does the test setting include physical and environmental limits?
  • Did the facilitator observe hesitation, errors, wrong meanings, repeated attempts, and workarounds?
  • Were access and consent barriers recorded?
  • Were support and maintenance clues captured?
  • Did the team separate task success from satisfaction?

Useful testing evidence includes what the user tried first, what they ignored, what they misunderstood, whether they trusted the automation, whether they noticed stale state, whether they could recover, and whether they could explain what the system did.

Iterate: Make The Learning Visible

Iteration is not just changing the design. It is recording what evidence changed the decision and what remains uncertain.

Review:

  • What was kept, changed, removed, split, or delayed?
  • Which observation, task result, failure, or risk drove the decision?
  • Did the team simplify connected behavior that was not needed?
  • Did the change introduce a new risk?
  • Does the next prototype test the riskiest remaining assumption?
  • Do the notes name an owner and the change that would reopen the decision?

Good iteration records prevent drift. They help future teams understand why a feature exists, why an alternative was rejected, and when the decision should be reopened.

IoT-Specific Risk Checks

Design thinking for IoT must include risks that pure screen design can miss.

Review:

Physical safety: Could a misunderstood action move, unlock, heat, dose, stop, start, or alert in a harmful way? Privacy and consent: Does the design collect presence, behavior, location, voice, image, health, or household data? Security and access: Who can control the device, share access, reset ownership, or override automation? Accessibility: Can people with different vision, hearing, mobility, cognition, language, or device access still complete core tasks? Failure recovery: What happens during low battery, weak link, app unavailability, cloud outage, stale state, or automation conflict? Support and maintenance: Can a user, installer, operator, or support person diagnose and recover without guessing? Lifecycle: What happens during onboarding, replacement, transfer, update, and decommissioning?

These checks belong inside the design thinking loop, not after launch.

Back to the chapter