Internal search should make scope and ranking understandable. Define searchable objects and result recognition before adding advanced retrieval features.
Begin with a real lookup task
In a fictional case-management product, searching “Taylor” might refer to a person, company or case. Display the object type and distinguishing context. Users should be able to tell identical names apart without opening every record.
| Situation | Behaviour to design |
|---|---|
| Ambiguous name | Type, identifier or distinguishing context |
| No matches | Reformulation or filter removal |
| Historical record | Relevant date or status |
| Restricted data | No exposure of unauthorised content |
| Delayed indexing | Explain freshness when it matters |
Maintain reference queries
Keep a small set of representative searches: exact name, common typo, identifier and domain-specific term. Record expected results and costly mistakes. After a change, compare those cases rather than searching only for familiar records you created yourself. Include language variants when the customer base needs them.
Does a V1 need intelligent search?
Start with observed needs. Clear filtering and consistent labels may help more than opaque ranking. If semantic retrieval is introduced, retain access controls and explicit evaluation cases. Success means finding the correct object, not advertising a sophisticated search technique.
Names and identifiers travel differently across languages
A customer may search a translated category but an unchanged product code. Include both patterns in reference queries. Avoid translating stable identifiers, and show enough context that a user can recognise the intended object even when its display label is localised.
From this guide to your project
Product ↗
The experience connects your promise to the job your user needs to get done. We design that journey before adding more screens.
Tell us about your ideaExamples are educational and do not describe client results. Content prepared with AI assistance; see our editorial policy. Our method ↗