PROS Data Management Redesign

From Upload Tool to Operations Platform

Figma

Design Tokens

SaaS

PROS provides revenue management and pricing optimization software serving industries from airlines to manufacturing. At the heart of their platform is a data management application where customers upload datasets to power pricing algorithms and business intelligence across the PROS ecosystem. In early 2024, I led the complete redesign of this critical application, transforming it from a basic file upload tool into a comprehensive data operations platform with AI-assisted workflows.

Dec 18, 2025

Green Fern
Green Fern
Green Fern
Role

Lead UI Designer

Lead UI Designer

Lead UI Designer

Team

1 PM, 1 Frontend Developer, 1 UX Strategist and 1 Lead Ui Designer (myself)

1 PM, 1 Frontend Developer, 1 UX Strategist and 1 Lead Ui Designer (myself)

Timeline

January - October 2024 (Phase 1 Full Handoff Q3-Q4 2024)

January - October 2024 (Phase 1 Full Handoff Q3-Q4 2024)

Key Achievement

Phase 1 Handoff to dev team, validated by continued Phase 2 investment

Phase 1 Handoff to dev team, validated by continued Phase 2 investment

The Challenge

The original application consisted of just two simple cards: "Upload" and "Data Tracking". While functional, it created significant friction for users:

Core Problems

Manual Repetitive Work

  • Users had to manually map dataset fields to PROS schema every single time they uploaded data

  • Even identical datasets required full re-mapping on subsequent uploads

  • No learning or pattern recognition between sessions

Limited Visibility

  • No dashboard showing dataset health or status

  • No way to track data lifecycle from upload to processing

  • Minimal insight into validation errors or data quality issues

No Collaboration

  • No ability to share datasets between team members

  • No task management for data operations

  • No access control or permission systems

Inefficient Workflows

  • No batch upload capabilities

  • Limited error handling and recovery

  • No historical audit trail

The business impact was clear: customers were spending excessive time on data operations instead of using PROS insights to make strategic pricing decisions.

My Approach

Cross-Functional Team Structure

I worked in a tightly integrated team with weekly validation cycles:

  • Product Manager: Provided requirements and business context

  • UX Strategist: Validated design decisions and user flows

  • Frontend Developer: Ensured technical feasibility

  • Myself: Led UI design, information architecture, and system logic definition


Iterative Design Process

I organized our Figma workspace by quarter (Q1-Q4 2024), with each sprint producing weekly design iterations. This allowed us to:

  • Track design evolution over 9+ months

  • Reference previous decisions during reviews

  • Maintain transparent progress for stakeholders

  • Enable real-time collaboration (visible multiplayer cursors in our workspace)


Design System Integration

All work leveraged the KIT design system in Figma and Pillar component library I was simultaneously leading, ensuring consistency across PROS applications and 95% design-to-code fidelity.

The solution

I reconceptualized the entire application from a simple upload tool into a comprehensive data operations platform with four major feature areas:

1. Dashboard Transformation

Before: Two basic cards with no context or task visibility

After: A command center providing:

  • Task Management - Pending validations, mapping approvals, workflow steps

  • Dataset Access - Quick access to frequently used datasets with status indicators

  • Collaboration - Share datasets with team members, manage permissions

  • Status Visibility - Color-coded health indicators (green/yellow/red) for all datasets

  • Contextual Actions - Direct access to relevant operations without deep navigation

The dashboard became the central hub where users could see what needed attention, access critical datasets, and collaborate with colleagues.

2. AI-Assisted Dataset Mapping

This was the flagship innovation solving the manual mapping problem:

First-Time Upload Flow
  1. User uploads a new dataset structure

  2. AI analyzes the data and suggests field mappings based on:

    • Field names and semantic meaning

    • Data types and formats

    • Historical patterns from similar datasets

    • PROS schema requirements

  3. User reviews AI suggestions with confidence indicators

  4. User confirms or adjusts mappings

  5. System learns from corrections to improve future suggestions

Pattern Recognition Flow
  1. User uploads data matching a previously mapped structure

  2. System automatically recognizes the pattern

  3. Stored mapping is applied instantly

  4. User verifies rather than re-mapping from scratch

  5. Massive time savings for recurring imports

Complex Scenarios Handled
  • Partial matches - 80% matches known pattern, 20% new fields

  • Confidence scoring - Visual indicators show AI certainty

  • Conflict resolution - Multiple possible mappings for ambiguous fields

  • User learning loop - Corrections improve future AI performance

  • Validation rules - Ensures mapped data meets platform requirements

I collaborated closely with the PM to define the complete mapping logic, which was documented in Confluence, specifying system behavior, edge cases, and validation rules for the development team.

3. Upload & Validation Flow

I designed a comprehensive workflow handling:

  • File upload initiation with drag-and-drop or file picker

  • Format validation - Multiple checkpoints with clear error messages

  • Data quality checks - Real-time validation as data is processed

  • Error recovery paths - Users can fix issues without starting over

  • Mapping interface integration - Seamless transition to AI-assisted mapping

  • Success confirmation - Clear completion states with next actions

The flow included multiple decision points, branching logic, and recovery mechanisms documented in detailed flowcharts.

4. Data Tracking & Management

Data Tracking Page: Monitor ongoing operations

  • Batch upload tracking - See all files uploaded in last 30 days

  • Status visualization - Green (success), red (error), yellow (warning)

  • File-level details - Drill down into individual files within batches

  • Complete history - Full audit trail of data operations

  • Download functionality - Retrieve processed files when needed

Datasets List Page: Organize and access data

  • Comprehensive table view with filtering and sorting

  • Status indicators showing dataset health

  • Quick inspection panel for dataset details

  • Bulk operations for efficient management

  • Search and organization tools

Design Process

Figma Organization

I structured the Figma file for maximum team collaboration:

Pages Structure:

  • Welcome - Project overview and navigation

  • Visual Designs - Date-stamped iterations (April 2024 → July 2025)

  • UX Checkpoint - Formal review gate with UX strategist

  • Workspace - Active design work organized by quarter

  • Storyboard - User journey mapping

  • Vision - Product direction documentation

  • Personas - User research artifacts

  • Inspiration - Design exploration

  • Components - Reusable UI patterns


Workspace Activity

The workspace showed intense collaboration:

  • Q1 2024: Initial explorations and concept validation

  • Q2 2024: Massive activity - core redesign work (20+ frames with multiplayer activity)

  • Q3 2024: Refinement and production preparation

  • Q4 2024: Final iterations leading to Phase 1 delivery


Multiple team members (visible by colored cursor circles: K, A, M) were actively reviewing designs simultaneously, enabling real-time feedback loops rather than static handoffs.

Iteration Cycles

Each week produced new design iterations clearly labeled (W38-2024, W44-2024), showing:

  • Rapid refinement based on feedback

  • Progressive complexity as requirements clarified

  • Evidence of testing and validation

  • Evolution toward final production state


Influencing Product Direction

I didn't just execute designs - I helped shape the product strategy:

  • Identified the AI mapping opportunity as the key innovation to eliminate manual work

  • Proposed the dashboard transformation to serve as operations command center

  • Advocated for collaboration features to support team-based workflows

  • Defined system behavior through detailed Confluence documentation


Cross-Functional Coordination

Weekly validation cycles with PM and UX strategist ensured alignment:

  • PM validated business requirements and prioritization

  • UX strategist confirmed design decisions and user flows

  • Frontend dev verified technical feasibility throughout

  • I synthesized feedback and iterated designs rapidly


System Logic Definition

I worked closely with the PM to define the AI mapping system behavior, contributing to Confluence documentation that specified:

  • Mapping logic and validation rules

  • Edge case handling and error states

  • Confidence scoring mechanisms

  • Pattern recognition criteria

This collaboration ensured the development team had clear specifications while I maintained focus on the user experience implications of each system decision.

Impact & Results

Quantitative Impact

Qualitative Impact

Key Learnings

AI-Assisted Workflows

Designing for AI assistance requires balancing automation with user control:

  • Show confidence levels - Users need to understand AI certainty

  • Allow corrections - Human oversight improves system over time

  • Make learning visible - Users should see the system getting smarter

  • Provide escape hatches - Never force AI suggestions; always allow manual override


Enterprise Design Challenges

Working on B2B data operations taught me:

  • Progressive disclosure - Hide complexity until needed

  • Status visibility - Users need constant awareness of data health

  • Error recovery - Failures are inevitable; design for recovery, not perfection

  • Collaboration patterns - Enterprise tools serve teams, not individuals


Cross-Functional Success

The most effective design happens when:

  • Weekly validation beats big quarterly reviews

  • Documentation matters - Confluence specs were as important as Figma files

  • Real-time collaboration - Multiplayer Figma enabled faster iterations

  • Transparent process - Organized workspace built stakeholder trust


Design Systems Thinking

Every feature was an opportunity to strengthen the system:

  • Built patterns that could scale across PROS applications

  • Maintained 95% design-to-code fidelity through component discipline

  • Created reusable workflows applicable to other data-heavy products

Key Takeaway

This project transformed a basic file upload tool into a comprehensive data operations platform. By introducing AI-assisted mapping, we eliminated repetitive manual work. By redesigning the dashboard as an operations hub, we gave users visibility and control. By adding collaboration features, we enabled team-based workflows.

The successful delivery of Phase 1 and subsequent Phase 2 investment validated both the product strategy and design approach. Most importantly, this work created a foundation that continues to evolve, proving that good design creates platforms for growth rather than one-time solutions.

Note: Due to confidentiality, screenshots shown are from pre-production Figma files.

Create a free website with Framer, the website builder loved by startups, designers and agencies.