NDA (name changed)
NDA offers three primary methods for onboarding third parties to the platform: integrations, bulk upload, and manual entry. In most cases, clients prefer to onboard multiple third parties through integrations due to the efficiency it offers when dealing with large volumes. However, in situations where clients need to manually add a third party, they can provide their specific requirements. Based on these requirements, we can customize the form fields to accommodate the manual onboarding process. By providing these three onboarding options and customizing forms to align with individual client needs.
Compliance
Domain
3 weeks
Duration
The problem.
The visual elements are inconsistent and do not follow the heuristics, leading to user mistakes during the onboarding process.
The solution.
I conducted usability testing to confirm the hypothesis and provided the best possible solution that aligns with the development team's requirements and business needs.
Process
I created the script for interview based on what I thought, was going to be confusing during interview. This being said, one should aim to understand, rather than simply assume, what the problem is.
During the research, I generated a list of issues that had the potential to negatively impact user experience. Based on these insights, I formulated a hypothesis to verify or reject during the usability testing sessions.
1. The user should be able to “Onboard 3rd party manually”
2. The user should be able to “View error state” if any while adding it
3, The user should be able to “View mandatory field” while adding 3rd party
3. Question: Did you notice the mandatory fields?
But it was a struggle
Feedback
1. Company, Individual... that row is confusing
2. Show compulsory field more clearly
3. It should look modern and clean
4. It should have less numbers of fields
Below is a rainbow matrix showing the results tested against the hypothesis. Each circle symbolizes that the hypothesis was confirmed for each participant.
Final implementation
