Cox Automotive · Case Study

Dealership Reporting Tools

Building a unified operational reporting platform across Cox Automotive's dealership ecosystem — turning fragmented, product-siloed dashboards into one consistent, workflow-oriented reporting experience.

Role: Lead UX Designer/Architect Product Strategy UX Leadership Systems Architecture Discovery Facilitation
DMS+ Reports dashboard
My Role

Lead UX Designer/Architect

I led product strategy, UX leadership, and systems architecture for a reporting ecosystem spanning multiple dealership workflows and product lines.

  • Product Strategy
  • UX Leadership
  • Systems Architecture
  • Discovery Facilitation
  • Interaction Design
  • Design Direction
  • Cross-functional Alignment
DMS+ Reports dashboard screenshot
Business & Organizational Context

Organizational Challenge

This initiative evolved from a dashboard redesign into a platform-level effort to unify fragmented reporting systems across Cox Automotive's dealership ecosystem.

Core Challenges
  • Inconsistent reporting definitions, workflows, and interaction models across products
  • Siloed ownership between teams created operational fragmentation and low reporting trust
  • Manual reconciliation and legacy workflows increased cognitive and operational overhead
  • Competing priorities between customization, usability, delivery speed, and scalability
Strategic Leadership

The challenge was not consolidating dashboards — it was aligning teams around a shared operational reporting model that could scale across products, workflows, and dealership roles.

This required establishing
  • Standardized reporting principles
  • Scalable interaction patterns
  • Unified workflow behaviors
  • Cross-functional alignment across product, engineering, and operational stakeholders
Product Discovery
Discovery validation affinity clustering

Research revealed dealership teams struggled less with access to data and more with:

  • Inconsistent workflows
  • Conflicting reporting behaviors
  • Low confidence in operational metrics
  • Fragmented navigation across systems

This shifted the initiative from "dashboard redesign" to "workflow-oriented operational reporting."

Research Activities
Conducting surveys and interviews with stakeholders
  • Contextual inquiries with 5 dealerships
  • HCD exercises with SMEs
Identify core personas
  • Store Managers
  • F&I
  • RO Managers
Utilize HCD exercises to identify reporting goals
  • Look-back availability
  • Drill-downs, benchmarking, and anomaly detection
Research activities: card sort exercise
Key Insights
1. Data was abundant. Actionability was missing.

Users were overwhelmed by metrics but lacked prioritization and contextual guidance.

2. Reporting definitions varied between systems.

This created operational mistrust and manual reconciliation workflows.

3. Dealership roles required different levels of depth.

Executives needed fast summaries while operational teams needed drill-down workflows.

4. Consistency mattered more than feature expansion.

Standardization reduced friction more than adding new reporting functionality.

Strategic Design Decisions

Some stakeholders prioritized feature parity and data density, while operational users consistently prioritized clarity, prioritization, and trust.

I advocated for progressive disclosure and standardized workflows to reduce operational friction and improve decision confidence across dealership roles.

This required difficult tradeoffs between
  • Customization vs consistency
  • Depth vs clarity
  • Platform flexibility vs standardization
  • Short-term delivery vs long-term scalability
I prioritized
  • Progressive disclosure
  • Role-based workflows
  • Reusable reporting patterns
  • Actionable summaries over data density
  • Standardized filtering behaviors
  • Scalable visualization systems
Strategic design decisions process diagram
Design Evolution · Global Navigation
Global navigation design evolution
Initial Direction

Cross-product navigation exposed too many reporting systems simultaneously.

Problem

Dealership users struggled to understand

  • Where reports lived
  • Which system owned what
  • How workflows connected
What Research Revealed

Users thought in operational tasks, not product silos.

Design Shift

We moved from product-centric navigation to workflow-oriented reporting structures with progressive disclosure.

Tradeoff

Reduced surface-level discoverability in exchange for clarity and reduced cognitive overload.

Design Evolution · Data Viz
Initial Direction

Early concepts prioritized maximum data visibility.

Problem

Users struggled to identify which metrics required action.

Research Insight

Dealership leaders needed prioritization and contextual guidance more than raw data exposure.

Design Shift — Introduced
  • KPI hierarchy
  • Progressive disclosure
  • Contextual summaries
  • Standardized visualization patterns
Tradeoff

Reduced simultaneous data exposure to improve speed-to-insight and operational clarity.

Data visualization design evolution
Design System Experience
Design system experience components

A major challenge was reducing cognitive load while maintaining the depth dealerships required to manage operations effectively.

I introduced
  • Standardized chart behaviors
  • Unified filtering systems
  • Reusable grid patterns
  • Consistent KPI structures
  • Progressive drill-down experiences
  • Scalable visualization standards

The goal was to create a reporting experience that felt predictable, learnable, and actionable regardless of product area.

This significantly reduced the friction created by inconsistent workflows across dealership systems.

Final Experience

The final experience consolidated fragmented reporting workflows into a unified ecosystem that supported dealership operations more consistently across departments and products.

The platform enabled users to
  • Quickly identify operational trends
  • Navigate between summary and detailed views
  • Compare metrics consistently across systems
  • Move from reporting to operational action faster

The experience shifted reporting from static data presentation toward actionable decision support.

Final dashboard experience
Business Outcomes & Organizational Impact

The initiative established a scalable reporting foundation across Cox Automotive's dealership ecosystem while improving consistency, usability, and operational visibility across products.

Strategic Outcomes
  • Established a shared reporting framework through standardized patterns, KPI structures, and visualization principles
  • Aligned product, engineering, and operational teams around a common reporting model
  • Improved operational consistency with unified workflows and interaction patterns
  • Enabled platform scalability through reusable reporting standards and frameworks
  • Reduced complexity by consolidating fragmented reporting experiences into a cohesive ecosystem
  • Accelerated future reporting initiatives with reusable patterns and shared foundations
← Back to work Email me
© 2026 Chuck Greenwalt