Design around the place where information becomes action

A floor plan can be accurate and still be difficult to connect with the corridor ahead. I work with researchers and site teams to understand where a visitor stands, which way the display faces and what the next decision requires. Our kiosk exercise showed seventeen wrong first turns among forty participants after I had favoured a uniform north-up presentation. The revision allowed the display orientation to reflect its placement, with installation checks rather than a global visual rule. Thirty-five participants then chose the intended direction and five still needed help. I regard both numbers as useful evidence. They show a bounded improvement and remaining difficulty, not a universal navigation claim. The product brief should include the physical situation in which information is interpreted, as well as the accuracy of the drawing itself.

Visitors may arrive with a department name from a letter, while a kiosk shows an abbreviation familiar only to staff. I bring the content owner, design and product teams together to agree which public label identifies the destination and which approved aliases should help people find it. The product should preserve that relationship across a directory, search result and printed output. It should not invent a clinical synonym or rename a service without the hospital's approval. Our research found twelve of thirty participants could not connect the wording they carried with the kiosk's abbreviation. The response required a governed destination model, not merely a larger font. I also ask how changes reach every output, because a name that is consistent only on the newest screen can leave the journey fragmented at the next sign.

A cached map can remain visible when its information is no longer sufficient to direct a visitor confidently. I want the product to distinguish a confirmed route from one whose current status is unknown. The answer should explain the limitation and provide a practical way to seek assistance agreed with the site. In our simulated closure tasks, thirteen of eighty continued using an old route. The revised behaviour interrupted those known stale states and offered a staffed-help option. It did not invent an alternative route or claim that an offline display could know every change in a building. Engineering establishes the technical state and estate owners supply approved information; product defines how the user encounters the limitation. A clear interruption can be more useful than a smooth journey based on information the system cannot substantiate.

User research should be able to remove a feature, delay a release or change an assumption I have approved. I ask the team to connect a finding with the decision it affects and the cost of acting on it. The orientation, naming and stale-route cases each displaced other work, including a three-dimensional presentation feature that would have improved the demonstration without resolving the visitor's next question. I also distinguish a controlled exercise from use across varied sites and circumstances. A result should identify the task and participants, retain unresolved difficulty and guide the next inquiry. My role is to make those findings part of the product choice while engineering, site owners and specialist reviewers retain their authority. A research presentation that cannot alter priorities is not yet doing the work the product needs.