Registration is an important part of any service platform. More platforms are now adopting new methods of less fields to enter as well as social sign in’s in order to grab their customers attention.
The Ka-Pooch registration is outdated. It requires a user to
1. Download a PDF
2. Print PDF
3. Write on Form
4. Scan Form
5. Email Form
I decided to begin another self initiated project of redesigning the Ka-Pooch Registration Experience.
I began by looking at the current Ka-Pooch Sign up Form. This consists of 3 PDF pages.
From there, I analysed all the questions and categorised them into three steps.
I was able to jump to wire framing from the previous research I had done in the initial Ka-pooch project. I began prototyping my designs by laying out the information displayed from the categories determined above..
From this rough design, I decided to show 3 different potential users.
Upon taking them through the paper wireframes, I began to realise some of the problems I would encounter.
1. Excessive amount of questions: No one wants to fill out several rounds of questions however a lot of them are necessary for the staff to know.
2. Lots of fields: Because their are so many fields, the user experience will have to be convenient and easy so users do not drop off.
From round one of wireframes, I was able to identify some key areas to cut down on.
This allowed me to identify different types of styles and input fields the registration form would require for a smooth process.
I took on the feedback and looked into Registration as a holistic process.
In the second round of designs, I made the following improvements.
1. I decided to include a 3 step quick registration screen. This was important as I wanted to capture these clients details before requesting more. I did this because their is high likelihood that clients will drop off because of the length of registration. Therefore having basic details would make it easier to market to them, as well incentivise them to sign up if they do happen to drop off halfway through the process.
2. This 'quick registration' allows them to create an ‘empty’ profile, which can allow them to explore the app before they commit. This also allows for the potential of an on boarding piece.
3. This registration structure is more effective, as it allows for the potential to incentivise users to keep going if they happen to drop off.
I have also restructured the questions. The questions will now prompt you to elaborate depending on how you respond. I did this in order to streamline the process and keep it easy, considering most clients would not have to elaborate on all questions.
If a user has a dog with a certain condition they want to bring attention to - it will be easy for them elaborate however it should not be forced upon everyone.
Upon doing some research and bringing ideas back to my initial wireframes, I began to realise some of what I had designed would not be possible in order to account for messaging and user feedback to improve the registration process. There I took to re-designing parts of the experience again.
User Interface Design
The user interface style for a feedback form is very important because it must
1. Account for several different styles of questions
2. Provide instant feedback to the client
I first began with a more traditional style of using an input field with a label of what information belonged there. It would then disappear once the user taps this field, however I soon abandoned this believing that clients should be reminded of the field they have to fill in. I experimented with a series of styles until I was able to develop something functional and intuitive.
1. User Feedback: User Feedback is a very important part of the process. It must be instantaneous in order to streamline the process. Giving too little or no feedback will frustrate users and increase the likelihood of abandonment.
2. Social Logins and Emails: Allow people to use their email address instead of their username. It is frustrating to try remember your username or create a new memorable one. Social Logins are great because it means users have one less field to enter.
3. Less is more: Condensing information in this context was hard, as a lot of the information requested is a requirement. However, I was able to get around this by deciding which answers users would have to elaborate on.