<?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 OpenUX on Medium]]></title>
        <description><![CDATA[Stories by OpenUX on Medium]]></description>
        <link>https://medium.com/@openux?source=rss-65b87dfa88cb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lLm7QSwDbOTusZnIru06kA.png</url>
            <title>Stories by OpenUX on Medium</title>
            <link>https://medium.com/@openux?source=rss-65b87dfa88cb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:10:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@openux/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[Building great experiences for community managers with Console]]></title>
            <link>https://medium.com/@openux/building-great-experiences-for-community-managers-with-console-13f66cdfe923?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/13f66cdfe923</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[discord]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Mon, 08 Apr 2024 16:06:26 GMT</pubDate>
            <atom:updated>2024-04-08T16:06:26.282Z</atom:updated>
            <content:encoded><![CDATA[<p>Earlier this year we published reflections on a user research study we conducted with <a href="https://status.app/">Status</a> about the <a href="https://medium.com/@openux/what-will-it-take-for-communities-to-leave-discord-bd8141161042">suitability of Discord for managing web3 communities</a>. Discord works somewhat well for web3 groups due to its relative ubiquity, crypto bot integrations, easy sign-up and anonymity. <strong>It is still a pain for community managers, but not enough to get them to switch to a different platform.</strong></p><blockquote>“Most of the benefits a new community platform could provide pale in comparison with the risk of losing engagement and/or momentum by making a switch.”</blockquote><h4>But what about non web3-native community managers?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFhycg5Qs2Q1Lu6nzVQ8rg.png" /><figcaption>console.xyz</figcaption></figure><p>Recently we’ve been working with Chris Castig and the team at <a href="https://www.console.xyz/">Console</a> to explore the needs of community managers <strong>who are not in the web3 bubble</strong>. With coaching from OpenUX, the team interviewed community managers who owned networking, interest and mission-driven online communities, as well as content creators (some with paying subscribers). In all instances, growing their community and maintaining high quality engagement are their objectives, and for some managers generating revenue is also the purpose of their community.</p><p><strong>These communities were not using Discord</strong>; they run their communities on platforms such as Whatsapp, Facebook or Patreon. Some of them had tried Discord, but found it didn’t meet their needs. If they <em>did</em> try to move over to Discord, they found that fewer members engaged with that platform than the legacy platforms they were already using (e.g. Whatsapp).</p><p>At the end of the day, member-engagement is the most important factor for community managers; with so many members regularly using mainstream messaging apps like Whatsapp as part of their day-to-day, it makes sense to place the conversation where the user spends their time.</p><p><strong>So, how can a product team building community management platforms better support these community managers?</strong></p><p>Below are just 3 of the many powerful insights gleaned by the Console team, and with their blessing we are sharing them here so that others building in the space can also benefit from these insights…</p><h4><strong>1. Creating an online community tool is not enough, users have to be able to discover it via content platforms and transition to the community seamlessly.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*thlmJ6QxHlVTIroj" /><figcaption>Photo by <a href="https://unsplash.com/@christianw?utm_source=medium&amp;utm_medium=referral">Christian Wiediger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Managers tend to want to grow their community. But just having a space for the community to hang out isn’t enough to drive new people there.</p><p>Often the source for new members is generated from community-related content posted on sites such as Reddit, YouTube, Facebook or Instagram. This content captures user interest, and then drives the user towards the specific community platform (whether Whatsapp, Discord or Patreon).</p><p>The way these top-of-funnel content/discovery platforms integrate with community platforms is currently not optimal.</p><p>Managing a community is a multi-platform experience. Users are using content platforms to market themselves, operational software, CRMs, event listing platforms and other tools as part of their community-stack.</p><p>As builders of a singular product, we can get tunnel vision about the role of our product in the task of our users, and forget to see it as part of a much larger user journey. Product teams building a new community management platform should consider the routes from which members arrive and enable that experience to be as seamless as possible, as well as integrate operational features to make managers’ lives easier.</p><h4><strong>2. For any community, spam is a problem.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dc0NsDfOn950oqh-" /><figcaption>Photo by <a href="https://unsplash.com/@johnishappysometimes?utm_source=medium&amp;utm_medium=referral">John Schnobrich</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The quality of conversation in a community reflects on the community manager; they want their members to remain safe and for the conversations to be of high-quality. Weeding out bad actors is a challenge for all community managers, and for some it’s their biggest concern. The anonymity of user accounts on Discord is unappealing to many. That said, vetting and moderating members on any platform has its challenges.</p><p>Effective vetting, onboarding and spam controls are value adds for any new community management product.</p><h4><strong>3. Web3/crypto is a massive turn-off for some community managers</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LOVIBEBLAlyIxQdM" /><figcaption>Photo by <a href="https://unsplash.com/@kanchanara?utm_source=medium&amp;utm_medium=referral">Kanchanara</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Time and again we see web3 products market their web3-ness as a value add to target users. However, when we step out of the web3 bubble, we learn that <strong>a lot of people in the general population have strong anti-crypto sentiment</strong>. Many will not use a product they feel is heavily aligned with crypto and web3.</p><p>For community managers, this reservation is amplified; it’s not just their preference to avoid a web3 product, they don’t want their audience or members to be put off by their choice of platform either.</p><blockquote><em>“The logos on your homepage for Metamask, Wallet Connect, and OpenSea — I see these and immediately think that this is where scammers come to phish.”</em></blockquote><blockquote><em>“Whenever I see Bitcoin and web3, it’s an immediate turn-off for me.”</em></blockquote><blockquote><em>“A heavy focus on web3 could result in losing a lot of people. They wouldn’t just fail to convert; they wouldn’t understand it at all.”</em></blockquote><blockquote><em>“NFTs and apes feel scummy to me. It feels like it’s more about monetizing users rather than providing great content. Perhaps this brand is intended for a web3 community space? For a broader community, like the people on my server, I would never consider this option.”</em></blockquote><p><strong>So teams building for a non-web3 audience need to scrap the web3/crypto lingo from their marketing pages, and instead focus on explaining the value they bring to the user.</strong></p><p>This research by Console really illustrates the importance of getting out of our web3 bubble to understand users. What we as builders think/hope is important to people, isn’t always the case. In order to achieve mass adoption, we must listen to the needs, pains and perceptions of non-web3 audiences.</p><p>Props to the Console team for doing this important work and setting a great example for customer discovery outside of the web3-native audience.</p><p>Author: Georgia Rakusen</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13f66cdfe923" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What will it take for communities to leave Discord?]]></title>
            <link>https://medium.com/@openux/what-will-it-take-for-communities-to-leave-discord-bd8141161042?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd8141161042</guid>
            <category><![CDATA[discord]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Thu, 18 Jan 2024 16:02:49 GMT</pubDate>
            <atom:updated>2024-01-18T16:02:49.725Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OH1E3KWh6YFtd4AcgXPZ9g.png" /></figure><p>In this piece, we discuss:</p><ul><li>How to delight community managers by supporting their needs around member attention, moderation, and growth</li><li>How to support communities in switching off Discord</li><li>Which communities are ready to switch</li></ul><p><em>Thanks to </em><a href="https://status.im/"><em>Status</em></a><em> for funding and collaborating with OpenUX on this research.</em></p><h3>OpenUX and Status collaborated to ask community managers why they still use Discord</h3><p>Since the rise of web3 communities and DAOs in 2020 and 2021, Discord has been the web3 community standard. Its ‘good enough’ user interface and options for crypto-integrated bots made it an obvious choice for most community managers.</p><p>Three years later, is a platform originally designed for gamers and content creators still the best tool for web3 communities?</p><p><strong><em>What will it take for communities to leave Discord?</em></strong></p><p><a href="https://status.im/">Status</a>, an early entry to the web3 social space with the launch of the Status consumer app in 2017, wanted to explore this topic. While <a href="https://status.app/blog/we-have-been-building-the-whole-time">their flagship app</a> was focused on individual-to-individual messaging, Status had a hunch that the crypto social rails they had created could be leveraged to create a highly-tailored experience for tokenized communities.</p><p><a href="https://openux.xyz/">OpenUX</a> worked together with Status to develop hypotheses about the current experiences and needs of community managers. We recruited over 100 community managers from multiple industries to participate in a large survey and 1-on-1 interviews.</p><h3>How to delight community managers the most</h3><p>One of the outcomes of our research was the definition of different cohorts of communities. We found community managers’ behavior and preferences differed based on the <strong>size</strong> of their community, whether or not their community was <strong>monetized</strong>, and the overarching <strong>purpose</strong> of their community.</p><p>While we discovered insights relevant to only a few cohorts, there were many themes relevant to all community managers. Our recommendations are listed below:</p><h4>Build more reliable ways to grab members attention</h4><p>One of community managers’ most used features on Discord is roles: assigning members to categories that can be sent specialized notifications. While these features are advanced, community managers say utilizing them takes an enormous amount of time.</p><blockquote>“We cannot maintain the roles in our community ourselves. We have a lot of people helping us from the community. With so many people in the community, it becomes hard to send relevant announcements”<em> <br>— Manager of a large, non-monetized, crypto contributor community</em></blockquote><p>Even if a community manages to set up their roles efficiently, challenges grabbing members’ attention doesn’t stop there. The continuous chat-based layout of Discord makes it very difficult to direct members to information in a way that matches members’ natural user journey. Connecting members to important community information is another important area to improve on in competing applications.</p><blockquote>“Discord does a bad job at creating sources of truth and other pinned information for most members to see. When you have everything in one chat, it is super clustered, and super hard to find information.”<em> <br>— Manager of a small, non-monetized, crypto contributor community</em></blockquote><h4>Build more automated ways to moderate both improper and distracting member messages</h4><p>Managers from all cohorts invest a lot of time into moderating bad actors in an effort to protect their members and improve engagement. Workflows that make it easier to moderate bad actors and unfavorable content would serve a large, high-visibility need.</p><blockquote>“The biggest challenge we faced came from people who aren’t part of our community. They join with bad intentions and threaten the security of our members.”<em> <br>— Manager of a small, monetized, crypto social/educational community</em></blockquote><p>—</p><blockquote>“We have people on Discord focusing solely on security and it’s surprising to see how many bots, scammers, and exploiters try to join our server. If bad actors manage to get in they’ll direct message our members or spam our channels.”<br><em> — Manager of a large, non-monetized, crypto contributor community</em></blockquote><p>—</p><blockquote>“We’ve had people engaging in aggressive self-promotion and it’s something we struggle dealing with sometimes. How can we promote the right behaviors?”<br><em> — Manager of a small, non-monetized, crypto social/educational community</em></blockquote><h4>Help communities fuel their own member growth with tools that boost discoverability to new members</h4><p>Most managers are actively broadcasting on multiple platforms where their potential members may gather. If they have enough time and expertise, they’ll also seek promotional partnerships.</p><p>New platforms could build tools that boost outsiders’ ability to discover new communities or platform-wide benefits that grow the pool of active potential community <em>participants</em>.</p><blockquote>“Growth of the community is our biggest job. We’re always trying to figure out how we can grow it further. Right now our goal is to bring more Web2 people into the space and our community.”<em> <br>— Manager of a large, monetized, crypto product community</em></blockquote><p>—</p><blockquote>“It’s really about which partners are aligned with us and will amplify our message to help us find more members and get organic growth”<em> <br>— Manager of a large, monetized, crypto social/educational community</em></blockquote><h3>How to support communities in switching off Discord</h3><h4>Work with managers’ existing mental models by supporting basic channels, roles, permissions, and notifications</h4><p>Many managers have developed their mental models for how community management works in Discord. Those who do have existing mental models expect to set up their communities with a few core features, including multiple channels, roles, announcements, notifications, multi-platform availability, and bot integrations.</p><p>Discord’s broad suite of these essential features is another major inertia factor that keeps managers from trying newer, more focused tools.</p><blockquote>“I like that in Discord you can have multiple channels in one server. I don’t think Telegram has this function yet. That is a must-have.”<em> <br>— Manager of a small, non-monetized, crypto social/educational community</em></blockquote><p>—</p><blockquote>“I think the one thing I might miss about Discord would be the option to create a live call. So I can go to the lounge section and start talking to people there.”<em> <br>— Manager of a small, non-monetized, crypto contributor community</em></blockquote><h4>Support communities with their migration to alleviate concerns over member drop off and lost engagement</h4><p>For most community managers, momentum with growing engagement is the number one goal. Most of the benefits a new community platform could provide pale in comparison with the risk of losing engagement and/or momentum by making a switch.</p><p>New community platforms must share messaging that addresses managers’ concerns about lost engagement and builds confidence that hands-on help is available to manage the transition. Larger communities would especially benefit from services that automate member transfer.</p><blockquote>“We picked and continued to use Discord because our community was picking up steam and we had lots of engagement so we didn’t think about switching from it at all.”<em> <br>— Manager of a small, non-monetized, crypto contributor community</em></blockquote><p>—</p><blockquote><em>“I would say for now we’re gonna continue with our setup. Not currently interested in switching.” <br>— Manager of a large, monetized, crypto product community</em></blockquote><h3>Which communities are more ready to make the switch off Discord?</h3><h4>Smaller communities have a lower bar of requirements to switch and may also have less to lose in making a switch</h4><p>It may be no surprise that smaller and newer communities have less to lose in switching off Discord than larger communities. In addition to having fewer members to migrate, smaller communities may perceive the switch as less difficult given they have fewer sunk costs invested into Discord. Smaller communities are also often run by a few entrepreneurial leaders who are curious enough to explore and in need of new tools.</p><h4>Many larger, more corporate communities are ready to switch if the platform is right</h4><p>For all the reasons mentioned above, convincing a large digital community to leave Discord is no easy feat. However, a platform that highlights ease of migrating members and highly accessible UX appealing to less tech-savvy audiences may ease fears of these managers. Additionally, platforms can delight larger, more corporate communities in unique ways: supporting automated ways to manage large community bases, supporting payments and transactions from members, supporting modern support ticket-like features, etc.</p><h3>What does this mean for community managers and product builders?</h3><p>If you’re a product builder who is building for community managers, consider the insights we shared above and validate them by talking to your own active and prospective users. OpenUX is a collective of user researchers, designers, and product strategists working to make insights like these more available to builders. If you need help talking to your users, feel free to reach out to us at <a href="https://openux.xyz/">https://openux.xyz</a>.</p><p>If you’re a community manager who’s dissatisfied with Discord but uncertain about switching, don’t worry, you’re in the majority. We have seen a lot of new promising platforms propping up in 2023, including our very gracious supporter of this study, Status. If you’re interested in learning more about Status, visit <a href="https://status.im/">https://status.im</a>. We’re confident their support of this research demonstrates their commitment to supporting community managers.</p><h3>Credits</h3><ul><li>Authors and lead researchers on this project: <a href="https://www.linkedin.com/in/henry-harboe/">Henry Harboe</a> &amp; <a href="https://www.linkedin.com/in/manansh-shukla-08b483212/">Manansh Shukla</a></li><li>Special thanks to John Lea, Reise Officer, and the rest of the Status team for supporting this research</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd8141161042" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How node operator experience insights can help Rocket Pool continue to enhance the security of…]]></title>
            <link>https://medium.com/@openux/how-node-operator-experience-insights-can-help-rocket-pool-continue-to-enhance-the-security-of-c33bcc936a18?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c33bcc936a18</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[rocketpool]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Tue, 09 Jan 2024 20:22:08 GMT</pubDate>
            <atom:updated>2024-01-09T20:22:08.337Z</atom:updated>
            <content:encoded><![CDATA[<h3>How node operator experience insights can help Rocket Pool continue to enhance the security of Ethereum</h3><ul><li><em>How does a protocol encourage end users to become node operators, and what stops them in the first place?</em></li><li><em>What is the balance of effort vs reward needed for users to complete the set up of becoming a node operator?</em></li><li><em>How does a protocol turn someone who’s just learning about what a node operator is into someone who is actively contributing to the network?</em></li></ul><p>Over the last 3 months, OpenUX has been working with Rocket Pool on a grant-funded user research initiative to deeply understand, and find ways to improve, the experience for node operators in the Rocket Pool ecosystem. The goals of our study were to:</p><ul><li>Illuminate the existing user journey of becoming a node operator</li><li>Identify the pains and blockers that prevent an interested party from setting up their own node</li><li>Identify ways to encourage more people to become node operators</li></ul><blockquote><strong>The findings from this report are relevant to all staking services and blockchain ecosystems that depend on node operators to guarantee the robustness of their network and encourage growth.</strong></blockquote><p><strong>🌐 Please read </strong><a href="https://storage.googleapis.com/rocketpool/RocketPool-NodeOperator-UX-Report-Jan-2024.pdf"><strong>our full report</strong></a><strong> , which is packed with insights and includes ‘lite’ personas and recommendations to Rocket Pool 🚀</strong></p><p>Here are just a few key learnings from our study to whet your appetite:</p><h4><strong>1. Procrastination is the enemy of completion. Users need a suitable ‘trigger’ to encourage them forward with their investigations into becoming a node operator.</strong></h4><p>The <a href="https://behaviormodel.org/">Fogg Behavior Model</a> can be used by all product teams and protocols to explore whether they have the 3 necessary elements to encourage someone to use their product. According to the model, for a behavior to occur, there must be a convergence of <strong>high motivation</strong> (the person really wants to do it), <strong>sufficient ability</strong> (they are capable of doing it and/or the process is not too complicated/expensive etc), and <strong>an effective trigger </strong>(a moment in time that prompts them to action). If any of these elements is missing or too low, the behavior is less likely to happen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rK6jFjM-zfAuu1Bqnn83Hw.png" /><figcaption>The Fogg Behavior Model explains how encouraging a new behavior relies on a combination of sufficient motivation and ability by the end user, as well as a trigger to move them to action</figcaption></figure><p>Many in the Rocket Pool community are really interested in becoming a node operator. They are motivated by the potential returns and ethos driven, and many are able to follow and complete the process, but without a ‘trigger’, or moment in time that moves them to action, they get stuck in procrastination; trying to decide exactly what the right option is for them, what hardware to get, how to optimize their set up, etc.</p><p>Current ‘triggers’ are pretty limited, one-time events. They include: when the Rocket Pool beta went live, when Rocket Pool was launched, when LEB8 was announced and when staked ETH was enabled. While Rocket Pool has more updates in the roadmap, leaning on such rare events can be a limiting factor for the protocol’s growth.</p><p>Our recommendation for Rocket Pool is to generate more ‘triggers’ that create a sense of urgency, and prompt people to commit. An example of a trigger might be a Node Operator Introductory Course, which inspires someone to begin converting their interest into action.</p><h4><strong>2. Not all node operators are equal. Rocket Pool needs to shape a bundle of benefits that can appeal to this diverse set of users with different requirements and motivations.</strong></h4><p>Our research segmented participants to the study by two main dimensions: the amount of ETH they had bonded, and their technical ability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Uq7zkaSlM5yyymKM_WI4g.png" /><figcaption>Distribution of survey respondents, showing the spread of amount ETH bonded and technical ability</figcaption></figure><p>There were many notable differences in the needs and pains of these cohorts, and we encourage readers to check out the Segmentation &amp; Insights section (Chapter 2 in the full report), but here are some notable learnings:</p><ul><li>Node operators with <strong>more ETH bonded</strong> have greater concerns around tokenomics. The required exposure to RPL makes many potential users feel hesitant about becoming a node operator. While the token is volatile, it also comes with a high yield for RP node operators. Therefore it’s important to nuance the understanding of RPL through making sure the upside is clearly communicated.</li><li>Those with <strong>less ETH</strong> bonded are likely to attain fewer financial benefits from staking than those with more. Therefore it’s vital that Rocket Pool promotes the ‘softer’ reasons to be a node operator (community, exploring and learning about crypto, and helping to keep Ethereum decentralized). If Rocket Pool fails to communicate the softer benefits then people might rely solely on a rationalistic cost/benefit analysis. In that case alternatives with less effort, upfront investment and responsibilities will seem attractive in comparison.</li><li><strong>Less technically able</strong> node operators are more likely to struggle with node setup. The concept of consensus and execution clients is something that even most technical users need to learn in the onboarding journey. While this requires conceptual understanding of how Ethereum works, it also translates to tangible decisions with consequences for people, since the choice of clients affect hardware requirements and performance. Rocket Pool could optimize the experience by creating a more intuitive onboarding journey that prepares users for what’s to come, and provides the right level of guidance, at the right time, to aid decision-making.</li></ul><h4><strong>3. There are different reasons a user might drop-off at different stages of the user journey to becoming a node operator. These include:</strong></h4><p>Awareness stage (discovering Rocket Pool)</p><ul><li>The user knows about Rocket Pool, but assumes it doesn’t meet their needs,they might perceive that the effort or risk is not worth the reward. They might also have criteria (technological, legal, practical, ideological, social or cultural) that Rocket Pool doesn’t meet.</li></ul><p>Consideration stage (attracted to the value proposition of becoming a node operator)</p><ul><li>The user might choose another option due to tokenomic and/or security concerns, smart contract risk, be dissuaded by feedback from others, or be concerned about DAO governance — or just get stuck in indecision due to complexity, lack of information or motivation.</li></ul><p>Choice stage (choosing Rocket Pool as the right option for them)</p><ul><li>The user might come across usability barriers. They encounter a steep learning curve, and don’t have the resources they need to help them overcome the challenge. They may lack time, skill, funds, or motivation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewAt78bMeYmI5n71P5-OgQ.png" /><figcaption>The user journey of becoming a Rocket Pool node operator is split into 4 stages</figcaption></figure><p><strong>Read the full report here: </strong><a href="https://storage.googleapis.com/rocketpool/RocketPool-NodeOperator-UX-Report-Jan-2024.pdf"><strong>https://storage.googleapis.com/rocketpool/RocketPool-NodeOperator-UX-Report-Jan-2024.pdf</strong></a></p><p>What next?</p><ul><li>In the coming weeks OpenUX will be releasing more posts about the findings from this research, including a full user journey map.</li><li>We’re working with the Rocket Pool internal team and wider community to ideate and co-design possible solutions that can be implemented to ensure the continued success of the protocol in attracting and retaining node operators.</li></ul><p>If you work at a protocol that might find these node operator insights helpful, <a href="https://calendly.com/georgia-rakusen/openux-preliminary">get in touch</a> and we can happily talk about some of the findings with your team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c33bcc936a18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How crypto builders can beat web2 incumbents]]></title>
            <link>https://medium.com/@openux/how-crypto-builders-can-beat-web2-incumbents-fa2df9b1570c?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa2df9b1570c</guid>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[go-to-market]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[market-research]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Mon, 18 Dec 2023 22:38:18 GMT</pubDate>
            <atom:updated>2023-12-18T22:38:18.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52C3XVeQ516YXha3ST5oZA.jpeg" /></figure><p>In this piece, we discuss:</p><ul><li>Why new crypto products struggle to gain adoption</li><li>How you can understand the complexity of the ‘job’ users hire you for</li><li>How to attract users based on the ‘job’ you provide</li></ul><p><em>Thanks to </em><a href="https://endaoment.org/"><em>Endaoment.org</em></a><em> for funding and collaborating with OpenUX on this research.</em></p><h3>Why new crypto products struggle to gain adoption</h3><p>Why does Coinbase have <a href="https://u.today/coinbase-market-share-in-us-rises-to-61-despite-sec-lawsuit#:~:text=Specifically%2C%20it%20noted%20that%20Coinbase&#39;s,becoming%20public%20in%20April%202021.">so much market share</a>? Functionality? Usability? Price? Branding? In a larger context, how does any popular web3 app maintain its market share? <a href="https://www.coingecko.com/research/publications/decentralized-crypto-exchanges-market-share#:~:text=Uniswap%20is%20the%20largest%20decentralized,64.6%25%20of%20the%20DEX%20market.">Uniswap</a>, <a href="https://protos.com/what-is-gnosis-safe-and-how-is-it-centralizing-ethereum/">Safe</a>, <a href="https://sacra.com/c/consensys/">MetaMask</a> — all of these products compete with close substitutes, yet they dominate. Why?</p><p>The answer for each is nuanced, but a central theme throughout crypto is that trust reigns supreme. Time and time again as new products emerge and innovate on old paradigms, the bulk of users stick with brands they know and trust, causing many new builders to struggle to retain a customer base.</p><p><strong><em>How can new crypto builders succeed when incumbents’ moats of trust are so strong? Must all builders sidestep their competition by creating entirely new product categories? If not, which areas should new builders invest in?</em></strong></p><p>OpenUX explored this topic with <a href="https://endaoment.org/">Endaoment</a>, a web3 startup looking to re-invent how we all give to charities by modernizing Donor-Advised Funds (DAFs), a philanthropic financial instrument that makes donating flexible and tax efficient. We interviewed 21 donors with various degrees of crypto experience about the extent to which existing tools support charitable giving today.</p><p>What follows is a subset of the insights and recommendations OpenUX developed with Endaoment. Our goal is to help ambitious startups craft a compelling and sustainable product strategy in today’s challenging and incumbent-dominated space. Thank you to Endaoment for committing to keep insights like these open as a public good..</p><h3>How builders can out-innovate web2 incumbents</h3><h4>Understand the complexity of the ‘job’ users hire you for</h4><p>When we asked donors about their reasons for using (or ‘hiring’ in <a href="https://jobs-to-be-done.com/jobs-to-be-done-a-framework-for-customer-needs-c883cbf61c90">Jobs-to-be-Done</a> lingo) Donor Advised Funds (DAFs), we identified two main camps:</p><ol><li>The first camp hire DAFs for a <strong>narrow</strong> job: to deliver funds to charities with little hassle and cost. This group’s motivations begin and end with the transactional benefits of DAFs: give to a charity; receive a tax benefit. Additional benefits that improve the giving experience are of little interest to this group. Unless their DAF is actively making their lives difficult, they’re not seeking out alternatives.</li><li>The second camp hire DAFs for a <strong>broader</strong> job: to increase the impact they have through giving. This group is deeply motivated by the gratification of supporting causes they care about. They often go the extra mile to educate themselves on charities, meet individuals supporting the same cause, and take action in their local communities. This group pushes DAFs to their limit, often taking outside actions to achieve their giving goals.</li></ol><p>For all builders, it’s important to understand the job your users are hiring your products for. When the job is <strong>narrow</strong> (e.g. “execute a task with little hassle”), you have much less room to innovate to get prospective users’ attention. You may be able to carve out a wedge by offering something with better usability or lower cost, but you risk not enough people caring about the job to switch.</p><p>When the job is <strong>broad</strong> (e.g. “increase my impact”), you have much more latitude to impress users with novel features and experiences. Moreover, smaller usability improvements to the most basic, transactional part of the job may not be enough to get your users’ attention. When you’re in this situation, understand where users are putting effort into workarounds, and build something that meaningfully addresses their motivations.</p><h4>When focused on a narrow ‘job’, understand users’ inertia to craft a compelling GTM strategy</h4><p>There are two negative forces that deter someone’s decision to switch to new products:</p><ol><li>The first negative force is <strong>anxiety</strong> of new solutions — people are naturally averse to products they don’t understand, don’t see social proof for, or simply don’t like the look of. All products must combat user anxiety to gain adoption, and we provide some tips for investing in trust to overcome user anxiety in the last section of this article.</li><li>The second negative force is <strong>inertia</strong> of the current solutions — it takes a lot of energy for someone to consider, commit, and follow-through on switching from one solution to another. Some products have higher inertia than others, such as products that rely on network effects, ecosystem lock-in, or have high onboarding costs.</li></ol><p>What can you do if you observe your prospective users’ <strong>inertia is low</strong> — that is, they’re not at all loyal to your competitor’s product? If the job you’re providing for is narrow, you could try to build a product that better solves that narrow job — a “better mousetrap” if you will. If the narrow job is extremely important to your audience (e.g. a tax filing service), a combination of small improvements and crafty messaging may be enough to convert some of your competitor’s users. But if that narrow job is less important to your prospective users, a wildly better solution may fail to capture their attention enough to get them to switch.</p><p>What can you do if you observe your prospective users’ <strong>inertia is</strong> <strong>high</strong> — that is, they’re especially hesitant to leave your competitor’s product? As we mentioned above, if the job you’re providing is narrow, you could invest a fortune into marketing and still see poor results. A lower cost solution may be to find an audience of users who are good candidates for your product and have not yet been onboarded to a competitor. If the job you’re providing is broad, check out the next section in this article about providing unique upsides.</p><p>During our work with Endaoment, we spoke with users who use competitor products for a very narrow job and also have high inertia to leave. It turns out these users were not easily convinced by the proposition of switching to Endaoment based on new features and UX improvements alone given their position of high inertia. But we also spoke with individuals who have never heard of DAFs, despite making donations regularly¹. It turns out the biggest reasons these donors hadn’t tried DAFs was a lack of awareness and trouble onboarding. Endaoment may be able to gain traction faster with campaigns that target onboarding these non-consuming cohorts, rather than go after individuals already using a competing product.</p><p>¹ <em>Interview quotes about awareness of DAFs:</em></p><blockquote>“Nobody’s ever asked me about a DAF” <em>— Participant A, a financial advisor</em></blockquote><blockquote>“I didn’t even know they had a DAF. I mean, I’ve been with [my current wealth management platform] for years and I don’t even know if I saw a DAF option on their website.” <em>— Participant B, a donor</em></blockquote><p>Builders should consider how this applies to them. If your job is narrow and users are dissatisfied with incumbents, consider how much inertia will keep them from trying your ‘better mousetrap’. If your job is narrow and users are already satisfied with incumbents, consider the likelihood of converting non-consuming users with new branding and frictionless onboarding. And if none of this is true because your job is broad, read the next section for suggestions on going after a different job entirely.</p><h4>When focused on a broad ‘job’, provide a unique upside that incumbents can’t</h4><p>We just went over a few strategies for builders when the job they’re providing is narrow. But what if the job is <strong>broad</strong>? As we mentioned before, when the job is broad (e.g. “increase my impact”), you have more latitude to impress users with novel features and experiences. The reason for this is that broad jobs typically span multiple categories of benefits that reach users’ motivations. If you’re serving users for a broader job, more often than not you can find at least one benefit within that job that is underserved or has room to delight users beyond what they’re used to.</p><p>If you can’t identify any leads within the core job you intended to provide, look for adjacent jobs. For example, if someone’s digital payment needs are well served, ask about other financial needs in their business — how satisfied are they with invoicing, tax filing, etc? Even if this ‘secondary benefit’ is not the core part of your product today, if you’re able to provide it successfully, you may be able to leverage the trust it builds with users to upsell them on your product’s other core benefits.</p><p>Part of our research with Endaoment included interviews with Financial Advisors. Many established Financial Advisors hire DAF tools for narrow jobs and face significant inertia to switching. These factors include everything from forced ecosystem lock-in from an employer to concerns over new products’ compliance². However, throughout our interviews, we did hear from a subset of Financial Advisors about the continuous and frustrating challenge of growing a client base. Rather than wastefully designing and marketing features to Financial Advisors who have no interest in a new DAF tool, we identified an opportunity for Endaoment to win over Financial Advisors by providing an adjacent benefit: help them find clients by offering superior client-facing tools that make them standout</p><p>² <em>Interview quotes about awareness of DAFs:</em></p><blockquote>“There are 3 DAF sponsors that are approved. One is the American Endowment Foundation, one is BNY Mellon Charitable Gift Fund and the other is Renaissance Charitable Foundation. I didn’t choose Renaissance because it’s held on a separate platform as the other two.” <em>— Participant C, a financial advisor</em></blockquote><blockquote>“If I were to try a new DAF, I would have to have compliance approval from [employer]… That would probably be the first hurdle to overcome.” <em>— Participant D, a financial advisor</em></blockquote><p>Going after adjacent jobs is not only successful when the job you’re providing is broad, it can also be effective when an incumbent has a lot of market share and users are satisfied. When most users are locked into an incumbent product and it appears there are few users left to sell to, your best path forward may be to innovate into a new job category or user group entirely.</p><h3>Over-invest in trust</h3><p>A reality is that even if you do all of the above well, if new users have never heard of you, have no peers who use you, or don’t trust your brand messaging, your users’ anxiety factors are going to make everything harder for you. The reality of the tech industry — financial tech especially — is that people are more likely to trust institutions they or their peers already know. Trust is itself a network effect, and until you reach critical mass, you are going to have a hard time gaining adoption.</p><p>Through our interviews for Endaoment, we discovered a similar trend: most DAF users chose their vendor based on an existing relationship through another product line³. For example, DAF users who manage assets with Fidelity were extremely likely to be using Fidelity’s DAF product. While part of their rationale for using two products from the same brand was convenience, we discovered lack of trust in new brands would be a significant barrier to convincing any of these users to switch.</p><p>³ <em>Interview quotes about ecosystem lock-in:</em></p><blockquote>“Vanguard is an established name so they can kind of sit behind that brand recognition; there’s a certain trust factor. I had come from their personal investment platform, so I already knew them and figured their charitable arm was probably legit.” <em>— Participant F, a donor</em></blockquote><blockquote>“Vanguard is an established name so they can kind of sit behind that brand recognition; there’s a certain trust factor. I had come from their personal investment platform, so I already knew them and figured their charitable arm was probably legit.” <em>— Participant F, a donor</em></blockquote><p>While there are many ways to invest in trust, we recommend a few specifically based on insights gleaned during our interviews for Endaoment:</p><ul><li><strong>Word-of-mouth not only expands your reach but also makes a meaningful impact on trust</strong>: Our interviews revealed that people hear about financial tools and strategies through people they consider experts via podcasts, investment groups or clubs, reddit, and many other outlets. Builders should lean into the benefits of having other people talk about their product by creating referral programs, getting mentioned in online media, etc.</li><li><strong>User-centric messaging can make discoverability and onboarding easier:</strong> When someone visits a product site, they should be able to immediately understand the product, how it provides them value, and how they can start using it. Builders can achieve this by serving content and messaging with language that speaks to the challenges and benefits users associate with the job they’re hiring a product for. Brands that are disorienting on first impressions, project too much technicalities, and/or don’t ground users in where to begin can be very off-putting and create distrust.</li><li><strong>Human-based customer success can bridge feature gaps and provide additional stickiness through personal relationships with users</strong>: We learned through Endaoment’s users that the core team was amazing in bringing new users’ experiences to life and as a result felt deeply connected to the brand in many ways. Builders should recognize the value of having staff make themselves available to help new users in their early moments using a product. Someone representing the brand can bridge a lack of features or good experience delivery until product teams can catch up to a fully realized roadmap.</li></ul><h3>Take action on these suggestions</h3><p>If you’re a product builder and these insights sound meaningful to you, consider investing in understanding your users so you can chart the best path for your product and company. OpenUX is a collective of user researchers, designers, and product strategists working to make insights like these more available to builders. If you need help talking to your users, feel free to reach out to us at <a href="https://openux.xyz/">https://openux.xyz</a>.</p><p>If you’re an individual active or just interested in donating more to charities, we would strongly recommend Endaoment. Endaoment is committed to building tools for the modern donor, and have demonstrated that clearly by funding this research into their own users. For more on Endaoment, visit <a href="https://endaoment.org/">https://endaoment.org</a>.</p><h3>Credits</h3><ul><li>Authors and lead researchers on this project: <a href="https://www.linkedin.com/in/henry-harboe/">Henry Harboe</a> &amp; <a href="https://www.linkedin.com/in/eric-a-95a5636/">Eric Aker</a></li><li>Special thanks to Robbie Heeger, Vishal Kapadia, Noah Gallant, Alexis Miller, Bruxa, Dae, and the rest of the <a href="https://endaoment.org/">Endaoment.org</a> team for supporting this research</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa2df9b1570c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decrease risk by changing the way you think about user research findings.]]></title>
            <link>https://medium.com/@openux/decrease-risk-by-changing-the-way-you-think-about-user-research-findings-f970054272de?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/f970054272de</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[qualitative-research]]></category>
            <category><![CDATA[research-findings]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Mon, 04 Dec 2023 15:53:02 GMT</pubDate>
            <atom:updated>2023-12-04T15:53:02.488Z</atom:updated>
            <content:encoded><![CDATA[<p>Most user research findings are used the wrong way.</p><p>Findings are used incorrectly because it isn’t immediately obvious what to do with them. It’s unclear what needs to happen next.</p><p>The root cause of this problem? Not <em>knowing</em> how to <strong><em>translate</em></strong> a finding into a clear decision or next step.</p><p>Translating research findings is a hard skill to master. Here’s why:</p><ol><li>You need to trust in both the researcher and their process, which can be overwhelming</li><li>A “smart-sounding” finding can fool you. It’s hard to know what is credible without thinking deeply about a finding.</li><li>A finding alone doesn’t dictate action; it requires interpretation to guide the next steps.</li></ol><p>And so, while knowing how to translate findings is useful. It isn’t enough.</p><p>You also need to shift how you think about findings in the first place — that way you can feel certain that you’re reliably translating findings.</p><h3>Here’s how to think about findings so that you can reduce decision-making risk</h3><h3>1/ Before you start any research, develop a shared understanding of what findings are, why they’re important, and how they’ll be used.</h3><p>The researcher is responsible for educating their team, advocating for the research, and establishing a strategy for translating findings. While there’s no single ‘right’ way to interpret findings, it’s essential that the team agrees on a specific approach.</p><p>Answer these questions:</p><ul><li>What is a finding? What is a finding not?</li><li>Why are findings important?</li><li>How can we apply what we learn? In response to our findings, what decisions might we need to make? Consider the potential impact of your findings on your product or business strategy. What specific changes are you ready to undertake? Clearly define the range of changes you are willing to make in response to the research.</li><li>In what contexts should our findings not be applied, and where are they most relevant? Determine the limits of research findings. Recognize that findings relevant in one context may not transfer well to others.</li></ul><p>Again, the goal is to make sure everyone thinks about findings in similar ways.</p><h3>2/ Once your research is finished, translate findings into decisions</h3><p>1 — <strong>Examine context</strong></p><p>It’s easy to find facts. But it’s hard to figure out what those facts mean for your product/business. That takes a special skill. Without this skill, people will do what they can with the knowledge and biases they have to move forward. And this may not lead to favourable outcomes. This is why you need to examine context.</p><p><strong><em>Why?</em></strong></p><p>Because it’s risky to generalize a finding. And it’s even riskier to just “<em>wing it</em>”.</p><p>So, ask questions like:</p><ul><li>Does this finding fit in the context of the decision we need to make?</li><li>Where does this finding not apply?</li><li>What’s the “shelf-life” of this finding?</li></ul><p>2 — <strong>Once you understand context, think critically about what needs to happen next.</strong></p><p>Don’t make immediate and irreversible changes based on a research finding without first thinking about what the finding means. Avoid being <strong>reactive</strong>. Be <em>reflective</em>.</p><p>Reflect on the finding to figure out what it means for your business and the implications of applying this finding.</p><p>Ask questions like:</p><ul><li>What is the decision that needs to be made? Why does it need to be made? Is it the most important decision that needs to be made?</li><li>Is there finding x decision fit? Does the finding help inform the decision that needs to be made?</li><li>If we use this finding, what are the knock-on effects?</li><li>What are the risks of using this finding? What are the risks if we don’t use it?</li></ul><p>Once you’ve gotten answers to these questions, and it still makes sense to act on the findings…</p><p>3 — <strong>Make the decision and move on.</strong></p><p>If you’re a small-team building a new product, you don’t have 2 weeks to think about findings. As soon as you feel good about the decision, make it and move forward.</p><p>Your decision might mean a change to the product or business. It might also mean you need to do more research. Both are okay.</p><p>All that matters is that you make some type of decision because making no decision wastes a lot of time. Time that you may not have. So make the decision and move on to the next adventure.</p><h3>Wrapping up</h3><p>You now have everything you need to use user research findings correctly. The next time you need to do some user research, use these guidelines to help establish a shared understanding and reduce your decision-making risks.</p><p><a href="https://docs.google.com/forms/d/e/1FAIpQLSdzsv_0edjCVIu0kAg5QxssI38jUiVQMDrebDBnUcvU6_gVDg/viewform"><strong><em>If you need support applying findings, OpenUX offers complimentary office hours for products trying to level-up their UX practice. Click here to find time.</em></strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gDvXyrh8bvpYDqR9USGd9w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f970054272de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Ways to Convince Your Team to Invest in UX Research]]></title>
            <link>https://medium.com/@openux/3-ways-to-convince-your-team-to-invest-in-ux-research-94d7df0c2aac?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/94d7df0c2aac</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[convincing]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Wed, 22 Nov 2023 15:25:43 GMT</pubDate>
            <atom:updated>2023-11-23T19:13:24.875Z</atom:updated>
            <content:encoded><![CDATA[<h3>1/ Clearly articulate the problem and frame researching users as a solution for your team</h3><p>Start by communicating your context, constraints, and goals.</p><p>For example, you’re unsure why a specific feature isn’t being used. And your team needs to decide whether to keep it in the product. The team speculates why this is happening, but no one can say for sure.</p><p>Your team has ten days to decide. Which means you need to figure this out quickly.</p><p>So you think about your options. One obvious solution would be to talk to the people who <strong><em>are</em></strong> and <strong><em>aren’t</em></strong> using the feature to find out what’s happening.</p><ul><li>What do they think it does?</li><li>Why are they using it? Why are they not using it?</li><li>What is it helping them do?</li></ul><p><strong>Goal</strong> = Learning why people are not using this feature so you can decide whether to keep it.</p><p><strong>Context</strong> = Pressure from the team. Uncertainty around low/no usage.</p><p><strong>Constraints</strong> = Need to decide in 10 days. Haven’t researched users before. Some members are skeptical about researching users.</p><p>People on your team need to understand the connection between the “problem” (ignorance around why people aren’t using a feature) and the “solution” (researching users) in order to buy-in.</p><h3>2/ Answer the “so what?” question by tying user research outcomes to your team’s goals</h3><p>For example, If your team aims to improve onboarding so that at least 25% of new users make a “<em>valuable first action,</em>” ground all discussions about researching users in that context.</p><p>Communicate outcomes of the research process that can help reach this goal.</p><p><em>“When we research we’ll learn what our users goals, pains, and needs are while onboarding which we can then use to make decisions about the current flow.“</em></p><p>This way, people understand that researching users is a tool that supports the team’s goals and not a intellectual exercise.</p><h3>3/ Offer multiple options, clearly explain the trade-offs, and let your team pick one</h3><p>Make the decision to research users easy.</p><p>All you need to do is give them four options:</p><ol><li><strong>Do nothing</strong></li></ol><p>Pros</p><ul><li>It’s free!</li><li>You don’t need to change anything</li><li>A low energy/time commitment</li></ul><p>Cons</p><ul><li>You continue to build on risky assumptions that can eventually sink your business</li><li>You’re forced to make decisions without reliable information</li><li>You can’t reliably figure out the “why” behind user behavior.</li></ul><p><strong>2. Do research yourself</strong> (Do-it-yourself)</p><p>Pros</p><ul><li>The upfront cost is lower.</li><li>You can control the research process</li></ul><p>Cons</p><ul><li><strong><em>You can do it wrong</em></strong></li><li>High energy/time commitment with a potential for little return if the process is not executed correctly</li><li>If you don’t have the relevant skills/experience, you risk not getting the answers you need.</li></ul><p><strong>3. Do research with the help of a research coach</strong> (Done-with-you)</p><p>Pros</p><ul><li>Get coached by an expert (like our coaches at OpenUX)</li><li>Get access to all the tools/expertise you need to execute research end-2-end</li><li>Learn how to do the process yourself</li></ul><p>Cons</p><ul><li>There is an initial $ investment.</li><li>High energy/time commitment</li><li>You need to trust your coach</li></ul><p><strong>4. Hire/contract a researcher to do it for you</strong> (Done-for-you)</p><p>Pros</p><ul><li>Very low time/energy commitment</li><li>Get an expert researcher to do everything</li><li>Get answers in the shortest amount of time</li></ul><p>Cons</p><ul><li>The highest investment</li><li>You won’t learn how to do it yourself</li></ul><p><a href="https://calendly.com/openux/openux-office-hours"><strong>If your team is still <em>unconvinced</em>, book a complementary OpenUX Office Hour session to walk through your situation and get guidance here.</strong></a></p><p>UX Research isn’t about understanding users. It’s about minimizing risk.</p><p>The risks include building:</p><ol><li>The wrong thing (market risk)</li><li>The thing wrong (execution risk)</li><li>Something nobody can use (usability risk)</li></ol><p>If these risks aren’t minimized, if they aren’t dealt with. You put yourself, your company, and your vision at risk as well.</p><p>So research your potential users, customers, and stakeholders. It’s worth the investment.</p><p><a href="https://calendly.com/openux/openux-office-hours"><strong><em>Reach out to OpenUX to learn you can protect your biggest downside by researching users.</em></strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hGEXJFNvBVvyfnWvEGNhxg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94d7df0c2aac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get involved with ETH staking user research]]></title>
            <link>https://medium.com/@openux/get-involved-with-eth-staking-user-research-8131df9d9a89?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/8131df9d9a89</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Mon, 20 Nov 2023 18:55:51 GMT</pubDate>
            <atom:updated>2023-11-20T18:55:51.541Z</atom:updated>
            <content:encoded><![CDATA[<p>Are you an Ethereum fan? Running your own node? Or staking your ETH with a service like Lido, Rocket Pool, Stakewise, Coinbase or Frax? If any of these apply to you, then <strong>we want to invite you to take part in our research study!</strong></p><p>It doesn’t matter if you are a Rocket Pool user or not, your input is vital to the success of the entire Ethereum ecosystem.</p><p>It’ll take 5 minutes to complete the survey, and at the end you can opt in for paid user interviews too <a href="https://survey.alchemer.eu/s3/90637535/431aa5d2d435">https://survey.alchemer.eu/s3/90637535/431aa5d2d435</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-OG0i3PfWj3G5FT6hPHAdA.jpeg" /></figure><p>OpenUX is delighted to announce our work with Rocket Pool, to support the DAO and wider ecosystem with understanding how to increase Ethereum decentralization.</p><p>This study is funded by Rocket Pool grants. You can read all about this research project here: <a href="https://open-ux.notion.site/Rocket-Pool-x-OpenUX-Public-Project-Hub-Fall-23-c15a1feacfab4673b170a287896b8dcf">https://open-ux.notion.site/Rocket-Pool-x-OpenUX-Public-Project-Hub-Fall-23-c15a1feacfab4673b170a287896b8dcf</a></p><p>The findings from our research will be made public too! Stay tuned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8131df9d9a89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 3 reasons why builders in web3 need to do UX Research.]]></title>
            <link>https://medium.com/@openux/top-3-reasons-why-builders-in-web3-need-to-do-ux-research-f0a550b58e69?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0a550b58e69</guid>
            <category><![CDATA[builders]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Mon, 13 Nov 2023 21:02:18 GMT</pubDate>
            <atom:updated>2023-11-13T21:02:39.407Z</atom:updated>
            <content:encoded><![CDATA[<p>The reasons are:</p><p>“Building in the Dark” increases the risk of creating meaningless products.</p><ul><li>A meaningless product is a “thing” that no one wants that solves a problem nobody has.</li><li>Doing research with users “Turns the Light On.”</li><li>The point is understanding people’s goals, tasks, contexts, constraints, emotions, behaviors, beliefs, problems, and capabilities. So you can create something usable, useful, and widely used.</li></ul><p>Researching users is like taking an insurance policy out on your product.</p><ul><li>UX Research is risk management. And the best businesses are the ones who can manage risk the best.</li><li>Engaging with users correctly gives you an advantage because others can’t or won’t. And with better insight and resources, your chances of winning in the market increase.</li><li>Your new motto needs to be: “Don’t Trust. Verify with Users.“</li></ul><p>Researching users protects your business by helping you acquire, retain, and create value for users</p><ul><li>Researching users can help you acquire and retain more users.</li><li>Failure is mandatory, but it doesn’t have to happen in the market where stakes are high.</li></ul><h3>Reason 1: “Building in the Dark” increases the risk of creating meaningless products.</h3><p>A meaningless product is a “thing” that no one wants that solves a problem nobody has.</p><p>It’s the classic “<em>solution looking for a problem</em>” situation. I think it’s a delusion shared by builders who insulate themselves from actual users. Who would much rather be “creative” over spending lots of time understanding other people and their lives so that they can deliver a truly relevant solution. We think both are required.</p><p>And if you don’t understand your audience, your product will likely be “meaningless” to them. They provide the necessary feedback loops that keep you and your product honest.</p><p>You can stop building in the dark by turning on the light — by researching your users.</p><p>When you understand people’s:</p><ul><li>Goals</li><li>Tasks</li><li>Contexts</li><li>Behaviors</li><li>Emotions</li><li>Beliefs</li><li>Problems</li><li>Capabilities</li><li>Constraints</li></ul><p><strong>You</strong> are in the ultimate position to create something that they <strong><em>can</em></strong> want. And instead of guessing, go out and figure it out with <strong>them</strong>.</p><p>These people are your teammates. You should not fear them because they are the ones who will make you successful.</p><p><strong><em>Take action by attending an OpenUX Office Hours to learn how to make your users teammates through research. </em></strong><a href="https://calendly.com/openux/openux-office-hours"><strong><em>Learn more here</em></strong></a><strong><em>.</em></strong></p><h3>For example, you’re thinking of building a new NFT marketplace</h3><p>You’ve raised seed capital to build an MVP and hire a small team. Your vision is to build a “mobile-first” NFT marketplace that lets you “swipe” onchain art. If you swipe left, you mint the piece, and if you swipe right, you skip it forever.</p><p>You start by assuming that art is about the connection between artists and art lovers. And Tinder is the model for creating relationships online. So, putting the two together makes sense.</p><p>The MVP gets made. People get hired. And you inch closer to releasing it.</p><p>You give it to 10 artists for “onboarding” purposes. They seem to like it and give you lots of compliments. But when you check analytics, it’s unclear if you’ve got a hit on your hands or if you’ve got a dud.</p><p>After some time, you become frustrated because the artists appeared to support your product. And so, it doesn’t make sense that their usage is so low.</p><p>A colleague suggests speaking with 5 of these artists to see what is happening. And beforehand, you define what you want to learn.</p><ol><li>How do artists think about their relationship with their community?</li><li>What, if anything, frustrates artists about releasing their art?</li><li>Why aren’t the artists using the MVP? Where are they getting stuck?</li></ol><p>You book time and start having conversations. It becomes immediately clear that artists don’t think of their community in the way <strong><em>you thought they did.</em></strong> And so the swiping feature comes off as disingenuous, which might be why they aren’t using it.</p><p>Instead, you learn that Artists often struggle to distribute their content to collectors who own their other works. They find this important because it’s highly likely that existing collectors will mint new pieces over new collectors.</p><p>After you ask them about the MVP, you learn that the MVP is way too hard to use. And they couldn’t upload their art without investing a lot of time.</p><p>In the 5 conversations, you’ve learned that you’ve been thinking about the wrong problem. That there are specific things that artists care about more and that your MVP doesn’t address those. You also find out that the current MVP has big usability issues, which tells you where to make improvements.</p><p>The feedback loop that these interactions give you can adjust the course your product is on. You can learn unique insights into problems that aren’t available anywhere else.</p><p>It’s this feedback loop that gives you the chance to deliver a meaningful solution.</p><h3>Reason 2: It is like taking an insurance policy out on your product.</h3><p>Having more insight than anyone else is the ultimate business strategy. Many people only dabble in understanding their users. But research gives you an edge by uncovering information others miss, choose to ignore, or can’t find.</p><p>It lowers risk for the product, company, and yourself.</p><h3>For example, you’re about to invest $120k for a smart contract audit.</h3><p>You’re told that if your product uses a smart contract, then this is an important investment to make. So, you find a vendor who can do it for you.</p><p>The vendor completes the audit, suggests minor and major fixes, and gives you the green light to launch. When the stakes are this high, it’s important to make formally verify that the contracts work.</p><p>You launch your product.</p><p>After you launch, you might find some parts of your front-end experience aren’t working as planned. You notice that users feel frustrated when performing tasks with your product.</p><p>In a world where <strong>FUD</strong> can kill products, this is a <strong>problem</strong>. Frustrating experiences lead to people trusting your product less. And when people trust your product less, you risk killing your business.</p><p>And if the interface to your smart contracts doesn’t work properly, it’s as if they don’t exist.</p><p>That’s why conducting a formal UX verification is as important as a smart contract verification. Nobody wants the most frustrating way to do something. And so, save your users from that pain by verifying that your product is doing what it needs to.</p><p><strong>Contact OpenUX to learn more about our 5-week formal UX verification service. </strong><a href="https://calendly.com/openux/openux-office-hours"><strong>Learn more here.</strong></a></p><p>Research <strong>protects</strong> your biggest downside.</p><p>It clarifies your user’s goals. Instead of opinions, it reveals people’s behaviors in certain situations. It’s a way of collecting “revealed preferences” over just “stated” ones.</p><p>It is the ultimate form of “<strong><em>Don’t trust. Verify</em></strong>”. And we think it’s time builders take their own medicine. Don’t trust your assumptions. Use research to verify them.</p><blockquote><strong>“Don’t trust. Verify with users.“</strong></blockquote><p>Once you verify, you can avoid things that will cause you many problems later.</p><p>Your users don’t care about your goals. They care about theirs. So, make it your goal to understand them and invest in helping your users reach their goals.</p><p>Verify that you’re understanding them.</p><p>If you do, they will pull you to greater heights.</p><h3>Reason 3: It protects your business by helping you acquire, retain, and create value for users</h3><p>Here are some facts about building products.</p><p>Products that fail to…</p><ul><li>Acquire people to use their product, <em>fail</em>.</li><li>Retain those people, <em>fail</em>.</li><li>Create value for those people, <em>fail</em>.</li><li>Capture value from those people, <em>fail</em>.</li></ul><p>Researching your users influences the types of failure you’ll experience.</p><p>It can help you:</p><ul><li>Discover where people are hanging out online and appropriate ways to get your offer in front of them. (Acquisition)</li><li>Evaluate every part of your product so that churn becomes a “value” problem, not a “usability” problem (Retention)</li><li>Understand people’s goals, constraints and contexts to see if your solution fits into their lives (Value Creation)</li><li>Uncover how and if people will pay by running small experiments in the market (Value Capture)</li></ul><p>And instead of failing in the market. Fail in a “sandbox” while running experiments.</p><h3>For example, you’ve been told that you need to grow.</h3><p>And so you research your users to see what could be hindering your growth outside of marketing, etc. You check your web analytics and churn rates, and you speak with a few users.</p><p>You learn that you’ve got a bigger problem. Your <strong><em>retention</em></strong> is super low. Forget growth.</p><p>It’s like having a leaky bucket. You learn that many new users churn within 7 days of first use. And when you go to learn why, it’s because your product is confusing to use.</p><p>You already understand how to acquire more users. You’ve confirmed that you can capture value based on your value proposition.</p><p>But the “Value Creation” and “Retention” pieces will limit your growth.</p><p>And so, it may be true that you have to work on preventing churn first before investing in more user acquisition.</p><p>You invest resources to “plug the leaky bucket” and test again.</p><p>And again. And again.</p><p>So, if you didn’t know that your users found your product confusing and that was why they were leaving, you’d never think to fix it. The easy answer would have been to say, “<em>It’s a marketing problem. I need more users in the pipeline</em>“ but that never fixes the leaky bucket.</p><p>And so… You’re going to fail regardless. It’s your choice as to where.</p><p>In the market?</p><p>Or in a sandbox, where you can make changes.</p><p>It’s up to you.</p><p>—</p><p>Building something new and bringing it to market can be scary. But, you can reduce your anxiety by doing UX Research early and often, with expert support.</p><p><strong>Have a question? Need help figuring out if you need to do UX Research?</strong></p><p><strong>Reach out to one of our experts </strong><a href="https://calendly.com/openux/openux-office-hours"><strong>here.</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0a550b58e69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding sBTC product market fit amongst Bitcoiners and web3 DeFi users]]></title>
            <link>https://medium.com/@openux/finding-sbtc-product-market-fit-amongst-bitcoiners-and-web3-defi-users-d5850bf66264?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5850bf66264</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Mon, 18 Sep 2023 10:17:50 GMT</pubDate>
            <atom:updated>2023-09-18T10:17:50.318Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Coaching the Stacks product teams to effectively conduct their own product discovery and make better protocol design decisions.</em></p><h3>Background</h3><p>The team at OpenUX coached a working group of product and marketing teams from <a href="https://www.hiro.so/">Hiro</a> and <a href="https://stacks.org/">Stacks</a> to support them with a deep understanding of the potential target users for sBTC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p07WPqCnPoqI-GZvkaxk0g.png" /></figure><p><a href="https://stacks.org/sbtc-nakamoto">sBTC is a new Bitcoin synthetic derivative</a> that has a decentralized, two-way peg mechanism with Bitcoin. It uses Stacks smart contracts to facilitate the movement of BTC in and out of Bitcoin layers in a trustless manner. DeFi applications are in development right now, which means BTC holders will soon be able to put their tokens to work, just as they can on Ethereum today, thereby unlocking utility for the large amounts of BTC currently idle in wallets and on exchanges.</p><h3>Building for the unknown</h3><p>The team hopes that sBTC will benefit two potential retail audiences; Bitcoiners and Web3 DeFi users. The teams building sBTC are deeply immersed in the Bitcoin-sphere but, until engaging OpenUX, had conducted relatively little research around the more DeFi-savvy user profile.</p><p>Understanding these two audiences — what user needs, pains and goals are the same (and which are different) — was essential for reducing development risk and building the right products that are genuinely usable, useful and widely adopted.</p><h3>From assumptions to deep learnings</h3><p>Having conducted some research themselves in the past, the working group sought OpenUX as an expert to guide them through the process of gathering reliable and highly actionable findings that they could rely on.</p><h4><strong>The Coaching Program</strong></h4><ul><li>OpenUX worked with the team over an 8-week period. We created and led a workstream that progressed the team from assumptions and research questions all the way to deep insights widely shared within their ecosystem.</li><li>The coaching was hands-on and collaborative. We had working sessions for writing recruitment copy and screeners, designing questions to ask in user interviews, and what framework to use for analysis.</li><li>Each week included some best practice teachings, which were always grounded in the actual work to be done during that phase of the research.</li><li>OpenUX led by example, sharing our own templates and ways of working, and conducted some of the user interviews to give the team a grounding in how best to run qualitative research sessions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*ENyuExuz1grrPrh1aADoag.png" /></figure><h4><strong>Research Outcomes</strong></h4><ul><li>The mixed-discipline team successfully completed their own research. <a href="https://github.com/stacks-network/stacks/discussions/465#discussioncomment-6316885">Read the published findings by the sBTC team</a>.</li><li>The team landed on research-driven behavioral personas for their target users that aid decision-making.</li><li>The sBTC team had a useful framework to help developers in their ecosystem (who were not involved in the research activity) make sense of the learnings and apply them to their own product use cases.</li><li>By the end of the engagement, the team not only had reliable findings, but also had the templates, tools and frameworks they needed to be able to replicate the process without any hand-holding.</li></ul><blockquote>“Working with OpenUX was essential to the success of this research project. Georgia kept the team focused and on-track week over week, helping us break down a large, complex initiative into weekly, actionable steps.” Elena Giralt, Sr Product Marketing Manager, Hiro</blockquote><h3>A few key learnings</h3><p>The folks at Hiro and Stacks are committed to open sourcing their research findings, which is aligned with what we do at OpenUX. When research is widely shared, it provides more starting points for product teams who don’t have the skills or time to do this important work themselves, and lifts the entire web3 and crypto ecosystem.</p><p>You can read the <a href="https://github.com/stacks-network/stacks/discussions/465#discussioncomment-6316885">full report here</a>, and below we’ve pulled out 3 key learnings to share.</p><h4><strong>1. Bitcoin holders have an emotional attachment to their BTC, regardless of whether they identify as Bitcoiners or Web3 degens.</strong></h4><p>Regardless of what they do in crypto now, many experienced web3 users started off in the space by buying Bitcoin. As such, it holds a special place in their hearts; it marks their entry into the space, and due to lack of utility, a lot of users have not done much with it other than accumulating it or just hodling it.</p><blockquote><em>“Bitcoin is the first crypto I’ve bought and never sold. I’ve not sold it out of respect. Bitcoin is a very philosophical idea, it’s more than money for me. It’s a message. Ethereum is where you can play around, it’s more like a playground.”</em></blockquote><p>This means that whether Bitcoin maxis or Web3 DeFi users, products that ask users to move their BTC out of cold storage must speak to this emotional attachment, and make users feel good about putting it to work. The launch of Bitcoin Ordinals has reignited interest in “using” Bitcoin for many, so there’s precedent here, but it won’t hurt product teams to consider how their positioning and marketing resonates with the “respect” users feel about their Bitcoin in order to encourage users to make use of new BTC protocols.</p><h4><strong>2. Trust/Security and Financial Opportunity are more important than a Bitcoin-first UX design</strong></h4><p>The team used the “Trade-off Triad” method to test potential product trade-offs with users. We presented them with a visual, and asked users to place an icon where they felt they best sat between 3 opposing product features, whilst explaining their thoughts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yohfztAt7XimByjb" /></figure><p>We analysed the clusters where users placed their markers on the triangle, and listened to the rationale as they explained their choice between the trade-offs. When considering a Bitcoin first UX, Financial Opportunity, and Trust/ Security Design, most people said that financial opportunity and security design were the most important factors in deciding to use a new BTC DeFi product. Only a few mentioned the Bitcoin-First experience, if at all.</p><p>This means that any product utilizing BTC must be laser focussed on trust and security design in order to encourage users to adopt, and the financial opportunity has to be worth it for them to use their treasured BTC. These 2 factors trump UI designs that feel Bitcoin-native.</p><h4><strong>3. Decentralized lending and borrowing options are the unmet need for BTC holders</strong></h4><p>For many holders, the risk-to-ratio of lending their BTC on a centralized exchange doesn’t make a lot of sense, especially given what we know about their emotional attachment to BTC, the (comparatively) low returns on lending BTC with exchanges, and the recent exchange closures and risks.</p><p>When we interviewed users, the biggest unmet need was a way to earn interest on, or borrow from, their BTC — without counterparty risk.</p><p>This is good news for the Stacks team and Bitcoin DeFi builders as it confirms their hypothesis that a programmable Bitcoin could be widely adopted — if built and communicated the right way for users.</p><h3>What next for sBTC?</h3><ul><li>The Hiro and Stacks team are continuing with user research discovery, using the tools they learned through coaching to conduct interviews with developers in their community.</li><li>They’re using frameworks to help product teams building in the Stacks ecosystem to come to actions from the findings.</li></ul><h3>Talk to OpenUX about coaching</h3><p>To learn more about getting your team from assumptions to reliable insights, drop us a line. We’re happy to share advice and explore how coaching might work for you: hello@openux.xyz</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5850bf66264" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing our Gitcoin Grant: Providing UX insights for the whole web3 ecosystem]]></title>
            <link>https://medium.com/@openux/announcing-our-gitcoin-grant-providing-ux-insights-for-the-whole-web3-ecosystem-caf9b590ae33?source=rss-65b87dfa88cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/caf9b590ae33</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[gitcoin]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[OpenUX]]></dc:creator>
            <pubDate>Wed, 16 Aug 2023 07:26:23 GMT</pubDate>
            <atom:updated>2023-09-18T10:11:17.337Z</atom:updated>
            <content:encoded><![CDATA[<p>📢 🎉 🙌 Update Sept 2023: Huge thanks to all those who contributed, the grant round closed with a massive $3928.10 in donations from 126 individuals! We are thrilled, please keep your eyes peeled for more updates from OpenUX about the development of an <a href="https://medium.com/@georgia.rakusen/web3-ux-research-as-a-public-ood-e5e0bc5dc2b6">Open Insights Repository</a> (watch this space!).</p><p><em>How we plan to change the game for builders and users, and how donations to our grant application support us on this mission.</em></p><p>Today we’re announcing our <a href="https://explorer.gitcoin.co/#/round/10/0x2871742b184633f8dc8546c6301cbc209945033e/0x2871742b184633f8dc8546c6301cbc209945033e-23">Gitcoin Grant 18 application</a>. We’re seeking donations to fund several organizational workstreams that we believe will elevate the quality of web3 user experiences, and support teams and builders across the whole ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4pkEg4Lof5-uCWv_rQNb-A.png" /></figure><h3>The challenge for the ecosystem</h3><p>The web3 ecosystem today is at the whims of market movements. Bull-market conditions decouple the performance of products from their usability and utility — essentially any project can succeed with enough marketing spend.</p><p>But in bear markets, projects that fail to provide meaningful value to end users, or have poor UX, cannot survive these downturns, and we’ve seen plenty of once-successful projects fail to find and retain users.</p><p>Additionally, the massive benefits of decentralization (fairer systems that empower individuals, greater ownership, security and transparency) have not yet been realised in the wider mainstream. We believe one of the main reasons for this is a lack of expert user discovery and problem-definition, and a lack of reliable pre-made research insights they can readily access.</p><p>Why is there such little user data?</p><ul><li><strong>UX Research conducted in the space usually happens behind closed-doors</strong>. You’ve no way to know if a product has conducted discovery or evaluative research. If they have, these insights sit in silos and are not shared across teams, despite their overall benefit to the ecosystem.</li><li>Teams default to <strong>“code first, ask questions later”</strong>. As a result, many projects exist without certainty about what user problem to solve, with unclear value propositions, often targeting the wrong audience, and failing to reach their full potential.</li><li>Teams know data is important for decision-making, but <strong>many lack the time or expertise to run reliable user research </strong>— often it’s not the person’s core competency, and doing this work competes with other pressing priorities they have.</li></ul><h3>The OpenUX mission</h3><p>We envision a world where web3 development teams understand their users. OpenUX provides builders with context, meaning and insight by contributing expertise and promoting an ecosystem of open-source user research. We do this through a practice of collaboration, empathy and simplicity.</p><p>Donations to our Gitcoin Grant will go to funding a series of workstreams that map to our mission…</p><h3>Support our Gitcoin Grant and enable us to</h3><h4>1. Create an open research and insights repository</h4><p>Since OpenUX’s launch in January 2023, it has always been our intention to create an open UX insights repository that is public and available to all builders in the space. At OpenUX, <a href="https://medium.com/@openux">we publish the research we conduct</a>, and there are other fantastic researchers out there doing the same, but there’s no easy way to mine those insights to find learnings that are applicable to a specific use case or user, and no single place to discover them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*02LXU1hqTTcas6NduRnrSw.png" /></figure><p>We will build and launch an open UX research repository that solves this problem. It will give builders a jump-start, providing them with reliable findings that they can use for internal decision-making and better product strategy.</p><h4>2. Publish self funded and community funded research studies</h4><p>Currently our main revenue source is from bespoke client work. But there are important research themes to explore that a single client wouldn’t naturally fund. Donations to our organization allow us to self-fund ecosystem-wide research, and produce assets such as data-driven behavioral personas, ‘State of UX’ reports and more — which all feed into our open insights repository.</p><h4>3. Develop open learning resources on discovery and validation methods</h4><p>As a group of expert UX researchers, we are well versed in all discovery and validation methods. We want this knowledge to be shared and adopted by the very talented people building in web3, and we aim to do this through workshops, webinars, open office hours, best practice guides and more. Check out our webinar on <a href="https://youtu.be/Dk_qITtpQvY?si=mKvD2US7hCe5WpHp">how to recruit research participants in web3</a> as an example of the types of content we wish to be producing more of.</p><h3>How to donate</h3><ul><li>Gitcoin requires grant donors to set up a <a href="https://passport.gitcoin.co/#/welcome">Passport</a> as a means of proving your unique personhood (and avoiding bots from gaming the grants system). Here’s an easy to follow <a href="https://www.youtube.com/watch?v=l4sFKefMNj8">How To Video</a>.</li><li>Donations from passports that have a score of <strong>over 20</strong> make your donations eligible for Gitcoin’s match funding mechanism. So please verify as many Passport stamps as you can! This vastly increases the impact of your donation.</li><li>Grab some Ether or DAI on Optimism network.</li><li><a href="https://explorer.gitcoin.co/#/round/10/0x2871742b184633f8dc8546c6301cbc209945033e/0x2871742b184633f8dc8546c6301cbc209945033e-23">Donate</a>! Every dollar helps us achieve our mission. You can <a href="https://www.loom.com/share/96cfc517dda84536a59ea07b51937372">follow these instructions</a> for donating.</li></ul><p><strong>Any and all donations are welcome! We deeply appreciate your support in making UX in web3 better for all.</strong></p><p>Love, the OpenUX team 💙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caf9b590ae33" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>