At our first user conference back in February, Irene Kim, a product designer at NPR, shared her her tips for remote usability testing. Now that we’re all working remotely, the research team at Figma is learning how to collect, synthesize, and share insights from a distance.
Like any research initiative, process, frameworks, and documentation are key. Still, there are some tweaks that make the tactics—brainstorming questions, doing user interviews, collaborating on shared boards—a little easier. Whether you’re the middle of a journey mapping exercise or looking to do some usability testing, we’re sharing a few ways to make your research work, remotely.
Learning to see something through the eyes of your users is a cornerstone of research. Especially with all that’s happening right now, user empathy should be our guiding principle.
It’s possible (likely, even) that many people you’d like to talk to are experiencing their own difficulties, both on a personal and professional level. While some of your users might welcome a change of pace, others may not want to talk. Even if that means temporarily putting a workstream on hold or slowing things down, it’s ok.
As meetings move to calls or video conferencing, you might find yourself relying on more tools to make things happen. Remember that the people you’re talking to have differing comfort levels with technology, and may not be familiar with the apps you’re using. In her presentation, Irene reminded us not to assume that someone knows how to set up a video call: “Even for a lot of us who work in tech, this can be a challenge.”
In addition to sending screeners and prep work ahead of time, provide thorough instructions for joining the call and outline what to expect during the session. Some of the directions might seem obvious to you, but the extra thought and guidance will make the process easier for your participants (and they’ll likely feel more comfortable as a result).
While our team is used to doing remote user interviews, we’re not accustomed to having our internal teams distributed across cities. Now that we’re conducting all interviews over VC, we have to be more selective about who’s involved—having too many people on the line can make participants uncomfortable.
Here are a few tips for keeping your team in the loop, without overwhelming the participant:
One of our researchers at Figma, Christa Simon, has also started recording status updates and uploading them to Slack. In these videos, she reviews who we’ve talked to and who else is on the calendar, what we’re hearing so far from these interviews, and where to find project materials and insights.
Since we can’t huddle in a conference room or chat near our seating area, the team has been creating virtual boards in Figma to collate and synthesize findings. While the structure of your files will vary based on the type of research you’re doing, these sections are a good place to start:
Doing anything remotely can certainly come with its own challenges. But, as Irene reminded us, there are some benefits that are unique to remote research. NPR headquarters in Washington, D.C. are far from the audiences that Irene and her team want to interview, meaning that in-person sessions can be impractical: “We have listeners all the way from the most rural areas to the most metropolitan cities, so remote testing has been—and will continue to be—a really valuable tool for us to use.”
If you’re looking to run remote research, this template can get you started. Check out Irene's slides on remote testing and read through more resources on all things remote design here.