Human-Centred IoT Design · Study deck

IoT Research Methods: Fieldwork and Synthesis

A home visit can be a contextual inquiry: watching a task where it happens and asking the person about it.

UX Uma is your guide for this deck.

research-methodscontextual-inquiryinterviews
iotclass.org

After studying this chapter

Learning objectives

You will be able to:

  • Explain: Observation can show where setup stopped; an interview can explain a participant’s reasoning; event logs can locate a technical failure in the flow.
  • Explain: A spike in overrides might mean the automation is wrong, the UI is unclear, the context changed, or users do not trust the system.
  • Explain: Requirements should state what is sensed, what is not sensed, how data is summarized, who can see it, and how occupants can report problems.
  • Explain: A field pilot can test whether the revised handoff survives repeated use, but recruitment and device mix still bound the claim.
iotclass.org

Major section

Prototype and Usability Tests

Prototype tests answer whether a design representation is understandable before the team commits to implementation.

  • Prototype fidelity should match the question.
  • A sketch may be enough for sequence and wording.
  • A clickable prototype may be needed for flow comprehension.
  • A bench prototype or field prototype may be needed when physical sensing, placement, timing, or feedback affects behavior.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
iotclass.org

Major section

Telemetry and Support Logs

Telemetry and support logs can show field signals that research sessions miss.

  • Telemetry does not explain itself.
  • A spike in overrides might mean the automation is wrong, the UI is unclear, the context changed, or users do not trust the system.
  • Combine logs with observation, interviews, or support review before turning the signal into a requirement.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
iotclass.org

Major section

Incremental Examples

Contextual inquiry with account owners and household members during setup and first visitor use.

  • Requirements should distinguish pending invite, active credential, revoked credential, phone permission issue, reader offline state, and account ownership conflict.
  • Reopen the plan when the guest role, offline access behavior, support process, or reader firmware changes.
  • Prototype tests for alert wording, acknowledgement, escalation, and exception-resolution screens.

Key terms

Requirements should state what
Requirements should state what is sensed, what is not sensed, how data is summarized, who can see it, and how occupants can report problems.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
iotclass.org

Major section

Incremental Examples (continued)

Comfort findings from one building may not transfer to another building with different zones, work patterns, or governance.

  • Requirements should state what is sensed, what is not sensed, how data is summarized, who can see it, and how occupants can report problems.
  • Reopen the study when sensors, data retention, building zones, or automation policies change.
  • Diary prompts for drivers and warehouse staff when alerts occur outside scheduled observation.
iotclass.org

Major section

Incremental Examples (continued)

Field pilot across a small set of routes before expanding to more warehouses, carriers, and product categories.

  • The pilot can support decisions about the tested routes, sensor models, firmware, trailer types, gateway placement, and escalation workflow.
  • Requirements should separate product-temperature excursion, sensor fault, gateway offline state, delayed upload, driver acknowledgement, quality-manager release decision, and maintenance work order.
  • Reopen the plan when probe model, calibration interval, firmware, route profile, carrier role, alert threshold, or data-retention policy changes.
iotclass.org

Major section

Common Defects

Method mismatch: using a survey when the team needs field observation.

  • Happy-path testing: testing setup success but not failure, maintenance, support, or shared use.
  • Prototype theater: testing a polished flow after the decision has already been made.
  • No evidence boundary: writing conclusions that sound broader than the research supports.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
iotclass.org

Major section

Explain the Method Mix and Its Limits

Observation can show where setup stopped; an interview can explain a participant’s reasoning; event logs can locate a technical failure in the flow.

  • None alone establishes prevalence in the wider population.
  • A field pilot can test whether the revised handoff survives repeated use, but recruitment and device mix still bound the claim.
  • This preserves the useful connection between behaviour and system state without over-collecting household data.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
iotclass.org

Major section

Summary

Research methods help IoT teams make better design decisions when they are matched to the evidence gap.

  • Observation shows behavior and context.
  • Prototype tests reveal comprehension and recovery problems.
  • Surveys and telemetry help estimate scale after patterns are understood.
  • The best research plan is not the largest plan.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
IoT mixed-method evidence plan linking decision, method, participant role, context, evidence, boundary, and action record.
iotclass.org

Deck summary

Key takeaways

Prototype tests answer whether a design representation is understandable before the team commits to implementation.

  • Telemetry and support logs can show field signals that research sessions miss.
  • Contextual inquiry with account owners and household members during setup and first visitor use.
  • Comfort findings from one building may not transfer to another building with different zones, work patterns, or governance.
  • Field pilot across a small set of routes before expanding to more warehouses, carriers, and product categories.
iotclass.org

Retrieval practice

Recall check 1 of 3

UX Uma says: answer from memory, then check your reasoning.

Q1A team wants to understand why users abandon setup for a battery leak sensor under sinks and near appliances. Which research plan best matches the evidence gap?

ARun only a preference survey about automatic setup, without placement, connectivity, or state-message evidence.
BObserve first-time setup in realistic sink/appliance locations, review setup logs, then interview about confusing states.
CAsk engineers to predict setup error from the specification, without watching real placement or recovery.
DTest the polished app after launch, then use support tickets as the first evidence source.
Show answer

Answer: B Method choice should follow the decision and evidence gap.

iotclass.org

Retrieval practice

Recall check 2 of 3

UX Uma says: answer from memory, then check your reasoning.

Q2A leak sensor setup note says a participant stopped at pairing. What makes the finding diagnosable?

AJoin the observed pause to pairing events and firmware version.
BAsk the participant to recount the pairing steps afterward and code the interview.
CGroup the pause with similar pairing complaints across sessions by screen step.
Show answer

Answer: A The join helps distinguish misunderstanding from device failure.

iotclass.org

Retrieval practice

Recall check 3 of 3

UX Uma says: answer from memory, then check your reasoning.

Q3Field interviews explain two households’ setup problems. Which broader claim is warranted?

ATreat the same pairing issue in two homes as the leading setup barrier for the product.
BThese cases reveal failure paths worth testing in a wider sample.
CUse the recurring pattern to prioritize a revised setup flow for the next release.
Show answer

Answer: B The small set supports candidate problems and a next test.

iotclass.org

Print reference

Answers

Answer key.

  1. B · Method choice should follow the decision and evidence gap.
  2. A · The join helps distinguish misunderstanding from device failure.
  3. B · The small set supports candidate problems and a next test.
iotclass.org