Dscout

Say hello to dscout’s AI-powered Analysis! ✨ Looking to speed up the analysis of your research, without making a quality tradeoff? Our AI Analysis generates summaries, identifies themes, and categorizes topics—so you can focus on extracting insights and driving impactful change. Learn more about it here: https://lnkd.in/g5Ped7jn

On November 20-21, reimagine your approach to GenAI, UX influence, and business impact for 2025. We'll be playing back talks from this year's in-person Co-Lab event and holding several live Q&As with the speakers. With two day's worth of sessions from leaders at Google DeepMind, Headspace, Meta and more, we promise you'll walk away with plenty of ideas and strategies to ignite your organization. Register today and secure your spot 👉 https://bit.ly/3A75DHX

DON'T send a usability test participant to a page for exploration without defining their end goal. Instead, use this formula when writing tasks: 𝐀𝐜𝐭𝐢𝐨𝐧 𝐕𝐞𝐫𝐛 + 𝐎𝐛𝐣𝐞𝐜𝐭 + 𝐂𝐨𝐧𝐭𝐞𝐱𝐭 + 𝐆𝐨𝐚𝐥 + (𝐎𝐩𝐭𝐢𝐨𝐧𝐚𝐥) 𝐂𝐨𝐧𝐬𝐭𝐫𝐚𝐢𝐧𝐭𝐬 + 𝐄𝐧𝐝𝐩𝐨𝐢𝐧𝐭 1️⃣ Action: This is the specific action you want the participant to perform. 2️⃣ Object: What the participant interacts with. 3️⃣ Context: The scenario or context in which the action is taking place. This sets the stage for the task. 4️⃣ Goal: The purpose or objective of the task. What do you want the participant to achieve or find? 5️⃣ Constraints (Optional) : Any limitations or conditions that apply to the task. 6️⃣ End point: Where do you want the user to end? Writing tasks in this way helps you avoid data that can biased, unreliable, and unrealistic for the real-world experiences of your participants. Find examples of this formula in action here 👉 https://bit.ly/40Q56Tr

Driving action with your research starts long before the project even begins. If you want to architect a project that'll drive engagement and results in the long run, use Eniola Abioye's checklist. It's got: ➡️ core questions to ask stakeholders ➡️ tips on how to gather hypotheses ➡️ how to turn objectives into baseline metrics ➡️ how to do a roadshow after the research is done And a bunch of advice for everything in between. Download the full checklist for yourself here 👉 https://lnkd.in/g-wPunhM

A haunted house but it's just a room full of co-workers asking you, "Who are our users?" If this dreaded but fundamental question has you feeling frustrated, it's time to rip off the band-aid. Do a deep dive into segmentation with this handy six-part guide from Nikki Anderson, MA. ⤵️

Thanks to Product School's community of two million product professionals and experts for naming us this year's Top UX Research Product. 🎉 And an even bigger thanks to our team for making us a product worth naming. Check out the full list of awards and winners 👉 https://bit.ly/4eLz1Cx

Most revolutions start small. If you're hoping to build trust with stakeholders and up the impact of research within your organization, play the long game. 1️⃣ Identify low hanging fruit with a usability test or an insight sprint. 2️⃣ Promote successes. 3️⃣ Scale 'em up to something bigger. At the end of the day, you're trying to build a research *practice.* Let your metrics of success transcend the project cycle. And remember: Stakeholder relationships don't reset after each individual project—they compound over time. h/t Miro's Bo Liu

Researchers make customers visible to the organization by bringing in their voices, experiences, behaviors, and attitudes. But we can't stop there. In an era of "perpetual upheaval," we can (and should) also use customer insights to make the organization visible to itself. h/t Robin Beers, PhD

There's not enough emphasis given to tracking when features we design get deprioritized, descoped, or cut altogether. This commonly happens when: 👉 a design project is started with assumptions, not research 👉 a design is started without fully understanding the product requirements 👉 there's a lack of time or budget to work on all core features with the same care 👉 there's no user testing before implementation 👉 no one's observing users or the analytics of the product after it's in production 👉 there's no style guide or design system in place to structure future design work 👉 a bad dev handoff happens, where designers don't oversee the implementation of their work (Design QA) We get used to hearing "we'll come back and fix it later," and then later never comes. It doesn't have to be this way. Here's a detailed breakdown on how you can start tracking, managing, and resolving debt within your team ➡️ https://bit.ly/406yeYk