MyFIAT

Brazil's first digital car purchasing platform. The project that forced me to think in systems, not screens.

Service Design Systems Architecture Stakeholder Orchestration Mobile · Web Automotive
My Role Senior UX · Experience Architecture
Team Sr. Planner · Art Director
API Engineers · Tech Executives
UX Designers · Copywriters
Timeline Before 2023 · Delivery and rollout
Context First of its kind in Brazil. Automotive e-commerce with home delivery, unprecedented in the market.
Complexity API integration · Dealer network
Inventory management · Finance layer
Last mile logistics
1st
Car purchase
online in Brazil
100%
Purchase flow
digital
Delivery radius
anywhere
Before 2023Delivery year
Senior UXRole
Auto­motiveIndustry
SP·BRMarket
Platform statusStatus
My FIAT
01
Defining the Problem
Section 01
Challenge

The system was the real product

Buying a car isn't a checkout. It's a 30-day emotional, financial, and logistical journey.

The brief sounded simple: Brazil's first digital car buying platform. Within the first week it was clear this wasn't UI, it was service infrastructure.

I had to orchestrate API, inventory, credit, logistics, and customer emotion at once. A failure in any layer broke everything.

The gap was between what the customer believed and what happened behind the scenes. The old flow was a lead machine: you showed interest, a dealer called weeks later.

"The interface only works if the service works. Every screen was a contract with a backend process that had to exist."

Felipe Coletti · Senior UX · Experience Architecture

Before → After: the purchase flow transformation

Before
01
Customer visits FIAT.com.br
Lead capture
Interest submitted as a form. No confirmation, no tracking, no digital record.
Before
02
Data sent to the manufacturer
Black box
The customer enters a waiting void. No updates, no timeline, no visibility.
Before
03
Car arrives at the dealership
Offline delivery
The customer has to visit the dealership. Paperwork, waiting rooms, negotiation.
After
01
Configure and buy online
Full control
Model, color, options, and financing resolved digitally in a single session.
After
02
Real-time status tracking
Transparency
The customer tracks every production and logistics step on their dashboard.
After
03
Home delivery with a full tank
Moment of delight
Car delivered to the chosen address. Full tank. Document package. Zero dealership visits.
02
Research & Discovery
Section 02
Research

Mapping the system from every angle

I ran three parallel tracks: consumer mental models, technical constraints, and global benchmarks.

Stakeholder interviews: mapping the invisible

I interviewed the Senior Planner to map the audience and the API engineers to reverse engineer the system's constraints.

This research wasn't validating assumptions, it was discovering what was possible. Without real-time inventory, no real-time selection.

INS·01
Consumer mental model: buying a car feels like a leap in the dark
Customers described the traditional purchase as losing control the moment they signed. They wanted transparency, not speed.
INS·02
API architecture enabled a real-time inventory layer
Live inventory could be exposed via the dealer network API: real availability, not catalog.
INS·03
Global benchmarks: financing integration was the deciding factor
Platforms without integrated financing had far lower completion. Credit had to be a first-class citizen.

Journey mapping: partners, not subjects

We mapped the journey from consideration to the first week of ownership, with the whole team in the same room.

User journey map My FIAT
Journey map from initial consideration to post-delivery. Built in collaboration with the planning team.

Global competitor analysis

With no precedent in Brazil, I looked at every market where digital car sales had been attempted.

In every market that worked, the configurator was a confidence ritual, not a funnel.

03
Design Process
Section 03
Process

Workshop, sketch, iterate

Three tools: a workshop to surface competing needs, paper to move fast, wireframes to stress test the system.

The design workshop: deciding with the room

Before the first pixel, I facilitated a cross-functional workshop. The output wasn't a deliverable, it was a shared mental model the team used for the whole project.

It was the most important decision of the project: investing in alignment before investing in design.

Design workshop
Cross-functional design workshop: journey mapping and needs clustering with the full team.

Sketching: thinking on paper

The sketches came after the workshop: what the customer sees first and what decision comes next.

Wireframe sketches
Initial sketches focused on system logic and decision sequencing, not visual design.

The ecosystem insight

In wireframing came the turn: it wasn't a purchasing flow, it was an ecosystem.

Configurator, calculator, inventory, tracker, and scheduler weren't separate screens. They were states of a single system.

System Layer
Design Contribution
Discovery Layer
Catalog · Configurator
Model selection Emotionally intelligent, aspiration-driven
Color + options real available inventory, not catalog fiction
Price transparency no hidden costs appearing at checkout
Transaction Layer
Finance · Checkout
Financing simulation integrated into the decision flow, not post-selection
Down payment calculator live, responsive, removes commitment friction
Document checklist proactive, not reactive
Fulfillment Layer
Production · Logistics
Order status dashboard real-time visibility into production stages
Delivery scheduling customer-controlled, selectable date
Home delivery confirmation full tank + document handover moment
Post-Purchase Layer
CRM · Retention
My FIAT dashboard car data, service scheduling, ownership hub
Document repository all purchase documents, accessible and organized
Seed for the next car lifecycle communication from day one
Wireframes
Wireframes developed after the ecosystem model was established, each screen as a system state.
04
Visual Design and Execution
Section 04
Visual Design

Governing quality, directing execution

My contribution was architectural oversight: accessibility, hierarchy, and interaction quality.

At this stage my role shifted from creator to guardian. The art director executed the visual; I ensured hierarchy, contrast, and progressive disclosure.

The responsibility at this level is not to design every screen, it's to build the conditions where every screen gets designed well.

Design Principle
Visual Decision
Status
Accessibility-first typography
Minimum 4.5:1 contrast on text over photography, solved with shadow instead of overlay.
✓ Resolved
Trust through visual density
A high-consideration purchase needs more density than typical e-commerce. I refused to simplify the configurator for aesthetics.
✓ Resolved
Mobile-first hierarchy
Mobile first, with progressive disclosure: one decision at a time on a small screen.
✓ Resolved
Status visibility system
The tracker needed its own visual language, tied to the FIAT brand and not borrowed from logistics.
✓ Resolved

The interface in motion

The design made a complex transaction feel like a considered decision. Not frictionless: navigable. Not minimal: clear.

My FIAT mobile home screen
Home screen
My FIAT navigation system
Navigation
My FIAT model selection
Model selection
My FIAT color selection
Color selection
Card system
Card component system: model selection and comparison interface.
05
Results and Impact
Section 05
Results

What the system produced

Launched as Brazil's first digital car purchasing platform: configure, buy, finance, and receive without visiting a dealership.

I set a template for digital transformation in traditional industries: service design, not UI polish.

1st
In Brazil
First digital car purchasing flow in Brazil, unprecedented in the automotive industry.
0
Required dealership visits
From configuration to delivery, with no physical touchpoint.
Endtoend
Service coverage
Configuration, financing, production, and last mile in a single continuous experience.
Platform status
Platform status
The system kept operating and expanding after launch.
Retrospective

What this project taught me about leadership

My FIAT was designing with people and through them, not despite organizational complexity.

The instinct in complex projects is to retreat into individual work. The hard part is creating the conditions for quality to emerge from the room.

Lesson 01 · Systems Before Screens
The interface is the last 10% of the problem
The real design work happened in the stakeholder sessions and the API mapping. Every screen was a manifestation of a decision made much earlier.
Lesson 02 · Facilitation Is Design
The workshop was the highest-leverage design decision
A day of alignment before wireframing eliminated weeks of rework. Clarity upstream compresses execution downstream.
Lesson 03 · Directing vs. Executing
Senior UX: creating the conditions for excellence to emerge
Trusting the art director with the visual was right: two experts in their domains, not one person spread thin.
Lesson 04 · Ecosystem Thinking
Every screen is a state of a system
Realizing it was an ecosystem, not a flow, changed everything. I now frame products as interconnected states.
Next Project
SKY · Audience Strategy
and Experience Architecture
Back to top