Q5.05.3probes as inspirationdesignresearch

Probe results are inspirations, not conclusions

Aliases: probes as provocation · inspirational not evidentiary

What it is

Whether the yield is a technology probe’s logs or a design probe’s work, it is inspiration (and often provocation), not an estimate about a population and not a verdict on whether a scheme is feasible. Gaver later described the epistemology of probes as uncertain, subjective, even deliberately incomplete—meant to open design imagination, not close an argument. Writing three households’ night-time peaks as “users need a night mode,” or a metaphorical photograph as “this direction is validated,” treats inspiration as conclusion. Inspiration still has to pass through independently testable follow-up before it enters a product.

Why it happens

Probes sample small, intervene strongly, and leave material open—three bars to statistical generalization. Participants are people willing to take in a strange object; the device or pack itself changes the life being observed; returns admit many readings, and the designer’s priors help constitute the “finding.” Technology-probe logs look quantitative, but without controls, randomization, or complete features, counts only describe what happened on these devices. Design probes are poetic material: their force is that they move you, not that they are frequent. When a team needs closure—to show a scheme beats a control, to estimate an effect—probes cannot supply that kind of knowing. They supply candidate questions and surprises worth testing.

Studying it

Report probes in three layers: traces observed, ideas the designer generated from those traces, and the still-unmet tests those ideas require. Discussions of probe epistemology, including Boer and Donovan, refuse to write returns directly as findings. An audit question helps: would another designer jump from the same material to a wholly different idea? If yes, the material is not a vehicle for conclusions. Follow-up interviews, diaries, usability tests, or experiments can then test the inspired hypotheses; that round is what produces conclusions. Do not put confidence intervals or “requirement priority” in a probe report.

Where it stops holding

In generative, early work that needs to break a team’s settled view, inspiration is a legitimate product and needs no apology. Organizations that only accept “conclusions with data” will rewrite probes into pseudo-surveys and wreck the method. In some participatory projects the work itself is material for joint decision, closer to negotiation than inspiration; say so. Inspiration is also not a license for unlimited projection: ideas that contradict the material cannot pass on probe uncertainty.

Applying it

  • After every “finding,” mark it as trace, idea, or tested claim; untested items must not freeze requirements.
  • File probe output as a hypothesis list, each with a follow-up test.
  • Forbid using probe photographs in review as evidence that a scheme has passed.
  • If the decision needs an estimate or a contrast, open a validation study; do not powder the probe with sample size.

Related

  • Same group: Q5.05.1 Technology probes collect usage data in situ · Q5.05.2 Design probes elicit expression rather than answers
  • Adjacent: Q5.08 Technology probes and design probes · Q1.02 Exploratory and confirmatory research
  • Search terms: probes as inspiration · provocation · generative research

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/Q5.05.3