Help people choose confidently when names look the same.

Begin with the current product, intended users and the action that selection enables. Choosing a colleague for an internal handoff, a contact for a request or a destination for a message can have different consequences. The product owner defines the available information and permitted actions; design makes the decision understandable within that boundary. We can scope a focused journey improvement or a wider product and design system.

Discovery examines content, navigation, search and the points where a person needs confirmation. Representative records should include similar names, incomplete information and a result that is no longer available. Decide what identifying context is appropriate for the particular audience before drawing a richer result card. More personal information is not automatically a better answer to an ambiguous name.

The design work can include information architecture, wireframes, visual layouts, prototypes and evaluation with suitable participants. The handover explains the states, labels and response information the implementation needs. The actual application must supply approved data and enforce its access rules; a well-designed picker does not by itself verify identity or establish backend permission enforcement.

Imagine an operator searching for a recipient and seeing two identical display names. The task requires choosing one person, but the names alone do not reveal which result is intended. This is a hypothetical product-design exercise, not a San Francisco client system or an observed user-study result.

Ask what context the operator already understands and is permitted to see. A team, role or another approved identifier may be useful, depending on the product. Show the selected context consistently in search results and in the later review state. Avoid resolving the ambiguity by exposing unrelated contact fields or assuming the first result is correct.

Review an empty search, two plausible results, an unavailable recipient and a return to revise the choice. A colleague should be able to explain which person is selected before the consequential action occurs. The owner decides what happens if identifying information is still insufficient; the interface can provide an appropriate clarification route rather than invite a guess. The implemented journey needs the corresponding data and access checks before it is accepted as working behaviour.

Bring the current screen or a description of the proposed product, the action after selection and the people who use it. Include suitable sample names and the approved identifiers available to those users. Identify the product owner who can decide what information may be displayed and the technical contact who understands data and access constraints.

We work remotely with San Francisco stakeholders using dated reviews labelled America/Los_Angeles and Asia/Kolkata. Consolidated feedback should state whether it changes the task, an information rule or the visual presentation, so an accepted design remains understandable to the implementation team.