Skip to main content

Create Interviewer Packet

Purpose

PutTo all the infoprovide interviewers needwith a single, easy-to-use reference for each client project. The Project Overview document consolidates links, context, and guidance in one place.place, ensuring consistency, clarity, and readiness before interviews begin.

Responsible Party

Ops Support and Ops Manager

Interdependencies

  • TheMaster Calendly,Project interview,Folder survey,is andcreated meetingin linksGoogle Sheets

  • Calendly event link is finalized

  • Interview schedule is confirmed

  • Fireflies account is active

  • Project-specific details (eitherorganization Zoombackground, orhybrid/workplace Teams)context, etc.) have been created.reviewed with the Project Lead or Strategist

Directions
  1. Create the folder: In 3 - Challenge Seeking, create new subfolder titled "[Project] Interviewer Packet"  
  2. Master List shortcut: Add a Shortcut to the Participant List. 
  3. CreateProtocols: aEnsure protocols are available for interviewers to review prior to the interviewer Prep meeting.
  4. Project Overview document: Create the document from the Project Overview template. 
    • File name format: [Client Name] Project Overview.docx 
    • AddSave the file in the project’s folder under: /Projects/[Client Name]/3 -  Challenge Seeking/[Client Name] Interviewer Packet
    • Populate Standard Sections
      • Replace all placeholder names with the current client name (e.g., Citizens).
      • Links, add the following:
        • Interview link: Insert the open Question Pro link. Interviewers can use this link to familiarize themselves with the form before interviewing or as an alternative if the customized link doesn't work.
        • Survey link: Add the survey +link interviewfrom links,Question Pro. The interviewer can use this to pop into the meeting links,chat andto encourage the stakeholder to complete the survey.
        • Calendly link: Paste the scheduling link wherefor listed.reschedules. This
            can be added to the meeting chat if the stakeholder shows up to request a reschedule.
          1. Landing page link: Include the client's landing page or DORIS info page to share with participants. Interviewers can pop this into the meeting chat if they have questions about the DORIS study, who DORIS is, or what to expect.
          2. Add Organizational Context
            • Under “About the Organization,” provide a short description of companythe client using:

                • Mission, sector, and location
                • Type of organization (e.g., nonprofit, government, education, corporate)
                • Brief summary of what they do and who they serve
                • Source: client website or project overview.Delimitations document.
          3. AnythingAdd thatProject interviewersBackground should
              pay
            • attention
                to
              • Summarize project purpose and recent history
                • What prompted the project (e.g., leadership changes, hybrid policy shifts, space utilization concerns)

                  Current focus or avoidgoals saying.(e.g.,

                • understanding
          workplace needs, identifying opportunities, exploring consolidation)

        • DropSource: theproject linkDelimitations document or project charter.
    • Add any cultural context interviewers need to theknow.
    • Interviewer
    • Interview PacketNotes Guidelines - this will be present in the project'stemplate Slackand channel.should stay for all projects.
    • Update the No Show Email template with the correct Calendly reschedule link, and if we are using Teams or Zoom.
    • Keep the Fireflies note-taking instructions and Teams - Logging in directions.
    • Interviewer Schedule: add updated schedule for the interviewers to reference.

     


Resources

Creating a Google Drive Shortcut (Scribe)  
Creating Subfolders in Google Drive (Scribe) 
Create and Share a New Document Template (Scribe) 

  • Use Organization_Project Overview template
  • The Project's Charter file will be on main/top level of the Project's file (under the folders for each phase).