↓ Problem
↓ Insight
↓ Idea
↓ Implement
↓ Impact
Holds Management Empowered Quality Compliance teams to initiate inspections, assess damage, manage hold status, and control downstream vehicle flow.
I led design for the Holds Management product, partnering closely with product owners and Quality Compliance leads to understand existing workflows, pain points, and tool usage. To ground our approach, I developed Level 3 process maps and facilitated co-creation workshops that aligned stakeholders around key moments of intervention.
This collaborative work shaped our MVP definition and informed a longer-term experience roadmap.
I led this capability from concept through delivery, creating UI patterns, event associations, and inspection workflows. These foundations later informed the design of Event Management.
Fig 1/3: From the shared vehicle list, Quality Compliance starts a Hold Group for affected units.
Fig 2/3: Coordinated inspections and repairs across regional service teams based on damage severity.
Fig 3/3: Locating and drilling into specific vehicles was made easier through various views.
This not only accelerated delivery but also ensured consistency across two high-stakes systems with different user groups—one focused on managing large-scale events like weather incidents, the other on controlling vehicle status and inspection downstream of those events. They were deeply intertwined, often detailing two sides of the same coin.
Event Management focused on providing greater context to all operational partners and enabled the creation of rule-based automations to streamline response and communication during high-impact scenarios.
I provided design direction and critique for this area, partnering with a senior designer to execute the user experience. We focused on rule-based automation and operational coordination during large-scale events.
Fig 1/4: Create and share key event details to align operational teams and downstream partners.
Fig 2/4: View real-time event impact, affected vehicles, and location insights in one place.
Fig 3/4: View real-time event impact, affected vehicles, and location insights in one place.
Fig 4/4: Combine vehicle and event conditions to trigger smart, rule-based automation.
To ensure usability, I introduced guided templates and AI-augmented preview states so users could simulate outcomes before triggering rules. We also surfaced data confidence indicators (e.g., ETA certainty levels) to help teams assess signal strength before acting.
3rd Party System Integration
Lastly, I coordinated efforts for my team to work closely with external dealer and distributor systems so that they could tap into the same data fabric and UI patterns, aligning external stakeholders (such as dealers and customer services) with Toyota’s internal operations.
Dealer tools like Dealer Daily adopted shared visual and semantic patterns to stay aligned with our internal systems.
These weren’t standalone features. Each one laid the foundation for Cube. Toyota’s new supply chain nerve center also became a tool for organizational alignment.
One platform, one story.