Organization name : National Institute of Securities Markets (NISM).
NISM is an institution where any security market participants or any intermediaries or people interested in the stock market can get an official certification from. The certificates are mandated by The certification allows a person to become a practicing mutual fund advisor.
Main aim: To improve quality standards in the securities market of India
Eligibility: Person applying must be above the age of 18. Who MUST have a PAN card.( PAN is a mandatory document to work in the Securities market )
What is the problem ?
The registration for the certification is time consuming, confusing, complicated therefore causing high user drop of rates and an overall an unhappy user base.
Why do we need to solve this problem ?
This is the only platform in the country where a person can get certified to become an intermediary in the securities market. Therefore making the registration process simpler, quicker and efficient is important.
Who are our users?
Any person above the age of 18 who wants to get a certificate which will allow them to practice in the Securities Market of India.
My aim for the project
Is to create a better onboarding experience where the users are well informed every step of the way thereby allowing them to register and browse certificates with ease.
The Process Followed:
- Conducted a UX Audit ( Heuristic Evaluation )
A little bit about what it is exactly, Heuristics refers to experience-based techniques for problem-solving, learning, and discovery. Using this method we evaluated the website and found out any major issues that we leading to a bad user experience.
For the Heuristic evaluation of NISM On-boarding, I have referred and applied Jakob Nielsen’s heuristics and Severity scale.
Evaluation was done based on the following principles:
- Visibility of system status
- Match between system and the real world
- User control and freedom
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimalist design
- Help users recognize, diagnose, and recover from errors
- Help and documentation
Severity was based on :
- Low: Fixing this should be given low priority.
- Medium: Medium usability problem but important to fix.
- High: Major usability problem, so should be given high priority.
After conducting the evaluation there major design issues were found. The detailed report of the findings can be found below:
2. Persona was created
A persona is a fictional yet real user who represents the behavior and characteristics of the entire user group. It give us a direction for our design. The user must be kept in mind at all times through out the entire process, making a persona helps us empathize with the end users and design solutions to the problems they face.
I created a persona who represents a group of user that want to apply for an NISM certification. Goals, Pain points and Motivations have been noted.
3. Defining Project Goals
Now we some understanding of the user we are designing for with the help of a persona, but this cannot be the only thing kept in mind while designing. The other aspect that must be considered should be the goals of the business. A design can only be complete if it meets the goals of its users as well as the goals of the business.
So, the next step was to identify goals and pain points of both the user and the Business and find out the commonalities between each of them.
3. Defining Information Architecture
The next step in the process was to define the structure of the onboarding process. The information architecture was defined keeping in mind usability principles as well as the pain points of the users.
The flow aims to make the process simple and as less time consuming as possible as the everyday user does not like spending a lot of their time filling out forms and prefer a quick and simple process.
This is where all the work put in till now will start to take some shape. I used paper sketches to go through as many design solutions in the quickest amount of time.
After going through various design I finalized on this
Finally we reached the fun part of the process, actually designing the experience on Figma. Before we go into detailed design, a Low- Fidelity wireframe had to be done in order to test the design.
The main purpose of a Low- Fidelity wireframe is to allow the users to test the flow of the design and allow us, if required to make changes easily without us going through the effort of creating a very detailed design.
Link to wireframes : https://drive.google.com/drive/folders/1uD2JObmWhLauPiTezB4RhzlDBOd7HE-H?usp=sharing
6. High-Fidelity Wireframes
The next step was to make a high-fidelity wireframe. High-Fidelity ( Hi-Fi in short) give us the actual look and feel of the product.
Link to High-Fidelity wireframes: https://drive.google.com/drive/folders/1Qx9juymOMduoKB6JgHWjos6O-Bl_OROd?usp=sharing
Read the full article here