Loading the case study

Case study 04 · CDK Global · Legacy Reporting

MIS / DOC reportbuilder

Turned four green-screen reporting functions into one report builder that scored 9.8 / 10 in usability, in four days.

Scroll the story

Role

UX and product design lead

Timeline

Jul 20 – 23, 2026

Team

Accounting SMEs and product stakeholders

9.8 / 10post-fix usability score
4 → 1legacy function codes unified
13modules in one flow

The short version

01

The problem

Four rigid reporting functions, each needing a new report to move one total. Controllers had learned to live with it, which is not the same as liking it.

02

What I owned

Reverse-engineering the legacy behavior, the consolidated PRD and the prototype.

03

The approach

Read what every legacy screen actually did, validated it with stakeholders, flagged every invented detail, then built all 13 modules as one flow.

04

The result

An evaluated prototype and a spec ready for sign-off, with 33 open decisions surfaced instead of discovered in production.

The long version · for the detail-inclined

02 / 11 · By the numbers

T H E G O A L Turn four rigid, green-screen reporting functions into one report builder that can produce any dealership metric — without rebuilding a report to move a single total. 13 functional modules consolidated into one end-to-end flow 4 → 1 legacy function codes MIS · MIR · MSS · MGS unified 33 open decisions surfaced gaps made explicit, not buried 9.8 / 10 post-fix usability score internal heuristic evaluation Success looks like a controller building any report they can imagine — and drilling from a total to a journal line — without ever leaving the tool or calling for a new function code.

03 / 11

Four stages, in the order they actually happened

04 / 11

What we reverse-engineered from

05 / 11

From legacy behavior to an agreed specification

06 / 11

Decisions and corrections the specification locked in

07 / 11

Create a report, then read it — no new function code

08 / 11

Compare against goals, then drill to the detail

09 / 11

One flow, end to end — from scheduling to audit

10 / 11

Four days, from legacy analysis to evaluated prototype

11 / 11

An evaluated prototype and a spec ready for sign-off — with the open decisions named