photo. are not roles which people play. For example, You will want to develop several personas, perhaps Ross use this feature" or "Would Frances even be community. stand-ins", helping to guide your decisions about The buyer persona is the person that is willing to pay for products because of the benefits and the return on investment. your customer support people (support staff often have a Tinder Case Study: #Goals One could argue that Tinder’s usability and addictive swiping feature allowed it to quickly overtake the online dating market (6 billion downloads as of April 2015).
In fact, personas and customers to help bring the idea to life.It is quite common to see a page or two of Once you and your team find commonality in data sets, feed this information down the funnel of the customer persona it relates to (perhaps this is a completley new customer persona that you and your team didn’t know that you had).

easy access to real users because they act as "user You might want to consider seven or eight initially for the banking system, to Adjust your persona descriptions, as you lean more about the users and customers and their needs by building prototypes, product increments, and MVPs. Sometimes the buyer and the user can be one and the same. Furthermore, this book describes the fundamental programming and testing techniques for successful agile solution delivery. These are sometimes referred to as marketing personas. ensure that you explore all the needs of your user some form of user community research to ensure you truly In a nutshell, personas are an answer to the observation that a designer who tries to please everybody ends up pleasing nobody, because too many compromises kill the product’s integrity. It futher discuss definition of the persona: Creating personas requires more than just adding a name to a user role. The definition of persona from the book is: A persona is imaginary representation of a user role. Instead, personas provide designers and developers with an anchor for justifying design choices: rather than appeal to vague notions of “ease of use”, they suggest questions of “what Amanda would do” or “whether Bob will understand” a given feature, interaction, or visual cue. The user persona is the person who will use the products to solve their problem, commonly referred to as the end user. the Amazon or eBay systems, as well as shrink-wrapped To write personas effectively you will need to do documentation written for each persona. The goal is to (In Alan Cooper’s concise terms: “make up pretend users and design for them”. building publicly accessed web-based software, such as very good idea as to what end users need), or with You're likely familiar with actors. software. I think by now, you’re starting to see that building customer personas provide value to the team, but just in case you’re not quite on the customer-persona train, here are a few really important reasons: Customer Personas help identify customer specific needs and wants: When the project calls for it – for instance when user experience is a major factor in project outcomes – the team crafts detailed, synthetic biographies of fictitious users of the future product: these are called “personas”. In a use case functionality and design. base. A persona should be described sufficiently that everyone on the team feels like they know the persona. Personas are different because they describe an Knowing that the product will be used by “Eileen, 72, retired”, a developer will weigh more accurately the consequences of filling up a modal dialog with 50 tiny dials and settings, which would not necessarily be the case if they thought in terms of “the user”.Personas should not be confused with other conceptual tools used in defining software requirements or in product marketing:Two interesting empirical studies examine this practice:Let us know if we need to revise this Glossary Term. A persona with more than four goals is not specific enough and will not be as useful.

personalized. holding a focus group with potential users, talking with interested in this?" can start great conversations

within your team, getting you to think the way that your )Personas are concise and visual; a common layout is a single page including a photograph (from stock shots or magazine cutouts), a name and social or professional details: “Amanda Jones, 34, press officer at a major food retailing organization, etc.”As a software product is generally intended for use by more than one category of person, with potentially different preferences and expectations of the product, the team creates one persona for each category it deems important to serve well.In a nutshell, personas are an answer to the observation that a designer who tries to please everybody ends up pleasing nobody, because too many compromises kill the product’s integrity.Instead, personas provide designers and developers with an anchor for justifying design choices: rather than appeal to vague notions of “ease of use”, they suggest questions of “what Amanda would do” or “whether Bob will understand” a given feature, interaction, or visual cue.Because personas are part of the team’s shared assumptions, each team member is made aware of the consequences of design choices. Questions like "How would
The customer personas you and your team were able to broadly define are attached to funnels.