Production
Loss
Accounting
AI design solution for B2B web software (2026)
Launched
2026
My role
Lead designer
Research/Testing
Product Strategy/Roadmap
Team
2 Product Managers
Technical Product Manager
Subject Expert Engineer
8+ Dev Engineers
OVERVIEW
Central dashboard for Admin users to track and recover the losses
Bridge the gap between operational performance and business results for business leaders by quickly identifying Target vs. Current production and converting it to financial losses.
PROBLEM & CHALLENEG
Hard to calculate losses, find the root cause, or take recovery action in product ecosytem.
As Cordant Suite software expanded, each module has separate, product-specific KPI dashboards. High-level administrators lack a unified view across departments, which limits their ability to recover losses effectively.
outcome & impact
This solution decreased 80% time for admins to get a comprehensive view
The result is faster decision-making, greater visibility, and improved alignment between operational activities and business priorities.
Solution workflows
How? Find losses fast, fix them faster
The result is faster decision-making, greater visibility, and improved alignment between operational activities and business priorities.
Define the top losses
View the root cause
Fix losses
Research
Fixing losses is not a new feature, but it is done in different ways and leading to a mess
"I usually jump between several apps to spot the major losses, assign them, and then track the performance over time."
- Admin user from interview
I started by reviewing each module's KPI dashboard to understand workflows and talk with users to identify overlapping user journeys. As I thought, recovery actions were duplicated across different applications for the same losses.
brainstorm
Exploration with AI defined 3 ways to handle losses
I used Claude to explore the solution. I narrowed it down to 3 possible solutions that aligned with business & users' goals, then discussed options with stakeholders along with the generated wireframes.
Option 1:
Connect what exists. A possible duplicate banner with a unified ID links to the same loss, and its status stays in sync within the apps.
Option 2:
One hub. The PLA app holds the full list of losses and all the recovery actions.
Option 3:
Build once, embed everywhere. All apps embed the same loss panel with the same data.
Stakeholder Conflicts
Product concept VS. design reality
As we aimed to build a centralized dashboard for business leaders, it makes sense to build one hub from a product perspective. However, embedding the same loss panel with the same data will break the original workflow in other apps. Not to mention, each product's licenses restrict the information users can access for different role-based personas.
Final solution - Key Feature 1
A high-level executive view with top losses
By surfacing these critical metrics, admin users can immediately assess the bottom-line impact, evaluate revenue implications, and seamlessly navigate deeper into the product suite to take corrective actions.
Final solution - Key Feature 2
A full list of action data syncs across the product ecosystem
With a full list view, users can customize the date period for specific events on the detailed losses page and track daily production. This empowers users to easily capture financial losses by each facility and identify high-cost breakdowns for loss recovery.
Final solution - Key Feature 3
No duplicated recovery action anymore
After identifying the root cause of losses, admin users can either use an existing action in the product ecosystem or create a new one for loss recovery.
