UX/UI Design Study

Follett Universal Search

Designing a unified K-12 discovery experience that helped students, teachers, librarians, and administrators search across books, eBooks, websites, databases, and digital learning resources from one clear interface.

Methodology

Design Approach

Universal Search was not simply a search interface. It was a product simplification effort that required understanding fragmented content systems, organizing them into one clear experience, designing repeatable patterns, validating usability, and creating a foundation the platform could continue to build upon.

01 / Understand

Discovery

The work began by understanding how students, teachers, librarians, and administrators searched across disconnected catalogs, eBooks, databases, websites, and digital learning resources before the interface attempted to unify them.

Project Tags

  • UX Design
  • UI Design
  • Federated Search
  • K-12 Education
  • Enterprise Software
  • Information Architecture
  • Faceted Navigation
  • Design Systems
  • Front-End Design

Executive Summary

Follett Universal Search was designed to solve a common problem in school libraries: content lived in too many separate places. A student might need to search the library catalog, eBook collections, database subscriptions, curated websites, and digital learning tools separately before finding the right resource.

The project unified those discovery paths into a single product experience. Instead of asking users to understand the underlying content systems first, the interface allowed them to begin with a familiar search pattern, then refine, browse, evaluate, and act on results across multiple sources.

My work focused on front-end design, UX design, interaction patterns, visual hierarchy, interface consistency, and collaboration with product, engineering, architecture, sales, leadership, and external stakeholders.

12+ Content Sources
50+ Developers
K-12 Education Market
1 Unified Experience

The Problem

Students had to know where to search before they could search.

School library ecosystems had become increasingly fragmented. Physical books, eBooks, subscription databases, websites, reading tools, and classroom resources were valuable, but they often lived behind different interfaces, labels, and search behaviors.

Universal Search reframed that experience around the user. Rather than exposing the organizational complexity first, the product brought multiple sources together and presented them through a consistent discovery model.

Before

  • Library catalog
  • Follett Shelf
  • Subscription databases
  • Digital resource links
  • WebPath / websites
  • Local collections

Universal Search

One search model, one visual language, one path into many kinds of educational content.

After

  • Grouped results
  • Faceted refinement
  • Consistent metadata
  • Clear calls to action
  • Item-level details
  • Personalized tools

Design Decisions

Design decisions that mattered

The most important work was not simply arranging screens. It was creating a system of patterns that could scale across content types, users, roles, workflows, and future product evolution.

Start with search

Make the primary action obvious and immediate, especially for students who may not understand how content is organized behind the scenes.

Group results by type

Respect the differences between books, digital content, websites, and databases while presenting them within one unified search model.

Use facets for refinement

Allow users to narrow results through meaningful educational metadata such as author, subject, format, interest level, and reading level.

Create repeatable cards

Use a consistent result pattern so users could scan titles, authors, cover art, availability, ratings, and actions without relearning each content type.

Separate detail content

Use tabs to keep deeper metadata, copies, previews, and reviews accessible without overwhelming the first view of the item detail page.

Keep actions visible

Prioritize high-value actions such as Open, Hold, Checkout, Favorite, Cite, Share, and Return where they supported the user journey.

Collaboration and Scope

Universal Search required alignment across a large, multi-disciplinary organization. The work involved product management, architecture, development teams, sales, leadership, executive stakeholders, external market consultants, and customers who cared deeply about how students and librarians discovered content.

The biggest challenge was not only deciding what the interface should look like. It was helping the organization agree on a single approach to layout, functionality, branding, search behavior, and long-term product direction. The design had to be simple enough for students, useful enough for librarians, credible enough for administrators, and technically feasible enough for engineering teams to build and maintain.

The work succeeded because the interface reduced visible complexity without hiding the depth of the educational content ecosystem behind it.

Outcome

The product performed well in usability studies and received positive customer feedback. Leadership felt the experience stood apart in the K-12 education technology market because it gave schools a clearer, more modern path into their growing collections of physical and digital content.

Universal Search also established a foundation for the broader Destiny Discover experience, expanding from a search-centered application into a larger discovery, reading, and resource-management platform.

Looking Back

Looking back more than a decade later, Universal Search feels like an early design-system effort as much as a search project. The screens use consistent navigation, repeated card structures, reusable tab patterns, predictable actions, and disciplined metadata hierarchy across many product areas.

If I were approaching the project today, I would spend even more time on accessibility, responsive behavior, semantic search, personalization, recommendation models, and AI-assisted discovery. The underlying problem remains relevant: users still need help finding the right information across too many disconnected systems. The tools have changed, but the design challenge is very familiar.

Supporting Design Documentation

Original design specifications, interaction documentation, and implementation guides created during product development.