Q5.08.1probe deployment durationdesignresearch

Technology probes typically last weeks, shorter than the incubation of design probes

Aliases: probe timescale · design-probe incubation

What it is

The two probe families differ in timescale, not only in materials. A technology probe is usually deployed in weeks: the device must live past novelty and come back before faults and upkeep explode. A design probe (cultural probe) needs a longer incubation: the pack stays in a life until odd moments get filled, photographed, posted—often across weeks to months. Chase a design probe on a technology probe’s one-week clock and you get homework. Leave a technology probe hanging for a design probe’s quarter and the logs become unmaintained noise.

Why it happens

A technology probe is a living system; the clock starts at install. Battery, network, crashes, whether anyone still bothers with it, all move by the day. Novelty peaks in week one; if a stable practice appears, it is usually in the week or two after. Stretch too long and faults and forgetting swamp interpretable use. A design probe hardly depends on continuous running; it depends on life supplying triggers—a quarrel, a trip, a corner that should not be seen. Those triggers do not follow the study calendar, so the material has to lie there until it is used. Chasing cuts incubation into “finish this tonight,” and expression turns from a trace of life into compliance. The periods are not interchangeable because one is bounded by system lifetime and the other by the density of life events.

Studying it

Write install day, planned return day, and “earlier than this is too short / later than this is neglected” into the plan. Technology probes should log daily activity and faults, using the curve to judge whether novelty has passed and whether the device is dead. Design probes should log intervals from send to first return to last return, not only return rate. Hutchinson and colleagues’ technology probes typically ran weeks; Gaver and colleagues’ cultural probes left packs until a set of returns formed, rather than chasing the next day. Do not treat one week of device logs and three months of postcards as contemporaneous data.

Where it stops holding

Holidays, moves, and hospital stays stretch or void both clocks; the protocol needs a pause rule. Workplace technology probes may need only days, because use is compressed by shifts; homes more often need a weekend. In highly routine institutional life, design-probe incubation is not necessarily longer—it may simply be ignored. Customs and shipping for remote packs can turn incubation into blank time rather than richer life time.

Applying it

  • Schedule technology probes as install, week-one follow-up, a post-novelty stable window, and a hard return; do not extend the return for “let’s watch a bit more.”
  • Schedule design probes with an earliest and latest return after sending; no chase in between, one light reminder.
  • Do not share one deadline sheet across both probe types.
  • Report the window: how long the material sat in a life, and whether that span crossed novelty or was cut by chasing.

Related

  • Same group: Q5.08.2 Technology probes yield countable logs; design probes yield works that need interpretation · Q5.08.3 The material quality of a probe pack shapes engagement and return rate · Q5.08.4 Probes suit early inspiration, not validating a specific design
  • Adjacent: Q5.05 Probes · Q3.14 Novelty and learning effects
  • Search terms: probe deployment duration · incubation period · novelty effect

Cards in the same group

Quick Actions

Share

Share this page

ios_share

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