Here are some of the few common pitfalls in building user persona:
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n A few more examples:<\/p>\n\n\n\n https:\/\/marketsplash.com\/persona-examples\/#more-418<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Note:<\/p>\n\n\n\n A persona is NOT a replacement for real user testing. This should never replace conducting usability activities with end users.<\/p>\n\n\n\n References:<\/p>\n\n\n\n https:\/\/en.wikipedia.org\/wiki\/Persona_(user_experience)<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Next in series:<\/p>\n\n\n\n Product Visioning: 2.2 User Persona \u2013 Goals, Pains and Gains<\/p>\n\n\n\n After identifying our personas, we have to detail out their goals, motivations, pain points and gains. Pains are their challenges and the gains are benefits if and when they use our system.<\/p>\n","post_title":"Product Visioning: 2.1 User Persona","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"product-visioning-2-1-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:00","post_modified_gmt":"2024-01-29 12:55:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7413","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7290,"post_author":"28","post_date":"2017-03-05 12:30:57","post_date_gmt":"2017-03-05 07:00:57","post_content":"\n We know User Persona<\/strong> is an incredibly powerful tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls \/ mistakes<\/strong> in builing user persona?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Here are some of the few common pitfalls in building user persona: From our experience, we could still come up with more patterns.<\/p>\n","post_title":"CHOW #49\u2013 Common Pitfalls in building user persona?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-49-common-pitfalls-building-user-persona","to_ping":"","pinged":"","post_modified":"2024-01-29 12:55:34","post_modified_gmt":"2024-01-29 12:55:34","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7290","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n A few more examples:<\/p>\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\u2022 Rapid Persona
\u25cb Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl
\u2022 Fake Persona
\u25cb To justify a product feature the team have developed or planning to develop, one or more personas could be invented \/ created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas.
\u2022 Averaging
\u25cb Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn\u2019t help innovation. We need personas as close to the real customer as possible.
\u2022 Rusting Persona
\u25cb Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to be used at all. This is waste of effort and energy. Usually, it is better to start with 2 or 3 key personas and grow more only when there is a need.
\u2022 Personas exist but real customers are avoided
\u25cb I\u2019ve seen cases where fantastic personas are developed. The team gets very comfortable and confident with that shying away from meeting with real customers. This should be avoided.<\/p>\n\n\n\n
\n\n\n\n
Image Courtesy: http:\/\/www.openlawlab.com\/2014\/09\/19\/persona-template-user-centered-design-process\/<\/a><\/figcaption><\/figure>\n\n\n\n