<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Landon LaPorte on Medium]]></title>
        <description><![CDATA[Stories by Landon LaPorte on Medium]]></description>
        <link>https://medium.com/@landonlaporte?source=rss-46fe988badce------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HmslkYSLFZzhu11tC4gOjQ.png</url>
            <title>Stories by Landon LaPorte on Medium</title>
            <link>https://medium.com/@landonlaporte?source=rss-46fe988badce------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:09:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@landonlaporte/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The problem of persona relevancy: tackling issues of applicability & sustainability]]></title>
            <link>https://medium.com/design-bootcamp/the-problem-of-persona-relevancy-tackling-issues-of-applicability-sustainability-5fa81bab70f5?source=rss-46fe988badce------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fa81bab70f5</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[Landon LaPorte]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 14:16:57 GMT</pubDate>
            <atom:updated>2023-07-24T18:21:08.754Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article was co-written by Allison Hansen, User Researcher.</em></p><p>Personas are often a standard instrument in every UX Researcher’s toolbox as they offer representations of key user groups and help create empathy between those developing a product and that product’s potential users (Usability.gov, <a href="https://www.usability.gov/how-to-and-tools/methods/personas.html">link</a>). The creation of personas is often completed at the beginning of a project or development initiative where product, user experience, engineering, and many other teams can have an opportunity to learn about their users before embarking on a solution.</p><p>Yet personas can often fail for a variety of reasons such as limited use, lack of buy-in, lack of collaborative involvement, poor dissemination, or poor persona construction (Salazar, 2018, <a href="https://www.nngroup.com/articles/why-personas-fail/">link</a>). Poor persona construction can manifest in a variety of ways and can lead to issues of <strong>applicability</strong> (personas that are too general and not applicable to a specific product or solution) or issues of <strong>sustainability</strong> (personas that are no longer relevant over time). These issues can especially be the case for teams that service a complex ecosystem of products or experiences. In a world where products, applications, processes, and strategies are constantly evolving it is important to develop personas and a persona library that are contextually specific yet flexible enough to evolve over time.</p><h3>Applicability</h3><p>Perhaps the most important feature of a persona is the ability to provide insight into how a user, user group, or stakeholder interacts with specific products or experiences. When creating a persona, it is vital to provide details about a user group’s major desires, frustrations, challenges, and touchpoints. Personas should be built with these details to evoke empathy and understand for the actual users or audience segment from the solution-makers (designers, researchers, engineers, product managers, etc.).</p><p>One pitfall of persona construction is the tendency to make persona content too vague or generalizable. This can be the result of a team trying to create a broader representation of a user group that many teams or projects can leverage (this is typically the case with marketing personas). However, when a persona lacks the appropriate amount of specificity, it can severely diminish its value and <strong>applicability </strong>as it relates to an individual product or experience. Ultimately, a persona that tries to be too general to apply to all situations might hinder its ability to be valuable at all.</p><h3>How to Address Applicability</h3><p>Addressing applicability can be challenging for teams because persona details live at a variety of levels. Consumers of personas need to both understand high-level details of a user group while also understanding how that user-group would experience a specific situation or context. have both high-level role-based attributes and context-specific experience-based attributes. To address this, it is proposed that personas should contain two sections of role-based attributes and experience-based attributes. <strong>Role-based attributes should focus to the overall intentions and primary objectives for a user or user group. </strong>Role-based attributes are and should be tool-agnostic (i.e., attract clients, produce goods, or provide services). Unlike role-based attributes, <strong>experience-based attributes should directly link to the intentions or needs as they relate to a specific tool, product, or initiative</strong>. A properly constructed persona should be able to address the consistent nature of role-based attributes while being flexible to address the changing elements of experience-based attributes. Essentially a persona should have a foundational section that lets reader understand consistent, role-based attributes of a persona regardless of the experience while allowing a reader to understand the experience-based details that change with the evolving context of the experience.</p><p>To exemplify the delineation between role-based and experience-based attributes, one can use the role of a salesperson as an example. A salesperson has a role-based goal of creating revenue for their company. Associated to creating revenue are the basic role-based goals of gathering leads, presenting value to clients, demonstrating value, and (hopefully) securing revenue. All of these role-based goals are foundational to a seller’s role and drive their day-to-day responsibilities, performance assessments, and typically compensation.</p><figure><img alt="Table describing Role-based Attributes vs. Experience-based Attributes" src="https://cdn-images-1.medium.com/max/1024/1*Uegqn0MAvkIxxQtK_TMCYQ.png" /></figure><p>But to achieve the goal of creating revenue a seller might potentially interact with several different tools or experiences such as CRM platforms, sales demo tools, or processes like a new marketing tactic. These experiences each have their own function of supporting a seller achieve its role-based goal (such as a CRM platform having an experience-based goal of fostering better communication between sellers and clients). These tools create experiences that have their own goals and challenges that, while linked to the overall role-based goal of creating revenue, ultimately achieve that goal in their own specific methods. As such, a persona should be able to delineate how an experience’s goals are largely different yet related to role-based goals.</p><figure><img alt="Image of the collection of personas with role-based attributes and experience-based attributes section. One role-based attribute image on the left of a salesperson with 4 corresponding expanded personas with experienced-based attributes on the right side that detail different experiences for the persona based on the application with which they work." src="https://cdn-images-1.medium.com/max/721/1*OYSdtTV0vYa1xjO6XLZsLA.png" /><figcaption>Role-based attributes contain consistent attributes while experience-based attributes can between tools, initiative, or experience.</figcaption></figure><h3>Sustainability</h3><p>While applicability deals with providing appropriate detail and context of a persona, a persona can also falter by failing to evolve over time (Brown, 2023, <a href="https://www.nngroup.com/articles/personas-are-living-documents/?utm_source=Alertbox&amp;utm_campaign=4a7ee53013-EMAIL_CAMPAIGN_2020_11_12_08_52_COPY_01&amp;utm_medium=email&amp;utm_term=0_7f29a2b335-4a7ee53013-40494377">link</a>). Despite the need to adapt, persona maintenance is often a task left on the backburner of a researcher’s task list. As such, personas that might have been carefully developed from deep data digging and crafted into high-fidelity assets can ultimately become stale, dated, and unretrievable.</p><h3>How to Address Sustainability</h3><p>Dealing with persona sustainability is a question of ownership and maintenance. It should be noted that the perceived value of the persona themselves is not enough to sustain their utility. There should be a specific team identified to support the care and maintenance of personas over time. Often these teams will either be User Research, User Experience, or Market Research teams due to their proximity to users and access to user data.</p><p>While certain teams should be tasked with maintenance, this does not preclude other teams from using, editing, or creating new personas. In fact, this should be fully supported and encouraged. By using the template above of role-based attributes and experience-based attributes, persona creation might even become more feasible and applicable. By focusing other persona users or creators on the role-based and experience-based attributes it is assumed that new iterations of personas can more easily be created and added to the overall persona repository.</p><h3>Tools to Help with Sustainability</h3><p>When determining ownership and maintenance, there should be a consideration for the tools being used for creation and dissemination of personas. Personas can be created with a variety of tools and at a variety of levels of fidelity. From low-fidelity pen-and-paper sketches to high-fidelity mock-ups, personas experience a wide range of approaches. Most of these approaches are created in a time-boxed moment of a project or initiative though. Personas that live as hand-drawn sketches or slides in a PowerPoint can lose relevance over time as they experience issues of versioning and upkeep.</p><p>By leveraging a more dynamic solution that affords persona owners flexibility and version control, owners of personas can help mitigate issues of sustainability. Using a design prototyping tool, such as Figma, helps to maintain version and design control of a persona repository. Unlike a static asset (such as a pdf or slide deck), a design tool can provide a centralized version that serves as a source-of-truth for persona content. It can also be used with efficiency to create a dynamic repository with templates, linkages, and hierarchies. Another benefit, particularly of Figma, is that it also allows for easy templatization and sharing, providing the ability to embed personas into local sites or tools where an entire team, department, or company can have access to the most recent persona versions. This becomes especially important when implementing revisions as Figma can cascade changes to any embedded version of a persona and push updates through the persona ecosystem.</p><h3>Why Is This Important?</h3><p>Persona failure can be frustrating for persona creators and effect the perceived value of persona use. Personas are widely accepted as valuable, but the associated effort with making relevant, data-driven personas and their maintenance costs frequently get overlooked. It is suggested that to address issues of applicability, teams should consider a templatized approach of role-based and experience-based attributes. Teams should also engage in serious conversations of ownership and maintenance to ensure the longevity of personas. When possible, tools such as Figma can also help in maintaining version control and cascading revisions. Ultimately, by addressing issues of applicability and sustainability it is hoped that personas can remain more relevant and useful for longer periods of time.</p><figure><img alt="Image of final product persona in the ecosystem of personas" src="https://cdn-images-1.medium.com/max/1024/1*5HcgqN4bfa58dWJPD4ey4w.png" /><figcaption>Our product persona repository detailing how each persona interacts across initiatives.</figcaption></figure><p>Special acknowledgements to Allison Hansen for editing and contributions, Madeline Hermann for illustrations and images, and Betsie Garner for revisions and candid feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fa81bab70f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-problem-of-persona-relevancy-tackling-issues-of-applicability-sustainability-5fa81bab70f5">The problem of persona relevancy: tackling issues of applicability &amp; sustainability</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>