Loading the case study

Case study 01 · CDK Global · AI-Led Process

The AI-Assisted UXPractice

Four programmes, one six-step method: source material and SME sessions in, specified and evaluated prototypes out, in days rather than quarters.

Scroll the story

Role

Method owner and design lead

Timeline

April – July 2026

Team

SMEs, stakeholders and product partners, with AI as pair-builder

4clickable prototypes, all in RDS
8PRDs and specifications
48open decisions named, not buried

The short version

01

The problem

Four unrelated problems, from green-screen reporting to a voice assistant. Each would traditionally take months of discovery, then a meeting about the discovery.

02

What I owned

The method and the work: six gated steps, run the same way across all four programmes.

03

The approach

AI ingests every artifact, recorded SME sessions become the spec, one PRD flags every gap, and the prototype is pair-built in the design system, then evaluated and re-scored.

04

The result

Four prototypes, eight PRDs and 48 decisions out in the open. Next frontier: prototypes to production code.

The long version · for the detail-inclined

02 / 21

The context UX will codify for AI

03 / 21 · By the numbers

T H E P O R T F O L I O Four programmes at a glance Same method, four very different problems — legacy reconstruction, onboarding consolidation, a new AI surface, and role-based navigation. 01 MyInstall 3.0 Dealer onboarding, end to end Jul 1 – 15, 2026 Four PRDs, a 36-narrative discovery workbook and 109 pain points consolidated into one traceable flow, IA and prototype across three separated surfaces. 36 functional narratives consolidated 02 MIS / DOC Legacy reporting, rebuilt as a report builder Jul 20 – 23, 2026 Six green-screen functions reverse-engineered, then collapsed into a single report builder with drilldown, scheduling, benchmarking and audit. 13 modules in one prototyped flow 03 MR Mobile · AIVA The voice-assisted sales companion Apr 14 – Jun 10, 2026 A voice assistant specified against existing platform endpoints, prototyped to fourteen screens, and scoped by decisions tha

04 / 21

One repeatable process, run on every programme

05 / 21

MyInstall 3.0

06 / 21

The six steps, as run on MyInstall 3.0

07 / 21

Two weeks, one thread

08 / 21

One prototype, three audiences

09 / 21

MIS / DOC

10 / 21

The six steps, as run on MIS / DOC

11 / 21

Four days, from legacy analysis to evaluated prototype

12 / 21

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

13 / 21

MR Mobile · AIVA

14 / 21

The six steps, as run on MR Mobile

15 / 21

Fourteen April to ten June

16 / 21

The rep's working surface

17 / 21

Unify 3.0

18 / 21

The six steps, as run on Unify 3.0

19 / 21

Seven to twenty-eight May

20 / 21

One prototype, eleven behaviours

21 / 21 · By the numbers

W H E R E W E A R E Four prototypes in hand. The conversion to code is the frontier. 4 clickable prototypes, all built in RDS 8 PRDs and specifications written 5 recorded SME and stakeholder sessions 48 open decisions named, not buried R E A D Y N O W • Four demonstrable prototypes, each a self-contained artifact in the Radial Design System • Consolidated PRDs and traceable requirement registers on every programme • SME and stakeholder validation recorded on MyInstall, MIS / DOC and MR Mobile • MIS / DOC heuristic evaluation closed at 9.8 / 10 W H A T W E N E E D N E X T • Decision sessions to close the named open items — 6 · 33 · 2 · 7 by programme • Usability sessions run against the validated Unify Fixed Ops flows • Green light and resourcing for step 06: prototype to React / RDS front-end code • SME coverage extended to Variable and Business Ops personas Every prototype is already bu