Case study 08 · CDK Global · Platform Architecture
Unify PlatformCreation
Asked for an app launcher; delivered the CDK platform: single sign-on, shared services and one front door for 10+ products.
Role
Concept, research, prototypes and requirements through alpha and beta
Timeline
Pitch and prototype in under 6 months
Team
Visual designer, creative technologist and 2 UX architects
The short version
The problem
Customers logged in to 10+ products acquired over 20 years, each with its own front door. CDK had no shared channel to tell them anything.
What I owned
The concept, the research and the prototypes that turned a launcher request into a platform pitch.
The approach
Workshops with support and product teams, then dealership visits to watch how people actually move between apps. Requirements came from the floor, not the org chart.
The result
SSO adoption up 90%, a framework for shared platform services and a central place to message customers. The launcher shipped as well.
The long version · for the detail-inclined
01 — Strategy
Strategy
Putting it all together
Goal:
Evolve various features and functions that are common to platforms into a single concept that can showcase CDk’s innovative spirt. All of these features have been requested by customers but have never been brought to the light of day.
- Features:
- Single authentication to all products
- Global header
- Global messaging / Notifications
- Personalizable
- Modern UI
- Centralize support, help and payments
Strategy
The power of Uniformity with Unify | Branding and platform thinking
- Standardizing IA enterprise architecture
- Combine multiple competing approaches and initiatives onto platform approach
- Brand the suite of apps CDK versus individual products ( marketing collaboration)
- Elimination of UX issues and “ sloppy” implementation impacting CDK brand and perception
- Can pair with consumer UI standards in Roadster
Strategy
Authentication was just the beginning
CDK also had no centralized method or location to login to the 10+ products and app that had been acquired and built over 20 years.
Strategy
Solving for real business problems
CDK had gone years without a unified communication strategy or channel in which products and services could be advertised or customers to be alerted to issues around their accounts.
02 — Research
Research
What.. Exactly are we building?
While the concept of a centralized launcher was fairly straightforward we looked to other organizations that had taken collections of unrelated / related applications and turned them into a coherent suite or standard platform.
Research
Workshopping / Use case collection
While the concept of a centralized launcher was fairly straightforward we looked to other organizations that had taken collections of unrelated / related applications and turned them into a coherent suite or standard platform.
Research
Going to Dealerships
While the idea of collecting all the apps together was great, we needed to understand how the typical user across a dealership would leverage these abilities and what else could it do?
03 — Analysis
Analysis
Site Map
Analysis
Flow Diagram
Analysis
Requirements
Out of our workshopping and interviews of customers and departments like customer support, applications, installers and more we got the requirements that would feed into the backlogs and feature lists that we would build.
04 — Design
Design
Interface
Design
Chatbot Help / QA
Design
Centralized profile
05 — Results
Results
What Did It Do?
Results:
- Increased adoption of SSO 90%
- Brought a place to showcase CDK innovation
- Provided a mechanism for features to be adopted to solve business problems
- Provided the framework for platform standardization
- Springboard ability to address common customer requests ( like a modern UI)
- Introduced centralization and common functions