case study

List page redesign

Context

This project focused on improving the main landing page of a facility/work management platform. The original design presented a flat table list of records, with basic filters and limited guidance. It served as a static table showing ongoing work and lacked the clarity and motivation needed for users to act effectively.

Outcome

Collaborated with cross-functional team to explore Recommendation Engine Solutions and provided the unique selling points at an early stage to increase organizational effectiveness for clients.

Role

Senior UX Designer

Led the end-to-end redesign: content restructuring, interaction flows, layout prioritization, and prototyping in collaboration with PMs and engineers.

Goal

Redesign the page from a passive browsing list making it easier for users to take meaningful steps and tasks - help to improve the Facilimity Manager working efficient and make sure the consistent performance to provide high quality service to clients.

The Problem

  • No clear user path: Users were overwhelmed by options with no guidance on what action to take next.

  • Flat information hierarchy: Every item looked equally important — no visual or behavioral cues to guide user attention.

  • No emotional or motivational triggers: The page lacked urgency, intention, or context — it didn’t answer “why now?” or “why me?”

  • The original experience failed to support the way users actually work:

    • Users had to scan manually for tasks needing attention — no prioritization or cues.

    • Summary metrics were disconnected from the list — users couldn’t click them to drill down or take action.

    • The page treated all items equally, regardless of urgency or status, forcing users to constantly triage on their own.

Design Approach

Key Shift: From “listing items” to “supporting intent.”

Instead of presenting what we have, we reframed the landing page around what the user wants to do.
Every section had to answer one question: “What action does this invite the user to take?”

Design strategies:

  • Group content by user motivation, not by internal categories

  • Use clear calls-to-action, visual signposts, and microcopy that invites interaction

  • Prioritize progressive disclosure — surface the most relevant next steps first

Design Strategy

We transformed the landing experience around two principles:

  1. Prioritize by state, not time
    → Bring critical task states (unassigned, paused, overdue) to the top as clickable summaries

  2. Make summaries actionable
    → Each metric became a filterable entry point into the table — allowing instant triage

Design Process

  1. Content Audit + Behavior Mapping

    • Reviewed the original list and tagged each item with its intent type (e.g., “learn more,” “take action,” “get inspired”)

    • Reorganized content into clear, user-centered sections

  2. Wireframing + Prototype Iterations

    • V1: Simply grouped items under new headers

    • V2: Embedded actions into each section (e.g., “Get started,” “Try now”)

    • V3: Focused on visual hierarchy — strong headlines, scannable blocks, emotion-evoking subcopy

  3. Usability Testing

    • Ran qualitative testing with lightweight prototypes

    • Users found their way to key actions 2× faster than with the original layout

    • Heatmaps showed increased engagement on new action zones

Final Design Highlights

  • Landing page evolved from a passive scroll to a layered action map

  • Used intent-based sections such as:

    • “Ready to explore?” → links to top destinations or ideas

    • “Need help getting started?” → tool or quiz

    • “For returning users” → personalized pathways

Before vs. After (Visual Example):

  • Before: Wall of items, no CTA

  • After: Distilled blocks with clear intent + interactive cues

Outcomes

  • Bounce rate dropped by 18%

  • Primary action clickthrough increased by 32%

  • Internal stakeholders adopted the new “intent-led layout” framework for other product pages

  • Qualitative user feedback: “Much easier to know where to start”

Reflections

  • Designing for behavior is more powerful than designing for content

  • The question isn’t “what should users see?” — it’s “what should users do next?”

  • Landing pages should function like a conversation, not a catalog