Every time you ask the user click you lose half of them.
(And this why tutorials, splash screens, and lengthy signup flows are a bad idea)
If you’ve been building apps for a long time and have seen the results of a lot of A/B tests, you quickly realize that people are a flighty bunch. Ask them to download an app and 80% will bounce right on that page. Ask them to sign up and 90% will hit the back button to avoid putting in their email and password. Ask people who’ve arrived from Google to read an article, to subscribe and get more updates, and 99% will head back to find the next article.
What happens when you ask for credit card and email
In the early days of Uber the only way to sign up was to give your email address a bunch of other fields and also your credit card number. Some of the big early winds in acquiring customers was just to make it so that you could sign up with a phone number and a password, and put in your credit card lead in the flow. If memory serves me right, these were increases on the order of +50%.
You get the drift of what I’m arguing.
So what happens when your designer has the fantastic idea of a stark and beautiful homepage for your new product that takes a few clicks to sign up, followed by a lengthy tutorial to explain all the features? Sometimes this becomes a life and death decision, because rather than signing up thousands of users into your private beta, which provides the traction to raise your next round of funding, instead only a few hundred make it through.
Streamline critical flows by minimizing steps
This is why, when I get feedback on a critical flow within a product, I always start by minimizing the number of clicks and steps. I asked whether each field in a sign-up form is really needed, or is optional. I ask the question of whether you need to user to do something now versus having them set it up in the future, when they’re more bought into the product. I ask to remove all the glitzy, visual steps that explain things and just ask the user to hit next. I move the sign-up form to the first experience, whether that’s on the homepage, or the opening screen of an app. If there’s a call action, while the user is doing something else, like reading an article, my theory is that you should be very upfront with it and make it a blocking modal, or not do it at all. No half measures.
The point of all, this, of course, is to get people into the magic of your product.
The magic is not in filling out forms or watching cute videos about your product, it’s about using your product as quickly as possible. As a result, the only acceptable forms of friction are ones that ultimately enhance the users ability to have a great experience. Thus product is much better experienced as an app, where you have a notifications channel and a richer experience, then, by all means, ask the user to download something. If a product is much better, when used with colleagues or friends, that it might make sense to take a lower conversion rate during the sign-up flow in exchange for some sharing or inviting functionality, that brings more people into the app. Ultimately, it’s all a trade-off, where every click drops off a huge number of users, so you need to spend that user intent very very well.
Add friction when it helps
Ironically, it can also be an anti-pattern to not ask users to sign up or install or do anything at all, because once they bounce, which they will inevitably, do, you have no way to get them back. That’s why it’s all a trade-off, and one of the trickiest things about the user growth discipline is knowing when to add friction, and when to take it away.
Also, interestingly enough, as you make it easier and easier to sign up to reduce friction the quality and intent of the users also decreases. If you double the number of sign-up typically, you do not get twice the number of paying customers.
Nevertheless it’s an important thing to remember: Every time you ask the user click you lose half of them. Be careful.
