On entering a kitchen, someone may notice the light, colors, and worktop. Cooking a first meal introduces retrieval, washing, and preparation. After repeated use, objects may move, two people may divide the work, or someone may start avoiding an awkward area.
These are hypothetical situations, not findings from a residential study. They suggest that asking whether a space provides a good experience combines several different questions.
I want to organize experience simulation around time because time may change the mechanism, not simply the number of repeated tasks.
First contact concerns how understanding develops
How a drawer opens, how an appliance starts, and whether an interaction responds are questions that can be examined during first contact.
A task script should not silently assume prior knowledge. If we teach the operation before evaluating completion, we measure performance after instruction. We cannot quietly report that result as intuitive use.
In the service-robot study, separating the period before interaction, initiation, execution, and closure turned a broad ambition into specific checks. I think spatial experience needs a similar account of what people know at each stage.
First-use speed should not automatically become a universal objective. Some pauses help people check consequences. Removing them could accelerate action while weakening understanding.
Repeated use introduces arrangements and collaboration
Repeated tasks may change object placement, familiarity, and action order. Shared spaces introduce turn-taking, waiting, avoidance, and negotiation.
A simulation making claims about these phenomena needs states that can change. Where do objects remain after a task? Does the next task inherit that state? Does learning affect later choices? Can people adopt different strategies after a conflict?
Resetting the world each time gives multiple first uses. Looping an unchanged script gives repeated execution. Both may be useful, but neither automatically represents extended living.
Karapanos and colleagues used longitudinal research to examine changes in experience during use. That provides a reason to attend to time, while its product context does not establish the validity of a residential simulation. User Experience Over Time: An Initial Framework, 2009
My extension is that a claim to cover more time should explain which changing mechanism has actually been added.
Adaptation can conceal a design problem
Imagine someone stops colliding with a cupboard because they learn a detour. Errors fall, but did the design improve, or did the person learn to absorb a cost?
Someone else might stop complaining about a shared worktop after moving their cooking to a later hour. The visible process becomes smoother while their routine accommodates the space.
I would therefore examine both performance and cost: completion, extra steps, whose schedule changes, and which activities are abandoned. Satisfaction or completion alone may miss these transfers.
Adaptation is not inherently undesirable. Good spaces can support people developing their own routines. The question is whether change represents valuable familiarity or accommodation of an avoidable problem.
What an experience storyboard should carry
A plan explains location, a timeline explains order, and a storyboard can connect people, tasks, and conflicts into a process that others can discuss.
Its purpose should come first. A discussion of worktop sharing needs overlapping tasks, waiting, and the segment a modification could change. More expressive faces or cinematic treatment may add little to that decision.
I would identify the basis of each scene: observation, model output, or an illustration of a hypothetical situation. Generated imagery can explain a hypothesis; it cannot become evidence that the hypothesis occurred.
Narrative completion is a particular concern. If the model predicts waiting and the image depicts anger, readers may remember both as findings. Visual expression needs the same limits as the written conclusion.
Show the alternatives and their costs
For an unvalidated design, I would show two versions of the same task: where the current layout is expected to cause difficulty and which step a proposed change aims to affect. Mark unchanged conditions and the points requiring observation.
This supports a concrete discussion. Moving storage may reduce one conflict while increasing another task’s travel. Widening a route may consume space needed elsewhere. A storyboard showing only effortless life after redesign hides the actual tradeoff.
The same principle applies to reports and technical writing. A visual belongs when it helps readers understand a relationship, compare a choice, or identify a test. Rich presentation should follow the structure of the problem.
How long should the next study be?
I would not start by prescribing several simulated months and then invent activity to fill them. First ask whether the current decision depends on initial understanding, repeated arrangements, or long-term adaptation.
Short tasks can examine entrances and feedback. Repeated tasks can examine changing routines. Claims about extended living need real material covering the relevant period and an account of what remains outside the model.
I want an experience story to expose a process that can be modified, compared, and checked again. Connected to reality checks for virtual users, it can become part of design work rather than an endpoint in presentation.