<?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 Wynde on Medium]]></title>
        <description><![CDATA[Stories by Wynde on Medium]]></description>
        <link>https://medium.com/@wynde.io?source=rss-836f746a35b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*339jHFbxUS-aHd-6coX8LQ.png</url>
            <title>Stories by Wynde on Medium</title>
            <link>https://medium.com/@wynde.io?source=rss-836f746a35b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:55:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wynde.io/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[8 Participatory Methods for Research Interviews]]></title>
            <link>https://medium.com/@wynde.io/8-participatory-methods-for-research-interviews-1aec3dbbf7a6?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1aec3dbbf7a6</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[uxr]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Thu, 22 May 2025 11:57:17 GMT</pubDate>
            <atom:updated>2025-05-22T11:57:17.067Z</atom:updated>
            <content:encoded><![CDATA[<p>What if your research participants didn’t just answer questions, but helped shape them?</p><p>In traditional research interviews, we often extract insights like miners with pickaxes. But participatory methods flip that script — inviting participants to co-create meaning, surface the unsaid, and dream about what’s possible.</p><p>To explore this, we invited <a href="https://medium.com/u/8e19b65f0ce5">Amanda Gelb</a> — UX &amp; Product Research Strategist, Professional Question Asker, and founder of Aha Studio — to share essential participatory techniques that will enrich your research perspective.</p><p>✔️ With over 15 years of experience at Google, Lyft and Asana, Amanda helps startups, new teams, and established organizations turn challenges into clear, strategic steps through deep research and dynamic workshops.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fQxOwTdLIGlqI9UBx_NMcw.png" /></figure><h4>Why Participatory Methods Matter?</h4><p>Traditional interviews often feel extractive. Participatory methods transform this dynamic by:</p><p><strong>• </strong>Inviting participants to co-create meaning<br><strong>• </strong>Building deeper trust and rapport<br><strong>• </strong>Surfacing insights that might otherwise remain hidden<br><strong>• </strong>Creating a more equitable research relationship</p><p>Use participatory methods when you want richer, more collaborative interviews, especially in complex or sensitive research areas.</p><h4>1. Co-Creation of the Interview Agenda</h4><p>First step: co-create the agenda.</p><p><strong>Objective:</strong> Build participant investment from the start. <br><strong>Activity:</strong> Invite participants to share what they’re most curious to explore. <br><strong>Prompt:</strong> “Before we dive in, is there anything you’re hoping we talk about today?” <br><strong>Bonus: </strong>Weave their input into your flow for deeper engagement</p><h4>2. Journey Mapping Together</h4><p><strong>Objective: </strong>Make abstract experiences tangible — and reveal pain points participants might not articulate on their own. <br><strong>Activity:</strong> Provide a blank canvas (digital or paper) and collaboratively sketch their process while discussing key moments <br><strong>Prompt 1: </strong>“Let’s map your experience with [task]. I’ll sketch as we talk, where does this typically begin for you?” <br><strong>Prompt 2:</strong> “If you had to draw how this process works (or doesn’t!), what would it look like?”</p><h4>3. Sentence Starters</h4><p><strong>Objective: </strong>Encourage reflection and deeper sharing. <br><strong>Activity:</strong> Offer sentence starters to help participants express ideas that may otherwise stay hidden. <br><strong>Prompt: </strong><br>“A sentence I often hear from colleagues about this is…”<br>“One thing I wish people understood about this is…”<br>“What surprises me most about this process is…”</p><h4>4. Quick Prioritization</h4><p><strong>Objective:</strong> Surface what matters most — fast. <br><strong>Activity: </strong>After discussing a few themes, ask participants to prioritize or rank them. <br><strong>Prompt: </strong>“If you could only fix one of these challenges tomorrow, which would it be?”</p><h4>5. Build the Future</h4><p><strong>Objective: </strong>Shift focus from problems to possibilities. <br><strong>Activity:</strong> Invite participants to dream a little and sketch an ideal version of the product, service, or experience you’re discussing. <br><strong>Prompt:</strong> “If you had a magic wand and could redesign this experience from scratch, what would be different?” <br><strong>Bonus:</strong> Frame it as future-back thinking to unlock more aspirational insights.</p><h4>6. Emotion Checkpoints</h4><p><strong>Objective: </strong>Tap into feelings, not just facts. <br><strong>Activity: </strong>Throughout the interview, pause and ask participants to name how they’re feeling about what’s being discussed. <br><strong>Prompt: </strong>“If you had to pick a feeling emoji for this part of the process, what would it be?” <br><strong>Bonus:</strong> You can offer a quick feelings list or use physical cards if in-person.</p><h4>7. Role Reversal</h4><p><strong>Objective:</strong> Invite fresh perspectives. <br><strong>Activity: </strong>Ask participants to momentarily put themselves in someone else’s shoes, a client, a new user, a boss. <br><strong>Prompt:</strong> “Imagine you’re a brand-new shopper seeing this for the first time. What would confuse or delight you most?” Bonus: Helps reveal hidden assumptions and biases participants may not recognize.</p><h4>8. ‘If This Were a Movie’</h4><p><strong>Objective:</strong> Surface tone, stakes, and emotional narrative. <br><strong>Activity:</strong> Ask participants to imagine the experience as a movie and describe the genre, plot, or key scene. <br><strong>Prompt:</strong> “If this experience were a movie, what kind of movie would it be?” <strong>Bonus:</strong> Reveals emotional undertones quickly and creates a shared metaphor. Was the movie a Comedy? Drama? Mystery? Use that as a jumping off point for follow up questions.</p><h4>Beyond the Interview</h4><p>Participatory methods are essential to a modern research approach and offer value far beyond traditional interviews. They can be applied in:</p><p><strong>• </strong>Unmoderated research settings<br><strong>• </strong>Remote research environments<br><strong>• </strong>Longitudinal studies<br><strong>• </strong>Cross-cultural research contexts</p><p>These approaches show greater consideration for participants and create space for authentic expression and emotional engagement.</p><h4>Ready to transform your research practice?</h4><p>👋 Connect on LinkedIn → Follow <a href="https://www.linkedin.com/in/amanda-gelb-b92b0546/">Amanda </a>for weekly research innovations, strategy frameworks, and workshop techniques <br>🧩 Transform your practice today → DM Amanda about personalized coaching to implement these powerful methods and other strategies that will elevate your research quality and impact <br>🔍 Elevate your entire team → Bring Amanda in for a high-impact lunch &amp; learn session or a comprehensive training series that will equip your organization with cutting-edge research skills and methodologies</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fujzWjqsPu70IIhxDFFeQw.png" /></figure><p><a href="https://wynde.io/">Wynde </a>is a platform that simplifies usability testing and participant recruitment for modern product teams.</p><p>If you and your team are interested in trying out Wynde, <strong>you can start with our free plan</strong>. This will allow you to create your first 3 tests and invite up to 250 testers: <a href="https://app.wynde.io/">https://app.wynde.io/</a></p><p>And make sure to <a href="https://www.linkedin.com/company/wynde/">follow us on LinkedIn</a>, for more tips, product updates and team’s news:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1aec3dbbf7a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 UXR Trends to Watch Out for]]></title>
            <link>https://medium.com/@wynde.io/5-uxr-trends-to-watch-out-for-d96579f9dec1?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d96579f9dec1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[uxr]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Tue, 20 May 2025 14:03:54 GMT</pubDate>
            <atom:updated>2025-05-20T14:03:54.521Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>With Dale Harvey H from UXR Minds</blockquote><p>Since the start of the year, we’ve conducted several in-depth discovery interviews to learn more about researchers’ and product designers’ challenges and pain points. What we’ve found aligns with our observations of active discussions on LinkedIn and in community chats.</p><p>To explore the industry from within, we need to hear each other, build connections, and communicate more. That’s why we asked <a href="https://www.linkedin.com/in/dalehusband/">Dale Harvey</a>, host of the UXR Minds Podcast, to share his observations about what awaits the world of researchers in 2025 ⬇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GvxiAz4LD1OccifkfcUHNg.png" /></figure><h4>1. Ethical Data Collection</h4><p>With stricter global privacy regulations and increased user awareness, researchers must adapt their data collection approaches. What you should prioritize:</p><blockquote><strong>•</strong> Implement <strong>privacy-first tools </strong>that anonymize data at the point of collection<br><strong>•</strong> Ensure<strong> transparent consent processes</strong><br><strong>• Secure data storage solutions</strong><br><strong>•</strong> Methods for gathering meaningful insights <strong>without collecting personally identifiable information</strong></blockquote><blockquote>💡 Pro Tip: The focus on ethical data collection often leads to more authentic feedback as participants feel safer sharing their thoughts.</blockquote><h4>2. Democratized Research Operations: Scaling Without Sacrificing Quality</h4><p>As organizations acknowledge the growing value of user research, expect to see a transformation in how research operations are structured. Key components include:</p><blockquote><strong>• </strong>Self-service research platforms with <strong>built-in quality controls</strong><br><strong>• Automated participant recruitment</strong> and scheduling systems<br><strong>• Standardized templates and playbooks</strong> for common research scenarios<br><strong>• Training programs</strong> that help non-researchers conduct basic studies effectively</blockquote><h4>3. AI: Empowering, Not Replacing</h4><p>AI tools are revolutionizing how we analyze research data. However, AI should enhance, not replace, human analysis. Key developments include:</p><blockquote><strong>• Advanced theme detection</strong> that works across multiple languages and cultural contexts<br><strong>• AI-powered research repositories</strong> that automatically connect insights across projects</blockquote><blockquote>⭐️ Best practice: Use AI for initial data processing while focusing your expertise on validation and strategic recommendations. The goal is to leverage AI to become a more effective researcher, not to automate the entire research process.</blockquote><h4>4. Mixed Reality Research: Understanding Three-Dimensional Interactions</h4><p>The rise of spatial computing creates new challenges for traditional research methodologies. A few methods used to conduct research on this emerging technology:</p><blockquote><strong>• Spatial journey mapping for AR/VR experiences</strong><br><strong>• New metrics</strong> for measuring presence and immersion<br><strong>• </strong>Tools for c<strong>apturing and analyzing gestural interactions</strong><br><strong>• </strong>Methods for <strong>evaluating physical comfort</strong> and<strong> cognitive load </strong>in extended reality sessions</blockquote><h4>5. Global Research Evolution</h4><p>As research becomes increasingly global, researchers are developing sophisticated approaches to cross-cultural studies that go beyond simple translation to create truly culturally adaptive methodologies. Current developments include:</p><blockquote><strong>• Culturally adaptive research frameworks</strong> that flex to local contexts<br><strong>• Tools for identifying and accounting</strong> for cultural bias in research design<br><strong>• Standardized approaches</strong> for managing international research teams<br><strong>• </strong>Methods for<strong> balancing local insights</strong> with <strong>global product strategies</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FME6Iyfo53uD-aKQoWGncw.png" /></figure><p><a href="https://wynde.io/">Wynde </a>is a platform that simplifies usability testing and participant recruitment for modern product teams.</p><p>If you and your team are interested in trying out Wynde, <strong>you can start with our free plan</strong>. This will allow you to create your first 3 tests and invite up to 250 testers: <a href="https://app.wynde.io/">https://app.wynde.io/</a></p><p>And make sure to <a href="https://www.linkedin.com/company/wynde/">follow us on LinkedIn</a>, for more tips, product updates and team’s news:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d96579f9dec1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Questions That Will Help You Find the Right B2B Participants]]></title>
            <link>https://medium.com/@wynde.io/6-questions-that-will-help-you-find-the-right-b2b-participants-eff7750f5bdc?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/eff7750f5bdc</guid>
            <category><![CDATA[b2b]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Thu, 15 May 2025 09:32:27 GMT</pubDate>
            <atom:updated>2025-05-15T09:32:27.486Z</atom:updated>
            <content:encoded><![CDATA[<p>B2B audience: notoriously busy and hard-to-reach, important and mysterious… At <a href="https://wynde.io/">Wynde</a>, we work with such audiences as well — embracing continuous discovery culture within our own team and helping our clients with recruitment.</p><p>In these material, our brand and business development manager <a href="https://www.linkedin.com/in/kszhebrovskaya/">Ksenia Zhebrovskaya</a> shares her expertise in finding B2B participants through 6 key questions that streamline her recruitment process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cfanQPVlJAgGOAjq1LygRw.png" /></figure><h4>1. Who am I exactly looking for?</h4><p>Working with B2B participants involves higher costs and incentives compared to other research participants. Given this investment, it’s essential to engage participants who can provide truly meaningful, actionable insights.</p><p>When building your participant profile, ensure each criterion directly supports your research objectives.</p><h4>2. Can I use my network?</h4><p>One of the most effective ways to connect with specific respondents is to <strong>build your network around them.</strong></p><p>For example, if you’re working with a platform for product designers, connect with designers who use your software or similar products. <strong>LinkedIn</strong> is my go-to: connect with your audience and monitor their posts and discussions. This helps you build relationships (when the right moment comes, they’re just one message away) and better understand your audience’s needs.</p><h4>3. Is it actually that “hard to find B2B audience”?</h4><p>Sometimes B2B participants can be found <strong>within a broader audience.</strong></p><p>For example, if your SaaS helps teams manage processes and build transparent organizational culture, many people will have experience with similar tools. At this point, it becomes simply a matter of effective screening (or even automatic targeting on platforms like Prolific or Respondent.io).</p><h4><strong>4. What are others doing?</strong></h4><p>When practicing researchers mention a resource or specific technique, <strong>it’s worth exploring.</strong></p><p>This approach helps expand your toolkit. For example, beyond User Interviews, we now work with Tandemz, TestingTime, and Polar Insight. Pay attention to specific use cases mentioned. For instance, Tandemz is praised for recruiting testers from Brazil, TestingTime excels with Dutch participants, and for UK-focused research, FieldworkHub or People for Research are your go-to options.</p><h4>5. If it’s too difficult: what could be changed in my current approach?</h4><p>It could be your participant criteria, the incentive you offer, or the message itself. Treat all these as hypotheses and validate them step by step.</p><p>Sometimes<strong> even a change in messaging</strong> can transform the situation.</p><h4>6. Have I tried to go beyond obvious options?</h4><p>Sometimes <strong>you need to get creative.</strong></p><p>Here’s a great example I’ve come across: when a team needed to understand the Chinese-speaking market in Hong Kong, they hired a talented marketing manager from the startup community. She leveraged her network to bring the exact sample they needed for in-person focus groups at their office. This case perfectly illustrates how personal connections and creative thinking can lead to recruiting success</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ceGXq_z8QI_cwQTQuChhzA.png" /></figure><p>Want to learn more? We recently made a post with 5 tips to recruit B2B participants for your research with <a href="https://www.linkedin.com/in/jdelmat/">Julian Della Mattia</a>. And make sure to <a href="https://www.linkedin.com/company/wynde/">follow us on LinkedIn</a>, for more tips, product updates and team’s news:)</p><p><a href="https://wynde.io/">Wynde </a>is a platform that simplifies usability testing and participant recruitment for modern product teams.</p><p>If you and your team are interested in trying out Wynde, <strong>you can start with our free plan</strong>. This will allow you to create your first 3 tests and invite up to 250 testers: <a href="https://app.wynde.io/">https://app.wynde.io/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eff7750f5bdc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Choose the Right Statistical Method for Your UX Research Problem]]></title>
            <link>https://medium.com/@wynde.io/how-to-choose-the-right-statistical-method-for-your-ux-research-problem-31fe3967be81?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/31fe3967be81</guid>
            <category><![CDATA[statistical-analysis]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Tue, 13 May 2025 10:14:36 GMT</pubDate>
            <atom:updated>2025-05-13T10:14:36.658Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>With Bahareh Jozranjbar, researcher at the Perceptual User Experience Lab</em></blockquote><p>Sometimes research starts with a problem. While spotting and defining the problem might be easy, the next step — finding the right research method to solve it — can be challenging.</p><p>To bridge the gap between research intent and methodological choices, we asked <a href="https://www.linkedin.com/in/baharehjozranjbar/">Bahareh Jozranjbar,</a> UX researcher at the Perceptual User Experience Lab, to share insights on this topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dv5KDcWtN_XsgFF6Lu7kww.png" /></figure><h4>1. Let Your Research Question Choose the Method</h4><p>Your method should answer what you’re really asking. Start with the question, not the tool.</p><blockquote>“Do Gen Z and Millennials react differently to the same design?” → <strong>Independent samples t-test<br> </strong><br>“Did our redesign improve satisfaction for the same users?” → <strong>Paired t-test</strong></blockquote><blockquote>“Do users with high cognitive load make more errors?” → <strong>Regression analysis<br> </strong><br>“What UX dimensions emerge from our survey?” → <strong>Factor analysis</strong></blockquote><h4>2. Match Your Method to the Study Design</h4><p>Design structure = your testing blueprint.</p><blockquote>Between-subjects — different participants in each condition (e.g., A/B testing two signup flows) →<strong> Independent-samples t-test </strong>(2 groups) or <strong>One-way ANOVA</strong> (3+ groups)</blockquote><blockquote>Within-subjects — the same participants measured in all conditions (e.g., measuring performance before vs. after a UI update) → <strong>Paired-samples t-test </strong>(2 conditions) or<strong> Repeated-measures ANOVA </strong>(3+ conditions)</blockquote><blockquote>Multi-variable outcomes — you’re tracking more than one outcome at the same time (e.g., task time and satisfaction across 3 UI versions) → <strong>MANOVA </strong>(or <strong>MANCOVA </strong>if you need covariates)</blockquote><p>👉 Example: Want to see how Design A vs. Design B affects both task time and satisfaction? Use a MANOVA to test both outcomes together instead of running two separate ANOVAs</p><h4>3. Think Beyond p-values</h4><p>Significance isn’t the whole story.</p><blockquote><strong>Report effect sizes </strong>(e.g., Cohen’s d) → they show how big the difference is</blockquote><blockquote><strong>Include confidence intervals </strong>→ they show how precise the estimate is</blockquote><blockquote><strong>Use Bayes Factors </strong>→ especially in small-sample iterative testing</blockquote><p>👉 Example: Your t-test says p = 0.048, but effect size = 0.2? That’s a tiny difference, even if it’s “significant.”</p><h4>4. Use Bayesian Methods for Iterative UX Testing</h4><p>Great for small samples, prior data, or when testing continuously.</p><blockquote>A/B testing in sprints? → Use <strong>Bayesian A/B testing </strong>to update beliefs as new data comes in</blockquote><blockquote>Prior knowledge from past studies? → Build it into your model with <strong>Bayesian regression</strong></blockquote><p>👉 Example: You’ve tested 5 versions of a mobile onboarding. Bayesian stats let you use what you’ve already learned to inform version 6 — without restarting the analysis.</p><h4><strong>5. Bring in Machine Learning for Complex Patterns</strong></h4><p>When traditional stats hit a wall, ML can help.</p><blockquote>User segmentation → Clustering (e.g., K-Means)</blockquote><blockquote>Feedback analysis → NLP + Sentiment Analysis</blockquote><blockquote>Predicting task failure →<strong> </strong>Logistic Regression / Decision Trees</blockquote><p>👉 Example: You’ve got 2,000 open-ended survey responses. Use ML-based topic modeling to surface pain points fast.</p><h4>6. Don’t Forget Power &amp; Sample Size</h4><p>Too few users? You risk false negatives</p><p>Too many? You might find meaningless differences</p><p>Use power analysis tools like G*Power to get it right.</p><p>👉 Example: Running a usability test with 10 users per group? It’s fine for early design feedback — not for making product-wide decisions. Know your limits.</p><h4><strong>7. Use a Simple Framework When in Doubt</strong></h4><p>Here’s a 3-step shortcut:</p><blockquote>1. What’s your goal? → Compare, predict, describe, relate?</blockquote><blockquote>2. What kind of data do you have? → Categorical, ordinal, continuous?</blockquote><blockquote>3. How’s the study structured? → Groups, conditions, repeated measures?</blockquote><p>👉 Example: I’m comparing three UI versions on satisfaction (Likert scale) → Kruskal-Wallis test. <br>I want to see if session duration predicts conversion → Linear regression</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OXfN4S6fuS6YlCaEn3mt8A.png" /></figure><p><a href="https://wynde.io/">Wynde </a>is a platform that simplifies usability testing and participant recruitment for modern product teams.</p><p>If you and your team are interested in trying out Wynde, <strong>you can start with our free plan</strong>. This will allow you to create your first 3 tests and invite up to 250 testers: <a href="https://app.wynde.io/">https://app.wynde.io/</a></p><p>And make sure to <a href="https://www.linkedin.com/company/wynde/">follow us on LinkedIn</a>, for more tips, product updates and team’s news:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31fe3967be81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eurasian Bank x Pathway: How the team tested navigation and identified user pain points after app…]]></title>
            <link>https://medium.com/@wynde.io/eurasian-bank-x-pathway-how-the-team-tested-navigation-and-identified-user-pain-points-after-app-0ed824ebc195?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ed824ebc195</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[tools]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Tue, 03 Dec 2024 09:26:29 GMT</pubDate>
            <atom:updated>2024-12-03T09:26:29.373Z</atom:updated>
            <content:encoded><![CDATA[<h3>Eurasian Bank x Pathway: How the team tested navigation and identified user pain points after app redesign — in just a couple of weeks</h3><p><em>Our new story with the Eurasian Bank team</em></p><h3>Context</h3><p>Eurasian Bank JSC, the ninth-largest lender in Kazakhstan, recently redesigned their “My Bank” service. Using Pathway, the product design team conducted several prototype tests to check how new users navigate the app after its recent redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4QgPcFDXHyVqV-hNaUJTA.png" /></figure><h3>Process</h3><p>The team tested various scenarios to evaluate user navigation and understanding within the app. Testers were asked to complete the following prototype tasks:</p><p>01</p><p><strong>To check if users understand how to activate bonus spending</strong></p><p>→ Scenario: You’re making a purchase and want to use your accumulated bonuses. What would you do?</p><p>02</p><p><strong>To check if users understand that they can open status details by clicking on it or through the banner</strong></p><p>→ Scenario: There’s a limit on your card account. How would you check the details of this limitation?</p><p>03</p><p><strong>To check if users can find the needed service on their own and understand its purpose</strong></p><p>→ Scenario: You want to check your card balance. Where would you look for it?</p><p>04</p><p><strong>To check if users understand they can access product details and know where to find the statement</strong></p><p>→ Scenario: You need to check your recent card purchases. What actions would you take to find information about your spendings?</p><p>05</p><p><strong>To check if users understand that they can make payments through the “Payments” service</strong></p><p>→ Scenario: You’ve run out of mobile phone credit. How would you top up your phone balance?</p><p>06</p><p><strong>To check if users</strong> <strong>will pay their monthly payments through the credit banner</strong></p><p>→ Scenario: You have a monthly loan payment. How would you pay it?</p><h3>Metrics the team tracked in Pathway</h3><ul><li>Median Time to Task completion</li><li>Clicks: the number of clicks users make to succeed</li><li>User flow maps: comparing those who followed the target scenario vs. alternative paths taken</li></ul><h3>Results</h3><p>Quick tests via Pathway showed that Eurasian Bank users navigate the application well, even when seeing it for the first time, and utilize omnichannel capabilities in completing tasks. The team confirmed 5 out of 6 usability hypotheses, outlined a plan for changes, and scheduled follow-up tests.</p><p><em>“We really liked how the heatmaps work in Pathway — they show erroneous clicks and first clicks with great precision. These insights make it easy to draw clear conclusions”</em></p><p><strong>Team’s next steps</strong></p><p><em>“In just a couple of weeks, we validated all these new features with Pathway. We’re committed to maintaining strong research practices going forward. Our next step is to conduct focused research on some of the banners. The insights will help us develop and implement effective onboarding for our new users ensuring their experience with the app is smooth”</em></p><p>🟡🟢🔵🟣🔴</p><p>If you and your team are interested in trying out Pathway, <strong>you can start with our free plan</strong>. This will allow you to create your first 3 tests and invite up to 250 testers: <a href="https://pathway.cc/">https://pathway.cc/</a></p><p>And make sure to <a href="https://www.linkedin.com/company/pthwy/">follow us on LinkedIn</a>, for more tips, product updates and team’s news:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ed824ebc195" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[‘Without AI question we would have only gotten superficial answers’: how Pathway AI helps get…]]></title>
            <link>https://medium.com/@wynde.io/without-ai-question-we-would-have-only-gotten-superficial-answers-how-pathway-ai-helps-get-08be51450281?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/08be51450281</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Thu, 07 Nov 2024 10:14:11 GMT</pubDate>
            <atom:updated>2024-11-07T10:14:11.100Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>‘Without AI question we would have only gotten superficial answers’:</strong> <strong>how Pathway AI helps get deeper insights from users without the need for interviews</strong></h3><p>Our new user story with the Kolesa team from Kazakhstan</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9QCbRoK2nh7K3yyy0iQ3nA.png" /></figure><h3><strong>Context</strong></h3><p>Kolesa Group specialises in creating and developing classified ads platforms — services for posting private and business listings in the automotive, real estate, and services sectors. One of the team’s key metrics is retention.</p><p>Kolesa recently introduced paid renewals for listings and observed a sharp decline in renewals in one specific category. With Pathway, the Kolesa team investigated why users weren’t renewing their listings after the introduction of paid renewals.</p><p><em>“We had no hypotheses about why this was happening. Yes, part of it was due to the cost, but such a large proportion shouldn’t have been dropping off.”</em></p><h3><strong>Process</strong></h3><p><em>“If we had known the reasons, we could have used multiple-choice options like ‘I’m no longer selling’ or ‘I don’t see value’ or ‘I’m not getting calls’, etc. Since we didn’t know the reasons, we decided to use an AI question. The instructions from Pathway were extremely detailed, allowing us to quickly grasp the concept and implement it effectively. We launched a pilot with about 200 people.</em></p><h3><strong>Prompt for AI</strong></h3><p>‘You need to analyse user responses and understand what influences their decision not to renew the lifespan of an advertisement on <a href="http://krisha.kz/">Krisha.kz</a>. Try to gather detailed information. Be sure to thank them for their response, and remain as polite as possible. If a user does not want to answer, do not insist. If a user’s response is not detailed, ask for more details. But in no case should you ask more than 3 questions.’</p><h3><strong>Results</strong></h3><p>Users of this specific category with the decline in renewals happened to be less motivated. There were many responses like ‘I’m not in a hurry’, ‘When I saw it became paid, I didn’t bother to renew the listing’ or ‘I’m selling on a neighbouring platform’.</p><p>It turned out that in some regions, for this particular category in private sales, there’s a neighbouring classified site.</p><p><em>“As a result, we outlined new directions for our team. We realised that we need to conduct top-of-mind awareness studies in these areas before introducing such changes. We ended up rolling back this change specifically in that category and now have an understanding of what other hypotheses we need to test.”</em></p><h3><strong>Open-ended question vs. AI-question</strong></h3><p><em>“If we had used open-ended questions, we would have only gotten superficial answers like ‘I don’t need it right now’ or ‘It’s paid now’. To go deeper into whether it’s really just about money, or if the amount matters, or if urgency plays a role, we could have done it only through interviews, but that’s far more expensive.”</em></p><h3><strong>How the team will continue working with AI-question</strong></h3><p><em>“Right after AI-question was released, we were anticipating trying it out. We even held an internal demo day showcasing everything that can be done with the AI block.</em></p><p><em>Also we’re really excited about the voice recording feature for AI questions! We’ve noticed that our team really digs listening to users’ voices — it gives us way more motivation to make changes than just slides with quotes.”</em></p><p>🟡🟢🔵🟣🔴</p><p>If you and your team are interested in trying out Pathway, <strong>you can start with our free plan</strong>. This will allow you to create your first 3 tests and invite up to 250 testers: <a href="https://pathway.cc/">https://pathway.cc/</a></p><p>And make sure to <a href="https://www.linkedin.com/company/pthwy/">follow us on LinkedIn</a>, for more tips, product updates and team’s news:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=08be51450281" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Develop Research Skills in Your Design Team and Measure Their Impact]]></title>
            <link>https://medium.com/@wynde.io/how-to-develop-research-skills-in-your-design-team-and-measure-their-impact-2c4c760e09a7?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c4c760e09a7</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Thu, 29 Aug 2024 11:28:26 GMT</pubDate>
            <atom:updated>2024-08-29T12:08:32.721Z</atom:updated>
            <content:encoded><![CDATA[<p>At <a href="https://pathway.cc/">Pathway</a>, we’re all about teams supporting teams, and that’s exactly how we create our content. It’s always exciting to see how our customers share their experiences and learn from each other along the way.</p><p>To get started, we asked one of our friends, Kirill, to share his experience in fostering a UX culture within his team. He provided some short, easy-to-implement tips on how to develop research skills in your design team and measure their impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RLkVd_YCKYWggbGkfguryA.png" /></figure><h3>How to Develop Research Skills in Your Design Team and Measure Their Impact</h3><p><strong>01 Start with a dedicated research lead</strong></p><p>To kickstart the development of research skills across your design team, one person is enough to get started. Often, one experienced person can set the tone and lead the way. This person becomes the go-to for anything research-related, helping to embed these practices within the team.</p><p><strong>02 Create collaborative research guides</strong></p><p>Begin by building out research guides that cover the essentials. What’s important here is to involve the whole team in the process. When everyone contributes, these guides become shared resources that reflect collective knowledge, rather than just the insights of one individual.</p><p><strong>03 Make ongoing training a habit and build a culture of continuous learning</strong></p><p>Regular training should be a staple in your team’s routine. The research lead could run workshops on key areas like Jobs To Be Done, filling in any gaps in the team’s skillset. Encouraging designers to review each other’s interview recordings is another great way to build a culture of continuous learning.</p><p><strong>04 Appoint UX and research deads as your team grows</strong></p><p>As your design team expands, think about designating leads for both UX and research within each sub-team. These leads can help maintain a strong focus on research as the team scales.</p><p><strong>05 Implement a structured review process</strong></p><p>Make research reviews a standard part of your process. The research lead should step in at two crucial points: first, when the research plan is being crafted, and later, when the findings are being interpreted. This ensures consistency and quality across all research activities.</p><p><strong>06 Host regular knowledge-sharing sessions (once or twice a month)</strong></p><p>Aim to gather the team once or twice a month to exchange experiences, explore new tools (like the latest features in <a href="https://pathway.cc/">Pathway</a>), and address any challenging issues together. Keep these sessions informal — we call them “Fun With Research” to keep the energy light and engaging.</p><p><strong>07 Measure research impact with 2 key metrics: the type of impact and the extent of that impact</strong></p><p>To understand the value of your research efforts, start by tracking two simple metrics: the type of impact (like whether a new feature was launched as a result) and the extent of that impact (how much of the product was influenced). This will give you a clear picture of how research is driving the product forward.</p><p>🟡🟢🔵🟣🔴</p><p>If you and your team are interested in trying our platform, <strong>you can start with our free plan</strong>. This will allow you to create your first 3 tests and invite up to 250 testers: <a href="https://pathway.cc/">https://pathway.cc/</a></p><p>And make sure to <a href="https://www.linkedin.com/company/pthwy/">follow us on LinkedIn</a> — for more tips, product updates and interviews:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c4c760e09a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Prepare for and Conduct a Scenario Test: A Checklist]]></title>
            <link>https://medium.com/@wynde.io/how-to-prepare-for-and-conduct-a-scenario-test-a-checklist-84f2447f4d3f?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/84f2447f4d3f</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Wed, 07 Aug 2024 14:20:00 GMT</pubDate>
            <atom:updated>2025-04-28T13:49:49.764Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey! It’s <a href="https://wynde.io/">Wynde team</a>. We build a tool for research and product design teams to hire testers from all over the world and swiftly validate UX solutions.</p><p>One of the most common tasks our users perform on our platform is testing Figma prototypes. To help you do this efficiently, we’ve put together some helpful tips and compiled them into a handy checklist. Let’s go:)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i5gNexiT8MuJPulOnSKb2g.png" /></figure><p>“We’ll just create a prototype and let users play around with it”. It often seems like you can test a user scenario without much preparation. You have a prototype built in Figma, and now you just need to send it to users and ask them to go through the scenario. Maybe add a couple of follow-up questions afterwards.</p><p>However, in most cases, to create a good “design” for unmoderated scenario testing, you first need to ask yourself a few questions. We’ve compiled them into a checklist:</p><p><strong>01 Do you understand the goal of the research?</strong></p><p>What do you want to learn, and how will you apply the results?</p><p><strong>02 Do you have specific hypotheses or research questions?</strong></p><p>For example: “In scenario A, users will complete the task faster than in scenario B,” or “Which path do users most frequently take to reach the target action in the scenario?”</p><p><strong>03 Are you sure you want to do this without human involvement?</strong></p><p>Some hypotheses simply shouldn’t be tested without a moderator. For instance, if we’re conducting research to catch issues in the user journey, and the scenario is quite large, hearing users’ thoughts out loud might be crucial, or you might need to ask questions on the spot to clarify or steer the research.</p><p><strong>04 Have you prepared the prototype?</strong></p><p>Are the images and texts in the mockups realistic? Are there any dead-end paths? If the target action can be reached in multiple ways, do the alternative paths work in the prototype?</p><p><strong>05 Have you set the context for the user?</strong></p><p>Sometimes it’s helpful to add additional information before starting the scenario: immerse the respondent, explain what is going on, and maybe provide an entry point “from afar” in the prototype to make the scenario more realistic. For example, when testing a scenario in an app, start with a push notification on the phone’s home screen, or ask the user to complete a preliminary task to smoothly lead them into the main scenario.</p><p><strong>06 Have you prepared follow-up questions?</strong></p><p>Sometimes you can do without them, but often, follow-up questions after completing the scenario help uncover valuable additional information. For instance, at the end of the scenario, you can show screenshots of individual screens (so the user can see the interface you’re asking about) and ask about specific elements on these screens.</p><p>🟡🟢🔵🟣🔴</p><p>This is all for now. Perhaps you have your own checklist or questions to review before starting scenario research. Feel free to share them in the comments 🙌</p><p>If you and your team are interested in trying our platform, <strong>you can start with our free plan</strong>. This will allow you to create your first 3 tests and invite up to 250 testers: <a href="https://app.wynde.io/">https://app.wynde.io/</a></p><p>And make sure to <a href="https://www.linkedin.com/company/wynde/">follow us on LinkedIn</a>, for more tips, product updates and team’s news:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84f2447f4d3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Preparing for Unmoderated UX Testing: The 10 Most Common Mistakes. Part 1]]></title>
            <link>https://medium.com/@wynde.io/preparing-for-unmoderated-ux-testing-the-10-most-common-mistakes-part-1-facd15ebc8b7?source=rss-836f746a35b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/facd15ebc8b7</guid>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Wynde]]></dc:creator>
            <pubDate>Thu, 11 Jul 2024 12:13:15 GMT</pubDate>
            <atom:updated>2024-08-29T07:52:42.502Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey! It’s <a href="http://pathway.cc/">Pathway team</a>. We build a tool for research and product design teams to hire any testers needed and swiftly validate UX solutions.</p><p>In an unmoderated test, users answer questions on their own, go through simple scenarios, and compare interfaces — with no interference from another person. This type of study does not require a moderator, but it is important to clearly define the goal, select the right audience, choose the task, and the testing method. Otherwise, mistakes can occur, leading to wasted time, money, and incorrect conclusions.</p><p>Here are the first 5 common mistakes and our team’s tips on how to avoid them.</p><h3><strong>— 1 Conducting an unmoderated test instead of a moderated one</strong></h3><p>An unmoderated test is best suited when you need to quickly survey a large number of people or have specific questions you want answered.</p><p>However, if you want to test a really complex scenario and delve deeper into user motivations, it’s better to conduct a moderated study.</p><p><strong>When is an unmoderated test appropriate?</strong></p><ul><li>When you need to confirm something quantitatively: to validate or refute a specific hypothesis with data from a large number of users</li><li>When you want to get an answer to a specific research question. For example:</li></ul><p>— Will users find the entry point to the scenario?</p><p>— Which solution or element inspires more trust / looks more advantageous or attractive?</p><p>— Where in the navigation will users look for X?</p><p>— Will they understand what the icon does?</p><p>— Which scenario option will users complete faster?</p><p><strong>When is it better to use a moderated test?</strong></p><ul><li>When testing a really large and complex scenario, the more entities and events involved, the harder it is to interpret the research results without a moderator, as you won’t be able to ask specific follow-up questions during the test.</li><li>When you want to learn in detail about user needs and motivations, it might be more productive to have an in-person conversation.</li><li>When you want to delve into the context and causes of a problem.</li></ul><h3><strong>— 2 Incorrectly identified target audience for the test</strong></h3><p>The main rule is that respondents should have relevant experience to participate in the study.</p><p><em>For example: If you want to test onboarding scenarios for your advertising platform, you need business owners and marketers who are potentially interested in advertising on the platform. If you survey everyone indiscriminately, participants might lack the necessary context and experience, which can distort the results.</em></p><p>Sometimes it’s also important to consider demographic factors: age, geography, gender, education level, income level, and other contexts.</p><p><em>For example: If you are working on a premium taxi service, respondents with a salary of less than $1,000 are unlikely to be your target audience — a study with such a sample may distort the results.</em></p><h3><strong>— 3 Wrong number of respondents</strong></h3><p>For example, you surveyed too many or too few people without a clear reason. A small sample size leads to a large margin of error for the entire audience of your product. Conversely, a large sample size that wasn’t necessary results in wasted resources on recruiting respondents.</p><p>To determine the number of respondents, you need to understand the type of research you will be conducting:</p><ul><li>Qualitative — to identify problems and come up with solutions</li><li>Quantitative — to test hypotheses and gather statistics</li></ul><p>For qualitative research (such as conducting an open card sort, identifying problems in a scenario, or analyzing responses to open-ended questions), we recommend recruiting small groups of 5–7 respondents until insights and issues start to repeat. In our experience, a total of 15–20 respondents is usually sufficient.</p><p>For quantitative research, it’s important to understand that the number of respondents affects the margin of error of the results. We recommend involving 95–100 respondents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jaR5DGtfnz1N0wA68dr1pA.png" /><figcaption>For example, you conducted an unmoderated test and surveyed 24 respondents. You ended up with a 70% result for your sample of the entire user base. But with 95% confidence (confidence level), the same answer would be given by between 51.67% and 88.33% of the total user base. This is a wide range, and making decisions based on such data can sometimes be risky.</figcaption></figure><h3><strong>— 4 Poorly defined goal</strong></h3><p>The research goal should align with the product goals. In this case, the test results will increase the chances of making the right product decisions.</p><p>Sometimes at this stage, you can get confused and start testing minor hypotheses while the most important questions lie elsewhere.</p><p><em>For example: You want to introduce a paid subscription for express delivery in an online store. For this, you use a banner at the top of the screen:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BgJDLD-TQVT_1ymCRP0iMA.png" /></figure><p><strong>Mediocre goal</strong>: to choose from several banner visualization options the one that users like the most.</p><p><strong>Good goal</strong>: to check that users understood the meaning of the offer. To choose the offer that looks the most beneficial to users.</p><h3><strong>— 5 Testing things that don’t need to be tested</strong></h3><p>Not all decisions need to be tested, especially those already known from best practices or from your other experiments.</p><p><em>For example: you asked the user to look at the screen of a taxi ordering app.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZiDpuZim007JoEr6BQOTaA.png" /></figure><p><strong>Shouldn’t be tested: </strong>people will understand that they can ask about a child seat in the “Preferences” section. This is a common and time-tested scenario.</p><p><strong>Good to test: </strong>users will understand how to schedule a taxi. Users will understand that the clock icon next to the “Order” button helps to schedule a taxi. Such a multi-button with an icon may cause difficulties, especially considering there is a “Preferences” button nearby.</p><p>🟡🟢🔵🟣🔴</p><p>This is it for now. Part 2 is already cooking. Thanks for reading and feel free to share any feedback!</p><p>To try Pathway you can sign up here: <a href="https://app.pathway.cc/">https://app.pathway.cc/</a> You’ll be able to create your first 3 tests and hire up to 250 testers for free</p><p>Remember to stay curious and make sure to <a href="https://www.linkedin.com/company/pthwy/">follow us on LinkedIn</a> — for more tips, product updates and team’s news:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=facd15ebc8b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>