Creating User Persona
When designing product, it is important to know what your user wants. The more user found it nice and comfortable to use your product then the more reason they want to invest on your product. That’s why there’s a need to make User Persona.
What is User Persona?
User Persona is a description of user that represents the needs of a larger group of users. Mainly a User Persona consist of basic information, their goals for using the product, motivations, as well as their frustrations. Let me explain for each part:
1. Basic information
Consist of name, age, occupation, etc, depending on what category that has impact to your product. For the example, tech skills (low/medium/high) as reference for making a website, literate (yes/no), etc. You can even add bio if you want to. For name, I usually use fake name generator that can be found with searching using Google.
What user want to achieve while using the product. For the example, a chef wants the pizza cooked in 10 minutes while using the product. Goals can also be more than 1 especially if your application has many features.
What makes user want to use your product. For the example, some user love to use some websites because it is efficient. This is the one that I found hard to determine, since it is usually based on what I experience. It is better to find a friend or other people to confirm what you write, you can also ask their own perspectives about it.
What makes user need to use your product based on what your product offers. For the example, a student found it hard to read text book because the content is too long. Depending on how you collect data can help making this easier to determine, especially if you use interview as a way to collect data since you can just ask while interviewing.
Here’s an example of User Persona for that my team and I made.
For me things that helped when making user persona are based on what I see/experience in daily life, problems that people around me have, and forums in internet. You can also collect some data with questionnaires, interviews, and more other ways depending on which one that makes the data collected easier to process.
It is important to make User Personas before designing the application. You can take notes of which user problems need to be fixed, what features to add, determining the interface designs, and leave the rest that are not needed.
Not all user feedback need to be implemented in your application, just take some that relevant for your application and can create positive impact for the most users.
After researching more into creating persona, I found this picture that explains a bit about the role of persona and how to make persona in a way that is more easier to understand.
Implementing needed features
As what I have said before, how to implement the design and structure of the application is based on user persona. For the example if the user is kind of in need of snappy or fast access to features, then it is important to place that specific feature access in the navigation bar or even show the most needed thing in the table.
In the example below, the proposal status, title, and creator is important (for student), so they are shown. The details such as the teacher associated with the proposal is also important but not as important as the previous part mentioned.
So for the best design implementation, it is not shown in this list (a list is better simple and not too many information). Well the more reasonable excuse is so that the proposal details has function (why need details page if all the details of an item is shown in the table).
And also, the shown proposal is the one that has connection with the current student that is logged in.
There’s a bit similarity between teacher view with the student view, it only shown which proposal that is submitted to that teacher (current logged in teacher). There’s a filter and sort for easier access to specific type of proposal.
There’s also an importance in the content. If the content can only be accessed after logged in then it is better to redirect it to the login page. In this case even the home page shows that you need to log in first
There’s also a terms of familiarity when designing, such as accessing profile by clicking your profile picture in the right of the screen. Or if the user is not really tech literate, the design needs to have more description. There’s also a thing in some forms, if the user is in need of detailed input such as time, password, etc. Then implementing a validator in the form would be the best. This is an example from my university project.
Then what is the thing needed to be done after implementing persona in the application/product? That is user testing using a real user of course. The first time can be done by the developer team for checking usability, error, and bugs. But after that, the real tester would be the some users that needed/assumed need to use product to solve their problem. There would be some feedback towards the product after testing be it majority positive then good, or negative that means there’s a need to change.
That’s all I know about Persona currently, there could be more updates to the article if needed.
Thank you for reading, hope this helps!