Independent product case study · September 2026

Finding an Instagram save
shouldn’t depend on luck.

I explored how frequent Instagram users recover posts they saved for later, identified a mismatch between what people remember and how Saved is organized, and designed a natural-language search concept to close that gap.

7
semi-structured interviews
2–15 min
reported retrieval attempts
1
focused MVP concept
0
claims of shipped impact

People save by tapping.
They retrieve by remembering.

Frequent savers often remember what a post contained—an outfit color, a recipe technique, a destination, or why they wanted it—but not the creator, caption, date, or collection.

Without search inside Saved, the fallback is visual scanning across a growing, inconsistently organized archive.

How might we help frequent savers recover a post using the clues they naturally remember?

Small sample, consistent signal.

I interviewed seven frequent Instagram users about the last time they tried to recover a saved post. I asked what they remembered, how they searched, whether they succeeded, and how they organized Saved.

01

Memory is semantic, not chronological

Participants remembered clues such as “one-pot pasta,” “blue saree,” or “rooftop restaurant”—but rarely the creator or exact date.

02

Collections only partially solve retrieval

Collections were broad, inconsistent, or skipped because choosing one added effort at save time. Several people searched more than one collection.

03

Scrolling creates a real abandonment point

Observed recall attempts ranged from about 2 to 15 minutes. Several participants could not recover the post or said they would stop after a few minutes.

What people remembered versus what the interface supported

Saved itemRecall cueOutcome
RecipeTopic + cooking methodNot found after 3–5 min
RestaurantPlace + visual appearanceFound after 10–15 min
OutfitBlue sareeNot found after 2 min
Movie reelCrime-thriller topicSearched for 3–4 min

Directionally useful, not statistically representative. Participants were a convenience sample, and timings were self-reported.

Improve retrieval before adding more organization.

I considered nested collections, automatic organization, favorites, and semantic search. Nested collections may help people who maintain a system, but the research showed the bigger mismatch occurs when users do not remember where—or whether—they organized a post.

PrioritizedNatural-language search across Saved

Matches the clues users already recall and works across collections.

LaterNested collections

Useful for organization-heavy users, but adds structure without fixing retrieval across the full archive.

Search Saved using the details people remember.

A search entry point inside Saved interprets descriptive queries across available signals such as captions, reel transcripts, creator metadata, collection names, and visual concepts.

1Open Saved

A visible search field appears above collections.

2Describe the post

For example, “pastel blue mirror-work lehenga.”

3Review ranked results

Results can be filtered by post, reel, creator, or collection.

Explore the retrieval flow

The prototype demonstrates the intended path and a representative query. It is a concept prototype, not a production Instagram feature.

Launch prototype ↗

Measure retrieval—not search-box activity.

Primary outcome

Saved-item retrieval success

% of retrieval tasks where a user opens the intended saved item.

Efficiency

Median time to intended item

Time from entering Saved to opening the target post.

Diagnostic

No-result and reformulation rate

Shows when search fails to understand a user’s recall cues.

Guardrail

Search abandonment

Ensures the feature does not merely replace scrolling with another frustrating path.

Validate usefulness before increasing scope.

  1. Usability testGive participants realistic retrieval tasks and compare search against the current scrolling path.
  2. Test relevanceMeasure success across visual, topical, creator, and time-based queries.
  3. Protect privacyKeep queries scoped to a person’s own Saved archive and explain which signals support matching.
  4. Explore structure laterEvaluate nested collections only after confirming the retrieval MVP solves the higher-frequency pain point.