Client Platform
Cybersort.io
Role
Sole Product/ UX
Strategist
Year
2024
Team
2 Developers, 1 Product Manager
Overview
I was brought in as a solo strategist and designer to support an early-stage B2B SaaS platform, Cybersort.io, piloting with a global manufacturing company operating across 50 plant sites. The platform enabled engineers and project managers to map physical factory assets into digital assets in order to monitor and manage infrastructure more effectively.
While the product was already functional for a small pilot group, increasing volumes of asset data introduced new risks around clarity, consistency, and usability. My role focused on assessing the system holistically and adapting design patterns and workflows so the platform could scale beyond the pilot without adding unnecessary complexity.
Problem
As engineers and project managers worked with an increasing volume of data assets, everyday mapping and update tasks became harder to complete smoothly. Friction emerged around filtering, editing asset status, and keeping work moving as complexity grew.
Context: Company Insights
The platform was built on an existing component design system and was functional enough for engineers and project managers to begin mapping systems during the pilot. As asset data increased, the question became whether existing patterns and workflows would continue to support everyday work without introducing friction.
To understand the complexity of the work, I met with the founder to get a clear view of the current state of the company and platform — including product goals, user groups, technical infrastructure, and how the platform was being used.
Research Process
I began with a structured evaluation of the platform to identify where friction in mapping and updating assets would increase as data grew. Each issue was mapped to the required UX intervention, expected user value, and priority level.
I then validated these findings through conversations with engineers and project managers, supported by analytics and workflow testing in a sandboxed environment. This process clarified where users were slowing down and helped define clear success measures: improving task completion in asset management and increasing clarity of asset status.
Outcomes: Flow
Design work focused on reducing friction in high-frequency tasks such as filtering, updating asset status, and tracking progress as data volume increased. Existing patterns were refined to make interactions clearer, more predictable, and easier to repeat at scale.
Key adjustments included clarifying system states (default, error, success), tailoring core components to real workflows, and simplifying asset management through structured tables and filtering. These changes supported smoother task completion and clearer progress visibility across roles.
Working with the engineers to find flexibility in editing assets on daily basis and receive instant feedback on status. While, making sure that multi workflows don't create blindspots for the core user groups. The tabs allow Project Managers to easily access report information and follow-up with engineers who edited the assets.
Developing the Design System
I refined the existing design system to better support high-frequency asset workflows as data complexity increased and form a functional platform identity that could build trust.
Impact
+ Clearer asset status communication
System states (default, error, success) were clarified to reduce ambiguity during updates.
+ Smoother data mapping workflows
Filtering and structured table patterns reduced friction in high-frequency asset tasks.
+ Reusable workflow patterns
Core interaction patterns were refined to support repeated use as data volume increased.
+ Scalable foundation beyond pilot
Design adjustments positioned the platform to grow in data complexity without introducing unnecessary UI complexity.
Learnings
Diagnose before redesign
Structured evaluation helped separate software constraints from UX opportunities before making changes.
Design for repetition
High-frequency enterprise workflows benefit more from clarity and predictability than visual overhaul.
Align patterns to real work
Tailoring shared components to actual workflows improved usability without increasing system complexity