This is the process we will look at:
The series of screenshots is here:
Who will register?
a) improper & fraudulent
There is unfortunately a category of users who come to the registration process with an intention to not use the platform in a way that we intend it to be used.
We can use techniques to block bots etc in the registration process. The most effective way to block abuse is no doubt to carefully monitor what value we are giving away ‘free’ when the user is trying out the platform rather than making the registration process cumbersome. The latter will turn away ‘good’ prospects too. The platform should be cumbersome (or impossible) to abuse, not to sign up for.
As a side-note I did complete the current registration process with a completely fake identity and data. So if one wants, they usually will find a way to get through registration.
b) proper | intended use
People who come to registration with a genuine intent to discover if we can help solve their problem. We should make this path as smooth as possible.
That being said - the numbers every SaaS is looking at is that 40-60% of users will sign up and never come back…
Screen 1: A choice
This screen offers users a choice to Sign or Register.
Plan:
Remove this screen, it has too limited (or negative) value.
We do not want registered users to have to go through this screen every time they want to log in.
The two links ‘Signup (Register)' or ‘Sign in’ can easily be added to any place where they are relevant.
Common usage patterns are the above, split links eg on main navigation, in context etc.
Screen 2: User identification
Visual / identity / background
Squint your eyes, you will see two things popping out on this screen:
a blue box
a thick red bottom
Neither of these are of prime importance to the goal here which is frictionless identification by the end user.
Additionally (and this can be subjective) the style is rather dated, not contemporary.
Suggestion:
Replace the background with:
a subtle, light visual which does not scream at the user
contemporary styling (we are leading edge so the styling reflects that ?)
Lacking the updated brand guide as it will be forthcoming from Teak, Red is combined with Blue.
Gradients = today
Toned down colors = appropriate for UI.
“Footer”
The “footer” is not needed here. The less CTAs we have on this focused page, the better. It is like a landing page in this aspect.
At this registration stage, it is not the time to send users of to look at documentation. They have clicked on a ‘register’ button, let’s keep them in that state of mind.
The “Update” request
We should find a way to not have to show this message all together, throughout the system.
But, for registration it makes not much sense. By far and large, these are new users and first thing we ask them is to manually update …
The fields and the # of fields
A lot of research has been done on this aspect re conversion rates, and the research can be confusing/contradictory. Bottom line is that we should run our own experiments later on when we have bandwidth. There is the eternal trade-off between lead quality and quantity.
“The takeaway here is you should use as few form fields as you can on your landing pages and be especially cautious with more sophisticated text areas and select boxes.”
“for each additional field you add, your conversion rate may drop anywhere from eight to 50 percent.”
Proposal:
Keep the amount of fields as-is but build up the form. It is a common and somewhat modern approach.
Test later more with other scenarios eg where we start with the full form.
The full form:
Building it up (mentally splitting it):
The form expands after information has been entered.
The benefit of this approach is a step-by-step validation of the entered information.
Eg valid email address:
domain validity
work-related email
…
