Field Research & Ethnography Template Pack

A practical, reusable pack of recruitment scripts, consent templates, semi‑structured interview guides, observation logs, synthesis grids, and a short facilitation playbook so teams can run defensible, repeatable in‑context research that directly supports experiments and decisions.

Purpose and use

This template pack helps teams run quick, rigorous field studies that produce high‑quality qualitative evidence. Use these templates to make recruitment, consenting, interviewing, observing, and synthesis consistent, auditable, and actionable across projects. The materials are intentionally pragmatic: they reduce setup friction, help avoid common procedural errors, and make findings easier to integrate into experiments and decision processes.

How this pack is organized

  • Recruitment screener & consent scripts (editable)
  • Semi‑structured interview guide with prompt bank and probing techniques
  • Observation log with time‑sampling fields and note conventions
  • Rapid synthesis grid for patterns, illustrative quotes, insights, and opportunity statements
  • Facilitation notes for a compact 2‑day research sprint
  • Guidance: ethics, sampling, tailoring, and version control

Quick start checklist

  1. Define the research question and the decision this research will inform.
  2. Pick a sampling frame and complete the recruitment screener. Keep a log of every contact attempt.
  3. Confirm consent wording with legal/ethics advisors if needed; use the provided consent script as a starting point.
  4. Run a pilot interview/observation to validate timing and prompts.
  5. Capture raw notes, audio (with consent), and one synthesized grid per session within 48 hours.

Template excerpts & structure

1) Recruitment screener & scheduling log

Purpose: find participants who match your sampling criteria while documenting inclusion/exclusion choices.

  • Study name, date, researcher
  • Eligibility checks (yes/no) — e.g., age range, role, prior experience
  • Contact attempts (date, method, outcome)
  • Scheduling fields: location, time, estimated duration, output deliverable

2) Consent script (example)

Always adapt to legal/ethics review. Example:

“Hello — thank you for joining. My name is [name]. Today we’ll talk about [topic]. This session will take approximately [x] minutes. Participation is voluntary; you can stop at any time. With your permission I will audio‑record notes to help accuracy — the recording will be stored securely and only used for analysis. Do you consent to participate and to recording?”

Fields to capture: verbal consent yes/no, consent time stamp, any restrictions participant requests (e.g., anonymize quotes), and whether recording allowed.

3) Semi‑structured interview guide

Format: section header, goal, warm‑up questions, core questions, probes, closing. Keep prompts short and open.

Sample sections and prompts:

  • Warm up: "Tell me about the last time you used X."
  • Context: "What part of your day does this happen? Who else is involved?"
  • Task walkthrough: "Show me how you do [task]. What are the pain points?"
  • Probe bank: "Can you say more about that? What happened next? How often does that occur?"
  • Closing: "Is there anything you wish I had asked? Any final thoughts?"

4) Observation log (time‑sampled)

Use during in‑context observation. Quick fields encourage consistent notes.

  • Observer, session ID, location, start/end time
  • Time stamp (e.g., 10:05), actor, observed action, short quote, contextual note
  • Rating (scale 1–5) for friction or value at key moments
  • Photo reference or asset ID (if collected) and privacy flags

5) Rapid synthesis grid

One grid per theme; short, evidence‑driven, and directly tied to opportunity statements.

ThemeEvidence (sessions)Illustrative quotesInsight / What it meansOpportunity / Experiment
Example: checkout confusion5/12 sessions, 3 same pain points"I always have to ask for help at payment"Navigation causes abandonmentPrototype simplified checkout and A/B test

6) 2‑day research sprint facilitation notes (compact)

Goal: run focused interviews/observations, synthesize, and surface 2–3 testable opportunities.

  • Day 1 Morning — Briefing, pilot interview, 4–6 sessions (pair up observer/interviewer)
  • Day 1 Afternoon — Continue sessions, begin quick notes and one‑page synth per session
  • Day 2 Morning — Cluster patterns on affinity walls, create synthesis grids
  • Day 2 Afternoon — Prioritize opportunities, define 1–2 rapid experiments and next steps

Practical tips & good practice

  • Always link each finding to raw evidence (session IDs, quotes, timestamps).
  • Use consistent naming for versions (v1.0, v1.1) and record protocol changes in a short changelog.
  • Prefer transparency: document recruitment fall‑outs, non‑responses, and deviations from the protocol.
  • Keep synthesis outputs short and prioritized — decision makers need one clear recommendation with the evidence that supports it.

Ethics and limits

This pack does not replace formal institutional review when required. Treat consent, data protection, and participant welfare as primary. Avoid collecting unnecessary personal identifiers and store recordings securely. Seek legal or ethics review for clinical, vulnerable, or regulated populations.

Tailoring, reuse, and version control

These templates are designed to be copied and tailored. Document every change and keep a master changelog. For enterprise use, consider creating a site‑specific copy that includes organizational standards, approved consent language, and storage locations for recordings and notes.

Next steps and capability suggestions

If you want stronger data capture and organizational memory, consider these platform enhancements:

  • Create InteractiveForm versions of the recruitment screener, observation log, and synthesis grid so team members can submit structured data and build a searchable evidence store.
  • Use the platform's submission endpoint to collect filled forms and tie them to session IDs for analytics and traceability.
  • Package these templates as an ownable domain/toolkit so sites can copy, adapt, and version them while preserving a core standard.

Everything in this pack is intended as a practical, defensible starting point. Adapt with care, pilot early, and link every recommendation back to the evidence you collect.


Discussion

Comments and conversation will live here.