Making the Invisible Understandable
Improving clarity in a connected automotive profile experience by evaluating how users understand profiles, account connection, and synchronization behaviors.
Connection
Settings
Clarity
A functional system still needed clearer communication.
An existing profile experience allowed users to manage preferences, connect an account, and synchronize selected settings. My role was to evaluate an early prototype, identify usability risks, and recommend improvements before product decisions were finalized.
The UI was visible. The system logic was not.
Participants could complete many tasks, but opportunities emerged to make the system behavior easier to understand. The experience needed to better communicate what information belonged to a profile, what changed after account connection, and which settings were synchronized.
Participants completed tasks, but the experience could better explain itself.
I evaluated task-based scenarios including switching profiles, connecting accounts, managing synchronization, setting privacy controls, interpreting feedback, and navigating profile-related workflows.
Profile ownership needed distinction
Participants needed clearer cues to understand which settings were personal, shared, or eligible for synchronization.
Connection needed more context
The action was understandable, but the benefit and outcome of connecting an account could be communicated more clearly.
Sync expectations varied
Some participants assumed all settings would synchronize, revealing a need to clarify scope and behavior.
System status could be more visible
Persistent indicators could help users understand connection state, synchronization state, and completion of recent actions.
Navigation introduced extra effort
Redundant actions, additional steps, and unexpected back behavior created opportunities for flow simplification.
Clarity improved product quality
Expert feedback helped identify refinements that could make the final experience more intuitive for end customers.
The goal was not to add more features. It was to communicate existing behavior clearly.
The evaluation reframed the opportunity from interface fixes to mental model alignment. Profiles, account connection, and synchronization needed to be separated, explained, and supported with clearer system feedback.
Before: Ambiguous System Behavior
Profile, connect, and sync felt closely tied together, requiring users to infer outcomes.
After: Clearer Mental Model
Connection and synchronization are treated as separate concepts with clearer choices and feedback.
Make system behavior visible
Clarify what is personal, shared, and synchronized.
Separate connection and sync
Treat account linking and data movement as distinct decisions.
Show system status
Communicate the current state of connection, sync, and recent actions.
Clarify value
Explain what users gain after taking each action.
Concept screens — anonymized for portfolio use.
These screens use generic labels and neutral styling to illustrate design direction. All proprietary details, branding, and platform specifics have been removed in line with NDA requirements.
Profile Overview
Surface ownership and current state before users make changes.
Connect Account
Explain the value of connecting before asking users to continue.
Choose What Syncs
Turn synchronization into an explicit and understandable choice.
Expert feedback helped refine the experience before broader product decisions.
The evaluation identified opportunities to improve information architecture, system feedback, navigation efficiency, and communication of profile-related behaviors.
This project reinforced that a successful experience is not defined only by whether users can complete a task. It also depends on whether users understand what the system does, why it matters, and what happens next.