IBM on assignment at Toyota
Overview
All Pricing features from Toyota's Supply Chain were being shifted and modernized to Toyota's Internal Cube Platform. This particular feature needed reorganization so power users can easily scan and manage incentive program Accounts with specific goals.
Below, I’ve adjusted the UI concepts and information to protect my client. While I can’t provide exact details, I’m confident my designs still communicate my skills as a Product Designer.
My Role: UX Designer
My Team: 1 CPO, 1 Tech PO, 2 SMEs, 1 PM, 2 UX Designers, 1 design director, 8 developers
I Owned: Wireframes, systems thinking, prototyping, user interviews
I Collaborated: Information architecture, requirements gathering, design reviews
Timeline: Jan 2026 – Present
I was asked to step in during the low-fidelity stage to finalize designing so Pricing's main UX designer could focus on other features. The ask was to make the final design cohesive and straight forward. I worked with the core pricing team to understand their users, business needs and scenarios. Our cross-functional team brought together diverse perspectives, from our product owner to the original legacy engineers. By collaborating closely, we ensured the new design preserved core legacy functionality while addressing user painpoints.
Snapshot of complexity from a single Requirements meeting
roadblocks in place:
This feature's information architecture had many different layers and multiple fragmented actions required by the user.
It was easy to get lost in the complexity of the data and hard to decipher what was happening at a glimpse.
There were many different stakeholders on the team from our Chief Program Officer to our core Pricing Team to our Technical Product Owners and they all had different opinions and preferences on layout.
Low-fidelity Pain Points
Landing Page
After much deliberation, we ultimately agreed that the landing page needed to be simple data table of all the Accounts and focused on high level summary information. This allowed users to see all the programs at a high level and easily expand each Account to see any exceptions.
series view page
Users requested to have a dedicated series view. This allowed them to easily see all Series and mapping of relevant Accounts for each of those Series.
Account Details Page
From the landing page users can click into a specific Account to see further details. There they can take all their actions to manage the Account details and values by the Series level.
Reduced the long learning curve for new users
Made the system less restrictive and rigid (10+ years old)
Harmonizing goals among diverse stakeholders.
As development progresses I will review and run QA testing across all development environments. I'll continue to iterate on the designed experience as dependent features are built and additional user testing occurs. Most notably, this landing page structure has set the standard for subsequent Pricing features — reaffirming our users value concise, summarized information and streamlined navigation.