I'm a researcher at Dunder Mifflin. My job is to make sure that we understand our users needs and that our paper production evolves accordingly. I'm the voice of the customer within our team.

It can be really hard to get a hold of our customers for research! They're just so busy

We have an internal participant pool of 100 folks we can reach out to. The problem is response rates can be low, and we also end up cycling through the same users over and over again.

I work at Acme as 1 of 5 researcheres. Kids have changed a lot over the years and so we do continuous research to understand what is interesting and exciting to them!

Kids are hard to recruit for research because you want to be mindful of their privacy and security. It ends up taking a long time to get the conversations going.

The other part is the analyzing the data is really hard! It takes such a long time to parse through tons of information and I struggle to communicate it effectively to my team. Luckily, more often than not, others on my team join the calls as well.

I've not been able to solve recruiting well, but for analysis I've started using this awesome tool called Loop!

At Stark we take design pretty seriously. We have a very good equation with Product Managers on our team and work with them, Engineers and Researchers for every product sprint.

Because the company is so large and we're running on short timelines, it can be really hard to analyze data quickly (so overwhelming!) and share the insights with the rest of the design & product organization so we don't repeat the same studies over and over.

Recruiting is also a pain - it takes a long time to get folks through the door, no matter how much money we throw at the problem.

We're trying to create a research repository but we haven't found the right way to structure it yet.

In terms of recruiting, we've hired a few agencies, but it still takes time. Besides, we actually want to speak to our own users more often.

As a Designer at Olivander's, my job is to design kick-ass wands. I make sure to speak to users before designing a new wand, and also test them before they go into production. One time we had a faulty wand go into production - boy, that was a mess.

I want to run a lot of tests and research during the design process, but it takes so long to make sense of the findings that sometimes I have to forgo that step.

I've started sharing video snippets of our findings in Slack - that really helps to get the team aligned around the voice of the customer!

No good solution on analysis yet - I use a patchwork of different tools like excel, google docs, and FigmaJam

At Wonka, our job is to delight users with our products! It's not just about taste, it's also about how they interact with the product. I love to get to know our customers so I can design solutions that genuinely make their lives better.

After conversations with users, I'm often left with 100s of pages of notes to wade through. I re-watch our call videos as well - it just takes so long!

I've started taking notes on FigmaJam notes right after a call so the data is all in one place. I then start grouping the data to see which themes begin to emerge.