If you do this, you risk creating a bias view of that persona. Never – and we repeat – never use an image of a celebrity or someone from your company. It can be a photograph, a cartoon or a sketch, but it must represent the person well in terms of age, lifestyle and occupation. Include psychographics – behaviors, attitudes, opinions, and motivations are what make your personas human.Try and make it as visually appealing as possible – you will have put a lot of work into your persona and you want it to stand out – using an attractive color scheme that’s indicative of your persona’s characteristics, as well as icons and graphics can help in understanding who they are.Try to make sure that your user personas don’t overdo text – the simpler the better, as they will be easier for your end users to internalize their details and mindsets while the product is in development.These are usually the key factors in coming up with your product design and development solution. Goals and pains should more-or-less take center stage.Below are some general best practices to keep in mind when choosing your user persona template. You want something you can refer back to again and again through the design process, even as you put your favorite prototyping tool to good use. Whatever the case may be, you should always bear in mind that too much detail can suffocate a persona, make them boring and less memorable for the end user. Sometimes, depending on budget and time-restraints, a well-researched user persona is in order, whereas, in other cases, a lean persona template might suffice. When deciding what information to include in the persona template, bear in mind that while certain details might be relevant to one project, they could be irrelevant for another. One great piece of advice from Twistlab Marketing is that a user persona’s design should ideally be based around the Pareto Principle, whereby they will represent that 20% of your userbase that will use 80% of your products’ features, or that will account for 80% of your revenue. How much detail you choose to include depends on what’s relevant, but the general rule of thumb is that less is usually more when talking about user personas. Keep in mind the effect you want it to have on whoever views it – you’ll want it to be memorable. When it comes to design, apart from some general best practices, there are no rules as to what your user persona should look like – the sky’s the limit! The type of persona that best fits your purpose will be determined by what kind of app or website wireframe you’re designing, as well as the scope of your product, the userbase the persona template will represent and your company culture. She echoes the type of person we at Justinmind are setting out to help with our prototyping tool. She’s young, single, full of energy and wishes to take charge and grow the UX team in her company, possibly looking to become a manager at some point. If they are inconsistent, they will feel more like a lie and you’re hence more likely to end up with an inconsistent product.Īt a glance, and from the colorful persona picture, we can already see that this user is a young innovator who is looking to place more of an emphasis on UX in an attempt to reform old UI design practices at her corporation. If your user persona is consistent, they will seem much more real and be more memorable. Everything from the bio, goals, frustrations and even the influences section reflects this quote. The entire persona can be summed up with the quote in the top right-hand corner: “I want to help my team deliver great user experiences”. Note that this user persona has a crucial element throughout and that is consistency. Even your MVP should be tailored to the right user personas. Sticking to this rule will not just save you time and money, but also ensure your product is a hit with your users. The time to use this user persona is during the design stage, not in the development stage. Therefore, the time to create a user persona is before the design begins, not after. You don’t want to lose these users by trying to cater to the masses because it’s precisely these users that will generate the most revenue for your product. The worst part is that they might even be your ideal users. User onboarding must be quick, otherwise you risk losing them. You then realize that the time to do the survey was before the design even started. For the user, it means the added interaction cost of actually filling in the survey and answering the questions, instead of getting straight into what they downloaded the app for: recipes! The survey feature might seem like a great idea at the start, but think about how much more time you would need to design an app that caters to all users, along with the extra time spent in development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |