for an interview guide includes: introduction of interviewers, background on the project, logistics (how long, acknowledgement that you are taking notes, and permissions). Begin the interview with open-ended questions about who the stakeholder is and how they got to where they are today. Keep in mind it is absolutely critical to let the person share. Their context is as important as the answers to specific questions you have. After you’ve created a sense of openness and trust, you can start specific questioning related to your research questions. When creating questions avoid “yes/no” types of responses by designing questions to elicit stories, where interviewees not only tell you what tools they use, but also share when, where and why they use them. For example, instead of asking “Do you like X [internet freedom tool]?” You can ask them “Tell us a about a challenge you or your organization faced related to concerns of privacy or security.” Then follow-up with “ Do you use, or have you ever used, software that was intended to help manage your privacy or security online? Tell us about it.” This opens up the interview to explore a topic deeper and thus give you a better opportunity to understand what you need to do, in this case, to improve the tool. Wrap-up the interview by letting them know a timeline for how their interview will be used, and if necessary a request to reach back out. Translation and Cultural Sensitivity: test the interview guide on trusted stakeholders to ensure it is translated accurately (if translated), that questions are worded appropriately, and it is culturally appropriate for your target audience. At the beginning of a project to develop a framework for needfinding in the Internet Freedom Space, the SecondMuse team got together to brainstorm a list of potential interviewees based on our own knowledge of and relationships within the space. We created a Google document that everyone on the team had access to where we input names, contact information, assigned responsibility for initial contact, identified the relationship of the interviewee to the Internet freedom space, and tiered our list by priority level. Our initial target group of interviewees included academics, users, funders, intermediaries, and developers. Later, we simplified the stakeholder groups to just three: developers, users and intermediaries. The intermediary group included trainers, funders, advocacy groups and academics. We also compiled a general list of questions we would ask of everyone as well as subsets of questions tailored for each stakeholder group. We then tested our interview guide with trusted allies within the space to get a better sense of flow, timing and to see if the wording of the questions was soliciting the information we were seeking. 2). During the Interview Format: Typically an interview lasts 60 to 90 minutes and in person is ideal, but audio-only will work if in person is not possible. We recommend two interviewers attend each interview; one to lead and the other to take notes. Recording is helpful in terms of keeping other teammates in the loop and/or going back to clarify points where the notes are unclear. When taking notes, it is best to take notes in the actual words and sentences used. Shorthand can change the meaning of a statement significantly; also pay attention to more than just the words used, but also the tone and flow of how words and concepts are related. FRAMEWORK ELEMENTS