General research
AuraScore 83/100

Fieldwork Observation and Participant Debrief Script

Design an operational field observation protocol and post-session participant debrief script for workplace research.

Use this template when conducting contextual inquiries, operational audits, or workplace human-factors research. It provides step-by-step facilitator prompts to capture real-time behavior and unearth friction points.

Template

Role: Lead Human Factors and Organizational Ethnographer with deep experience in operational field research and workflow productivity.

Context

  • Physical or virtual operational environment: {{workplace_setting}}
  • Target process under observation: {{operational_workflow}}
  • User cohort being observed: {{participant_cohort}}
  • Primary investigation focus: {{observation_focus}}
  • Suspected friction points and hypotheses: {{friction_hypotheses}}
  • Research compliance and consent framework: {{consent_protocol}}

Task

Author a dual-part field research script comprising an active contextual observation guide and a post-observation cognitive debrief script for {{participant_cohort}} executing {{operational_workflow}} within {{workplace_setting}}.

Method

  1. Formulate a low-intrusion introductory briefing establishing the observer's neutral role and reviewing {{consent_protocol}}.
  2. Design an active observation guide with scripted non-interruptive cues to track {{observation_focus}} in real time.
  3. Define structured micro-interruption prompts for rare moments when a critical workaround or failure event occurs.
  4. Structure a post-task 'think-back' retrospective debrief sequence to dissect moments related to {{friction_hypotheses}}.
  5. Embed cognitive workload rating prompts asking the participant to verbally calibrate task complexity and tool fatigue.
  6. Generate specific inquiry lines addressing unobserved workarounds, informal tools, and cross-team dependencies.
  7. Provide concrete neutralizers for participant rationalization or 'observer effect' performance bias.
  8. Conclude with a structured debrief wrap-up capturing participant suggestions and confirming data anonymization.

Constraints

  • MUST separate facilitator instructions [FACILITATOR ACTION] from spoken dialogue "FACILITATOR SPOKEN: ...".
  • MUST NOT include judgmental, evaluative, or performance-scoring phrasing.
  • Spoken prompts MUST focus on lived behavior, emotional state, and immediate actions rather than abstract opinions.
  • Debrief duration MUST be paced to take no more than 20 minutes post-observation.

Output format

  • Part 1: Pre-Observation Setup & Spoken Participant Onboarding (150 words)
  • Part 2: In-Situ Observation Protocol (Structured tracking table with situational spoken triggers)
  • Part 3: Post-Observation Retrospective Cognitive Debrief Script (5 thematic blocks with 2-3 spoken prompts each)
  • Part 4: Facilitator Post-Session Memo Template (standardized field-note extraction structure)

Self-review

  • Verify that the debrief prompts directly test the assumptions in {{friction_hypotheses}}.
  • Ensure all language reinforces that the workflow is being evaluated, not the individual worker.
  • Confirm that {{consent_protocol}} constraints are visibly maintained across all observation steps.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

research-analysis
research-general
research-productivity-operations
field-research
contextual-inquiry
human-factors