This article discusses the importance of defining your html"}]' tabindex='0' role='link'>target audience or html"}]' tabindex='0' role='link'>Personas as they might be referred to by UEX and Product managers.
html"}]' tabindex='0' role='link'>personas to help define your html"}]' tabindex='0' role='link'>target audience and better anticipate the user requirements that will need to be developed into your html"}]' tabindex='0' role='link'>Minimum Viable Product." width="600" height="350" srcset="" data-srcset="https://d2haskyseezqzi.cloudfront.net/wp-content/uploads/2013/06/target_audience01.jpg 600w, https://d2haskyseezqzi.cloudfront.net/wp-content/uploads/2013/06/target_audience01-300x175.jpg 300w" sizes="(max-width: 600px) 100vw, 600px"/>
Introduction
Envisioning your product also involves preparing your product requirements, which need to include a clear definition of your exact html"}]' tabindex='0' role='link'>target audience. This is usually refers to the special characteristic that your html"}]' tabindex='0' role='link'>target audience might have, which may include language, culture, age (whether they are kids, adults, or the elderly), the user’s web ability and several other criteria. These characteristics are important because they help you understand how to convey the product requirements into a set of functionalities that are prioritized within your html"}]' tabindex='0' role='link'>Minimum Viable Product as features that are geared towards fulfilling your html"}]' tabindex='0' role='link'>target audience’s needs.
Identifying your html"}]' tabindex='0' role='link'>Personas
html"}]' tabindex='0' role='link'>Personas are often used as a way to build more specific sets of characteristic around your html"}]' tabindex='0' role='link'>target audience needs. html"}]' tabindex='0' role='link'>Personas are fictional characters created to represent the different types of users within a targeted audience, these could be used to understand attitude and/or a behavior set of a person who might use a site, brand, or product in a similar way.
For example, in one of the mobile product projects I am working on, this new venture has two type of users that it is targeting. In this case, the target involves clients who are asking questions to a set of experts who are in turn answering them. Among these clients there can be identified several sub types which are differentiate them according to their exact needs and specific age group.
To make use of these definitions, first prepare a detailed description of each of the html"}]' tabindex='0' role='link'>personas you are targeting. This process starts by imaging and creating a story behind each persona. Next, ask questions about what that persona is looking for and in what way our product can help with their search. Then describe all of the elements within this persona that relate to our product requirements, which then gives you an idea of the features that need to be specifically addressed in your html"}]' tabindex='0' role='link'>Minimum Viable Product.
In our case example, here are some of the elements that factor into the decision making process
- Days/Time that the product would be used
- Mobile device type (brand / model / OS)
- Age Group
- Type of expert support required
- Mobile apps Savviness
Between product requirements and html"}]' tabindex='0' role='link'>personas
When preparing your product requirements, you may need to pause and review them from the point of view of the html"}]' tabindex='0' role='link'>personas you have now created. This may transform your needs into more specific requirements depending on the user type your persona is targeting and this will also help in adjusting the requirements for the initial html"}]' tabindex='0' role='link'>Minimum Viable Product. This will also help you identify what requirements need to be included as common dominators among all user types.
In some cases each persona will receive a unique user roll to play in the development of the product, allowing it to conduct different operations than what other users may be able to do. In the case with the above example, the expert has tools which will allow him to answer client questions and view client’s profile. This demonstrates that it needs to be addressed specifically in the product requirements.
Developing your html"}]' tabindex='0' role='link'>Minimum Viable Product to the lowest hanging fruit
While identifying your html"}]' tabindex='0' role='link'>personas and determining what your html"}]' tabindex='0' role='link'>Minimum Viable Product functionality should include important so that you know which audience you should address first, the most common practice is to address the lowest hanging fruit. This means that the audience that is the early adapter of your product and the easiest to recruit are the ones that you should be targeting first.
Wireframing and user testing
Transforming your product requirements into wire frames will also need to include, from the perspective of each persona, the product UEX. Consequently it is sometimes a good practice to first conduct a html"}]' tabindex='0' role='link'>walk-through of the product with different identified html"}]' tabindex='0' role='link'>personas just to see if the product html"}]' tabindex='0' role='link'>wireframes are coherent enough from the perception of those users that match the persona description. These people are most likely to help you see what is missing or unclear. Another suggestion is that you do the walk through in groups which gather the same type of users in one place. This will save you valuable time instead of testing every user separately and furthermore this can also encourage more group discussion.
Summary
While it is important to identify your html"}]' tabindex='0' role='link'>target audience generally, you can get a more detailed understanding if you define them with html"}]' tabindex='0' role='link'>personas that represent to you the specific needs of your html"}]' tabindex='0' role='link'>target audience.
This is an important step in the process that identifies what your html"}]' tabindex='0' role='link'>Minimum Viable Product should and should not include, helping you identify where your initial marketing efforts should be best spent.
By identifying your html"}]' tabindex='0' role='link'>target audience according to html"}]' tabindex='0' role='link'>personas you will also help your fellow venture team members share with you their specific feedback, that in turn help you maintaining a consistent understanding of your various html"}]' tabindex='0' role='link'>target audience groups. This also aids the ways that the data you gather about the groups you are targeting can be put in a proper context, be understood, and be remembered in coherent stories or metaphor.
This will also yield proposed solutions that can be guided and informed according to how well they meet the needs of individual html"}]' tabindex='0' role='link'>personas. Such features can then be prioritized based on how well they address the needs of one or more html"}]' tabindex='0' role='link'>personas.
And last and most important, using html"}]' tabindex='0' role='link'>Personas provide a human “face” to your html"}]' tabindex='0' role='link'>target audience, helping you relate and focus your empathy upon the persons that are represented by your specific html"}]' tabindex='0' role='link'>target audience.
