Case study 09 · CDK Global · Unify 2.0
Unify persona-basednavigation
Navigation that changes shape for each of 11 dealership roles, in a prototype real staff can be tested on.
Role
UX and product design lead
Timeline
May 7 – 28, 2026
Team
Fixed Ops SME and the Unify product team
The short version
The problem
One navigation for service advisors, technicians and parts staff serves none of them especially well.
What I owned
SME validation, navigation content and the clickable workspace.
The approach
Collect, validate, build, test, in that order. No navigation content was built until an SME signed off on the language.
The result
A clickable prototype covering 11 personas and 9 applications, with a 50-case usability script ready to run.
The long version · for the detail-inclined
02 / 11 · By the numbers
T H E G O A L A prototype real dealership staff can be tested on Not a concept deck. A clickable build that behaves differently for each role — so we can put it in front of service advisors, technicians and parts staff and watch what actually happens. 11 personas validated and built into the nav 2 recorded SME working sessions 9 applications wired into the workspace 50 usability test cases scripted and ready Success = navigation that reflects how a dealership actually runs, not how software is organised.
03 / 11
Four steps, in order
04 / 11
What we gathered before designing anything
05 / 11
Putting draft navigation in front of a Fixed Ops SME
06 / 11
Four corrections that reshaped the navigation
07 / 11
The navigation changes shape for every role
08 / 11
Search built to the UX vision, end to end
09 / 11
A working workspace, not a set of screens
10 / 11
Seven to twenty-eight May 2026
11 / 11