Imagine a screen displaying data in grid view.
All details are mentioned as rows and columns.
As a UX designer, when I sit down for discussions with stakeholders, i get a lot of comments lately on the number of clicks is equivalent.
All details are mentioned as rows and columns.
As a UX designer, when I sit down for discussions with stakeholders, i get a lot of comments lately on the number of clicks is equivalent.
💬 Some say that “least number of clicks is directly proportional to good UX”
While reviewing the prototype, I hear:
“Gautam, can we have this info displayed here on this page? The user has to click one more time to view this”
To this, I ask:
“ok, may I know the priority of the info? If it’s important I’ll avoid the click”
But to this I hear a reply from the stakeholder saying:
“That is not as important. It can be considered secondary. But the user may want to see it. What if the user is annoyed with too many clicks?”
I’m surprised. That’s not too many clicks.
That’s just one more click.
An extra click is not always a bad sign.
I remember there used to be a thumb rule that goes:
If you have to reach/find an information on the app/website, it better be found within three clicks from the landing page.
That stands true. I stand by that rule. The rule of three clicks could be used just as a yardstick to measure and meet good usability standards.
Wait, But…
But that doesn’t mean, you can always take the leverage of hiding things until you reach three clicks OR it also doesn’t mean having a fourth click is the most flawed idea to implement.
This should no way hinder exploration of clicks and proper navigation.
This should no way hinder exploration of clicks and proper navigation.
💡 A good UX-er has a muscle memory to not provide a design that involves a lot of clicks by default. But on the contrary, a good UX-er and a person who actually understands user-needs, recommends an extra click if it’s actually required.
Let’s say the business / the functionality comprises of multiple layers of information to be displayed. These details can be prioritised from highest to the lowest priority during the user research phase.
It’s always recommended to not display things until it’s actually needed for the user to use. If the user needs it, they navigate there within one click or two clicks depending on the priority.
So, the user may find it difficult at first.
There is a learning curve for the user. He learns the second time. He gets used to it from the next time. Simple.
Sample image of learning curve
They develop a muscle memory to go for an extra click without shedding any drops of sweat.
One kutty story
I’d like to recall something that I saw on Twitter. There was a customer who sent a mail to Steve Jobs, explaining the difficulty to hold his new iPhone 1. When the customer used the phone, his own fingers would accidentally hit on the volume buttons.
This may sound as a huge user problem, but Steve Jobs coolly replied:
This may sound as a huge user problem, but Steve Jobs coolly replied:
“Try not holding it that way.”
This is because it’s a use case. Not a usability problem.
One user is finding it difficult, but for some days. That one user goes through a short learning curve, develops a muscle memory and automatically amends their holding position.
So, the myth busted:
An extra click is always not a panicking moment. Infact an extra click if needed brings in more clarity.
It’s sometimes a boon than a bane.
Until next time.
View this post on my LinkedIn