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

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

You can yell, cry, and shake someone into believing user research is essential. Or you can use this method: Listening with silence. Here's an example scenario of how it might play it out between an internal stakeholder (IS) and the user researcher (UR). 𝐈𝐒: "I think we should implement this new feature that makes customers rate our products they just bought before being able to browse new products." 𝐔𝐑: (Silence) 𝐈𝐒: "I just think it makes sense because we want people to know how to rate things. And we need more product ratings. The more people who rate our products, the more people will buy them. People trust ratings." 𝐔𝐑: (Silence) 𝐈𝐒: "I mean, it matters to our revenue. If there aren't ratings, then people don't buy. Doesn't that make sense?" 𝐔𝐑: "Yes, it does make sense." 𝐈𝐒: "That's right. So, what do you think?" By listening, you gain access to the other person's mind. They're more likely to trust you, be more open, and feel like you are part of their "in-group." Another fun thing about silence is that people want to fill it. And when they keep talking, you may uncover important information they initially left out. Instead of imposing your ideas on the other person, you're learning more about what they need and waiting for them to ask you what you think. Making it easier to have a conversation about how to collaborate.

What does continuous research look like in action? Ask Bradley Mattan, Senior UX Researcher at Vivid Seats. On 10/30, he'll be giving a live look at his team's approach to research, testing hypotheses, and leveraging customer feedback for product innovation. The best part: You'll walk away with actionable techniques you can apply to your own team's decision-making process. Register to attend day of, or get the replay sent to your inbox ➡️ https://lnkd.in/gb2ziph7