It depends on users knowing what to look for
Aliases: knowledge in the head · search needs a query
What it is
A command palette is a recall channel: someone must first produce a query in the head, then recognise the target in the hits. Depending on knowing what to look for is why it does not serve exploration of the form “I do not know what this software can do”. Browsing a menu is recognition — seeing brings the name back. A palette is think-then-search. People who cannot produce a name open it and face an empty field with nothing to do.
Why it happens
Recognition is easier than recall: a menu spreads candidates, names appearing as external memory. A palette puts candidates away until a query summons them. Where does the query come from? From command names seen before, a colleague’s wording, terms in the docs. Without those, users do not even know which word to type. An empty query that only shows recents is still a short unlegend list for a newcomer, not a map.
So the palette is an expert accelerator, not a teaching device. If a product puts exploratory tasks (format for the first time, import for the first time) mainly in the palette, it asks people to already have the vocabulary that exploration was supposed to grow. The failure is typical: open, stall, close, search an external tutorial, ask “does this software even have X”. The function is there; a recallable name is not.
Studying it
Split tasks into “can produce the name” and “knows the outcome but cannot name the command”. Compare success on the palette versus the menu tree. Independent variable: whether the command name was seen beforehand. Dependent variables: whether a first keystroke happens, query reformulations, and abandonment to the other channel.
Treat spoken “I do not know what to search” as a primary measure; do not read an empty query as a lack of effort.
Where it stops holding
A palette that lists recommended commands for the current context on open recovers some recognition, but it still cannot cover the whole tree and cannot be the only way to explore. Voice or natural language that accepts “make this look like a heading” as an outcome description reduces dependence on recall — and that is already a different matcher. Extremely frequent commands move to muscle-memory shortcuts and never need the palette opened. A product with no menu, only a palette, will stall newcomers on day one.
Applying it
- Treat the palette as an accelerator: the first completion path for a main task should still be walkable in a visible menu, toolbar, or coach.
- On empty query, offer a short recognisable list in the current context, and say “type a name to search all”; do not leave a blank field.
- Put the searchable name next to menu items so browsing teaches the word for the next recall.
- How to check: give the palette to someone who has not seen the command name and only knows the outcome. If they cannot start a query, or immediately ask whether the function exists, the channel is demanding recall. Contrast with people who have seen the name; the gap is the recall dependence itself.