Collaboration driven interview

A Key to Better UX Research

I remember the feeling of being a junior UX researcher, running my first rounds of exploratory interviews. I was amazed that I could ask users anything. At the time, I didn’t understand the concept of a strict script—why control the conversation when users could lead the way and uncover hidden gems? So I only used the script as a guide. I was confident I would ask all the questions but in a more natural flow, letting the user dictate. Then analysis came, and I found myself with key research questions that were only answered by half of the users. It hit me. The timeline was tight, we had promised stakeholders clarity on an urgent topic, and because of my mistake, we had to run another round of interviews.

Of course, an open-ended approach has its place, especially in early discovery when you're exploring new user needs or seeking inspiration for new features. But even during this period, you need to set a limit on when to stop collecting new ideas and start refining the ones you already have. If you focus on the key research questions and objectives, you'll know when to draw that line. At this stage, a well-structured script isn’t just helpful—it’s essential.

Now, after years of experience running interviews, I have developed a practice collaborating with amazing reserachers, that I want to share with you. I invite you to make suggestions, share your wisdom, and help me become a better interviewer.

How to Make Interview Scripts a Collaborative Process

1. Kickstart with Collaboration: Workshop Your Research Canvas

Begin with a workshop where you create a research canvas that documents the following:


  • Main Research Question & Research Questions

  • Objectives, OKRs, Stakeholders, Timeline

  • Existing Evidence, Hypotheses, and Assumptions


This is one of my favorite stages. I invite stakeholders to share everything they know (or think they know) and capture it on post-it notes. This approach makes them feel valued—because they are!—and allows me to gently categorize their input into either evidence or hypotheses. It has saved me so much time in the past, especially when stakeholders initially rejected a research topic, assuming we already had the answer. By tagging their thoughts in the Miro board’s "Hypotheses" section, they could see their own words and realize, "Oh, yes, we still need to explore this." This collaborative moment is an excellent way to educate and align everyone.

TIP: Share the research canvas in advance and request input from busy stakeholders by sending them a brief “how-to” video with miro TalkTrack. This allows them to contribute offline.


Example of a Research Design Canvas


2. Isolate and Refine: Drafting the Research Questions

After the workshop, it's time to work independently. I carefully draft the question list, prioritizing those that are most closely aligned with the objectives and research questions.

Once the list is refined, I send it out in a collaborative Word doc along with a thank-you email, inviting stakeholders to provide further comments. This ensures that everyone stays engaged and has an opportunity to shape the process.

TIP: Organize the questions by Objectives, OKRs, and Main Research Questions. This structure is incredibly helpful during the interviews because it serves as a constant reminder of why each question is being asked.

3. Post-Interview: Sharing Findings & Gathering Feedback

When presenting findings, I always share a screenshot of the research canvas to remind stakeholders of the objectives, OKRs, and main research questions. I then show them how many questions have been answered, how many assumptions were tested, and how perspectives on certain issues have shifted as a result of the interviews.

Following the presentation, I send stakeholders a refined version of the research document with the updated research canvas and a list of questions. I highlight the ones we've answered and invite them to add comments or new questions based on the user insights. This is a crucial moment to revisit and align on the assumptions that still need testing, as well as to highlight what we’ve learned so far. If there's a follow-up round of interviews, this is a great opportunity to collaborate offline on new questions.

TIP: During the presentation, encourage stakeholders to add questions in the call chat if it’s remote, or collect them in a document if the presentation is in-person. This allows the presentation to flow smoothly, and you can always address the questions afterward.

TIP: Run an Assumption Smash workshop, where you collaborate with stakeholders to revisit assumptions and agree on which ones have been tested and which still need further work.

Prioritisation canvas

4. Final Thoughts

By making the process collaborative and transparent, we not only ensure that all voices are heard, but we also create an environment where everyone is invested in the outcome. When stakeholders feel included in shaping the research, it strengthens our shared understanding and drives better decisions. It's this kind of collaboration that leads to more meaningful insights and truly impactful results. Looking forward to seeing the positive change we can create together!