Skip to content
10 — Discovery · Information RetrievalSupporting project

One search box across a fragmented learning product

Designing a global search experience that treats courses, lessons, questions, posts and discussions as searchable information rather than forcing learners to know where each type lives.

Role
Product Designer
Status
Shipped project
Scope
Search UX · Information architecture · Result types · Filtering · Cross-product discovery
Global searchSynthetic results · reconstructed filter model
Filters for all resultsAccessibility
CourseQuant · 8 modulesEnrolled
Probability for CAT
Counting, conditional probability and expected value, built for the quant section.
LessonCAT Quant · Course 02Enrolled
Conditional Probability
How probability changes once new information arrives, with worked examples.
QuestionQuestion bank · Set 04Free preview
Bayes theorem practice
The answer explanation walks through the prior, the likelihood and the update.
PostNewsfeed · Quant Prep spacePublic
Probability shortcut guide
A short list of the substitutions worth memorising before the exam.
DiscussionQuant Prep · DiscussionMembers
Help with question 17
Thread on where the sample space was set up incorrectly.
One query, five content types, one scan pattern. Results are synthetic and the filter model is reconstructed.

Some product visuals have been simplified or reconstructed to protect confidential platform and customer information. Results are synthetic. The filter presentation shown here is a reconstruction of the filter model, not a claim about the shipped UI.

Chapter 01 — The problem

The learner should not need to know where the answer lives.

Content sits across products, communities, lessons, questions, posts, discussions and comments. Without global retrieval, finding one thing means walking the hierarchy that happens to contain it.

Before — walk the hierarchy
Find the course
Open the product
Find the section
Scan the lesson
Or: find the community, the post, the discussion
A different path per content type
After — one entry point
One query
Course · Lesson · Question · Post · Discussion
Any content reachable from the search bar

Search by meaning first. Entity type second.

Chapter 02 — The result contract

Many content models. One result contract.

Each type contributes different searchable text — a lesson has content, a question has an answer explanation, a discussion has replies. What comes out the other side has to read the same way.

01ProductsTitle · short and long description
02CommunitiesTitle · description
03LessonsTitle · description · content
04QuestionsContent · answer explanation
05NewsfeedContent
06DiscussionsMessage and reply text
Type · title · context · description · optional image
Six content models, one index, one row shape.

Three questions, in the same order, whatever kind of thing it is.

What every result has to answer, in this order
01What is this?
02Where does it belong?
03Can I access it?
Chapter 03 — Filtering

Start broad. Narrow when necessary.

Every result comes back first. Type narrows it, and only then do the filters that belong to that type appear — a learner filtering lessons never sees a question-type filter.

  1. 01All results, mixedThe default
  2. 02Narrow by typeCourses · Lessons · Questions · Posts
  3. 03Contextual filters appearOnly the ones that type supports
The filter presentation is a reconstruction of the filter model, not a claim about the shipped UI.
Shipped project

Search became a cross-product entry point.

Learners could retrieve information across multiple content types from a common search model instead of navigating each product surface independently. No success-rate, query-volume or time-saved figures are claimed.

This project taught me that discoverability improves when the system reflects what users remember — the information — rather than requiring them to remember the product hierarchy.

Have a complicated product problem?

Platform architecture, AI features, real-time systems, or a product that has grown more rules than anyone can hold in their head.

Or write it here

This opens your own email client with the message filled in. Nothing is sent or stored by this page.

Pragya Kumari — Product DesignerDiscovery · Information retrieval · 2026