Pricing Simplified Across Fragmented Systems
Pricing decisions were slowed by fragmented dashboards and competing signals.
In 4 months, we:
Unified 2 dashboards into 1, reducing context-switching
Cut redundant information by 25%, focusing attention on decision-critical signals
Delivered a clearer, more actionable experience that rated 8.8/10 for value
My Role:
Led the redesign of pricing workflows across fragmented systems
Aligned product, engineering, and analytics on decision logic
Delivered a unified, test-validated pricing dashboard
The Challenge
How might we streamline how tours are priced across multiple internal tools?
Pricing analysts were piecing together decisions across four disconnected tools, increasing cognitive load and slowing pricing action.
I led the design to streamline how key pricing signals were surfaced on a unified dashboard.
The result: more confident decisions during time-sensitive booking calls.
Defining the problem
Research Findings: Inventory levels unknown
Analysts were struggling to reconcile conflicting signals across tools.
It made it hard to act to confidently act and answer key questions:
How well am I selling right now?
What should my ideal rate be?
Prototyping
Low Fidelity
Sketching out different layouts via spreadsheet allowed me to quickly test out variations in information hierarchy.
Logic Diagramming
Pricing actions carried edge cases and failure states.
Outlining the logic aligned product, engineering, and analytics on how these scenarios actually worked before defining the interface.
High fidelity
The prototype supports key actions—understanding metrics, exploring detail, and adjusting pricing in place.
Check performance → Assess urgency → Set rate
The After
The Before
Conceptual visualization created for this case study via Nano Banana Pro AI. Not an actual representation of analyst workflows.
Outcome
"It’s well designed and pretty intuitive. It incorporates a lot of elements we are used to.
Reduced redundant information by 25%, helping analysts focus on the most relevant pricing signals.
Performed well in user tests, indicating stronger clarity and confidence:
Value: 8.8/10
Usability 9.2/10
Iteration
We refined the design based on analysts’ feedback.
Adjustments included:
A toggle to show/hide nested tour packages
Visual indicators to mark price changes above 30%
These changes clarified how analysts changed pricing in bulk and interpreted large price shifts.
Key Learnings
Dashboards don’t need more data—they need to support a clear next action.
Edge cases aren’t exceptions in pricing systems, they’re part of the core experience.
Visualizing data relationships early prevents downstream misalignment.