Functional Specs & Content Requirements

Stage 2 | Design Process Methodology

Form follows Function

It just does. No Ai will ever change that. For this stage 2 deep dive, we will assume the product I’m designing, the Vehicle Passport, is a first-generation disruptor. As such, the details of the technical stack and functional layers required to support the new experience concept are to be defined post proof-of-concept. For now, we’ll generalize on the technical stack and functional layers that are likely to be required to support the Vehicle Passport experience.

Using AI for Stage 2 Work
The workflows, artifacts and tools typically used in classical UX practices for this stage are being augmented, replaced and hastened by Artificial Intelligence. Click here to see some of the new tools and techniques I’m experimenting with.

Technology: Exploitation

➤ Technology should be exploited in order to:
Reduce (and likely remove) the burden of trade-in valuation distractions, errors and frustrations littering vehicle purchase funnels AND
➤ Technology should be exploited in order to:
Create more personalized transaction experience across buy, sell and trade-in funnels

Technology: Hypothesis

Introducing new Vehicle Passport functionality will likely need to leverage smart car live cockpits, native mobile Apps and other emerging IoT technologies to digitally collect, track, interrogate and manage a vehicle’s static and dynamic data attributes from cradle to grave.
Additionally, it is hypothesized that a digital Vehicle Passport could broadcast sell/buy intentions to the world around it — creating a robust peer-to-peer, crowd-sourced buy/sell network that would drive direct sales engagements.
➤ Examples of Static Attributes (these attributes are ‘hard’ and would not likely change over time due to events, conditions and activities):
VIN, Manufacturer, Origination Date, Year, Make, Model, Vendor, Color, Trim, Extras, Purchase Date (cradle), Sales Agent (cradle), Purchase Location (cradle), etc.
➤ Examples of Dynamic Attributes (these attributes are ‘soft’ and would likely change over time due to events, conditions and activities):
Mileage, Number of Owners, Photos, Trade-In Value, Number of Accidents, After Market Installs, Purchase Date (resell), Purchase Location (resell), Sales Agent (resell), etc.

From Cradle to Grave

Cradle

Manufacturing

Vehicle is manufactured in such a way that it’s static and dynamic attributes are digitized and accessible straight off the assembly line.

Supported by:
Hard/Firmware, Cockpit Technology, Manufacturer Installation, Central Source of Truth (Web), IoT Integrations

Retail Sale

Vehicle is manufactured in such a way that it’s static and dynamic attributes are digitized and accessible straight off the assembly line.

Supported by:
Hard/Firmware, Cockpit Technology, Manufacturer Installation, Central Source of Truth (Web), IoT Integrations

Ownership & Maintenance

Vehicle is manufactured in such a way that it’s static and dynamic attributes are digitized and accessible straight off the assembly line.

Supported by:
Hard/Firmware, Cockpit Technology, Manufacturer Installation, Central Source of Truth (Web), IoT Integrations

Trade-in Resale

Vehicle is manufactured in such a way that it’s static and dynamic attributes are digitized and accessible straight off the assembly line.

Supported by:
Hard/Firmware, Cockpit Technology, Manufacturer Installation, Central Source of Truth (Web), IoT Integrations

End-of-Life / Recycling

Vehicle is manufactured in such a way that it’s static and dynamic attributes are digitized and accessible straight off the assembly line.

Supported by:
Hard/Firmware, Cockpit Technology, Manufacturer Installation, Central Source of Truth (Web), IoT Integrations

Grave