How did we define use cases at Better Code
Defining use cases of our users is a kind of important part on the definition of the design persona.
Know who are your users, their interests, how are they going to get into your platform, what are they going to do… Are things that we need to know in order to giving them a better experience.
In this post, I’m going to explain how did we do it yesterday in order to help you to define your use cases.
Defining Users: How They Are
You may thing that not, but knowing the personality of your ideal user might help you a lot. List some caracteristics of them. Are they participative, happy, single? Depending on what your app is focus on you need a different type of reactions from your users.
Defining the user workflow: How are they going to find your product and what are they going to do there.
Because of the personality, they need to use your product. What are they going to do in your product, in which order and what are they going to get when they finished. Are they going to have an extra value using your product? If not, you’ve to redesign some things.
Defining goals.
A goal is something the user is going to achieve when it finishes the workflow, but it is going to achieve something to your product too. If it is the end of a purchase, the user is going to achieve products and your product or company is going to achieve some money.
Better Code is an online platform that allows you to share your projects or ideas in order to get help from other people. We’re still developing an awesome platform but you can visit our website now in order to get updated to changes and to follow us on social networks.
