Case Study · Content Discovery

Inspiring Feed

Redesigning Picsart's Browse page for a shifting user base, from an undifferentiated feed to a personalized, research-validated discovery experience for creators and prosumers.

Senior Product Designer · Solo Picsart iOS · Android · Web 2024
UNDERSTAND What users value Who the feed serves RESEARCH 4 structured cycles Value · Layout · Personalization DESIGN 3 testable prototypes Architecture decisions VALIDATE User tested Handed to engineering
At a Glance
Company Picsart
Product Browse — Inspiring Feed
My Role Senior Product Designer · Research · IA · Interaction design · Validation
Platform iOS · Android · Web
Timeline 2024
Users Consumers and prosumers (solopreneurs, small businesses, marketers)
Key Decision One-column feed with two-tab navigation, chosen after testing three layouts with six users
Outcome Design validated across four research cycles · Prototypes advanced to A/B testing
Why This Mattered
Problem

Picsart's prosumer segment was growing, but the Browse page hadn't been updated to reflect that. The gap between the audience Picsart was building toward and the experience the feed was designed for was a product strategy problem, not just a design one.

My Contribution

As the sole designer, I ran four structured research cycles end to end, from unmoderated value interviews to prototype testing with six users, then redesigned the full feed architecture, content tagging system, and personalization model.

Outcome

A research-validated feed redesign with a documented rationale for every decision. Prototypes advanced to A/B testing. A prior shift to one-column layout had already shown a meaningful increase in Time-to-Image engagement in Picsart's own product data.

The Work
One feed. Three structural problems solved.
Final Designs · Problem Discovery · Research Findings
Click above for more detail
Inspiring and Following tab navigation on Picsart Browse
Navigation
Two-tab structure separating curated discovery from social following
One-column Picsart feed with content type tags
Feed Architecture
One-column feed with content tags and calibrated carousel frequency
Personalized carousel and multi-action CTA design
Web Assets
Curated collection of content to help users move from inspiration to creation
Success Criteria · Outcomes

The goals I set and what I delivered

I left Picsart at the end of this project, so I don't have post-launch metrics. What I have is a clear record of what was validated and what was handed off.

Feed architecture validated

One-column, two-tab structure tested with users and confirmed through Cycle 2 testing and existing behavioral data.

Every decision traces to evidence

No decision in this redesign came from a preference or a stakeholder opinion. Each one connects to a specific research finding.

Prosumer relevance addressed

Feed architecture, content tagging, and personalized carousels designed for the professional user segment Picsart was growing toward.

Creative tools surfaced in-feed

Multi-action CTA puts Remix, Try, and Edit in front of users during browsing, not buried two taps away.

Prototypes advanced to A/B testing

Validated designs handed to engineering as A/B test candidates. Live measurement happened after my tenure.

One data point from before this redesign is worth noting. Picsart's own analytics showed a meaningful increase in Time-to-Image engagement after a prior shift from two-column to one-column layout, with minimal impact on editor opens. That data informed the layout decision but didn't solely determine it.

  • Feed architecture tested and validated across four research cycles
  • Layout decision supported by user preference data and existing behavioral analytics
  • Personalization model validated — balance of relevance and serendipity confirmed with users
  • Creative action visibility addressed through multi-action CTA design
  • Content tagging designed to make feed logic transparent and trustworthy
  • Prototypes handed to engineering as A/B testing candidates
Final Designs

The redesigned feed

Click to enlarge
Design walkthroughs
Feed architecture — navigation, layout, and content tagging
Personalization system and multi-action CTA
Design Principles

What I held to across every decision

🎯

Relevance over volume

A feed that shows less but shows the right content is more useful than one that surfaces everything. Fewer, better-matched items beat more items on every metric that matters.

🔍

Separation creates clarity

Different content types serve different intentions. The mistake in previous versions was separating by asset type. The right separation is by user goal.

Creative actions are first-class

Picsart isn't a mood board. Remix, Try, and Edit are what make it different from a social feed. The Browse page should surface those actions, not bury them.

🌱

Personalization must include serendipity

Users want their interests reflected. They also want to be surprised. A feed that only shows what someone already likes gets boring fast.

🔄

Freshness is a trust signal

Seeing the same content in top positions for weeks tells users the system is broken. Recency and rotation aren't nice-to-haves — they're the minimum.

Problem Discovery

The audience had shifted. The product hadn't.

Picsart built its Browse experience for consumers looking for visual inspiration. By 2024, the platform's growth was shifting toward prosumers, solopreneurs, small business owners, and marketers who came with fundamentally different browsing intent. The feed hadn't been designed for that difference.

Previous attempts to address this had missed the root cause. Separating content by asset type addressed format, not intent. Gross engagement signals surfaced what was broadly popular, not what was relevant to a specific segment. Both approaches treated the feed as a single-audience product.

4
Research cycles completed
6
Users tested across 3 prototypes
3
Prototypes evaluated in layout testing
5
Architecture decisions, each validated through research

What was breaking

Before the redesign
  • Undifferentiated feed mixing algorithmic and social content with no separation of intent
  • Two-column layout with frequent carousels, crowded and hard to focus on
  • No content type labels — users couldn't tell why something appeared in their feed
  • Generic carousels with no connection to user preferences or past behavior
  • Save was the only prominent action; Remix, Replay, and Try were invisible
  • Remix, Replay, and Regenerate were confusing or unnoticed by new users
After the redesign
  • Two tabs (Inspiring and Following) separating discovery from the social feed
  • One-column feed with calibrated carousel frequency, four content pieces between each carousel
  • Content tags (popular, suggested, for you) making ranking logic visible
  • Personalized carousels matched to onboarding preferences and past behavior
  • Multi-action CTA surfacing Try, Edit, and Remix alongside Save
  • Replay, Remix, and Regenerate surfaced in-feed with enough context to be understood
Research Findings

What four research cycles revealed

I ran research in tight, focused cycles not one large study, but four rounds each answering a specific question. These are the findings that shaped the most important decisions.

1

Prosumers and consumers browse with different intentions

Talking to users made the split obvious fast. Consumers browsed broadly — scrolling until something caught their eye, saving it, moving on. Prosumers came with a job to do. They were looking for a template, a style direction, something they could actually use for a project. When the feed couldn't surface that, they stopped scrolling. The same interface was working fine for one group and actively frustrating the other.

2

Users wanted to know why content appeared

When content felt arbitrary or off-topic, users lost trust in the feed fast. A simple signal like "suggested" or "for you" was enough to reset that. It didn't need to explain the algorithm — just acknowledge that one existed.

3

Full personalization would kill discovery

In the Spaces community research, users were clear that a fully personalized feed would get boring. They wanted content tuned to their interests alongside content that surprised them. Pure relevance without variety removes the reason to browse. What surprised me most was that users didn't want maximum personalization. They wanted relevance, but they also wanted discovery.

4

Carousels created friction at the wrong frequency

Carousels were valued for variety — seeing creators, communities, and templates in one row. But appearing too often, they broke the scroll rhythm. Solopreneurs especially found them distracting when they showed up back to back with content cards.

5

Creative actions were Picsart's differentiator, and the feed wasn't showing them

When users encountered Try, Edit, and Remix in the layout prototypes, they used them. A save-only CTA had trained users to treat Picsart like a passive mood board. Surfacing creative actions in the feed reframed it as a starting point for creation.

Research Process

Four cycles. One direction.

Each research cycle was designed to answer a single question. I worked alongside research partner Dr. Charlotte Pyatt-Downes across multiple cycles.

Cycle 1 — Value
  • Unmoderated interviews
  • Goal: Understand what users find genuinely valuable in the Browse feed
  • Identified high-value content categories for different user segments
  • Mapped the gap between what the feed surfaced and what prosumers actually needed
Cycle 2 — Layout
  • Unmoderated testing with 6 users (3 solopreneurs, 3 consumers)
  • 3 prototypes tested: two-column feed, one-column with two tabs, one-column with one tab
  • Goal: Find the layout that's most usable for content discovery
  • 5 of 6 users preferred two tabs · All preferred one-column over two-column
Cycle 3 — Personalization
  • Moderated interviews with the Picsart Spaces community
  • Users created collages of their ideal feed and discussed via comments
  • Goal: Find the right level of personalization — and how much serendipity to protect
  • Finding: users want their interests reflected, but not a mirror — variety matters
Final Evaluation
  • Unmoderated user testing
  • Evaluated how well the design drove the behaviors the KRs targeted
  • Produced validated concepts handed to engineering as A/B candidates
Research · Layout Testing

Three layouts. One winner.

Cycle 2 tested three distinct prototypes with six users (three solopreneurs and three consumers). The differences weren't cosmetic. Each prototype represented a real structural decision.

Click to enlarge
Prototype recordings
Prototype 1 — two-column feed with two tabs
Prototype 2 — one-column feed with two tabs
Prototype 3 — one-column feed with one tab
Key Decisions

Three decisions that shaped the feed

Each decision had a real alternative I tested. I didn't reject options because they felt wrong, I rejected them because the research made the right answer visible.

Decision 1: One-column vs. two-column feed

Should the feed show more content at once, or focus users on one piece at a time?

Option A · Rejected
Two-column feed with carousels
Pros
  • Higher content density per scroll
  • Familiar pattern from other platforms
Cons
  • Combined with carousels, the layout felt crowded and hard to focus on
  • Users couldn't give full attention to any single piece of content
  • Prior Picsart product data already showed a one-column layout performed better on Time-to-Image engagement
Option B · Chosen
One-column feed with calibrated carousel placement
Pros
  • Users can focus on one piece of content at a time
  • Cleaner scroll rhythm with four content pieces between each carousel
  • Consistent with existing behavioral evidence from Picsart's own analytics
Cons
  • Lower content density per scroll
How I reached this decision

Layout testing in Cycle 2 was the deciding input. Six users tested three different layouts. The combination of their stated preferences, the crowding problem at carousel intersections, and Picsart's own analytics data from a prior layout switch made the one-column choice clear.

Decision 2: Two-tab navigation vs. single combined feed

Should Inspiring and Following content share one feed, or live in separate tabs?

Option A · Rejected
Single combined feed
Pros
  • Simpler surface to design and maintain
  • More content visible without switching tabs
Cons
  • Algorithmic and social content serve different user intentions — mixing them created confusion
  • Previous mixed feeds at Picsart had not worked
  • Consumers and solopreneurs have distinct browsing modes they don't want combined
Option B · Chosen
Two tabs (Inspiring and Following)
Pros
  • 5 of 6 users in layout testing preferred two tabs, without prompting
  • Separation was by intent (discovery vs. following), not by asset type, which was what had failed before
  • Both user segments described wanting a clear switch between browsing modes
Cons
  • More navigation surface to design
  • Risk of users missing one tab entirely
How I reached this decision

The preference signal from testing was strong and consistent. What made it easy to commit was understanding why users wanted the separation. It wasn't about content type. It was about cognitive mode. When they opened the feed to get inspired, they didn't want to be pulled into the social layer. That distinction had been missed in previous approaches.

Decision 3: Multi-action CTA vs. save-only

Should the feed surface creative actions (Remix, Try, Edit) inline, or keep a single save CTA?

Option A · Rejected
Save-only CTA
Pros
  • Simple and familiar
  • Less cognitive load per card
Cons
  • Reinforces Picsart as a passive mood board rather than a creative tool
  • Hides the capabilities (Remix, Replay, Regenerate) that differentiate the platform
  • Prototype testing showed users reached for creative actions when they were surfaced
Option B · Chosen
Multi-action CTA with creative actions and save
Pros
  • Surfaces Picsart's differentiators at the moment of inspiration, not buried in menus
  • Users in testing used Try and Edit when they appeared as options
  • Reframes Browse from "save things" to "start creating"
Cons
  • More visual complexity per card
  • "Remix" label still caused confusion in testing — copy work still needed
How I reached this decision

The prototype testing made the gap obvious. Users described Picsart as a creative app, not a browsing app. But the save-only CTA was treating them like passive consumers. When creative actions appeared on the card, users reached for them. That was enough.

The Solution

What changed and why it mattered

Each design decision connects directly to a documented user problem.

Feature Problem it solved Outcome
Feature
Two-tab navigation (Inspiring + Following)
Problem

Algorithmic and social content served different user intentions but lived in one undifferentiated feed

Outcome

Clear separation by intent — curated discovery in Inspiring, creator and community content in Following

Feature
One-column feed
Problem

Two-column layout combined with frequent carousels felt crowded and prevented content focus

Outcome

One piece of content at a time, with a cleaner scroll rhythm and stronger focus per card

Feature
Content tagging (popular · suggested · for you)
Problem

Users couldn't tell why content appeared — felt arbitrary and eroded trust in the feed

Outcome

Transparent ranking signals help users calibrate what the feed is doing and why

Feature
Personalized carousels
Problem

Carousels were generic and unrelated to user preferences, making them feel like filler

Outcome

Carousels matched to onboarding preferences and past behavior — relevant communities, templates, and creators

Feature
Multi-action CTA
Problem

Save was the only prominent action; Remix, Try, and Edit were buried or unknown

Outcome

Creative capabilities surfaced inline, turning browsing into an entry point for creation

Validation

How each direction was tested before advancing

Every major decision was tested before it moved forward. I didn't present a single direction and ask for sign-off.

Unmoderated value interviews (Cycle 1)
Unmoderated layout testing — 3 prototypes with 6 users (Cycle 2)
Moderated community interviews — Spaces collage exercise (Cycle 3)
Behavioral analytics via Picsart Looker (existing product data)
Hotjar session analysis
Unmoderated final evaluation producing A/B candidates

Research partner Dr. Charlotte Pyatt-Downes collaborated across multiple cycles, contributing to research design and analysis in Cycles 2 and 3.

Reflection

What I'd do differently

The hardest part of this project wasn't the design. It was designing for an audience that was still arriving. Picsart's prosumer base was growing, but the product analytics were still weighted toward the existing consumer majority. Making decisions for a future user segment, against data that reflected the past, meant leaning heavily on qualitative research when the numbers were telling a different story.

Four research cycles sounds like a lot. But each one was tight and targeted, designed to answer one question and move on. That cadence worked well, and it's something I'd bring to any content-heavy design problem. Waiting for certainty before testing is almost always slower than testing early and adjusting.

The one thing I'd push harder on is the learnability cycle (Cycle 4). Feature discovery for Remix and Replay was identified as a problem early. The multi-action CTA addressed visibility, but the deeper question — how do users come to understand what these features actually do — was never formally tested. That's the loose end I'd tie off first.

What I Learned

Tools & Methods

Figma Hotjar Looker Miro Loom Unmoderated user testing Moderated interviews Community co-design (Spaces collage exercise)