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

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

These tips from LinkedIn's Andrea Lee on running successful global research sessions 👀 👏

🚀 Hiring Alert! 🚀 Are you a passionate Tech Writer eager to immerse yourself in cutting-edge products? Do you thrive in fast-paced environments and love diving into new features? If you excel at understanding customer needs and transforming complex ideas into clear, engaging content, come join the Product team at Dscout! https://lnkd.in/eKJBzRag

Creating a budget for user research (let alone ANYTHING) can be stressful. Budget too little and you risk not being able to do enough research. Budget too much and you risk not getting buy-in. Budget just the right amount and you're probably using our calculator. Try it for yourself with this full breakdown on how to use it—plus a bonus research proposal template. ⤵️

Midweek reminder: It's okay to get negative feedback on something. It's also totally normal to be terrified of getting that feedback. When fighting hard for people to value user research becomes the norm, the last thing we want is to jeopardize that work by doing something wrong. But you need feedback to learn and improve. You need to create safe spaces for receiving feedback. Start small with trusted colleagues. Have them walk you through their feedback in person so you can better understand it (and the tone). Tell them why you're nervous. At the end of the day, you're a person creating stuff for other people. It's okay to approach that as a human.

Here's how to avoid framing bias in your research by rephrasing questions. ▶️ Start by writing biased questions (it's okay to brain dump!). Then rewrite them using neutral language—similar to the visual below. ▶️ Use open-ended questions. ▶️ Use the participant's exact language. ▶️ Summarize what a participant says to make sure you understand it correctly. ▶️ Let the participant fully explain their point-of-view before asking more questions. When a participant has completed a sentence, try counting slowly to three in your head to make sure they're truly done/prompt them to keep talking. The goal here isn't to be perfect, but to bring the unconscious into conscious. 'Cause the same question reworded can lead to two different outcomes.

280 entries were submitted across all categories for the Market Research Society (MRS) and Research Live Awards 2024. One of them, an entry with our customer Vodafone for Business Impact of the Year. Cheers to Georgie Thompson, Ashton Snook, Nick Lockey and the rest of the project team for the finalist nod. We'll be waiting patiently until Dec 2nd... 👀 For a full list of the awards finalists, visit 👉 https://lnkd.in/gCHrmcf For a Vodafone-inspired guide that'll help you create a well-oiled research machine, visit 👉 https://lnkd.in/gZnhA_fS