
01
❋
The Problem
❋

The Current Product
Looking at the current product, the opportunities were clear; there were many issues, contributing to sense of overwhelm and tedium sales reps face when using the product.
The CPQ team was currently working on overhauling the product selection and quoting experience in CPQ, so the internship came at right time for me to play a part in this new vision for the product.
03
❋
Research
❋
Research Method
Rather than conducting new interviews, I reviewed the existing extensive research Jo Yung↗ conducted with sales reps across industries—from selling softwares to forklifts—using Oracle CPQ. Research methods included semi-structured interviews and think-aloud testings sessions.
Key Insights from Sales Reps
①
②
③
↓
Supporting statements from user research
Getting Close to the Sales Process
I had no enterprise sales background going in, so before sketching a single screen, I needed to understand how reps actually work.
I interviewed 9 members across the Oracle CX team: both product experts and those working directly with sales reps. Together, they helped me map the full sales process from first contact to closed deal.


How Current Products Fail
to Address Needs
Looking at the 6 leading CPQ products, I observed that they use the same UX pattern for product selection. This “questionnaire” design doesn’t address the needs discovered:
①
Answering many sets of questions is as tedious as browsing the whole product catalog itself
②
Reps still need to do the mental work of translating needs into product specs
04
❋
Design Process
❋
The research findings shaped a clear design goal. The statement serves as a north star that guided my every decision from brainstorming early concepts to final wireframes.
Project’s Criteria for Success
❶
Reps are able to identify buyer needs correctly with less time and effort
❷
Reps express confidence that recommendations match buyer needs

From Texts to Visuals
Moving away from text summary to generated interactive UI components and data visualizations makes the design more engaging




Verify Sources Before Committing
In the earlier versions, there was no way to check what the AI actually read. The final design shows a summary of each source, so reps can confirm relevance before anything gets generated.
05
❋
Reflection
❋
①
Testing with Sales Reps
②
Focus on “On-Call” Guidance
③
Build Out Product Sharing Workflow






