Sunday, July 22, 2018

UX Personas - the logic behind

Persona is a representation of a type of user. It gives a clear understanding of -

  • Who our users are  
  • The type of interaction they will be happy with 
  • The design trends they are familiar with 
  • The theme they will be most comfortable with  
It helps the business align their goals and strategies to the specific user groups.

Before creating a persona, visiting the users is ideal but if that's not possible we can use the technology to meet the goal via video calls, referring to lifestyle posts, videos etc. A persona has a personality, the more your observe and note during these interview the more realistic that persona will be.

To conduct a persona analysis, you can begin by compiling everything you know about your users and grouping them in a table. Use the heading relevant to your areas of study such as -

Or use Affinity Diagrams by organizing your findings on a post-it notes.

This will help us understand the patterns such as the industry they work in, the devices they use, their behaviors, habits, the time of day when they use the devices, and their location. This gives a scope to form questions about our users on what they have in common and how do they differ. Here, find the set of people who can form these questions either from your existing user database or by recruiting them - and then speak to them. It's a win-win situation, you get to speak to the real users, learn from them and make the information available to those who build the product.

You can then add more columns into the table based on your findings such as - office environment, the softwares they use at the moment, the collaboration they do and so on. Look for the shared attributes and predominant clusters, you might find that two of your personas share the same attributes - combine them. If you have different attributes altogether, then divide your persona into two.

Now, it's time for the representation of our persona; it might contain the name, photo, age, goals, technology, habits etc. The important part is that these personas should be distinct and memorable. Once we have the persona we can use it for designing the product for the users with accuracy and confidence.

Our goal is to create a shared understand of who we work for, and how everyone can better serve them. These personas give real insights of our users which helps us design and develop much better products. Always remember that personas keep changing, so create them, share them, learn from them and then re-visit them, and then, begin the process all over again.


Tuesday, November 8, 2016

Login form authentications

We have been using login forms from many many years now. As the web is continuously evolving these form have gone through many unnoticed changes over all these years.

There was the first era of showing fields like username, password, remember me, forgot password, need help, reset, and an anonymous question mark which was too much to think about and proceed with the login process.

Gradually, these forms have become shorter and shorter with only username and password fields because that's what the user is actually interested in using as interaction elements to accomplish the task.  

The validation process:
Ever since beginning websites do validate both the username and password fields, but there are another type validation requirements; such as, for security reasons some websites don't validate usernames; the login process is only completed after typing a correct password.

In such cases we face some common questions like:
1. Should I use the current trend of showing username on first screen and password on second screen?

2. What will happen if the authentication fails on second screen?

3. Should we redirect the user to first screen with a message 'your username or password is incorrect'?

4. Or should we use the traditional username and password fields on same screen and then so the failure message, and if we do which field should have a focus?

A lot to think on....

The best bet here would be to use the traditional login form with username and password fields placed on same page with a forgot credentials link in case if the user doesn't remember his credentials (username and password both), and a signup link for new users.

What about the focus?

Well, when you are not validating the username field there is no point in keeping the typed username in the field after validation error as there is a possibility that the username also could be wrong. So it's best the system resets the form entirely with a focus on username field.

Sunday, May 29, 2016

Mobile app notifications for business meetings

Annoying notification is one of the top reasons why people uninstall mobile apps, so the notification designers have to be very careful while designing their behavior.

At first the app should ask users as to when they would like to be reminded about the meetings, because the user behavior  vary; some people might want to be reminded a day before and also 30 minutes before the meeting starts as they might have to prepare for the meeting; and some people might be just ready to jump into the meeting without any delay so they would want to set the reminder to 5 minutes. So, let the user set time to receive a notification.

Once the notification is on screen; the user should be able to dismiss it or open the meetings app - this feature can be used with the slide option.

In case if the user doesn't attend the meeting and the meeting time is over, then the notification should still sit on screen but in negative state to let the user know that he/she has missed it. And there should be an option to dismiss it or send a message to the meeting organizer with the reason why the user couldn't attend the meeting.

Saturday, May 28, 2016

UX patterns for dates

Generally, users are quite fast at entering dates into input fields rather than selecting one from date picker. One reason why many web applications provide date pickers is that user may not be accurate about what date would it be on next Thursday.

The best approach would be allowing the user to enter/type date, and show a date picker on mouse focus. While using this pattern you have to make sure that the validations are working just fine as the user may enter dates in different formats such as:

Date & Time
In many situations date and time is combined together and many designer find a way to implement it in a better way every time. Here are some best ways to implement the date and time controls together:

Display the dates of course where students can apply as per their schedule considering they don't have to select from different months and the time is fixed:

Thursday, May 26, 2016

Mobile device volume controls Vs app volume controls

Should mobile apps have volume controls or they should use the device controls?

This question has been raised by many UX practitioners; the answer to it is mobile apps must have their own playback controls, but their functionality has to be synced with the device controls as well.

Reasons your app should have volume controls:
1. The inApp controls give the user the feel of carefully developed application which has all features of its own.
2. The user feels more in control rather than depending on the device.
3. Most mobile users don't use the device controls very often as they are a little careful that overuse of those hardware buttons would might cause damage.
4. We should not ignore the possibility that the user's device controls could already be damaged/non-functioning.

Many people are also having debates on the Mute feature as well. I think you should never use the device's mute feature as it may mute all other applications as well, for instance: A Phone Call.

Sunday, December 6, 2015

Basic UX Process for Travel Application

Anish (24, M)
Student, Pune

About Anish:
Anish is a college student who travels more often to visit his families and friends across the world. Also, he plans several short trips along with his friends to tourist places in India. Generally, his plans are last hour plans because he is a moody person. He prefers the flights with lowest fare, but always chooses better flights with good service – his preference goes to GO Air most of the time, and he loves to utilize the offers/rewards of the Airline companies.

- Adventures to see new places
- Has family attachments
- Active on smartphones
- Social with friends and community

Key Features:
1. Knowledge of technology and use: 80%
2. Experience of using websites/apps: 40%
3. Use of help documents: 26%
4. Confidence to use website/app: 90%

1. Lack of wireless/3G internet access.
2. Want to see clear information about the screen where I'm - such as if my flight time arrives, I would want to see the Gate number and seat number with appropriate details
3. ...

1. I want to plan my holiday.
2. I want to book tickets for my parents.
3. I'm in a rush and need to book ticket to USA.
4. I have planned my holidays after four months and want to check if any website/app has good deals/offers.

User Stories:
1. As a user I want to be able to search and book flights/hotels without logging in.
2. I want to be able to create my own account.
3. I want to be able to compare flight results and hotel results
4. I want to receive deals/offers/promotion emails.
5. I should be able to cancel my tickets and need to know the cancellation policy.
6. I want to be notified by email if any activity happens with my account.
7. ...

User Flow Diagram:

User Journey Map:


Thursday, December 3, 2015

UX Portfolio


- Wireframing, Prototyping, Interaction Designing, and Graphics Designing
- Usability Heuristics Evaluation
- UX Research techniques
- Principles of cognitive psychology
- Business Requirements gathering
- Field Studies and Usability testing principles and methods
- Information Architecture and Task flow analysis

- Front-end development with HTML5, CSS3, LESS, SASS, Bootstrap, Responsive Web Development, Mobile UX/UI, jQuery, AngularJS, JavaScript, Grunt
- Web Content Accessibility Guidelines (WCAG) 2.0

Domain Knowledge:

- Banking, Insurance, Healthcare, Automotive, Travel, Educational, E-commerce



Project Details:
- What is the project about
It is an education domain where Teachers/Students/Parents collaborate to share information, schedule meetings, and participate in school related activities.

- What problem it solves
Generally, the process of arranging meeting and passing messages between parents and teachers is a long procedure as it depends on the availability of both sides. To make this procedure easier with technology - SumEqual was developed.

- How it helps the end user
Most of the times it's difficult to the Parents and Teachers to discuss all things related to kids development whenever and wherever they want to. SumEqual helps them send/receive messages anytime/anywhere.

- Visual Language
It's derived from the Green Boards of the schools as it gives the sense of school related portal.

- Brand Identity
A combination of school board colors along with Notebook mockings and the typeface appears as a hand writing.

- Problem Statement
Create a Brand for school portal and a landing page where Teachers/Students/Parents collaborate with each other.

Hotel Stay UK

Skills Test

Mobile Apps

Travel app wireframes

My Voyages


Journal Doc

Pack Your Bags