The essentials of

The essentials of

The essentials of

AI Filters Update (Movers)

Duration: 12+ Months

Improving KPI tracking, task management, and navigation for users across the Workd CRM platform

20%

Task completion time

20%

Task completion time

20%

Task completion time

80%

Requested immediate release

80%

Requested immediate release

80%

Requested immediate release

15+

Client demos generated

15+

Client demos generated

15+

Client demos generated

  1. Project Overview

Setting an expectation

This project is less about stylistic UI and more about demonstrating my ability to solve complex UX problems at scale.

This project is less about stylistic UI and more about demonstrating my ability to solve complex UX problems at scale.

This project is less about stylistic UI and more about demonstrating my ability to solve complex UX problems at scale.

Role on Project

Lead Product Designer

Lead UX Researcher

Tools Used

Adobe XD

Figma

Miro

Jira

Microsoft Teams

ChatGPT

Team Members

Product Manager: Rafi Almhana

UI/UX Team Lead: Austin Holland

UI/UX Designer: Jesse Bruner

Business Analyst: Ryan Carroll

Project Summary

Who were the users?

The primary users were sales representatives and sales managers, primarily in the pharma sector, where quick and accurate access to data was essential for daily tasks.

What are Movers?

The Movers are an AI-powered filter system that helps users quickly sort, move, and manage large sets of data.

Why did they need an update?

The old experience was cluttered, inconsistent, and slowed workflows for both customers and internal users.

How did we solve the problem?

We simplified navigation, clarified filter logic, and rebuilt the interface to make it faster, more intuitive, and scalable.

  1. Discovery

Challenge statement

The old Movers feature wasn’t being utilized because it didn’t solve real user problems or fit into workflows.

Background

The AI Filters Update was built within the SupplyMover CRM to help sales teams complete their daily tasks faster and more efficiently.

Show more details

Show more details

Goals & Objectives

  • Improve user engagement with the Movers.

  • Enhance task prioritization and clarity.

  • Reduce task completion time and improve efficiency.

Constraints

  • Reliance on existing design system and components.

  • Limited client availability for testing and feedback.

  • Limitations from legacy system dependencies.

  • Conflicts from overlapping initiatives competing for resources.

  1. Research

We started with user interviews, focusing on daily workflows rather than just Movers, which revealed friction in prioritization, navigation, and efficiency.

A competitive analysis of platforms like HubSpot, Salesforce, and Monday.com highlighted best practices in task prioritization and navigation, showing how Movers could feel both familiar and unique.

User journey mapping with PM and BA uncovered delays and inefficiencies in navigation where users lost time.

From these efforts, clear pain points emerged: difficulty prioritizing tasks, poor KPI visibility, confusing navigation, and even lack of awareness that Movers existed.

Finally, through stakeholder alignment, we discovered even the internal team lacked a shared understanding of Movers — leading to a key outcome: redefining Movers as a task completion tool first, with KPI tracking as secondary.

  1. Ideation and Exploration

Early ideas tested tooltips, highlights, and icons to show why records appeared in a Mover, but these created clutter — leading to the decision that dedicated table columns were needed for transparency.

Through brainstorming sessions with the design team we created clear rules for when records should appear, and concepts like relocating Movers above tables as tab-like controls were pitched.

Using information architecture in Miro, we mapped current vs. ideal workflows, uncovering navigation inefficiencies and highlighting opportunities to streamline tasks.

Finally, user flows demonstrated how Movers could eliminate unnecessary steps and argued for major design changes, making the value proposition clear.

  1. Design & Prototyping

We began with initial designs, testing tooltips, highlights, and icons to explain why records appeared in Movers, but these approaches created clutter — leading to the decision that dedicated table columns were necessary for transparency.

From there, high-fidelity mockups redefined Movers as tab-like filters above tables, introduced a dual-column approach (“why it’s here” + “what action to take”), and differentiated static vs. dynamic columns.

Finally, prototypes built in Adobe XD simulated the redesigned Movers on the Clients page, where user testing showed strong adoption and minimal need for changes.

  1. Testing & Iteration

We created task-based usability tests with prototypes and ran them with Sales Reps and Managers, observing faster task completion, improved clarity, and stronger confidence.

Testing confirmed that transparency was the key factor for adoption, that users needed explicit task guidance rather than just explanations, and that the dual-column design validated the new definition of Movers.

Earlier iterations with tooltips and highlights exposed clutter and hidden key info, reinforcing the need for the dedicated column approach that ultimately drove adoption.

  1. Final Solution

UI Showcase

Problem Resolution

Problem:

Users didn’t know why records were included in Movers.

Problem:

Users didn’t know why records were included in Movers.

Solution:

Added dedicated “why it’s here” columns to every Mover view for complete transparency.

Solution:

Added dedicated “why it’s here” columns to every Mover view for complete transparency.

Show more details

Show more details

Problem:

Users had no clear path forward once records appeared.

Problem:

Users had no clear path forward once records appeared.

Solution:

Added actionable columns to show exactly what task needed to be completed to remove the record from Movers.

Solution:

Added actionable columns to show exactly what task needed to be completed to remove the record from Movers.

Show more details

Show more details

Problem:

Placing Movers inside tables blurred their role, making them feel like basic filters instead of a higher-level task navigation tool.

Problem:

Placing Movers inside tables blurred their role, making them feel like basic filters instead of a higher-level task navigation tool.

Solution:

Relocated Movers above tables to improve hierarchy and styled them as familiar tab-like controls for easier adoption.

Solution:

Relocated Movers above tables to improve hierarchy and styled them as familiar tab-like controls for easier adoption.

Show more details

Show more details

Problem:

Movers lacked consistency in visibility rules, leaving users unsure which Movers should always be present and which only appeared in special conditions.

Problem:

Movers lacked consistency in visibility rules, leaving users unsure which Movers should always be present and which only appeared in special conditions.

Solution:

Defined rules for static Movers (always visible, even if empty, to confirm cleared tasks) and dynamic Movers (only appear when records meet their conditions, like “At Risk” or “Warning”).

Solution:

Defined rules for static Movers (always visible, even if empty, to confirm cleared tasks) and dynamic Movers (only appear when records meet their conditions, like “At Risk” or “Warning”).

Show more details

Show more details

Problem:

Records lost all Mover context once users drilled into detail views.

Problem:

Records lost all Mover context once users drilled into detail views.

Solution:

Introduced priority-organized Mover tags on record detail pages to maintain visibility across the workflow.

Solution:

Introduced priority-organized Mover tags on record detail pages to maintain visibility across the workflow.

Show more details

Show more details

Problem:

Boolean-style Movers (like “New”) didn’t fit the new definition but were still needed.

Problem:

Boolean-style Movers (like “New”) didn’t fit the new definition but were still needed.

Solution:

Converted these into stackable smart boolean filters, available within tables but separate from Movers.

Solution:

Converted these into stackable smart boolean filters, available within tables but separate from Movers.

Show more details

Show more details

Problem:

Movers were inconsistently defined internally, leading to unclear design direction.

Problem:

Movers were inconsistently defined internally, leading to unclear design direction.

Solution:

Aligned stakeholders on a single definition: Movers are a task completion tool first, with KPI tracking as secondary.

Solution:

Aligned stakeholders on a single definition: Movers are a task completion tool first, with KPI tracking as secondary.

Show more details

Show more details

  1. Design Handoff

Implementation Phases

Because the Movers Revamp was an internal initiative and not directly funded by client work, development resources were limited and had to be balanced alongside client projects.

To make the redesign achievable, I broke the rollout into clear phases. Each phase delivered incremental value to users while keeping the workload manageable for the development team. This approach allowed us to release an MVP quickly, gather feedback, and gradually build toward the full vision.

Phase 1

Phase 1

Phase 2

Phase 2

Phase 3

Phase 3

Design System Documentation

New components that were documented and added to the the design system.

  • New Movers tab components

  • Updated table column patterns

  • Mover tag system in record details

  • Smart boolean filters

  • Static vs. dynamic Mover states

  • Interaction rules and constraints

  1. Results & Impact

Business Impact

  • Improved efficiency by 20% for Sales Reps and Managers.

  • Increased client interest and contract extension discussions.

  • Generated 15+ new client demos

Show more details

Show more details

User Feedback

  • 80% of testers requested immediate release of the update

  • Sales Reps and Managers emphasized that it would ease their workload on a daily basis.

  • 100% of users asked when the redesign would be available in production.

Show more details

Show more details

  1. Learnings & Next Steps

What Worked Well

User testing validated design decisions

Transparency is the most important factor for adoption

Transparency is the most important factor for adoption

Advocating for user-centered design built trust

Users need explicit task guidance, not just explanations

Users need explicit task guidance, not just explanations

Phased implementation improved rollout strategy

Dual-column design validated the new definition of Movers

Dual-column design validated the new definition of Movers

What to Improve

Lack of a centralized Information Architecture

Transparency is the most important factor for adoption

Transparency is the most important factor for adoption

Internal project = lower priority

Users need explicit task guidance, not just explanations

Users need explicit task guidance, not just explanations

Limited user touchpoints

Dual-column design validated the new definition of Movers

Dual-column design validated the new definition of Movers

Future Opportunities

  • Create a living Information Architecture for the entire system.

  • Improve personal documentation processes for smoother handoff.

  • Bring on a dedicated UX Researcher to improve user engagement.

Contact

JustinLJuco@gmail.com

https://www.linkedin.com/in/jjuco/

https://tinyurl.com/y3rn45xh

Contact

JustinLJuco@gmail.com

https://www.linkedin.com/in/jjuco/

https://tinyurl.com/y3rn45xh