Context
As customers published more stories, the dashboard became harder to navigate. Power users with 100+ stories struggled to find what they needed. The original card-based layout didn't scale.
How might we help users manage large libraries of content while keeping the dashboard approachable for new users?
Process
- Analyzed usage patterns to understand how people navigate their stories
- Interviewed heavy users about their organizational strategies
- Benchmarked content management UIs across CMS and DAM tools
- Designed and tested multiple view options (cards, list, table)
- Built filtering and search capabilities based on observed needs
Solution
A flexible dashboard with toggle between card and list views, powerful filtering by status/date/author, and improved search. Bulk actions let users manage multiple stories at once. The layout adapts to library size.
Outcomes
- Time to find specific stories reduced by 50%
- List view adopted by 60% of power users
- Support tickets about organization dropped significantly
Learnings
- Saved filters were more valuable than we anticipated
- Status indicators needed clearer visual hierarchy
- Empty states for filtered results needed helpful suggestions