Mercedes Me & MBFS
Mercedes Me is an application for Mercedes users to control their car. MBFS is an online payment platform

As Design Lead supporting Mercedes me and Mercedes-Benz Financial Services (MBFS), I help shape end-to-end digital experiences that connect vehicle ownership with financing—spanning discovery, account management, payments, and service journeys. The work sits at the intersection of premium brand expectations and regulated financial flows, requiring a high bar for trust, accessibility, and usability across web and mobile.
Background
My role: Design Lead
Responsibilities: End-to-end process
Details
Tools
Highlights
The MME feature has helped over 16 million users on a monthly basis.

4.5M
Mercedes Me
ratings collected
14 M
Visitors per month

CHAPTER 2
Branding
I designed the visual identity from the ground up, using dark tones and futuristic typography to evoke a sense of seriousness, sophistication, and capability in every interaction
Stakeholder Interviews
Understand Context
Tailor your questions to uncover the "why" behind the feature set.

CHAPTER 1
Discovery

CHAPTER 3
Wireframes

CHAPTER 4
Key Improval
Gamify
Introduce lightweight progress and milestone feedback that motivates owners to complete key tasks (setup, maintenance, payments) without feeling gimmicky.

Personalize
Tailor the home experience to each driver’s vehicle, financing status, and behaviours—surfacing the next best action, relevant offers, and timely reminders.

Hierarchy
Establish a clear visual and content hierarchy that prioritizes critical actions (status, payments, service) first, with secondary features and education consistently organized.

CHAPTER 5
Solutions & iterations

Interfaces
4/5
User
satisfaction score
40%+
Self-service
success rate
120+
screens
Outcomes
Retrospective
-
Premium brand vs. clarity: kept the Mercedes feel, but prioritized explicit hierarchy and plain language in billing/payment moments.
-
Speed vs. system: shipped incrementally using existing patterns while investing in reusable components to avoid more design debt.
-
Consistency vs. platform-native: standardized core flows across products, but followed iOS/Android/web conventions where it improved usability.
-
UX vs. compliance/security: used progressive disclosure and clear confirmations to meet legal/MFA needs without adding unnecessary friction.













