Driver Nation
About This Project
Driver Nation brings several parts of the automotive community together in one digital experience. Car enthusiasts can build profiles for their vehicles, share modifications, follow other builds and connect the businesses that worked on their cars. Clubs can bring together members, sponsors and events, while automotive businesses can create listings, promote services and discounts, and reach people already interested in the community.
The Challenge
The main challenge was the number of different users and actions the platform needed to support. A car owner, club administrator and automotive business all use Driver Nation differently. At the same time, those experiences needed to connect rather than feel like separate products.
The design therefore had to make it clear where users belonged, what they could do, and how their activity connected with the wider Driver Nation community.
The platform also included a large amount of searchable and user-generated content, from vehicle profiles and modifications to businesses, offers and events. That information needed enough structure to remain easy to explore as the platform grew.
Process
I focused first on understanding the different user types and how their actions connected, then used that structure to shape both the public experience and the management dashboards.
-
1. Map the Experience
I organised the platform around its main users and the content they needed to discover, create or manage.
-
2. Structure the Flows
I worked through the key journeys, from exploring cars and businesses publicly to creating profiles, managing listings and publishing content inside the dashboard.
-
3. Build a Consistent UI
I created repeatable patterns for profiles, search, tables, forms, cards and management screens so a large feature set could still feel like one product.
My Approach
1. Designing around different user roles
The Problem
Driver Nation needed to support users with very different goals. Car owners needed tools for vehicle profiles and community activity. Clubs needed to manage members, events and sponsors. Businesses needed listings, offers, analytics and account management.
My Approach
I separated the logged-in experience around the user’s role while keeping the overall interface language familiar. The onboarding and login experience introduces the relevant account type, while each dashboard prioritises the tools that user needs rather than exposing every feature in the platform.
This allowed the product to support different workflows without turning the navigation into one large collection of unrelated tools.
2. Connecting the community instead of creating isolated directories
The Problem
Cars, clubs, businesses, events and discounts could easily have become separate directories with little connection between them.
My Approach
The experience was designed so those areas could reinforce each other. A vehicle profile can show its specifications and modifications while also identifying businesses that worked on the car. Clubs connect members, sponsors, events and relevant offers. Business listings can exist as their own destination while also appearing naturally within the wider automotive experience.
This creates more context around each piece of content and makes the platform feel like a connected community rather than a collection of listings.
3. Making discovery practical across a large amount of content
The Problem
As more cars, businesses, events and offers are added, browsing alone is not enough. Users need ways to narrow down what is relevant to them.
My Approach
Search, filters and category-based browsing were built into the main discovery experiences. Cars can be explored using attributes such as make, transmission and body type. Business discovery includes categories and location. Discounts introduce filters such as price, category, distance and rating, while events can be searched using dates, suburb and category. The goal was to keep discovery usable even as the amount of content increased.
4. Creating a repeatable management experience
The Problem
The dashboard needed to support many operational tasks: creating profiles, publishing listings, adding discounts, managing events, maintaining club members and reviewing account activity. Designing each feature differently would make the product harder to learn.
My Approach
I used consistent management patterns across the dashboard, including side navigation, searchable tables, status indicators, forms and clear create/edit actions.
Once users became familiar with one part of the dashboard, the interaction patterns remained recognisable when they moved into another.
From Public Experience to Dashboard
One of the important parts of the project was maintaining a consistent experience between what visitors discover publicly and what members manage after logging in.
The public platform is more visual and community-driven, using automotive imagery and profiles to encourage exploration.
The dashboard is more functional and information-dense, but it retains the same dark visual direction and interface language so moving between the two experiences still feels connected.
Final Experience
The final design creates one platform around several connected automotive experiences. Enthusiasts can discover and showcase cars, clubs can organise their communities, businesses can become part of those conversations, and users can find events, services and offers without leaving the ecosystem.
Behind the public experience, the dashboards provide the tools needed to create and manage that content while keeping different account types focused on the actions relevant to them.
The result is a visual system that can support both community discovery and day-to-day product management without making them feel like separate products.
Results
The completed design established a consistent foundation for Driver Nation’s public platform and its role-based dashboards. It brought together community profiles, business discovery, events, offers and account-management tools within one visual system, while giving different user types clearer paths to the features relevant to them. No performance or conversion metrics were available for this case study, so the portfolio should focus on the scope of the experience, the product structure and the final interface rather than making measurable outcome claims.