Back to lab notesBuild notes
Build notes3 min read

Search should help when you forget the name.

People remember fragments, places, and reasons. A useful search should give those memories somewhere to start.

Imagine a drawer full of sewing patterns, with a small app to keep track of them. You want the jacket with the enormous pockets. You remember a blue cover and that you put it aside for cooler weather.

You do not remember the pattern number. That is partly why you opened the app.

A search box that accepts only the official name asks you to supply the information you came to find. It may work perfectly against its index and still be a poor place to begin.

The interesting design work is deciding which fragments someone can use, and what the results need to show before they recognize the right thing.

Give imperfect memory something to work with

For this imaginary collection, a description, a cover image, and the person’s own notes could all help. “Big pockets” might be written in a note even when the manufacturer calls them patch pockets. A season label could narrow the search without pretending that autumn is part of the title.

That does not require a conversation with an AI assistant. Searching notes as well as names may be enough. A few aliases might handle familiar differences in wording. Start there before choosing a more complicated way to interpret the request.

Someone should also be able to change their approach without starting over. If the words bring back too many patterns, let them narrow by garment type. If they remember the cover better than the name, make the images large enough to inspect. A list of tiny thumbnails beside nearly identical product codes is not much help to a visual memory.

The details worth showing depend on the collection. A parts drawer needs different clues from a music library. Ask what a person would say while looking for the item, including the unhelpfully human bits: “the other one,” “the version I liked,” or “the thing I bought before the trip.”

You do not have to understand every phrase. You do need to avoid treating every incomplete phrase as user error.

Help someone recognize the answer

Suppose “pockets” finds five patterns. A useful result could show the matching note beside its cover, with enough text to explain why it appeared. The person can then make a judgment without opening every record.

Keep an exact pattern-number match easy to find too. Supporting fuzzy recollection should not make a precise search worse. Someone who knows the identifier deserves a short path to it.

If the search expands “jacket” to related terms, make that expansion understandable and easy to remove. If there is no convincing match, say so. An unrelated result placed first with great confidence is a new puzzle, not an answer.

To review the design, choose a few entries and write down plausible ways to remember each one. Try a nickname and a description that never appears in the title. Include two items that share the same clue. Check whether the result gives a person enough evidence to choose between them.

Someone using the app wants to find the pattern and get back to the jacket. Remembering that the pockets were excellent ought to count for something.