OVERVIEW
The first experience had to explain the entire ecosystem.
Nezz wasn't a single-purpose product. Users could explore high-value products, interact with buyers and sellers, manage financial activity, and access banking features within the same platform.
That made onboarding particularly important. The experience needed to introduce enough of the platform for users to understand its value while avoiding a lengthy setup process that could make the product feel complicated before users had even entered it.
My goal was to create a guided introduction that answered three questions:
What is Nezz?
What can I do here?
What do I need to do to get started?
THE CHALLENGE
How much should we ask before users can explore?
One of the key onboarding decisions was determining what information users actually needed to provide upfront.
Nezz required information to personalize the experience and eventually support financial features, but asking for everything immediately would create a long and demanding onboarding process. At the same time, introducing users directly into a complex platform without context could leave them unsure of where to begin.
TOO MUCH UPFRONT
←
THE RIGHT AMOUNT
→
TOO LITTLE CONTEXT
Understanding the User
Gather enough information to personalize the experience.
Explaining the Product
Introduce Marketplace and Banking without overwhelming users.
Account Requirements
Complete the information necessary to establish the account.
Getting to Value
Allow users to begin exploring the product as quickly as possible.
Breaking onboarding into understandable stages.
MAPPING THE EXPERIENCE
One of the principles that shaped the experience was progressive disclosure.
Rather than presenting every feature, requirement, and decision at once, information was introduced when it became relevant to the user's journey.
Early stages focused on helping users understand the platform and establish their account.
More involved actions, particularly those connected to financial features, could appear later in the experience when users had greater context around why they were needed.
This allowed onboarding to feel less like completing a checklist and more like gradually entering the Nezz ecosystem.
PERSONALIZATION
Making the experience relevant from the beginning.
Part of onboarding involved learning enough about the user to tailor their experience.
Rather than collecting information without context, the goal was to connect questions to the experience users were about to enter.
This helped establish a clearer relationship between the information users provided and the product experience that followed.
The challenge was determining what information was valuable during onboarding and what could reasonably wait until later.
That distinction helped keep the initial experience focused.
Helping users make an informed choice.
Nezz included different account options, which introduced another decision during onboarding.
The plan-selection experience needed to communicate the differences clearly enough for users to make a decision without turning onboarding into a pricing comparison exercise.
I focused on creating clear hierarchy between plan names, key benefits, and the actions available to users. The goal was to make plans easy to compare and easy to understand before asking users to commit to one.
Onboarding didn't end when setup was complete.
PRODUCT EDUCATION
Because Nezz contained multiple product environments, completing account setup didn't necessarily mean users understood what they could do next.
The onboarding experience therefore introduced users to both the Dashboard and Marketplace before directing them toward more involved setup.
UX WRITING
Clear language for an unfamiliar experience.
UX copy played an important role throughout onboarding because users were being introduced to features, terminology, and decisions they may not have encountered before.
I focused on keeping instructions concise and action-oriented while making it clear:
Where the user was
What was being asked
Why it mattered
What would happen next
Labels and supporting copy were refined as the experience evolved to reduce ambiguity and make each stage feel easier to complete.
Good onboarding copy doesn't explain everything. It explains what users need right now!
Good onboarding copy doesn't explain everything. It explains what users need right now!
COLLABORATION
Turning product requirements into a user journey.
I worked with the founders and engineering team throughout the onboarding design process to understand product requirements, determine the order of key steps, and ensure the proposed experience could be implemented effectively.
As requirements evolved, I adjusted flows, UI, and supporting copy while maintaining the overall structure of the onboarding experience.
The process required balancing what the business needed users to complete with what users realistically needed to understand at each stage.
REQUIREMENTS → FLOW → DESIGN →
REVIEW → ITERATE → HANDOFF
From first visit to confident exploration.
FINAL EXPERIENCE
The final onboarding experience introduced Nezz progressively rather than attempting to explain the entire ecosystem at once.
Users moved through a structured journey that helped them:
Understand
Learn what Nezz offered.
Personalize
Establish an experience relevant to them.
Choose
Select the appropriate account option.
Explore
Become familiar with the Dashboard and Marketplace.
Activate
Continue into financial setup when appropriate.
Each stage had a clear purpose while contributing to the larger onboarding journey.
Creating an entry point into a complex ecosystem.
Good onboarding doesn't explain everything.
OVERVIEW
My work established a structured onboarding experience that introduced users to Nezz while guiding them through the information and decisions required to begin using the platform.
Rather than treating onboarding solely as account creation, the experience connected setup, personalization, product education, and exploration into one journey.
The completed designs provided the founders and engineering team with a defined onboarding direction that could be reviewed, refined, and prepared for implementation.
This project changed how I think about introducing users to complex products.
When a platform has many capabilities, it can be tempting to explain everything immediately. But more information doesn't necessarily create more understanding.
The better question is:
What does the user need to understand at this moment to confidently take the next step?
If I revisited the experience today, I would validate each onboarding stage through usability testing and measure where users hesitate, skip, or leave the flow. I would also explore whether certain setup requirements could be deferred even further until users demonstrated intent to use the corresponding feature.
The lesson I continue to carry into my work is:
Onboarding isn't about teaching users the whole product. It's about giving them enough confidence to begin.
REFLECTION