Digital Product Engineering3.21 Search
VOL. III · CH. 3.21 · COMPONENT

Search

Often the fastest path through a product's structure — when it actually works.

Division
Difficulty
Prerequisites
Related
1 min read · 133 words

3.21.1Definition & Anatomy

Search lets a user query content directly rather than navigating a hierarchy, typically returning ranked, filterable results — critical for any product with more content than fits in navigation.

3.21.2Common Mistakes

  • Exact-match-only search that fails on typos or synonyms a real user would naturally use.
  • No visible empty-state guidance when a search returns zero results.
  • Slow, unresponsive search with no loading indicator, making users unsure if it's working.

3.21.3Best Practices

  • Support fuzzy matching and common synonym handling, not exact string matching alone.
  • Design a helpful zero-results state suggesting alternate terms or popular content.
ExampleDocumentation sites with strong search (like Stripe's) return results as the user types, with fuzzy matching tolerant of minor typos — because a developer under time pressure won't retry a failed exact-match query.