Cisco: Converged Collector
We started work and exploration on how we would completely redesign the data sources pages in the admin settings of the CX Cloud platform. This was a project I was really excited to work on as it had a lot of routes we could take it in.
Summary
Project Scope Expansion
Initially focused on revamping data collectors and interactions.
Expanded to include redesigning the data sources section.
Inspiration and Navigation
Explored various user interfaces for inspiration.
Leveraged unconventional sources (e.g., car HUD) and established UX patterns.
Prioritized user-friendly navigation while minimizing engineering workload.
Enhanced User Experience
Provided “at a glance” information for users.
Reduced the need for constant drilling down into details.
Considered scenarios with one collector and UI adaptations.
Data Collection Scheduling Integration
Merged data collection scheduling UI into the redesigned space.
Included flows for editing schedules.
Initially, the project was intended for just revamping how we show users their data collectors and the interactions they can take there. The data collectors were what you might think, just collections scheduled to gather data at various intervals. It was great that we were able to expand this to redesigning the data sources section.
Between myself and my lead product designer, I started looking through various user interfaces for potential inspiration. Sometimes unexpected places like the car hud/main display. Other times it was more conventional, like being able to utilize ux patterns established in the dashboard section of the CX Cloud platform.
We explored these venues and were able to come up with some good ideas for navigation while minimizing the workload we’d be asking for from our engineering teams - which was great! We were also able to give our users more “at a glance” information from a high level rather than expecting them to constantly drill down to finite details as we had more so in the previous designs.
We created multiple view scenarios that captured events like only having one collector, and how the UI would adapt to that and vice versa. We were also merging our data collection scheduling UI into this space, so we created versions of what that could look like. I included flows for when a user would go to edit a schedule as well.