Pricing workflow redesign for Norwegian Cruise Lines

Outcome + Strategy

Making Pricing Logic Visible

By simplifying fragmented pricing workflows at Norwegian Cruise Lines, I reduced dashboard redundancy by 25% and made pricing decisions faster and easier to trust.

In 4 months, I redesigned workflows within tightly coupled systems—prioritizing decision clarity over raw visibility to support real-time pricing actions.

Decision Speed
+15%

Faster pricing resolution across workflows.

Workflow Redundancy
-25%

Reduced dashboard redundancy.

Delivery Timeline
4 mo.

Delivered redesign within complex constraints.

Collaboration

Product manager · Lead engineer · 2 UX designers · Data analytics team

My Role

Aligned product, engineering, and analytics teams around shared pricing logic—not dashboard outputs. Simplified fragmented workflows to support faster pricing decisions.

 

The Challenge

The Hard Part Was Deciding

Analysts had data—but no shared way to resolve conflicting pricing signals.

Pricing decisions varied across disconnected systems, making actions slower and harder to trust.

 

UX Research + Discovery

When Pricing Signals Stop Agreeing

Analysts compared multiple systems to determine which pricing signal to trust.

“You could get three different answers depending on which screen you looked at first.”
Pricing analyst workflow across fragmented systems
01 — Primary Friction

Fragmented Signals

Competing tools created conflicting pricing views.

02 — Workflow Behavior

Manual Reconciliation

Analysts compared screens to decide what to trust.

03 — Root Cause

No Shared Decision Logic

Teams lacked a shared model for resolving conflicting pricing signals.

This shifted the work from organizing screens to modeling decisions.

 

Logic Diagramming

Aligning System Behavior

Before redesigning the interface, I aligned product, engineering, and analytics around how conflicting pricing states should resolve.

Key Insight Defined decision rules before UI implementation.
Iteration
Final Model
Pricing logic diagram iteration Final pricing logic diagram
Reduced ambiguity

Replaced conflicting pricing interpretations with shared decision logic.

Aligned teams

Gave product, engineering, and analytics one model to work from.

Focused rollout

Prioritized high-frequency pricing behaviors before edge-case complexity.

 

Spreadsheet Prototyping

Testing Layout Priorities

Card sorting and workflow analysis helped identify which signals analysts relied on most.

I used spreadsheet prototypes to test hierarchy, scan patterns, and field prioritization before moving into high-fidelity designs.

Initial wireframe
Refined hierarchy
Initial spreadsheet prototype for pricing decisions Refined spreadsheet prototype for pricing decision hierarchy
01 — Decision Signal

Priority Fields First

High-frequency signals moved into the first scan zone.

02 — Legacy Constraint

Kept Familiar Fields

Legacy fields stayed visible to preserve analyst habits.

 

High-Fidelity Workflow

The After: Supporting Faster Pricing Decisions

Dashboard prototype interaction
 

Workflow Fragmentation

The Before: Disconnected Pricing Logic

Analysts stitched together pricing decisions across disconnected views.

Fragmented pricing workflow across disconnected views
Disconnected Views

Manual Reconciliation

Performance, urgency, and pricing signals lived across separate workflows and spreadsheets.

 
 

Outcome

Clearer pricing decisions in one workflow

“It’s well designed and pretty intuitive. It incorporates a lot of elements we are used to.”

Analysts previously reconciled pricing signals across fragmented tools.

I redesigned the workflow, unifying high-signal inputs into one experience—making pricing decisions faster, clearer, and easier to learn.

Decision Speed
-15%

Faster pricing decisions by reducing cross-tool reconciliation.

Workflow Value
8.8/10

Analysts rated the workflow highly for supporting pricing decisions.

Usability
9.2/10

Easier to learn through familiar patterns and clearer signal hierarchy.

Post-Prototype Testing

What I Refined Before Rollout

Testing showed which pricing signals needed faster visibility—and which regional logic could wait.

Pricing Visibility

Flag Pricing Risks

Analysts struggled to spot high-risk pricing changes quickly, so 30%+ price shifts were made easier to scan.

Rollout Strategy

Defer EU Pricing Complexity

EU pricing adjustments were deferred to keep the initial rollout focused and reduce scan complexity.

Reflection

Lessons From the Build

Building the workflow clarified which pricing behaviors mattered most—and which operational assumptions needed to evolve.

Key Learnings

Visualizing Relationships Early Reduced Ambiguity

Workflow diagrams aligned teams before implementation costs increased.

What I’d Do Differently

Prioritize High-Frequency Scenarios Sooner

Focusing earlier on repeated analyst behaviors reduced downstream churn.