Challenges of Searching and Assessing the Need for Search

Searching is cognitively demanding in a way browsing usually isn't, a person has to formulate a query, choose the right words, and then interpret a list of results, all before they've actually found anything. That cost means search isn't automatically the right investment for every information space. It earns its place in large or deep spaces, content that changes frequently enough that browsing structures can't keep pace, situations where users already know precisely what they're looking for, and collections too large to browse through effectively no matter how well organized.

The reverse is just as true: a small, shallow space with a primarily exploratory audience and easily browsable content may not need a dedicated search system at all, building one anyway spends effort solving a problem that doesn't really exist yet.

Search isn't a feature every site deserves by default: it's a specific answer to a specific set of conditions, and building it where those conditions don't exist is effort spent solving a problem nobody actually has.

Exercise

The scenario: Three information spaces, each considering whether to build an internal search system.

Space A: A small charity's website, forty pages of fairly stable content, a well-organized navigation system, visited mostly by occasional visitors who generally know what they're looking for.
Space B: A large corporate intranet with thousands of documents across dozens of departments, frequent content updates, and employees who regularly report failing to find policies and procedures they know exist somewhere.
Space C: A medium-sized e-commerce store with three hundred products in a clean, well-structured category hierarchy, whose customers largely browse rather than search.

1. Does Space A need a dedicated internal search system?
2. Does Space B need a dedicated internal search system?