Separate observation from inference at a Singapore journey map critique

The problem

A Singapore UX researcher presents a journey map whose observed behaviour, inferred motivations and proposed solutions look equally certain, making useful critique difficult.

Give each statement an evidence type

Choose a short stretch of the journey and mark direct observations, participant accounts, your interpretations and design proposals distinctly. Do not invent a quote to make an interpretation vivid. DesignSingapore describes customer observation and interview as inputs to design work. Your map should let a reviewer see how those inputs connect to the story you tell. Add the task and starting conditions to the action. A pause after a question, a movement back to an earlier screen and an answer to an interview question are different kinds of material. Record which you actually have, when it occurred within the task and what help was supplied. Put your interpretation in its own column rather than making a cause part of the action description. Check the people and conditions represented before making a population claim; here, trace whether the particular map annotation follows from its evidence. A visually polished map can still leave that link absent.

• DesignSingapore: understanding customers through design ↗ · Source checked 20 October 2026

Use four columns without filling the unknowns

For each relevant step, write observed action or stated words; interpretation; plausible alternative; and missing observation or question. Keep a small context note for the task, material origin and assistance. One row can contain an unanswered interpretation: “Cause unknown” is useful when the evidence cannot choose between explanations. Avoid filling every stage with an emotion merely because the map has an emotion row. Use the columns to decide what the current case study can honestly say before searching for feedback. Follow the actual project’s research method for any further work.

Locate the uncertain transition

Find one point where the map moves from a visible action to an explanation of why it happened. Write an alternative explanation that also fits the observation. For example, leaving a queue might reflect time pressure, unclear instructions or another reason. The critique question is which additional observation would help distinguish the explanations, not which narrative sounds most persuasive. Keep three entries together: the material you may show; how it was produced; and the particular claim it can support. A permitted exercise observation, participant statement and supplied fictional scenario have different origins. The cited DesignSingapore customer article discusses observing and interviewing customers, research questions and prototypes. It does not prescribe this column tool, prove a motive in your map or promise portfolio review at an event. Its business resources page provides programme context. Mark a recreated or invented example clearly instead of presenting it as a field visit.

• DesignSingapore: understanding customers through design ↗ · Source checked 20 October 2026
• DesignSingapore Design for Business ↗ · Source checked 20 October 2026

Inspect a wholly invented pause and return

Every person and screen in this practice case is fictional. A learner is asked to find a session beginning after an assigned time. The supplied observation says they open the details screen, pause, return to the list and open another session. The first interpretation on the map says “They distrust the provider.” The record contains no statement about trust. An alternative is that the learner was comparing start times; another is that the instructions were unclear. The map can retain the observed sequence while marking the motive unknown. Do not turn any of these possibilities into a user finding simply because it makes the story coherent.

Choose the decision affected by the ambiguity

State whether the map will guide signage, staffing, a digital step or another bounded change. An uncertain motivation matters differently for each decision. Ask peers which claim they would need to verify before making that particular change. This makes the discussion useful even when the whole journey cannot be researched again immediately. Ask the reviewer to point to the observation that supports the interpretation and identify an alternative that the record does not exclude. A helpful question is “What else could explain the return to the earlier screen, given these task conditions?” It is narrower than asking whether the person is indecisive. If the critique lacks the original context, treat its suggested cause as a hypothesis. The right next step might be a clearer annotation, a permitted follow-up question or a different task observation, rather than immediately redesigning the service.

Use a later statement for the question it addresses

Continue the invented case with a separate supplied statement: the learner says they returned because the first session began before the assigned time. That supports recording their stated reason under these toy conditions. It does not independently reveal every thought or establish that real users reject the provider. Keep the statement’s supplied origin beside the action row. The earlier trust annotation should be removed or left as unsupported; the task-time explanation has a stated basis. If the later statement concerns another attempt or person, retain the gap rather than silently attaching it to this sequence.

Keep disagreement useful without deciding the motive by vote

A reviewer may propose a different explanation for the same action. Record what additional evidence would distinguish the explanations instead of counting favourable comments as confirmation. If no further material is available, narrow the case study to the observed sequence and the hypotheses left open. An interview answer and an observed task can inform each other while remaining different records. A clear revision might replace “users mistrust this service” with “this supplied learner returned to compare the session time.” Preserve the original annotation so the change in reasoning is visible, rather than rewriting the evidence to match the preferred story.

Revise the map without erasing uncertainty

Keep unresolved interpretations visible and attach a proposed check to the important ones. If a session is only a design exhibition, do not expect structured synthesis feedback. Search Boardzip for service design workshops or research discussions and read their participation format. Use a shareable extract, with consent and organisational permissions handled through your actual research process. Save the before-and-after annotation with the reviewer’s reason. Write which interpretation you removed, narrowed or kept, and which question remains unanswered. Keep the evidence trace beside the separate question of who may decide or act on the findings. Confirm that an actual critique accepts research material, what participants may bring and whether individual work receives attention. Use an invented case when the original is unsuitable to share. A public discussion can improve the wording of a claim without establishing user behaviour or a completed design decision.