Contextual Inquiry Field Protocol

Template Overview

Traditional lab interviews often miss the real-world interruptions, physical post-it notes, multi-monitor setups, and informal workarounds that dictate actual customer productivity. The Contextual Inquiry Field Protocol enables qualitative researchers to conduct master-apprentice style field observations directly in user workplaces. It provides a standardized template to capture physical artifacts, environmental distractions, unprompted workarounds, and tacit workflow knowledge.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Contextual Inquiry: [Customer / Organization Name]"
date: [YYYY-MM-DD]
field_researcher: "[[Senior UX Researcher]]"
participant_role: "[e.g., Executive Assistant / Radiologist / Senior Trader]"
environment_setting: "[Physical Office / Remote Desktop / Clinic Floor]"
tags: [ux-research, contextual-inquiry, field-study, ethnographic, workarounds]
---

# Contextual Inquiry Field Protocol — [Organization / Role]

## 1. Study Focus & Contextual Inquiry Principles
- **Core Investigation Question:** How do professionals balance real-time audio note-taking against active conversation during high-stakes client reviews?
- **Master-Apprentice Stance:** The researcher observes passively, asking clarifying questions only during natural task pauses.
- **Partnership & Interpretation:** Interpretations of observed habits are validated immediately with the participant in real time.

## 2. Environmental & Physical Artifact Inventory
- **Hardware Setup:** Dual 27-inch monitors, mechanical keyboard, external boundary microphone, noise-canceling headphones.
- **Physical Desk Artifacts:** Paper spiral notebook filled with color-coded highlighters, sticky notes lining monitor bezels with recurring acronyms.
- **Software Ecosystem Running:** Outlook email client, Obsidian markdown vault, Slack messaging app, proprietary ERP software.
- **Environmental Factors:** Frequent ambient noise from open-plan floor, colleague walk-ups every 18 minutes on average.

## 3. Real-Time Observational Event Log
| Timestamp | Observed Activity | Tool Utilized | Observed Friction or Workaround | Participant Quote / Rationale |
|---|---|---|---|---|
| 09:15 | Client calls unexpectedly | Softphone app | Participant scrambles to find clean paper page | "I can never find my previous meeting notes fast enough." |
| 09:22 | Capturing action items | Paper scratchpad | Copies acronyms from physical sticky note on bezel | "I keep client billing codes taped to the monitor." |
| 09:41 | Post-call data entry | Obsidian + ERP | Re-types handwritten notes into Markdown template | "Typing everything twice is exhausting but necessary." |
| 10:05 | Colleague interrupts desk | In-person | Minimizes all windows to protect client confidentiality | "I can't let visitors see proprietary financial data." |

## 4. Key Workarounds & Tacit Knowledge Discovered
- **The Double-Capture Loop:** The participant writes by hand during meetings because typing feels impersonal and noisy to clients, then spends 45 minutes every evening transcribing into Markdown.
- **Confidentiality Shielding:** The user refuses to use cloud transcription bots because corporate compliance bans external AI bots from internal networks.
- **Sticky Note Taxonomy:** Color-coded physical post-it notes serve as an externalized working memory that digital bookmarks have failed to replace.

## 5. Design & Workflow Opportunities
- [ ] Develop zero-latency local speech-to-text dictation that operates without internet connectivity.
- [ ] Provide lightweight global hotkey capture that doesn't obscure active screens.
- [ ] Introduce persistent desktop sticky-widget mode for pinned reference tags.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Contextual Inquiry: Clinical Research Coordinator"
date: 2026-10-09
field_researcher: "[[Dr. Gabriel Ortiz]]"
participant_role: "Senior Clinical Trials Coordinator"
environment_setting: "Academic Hospital Outpatient Research Office"
tags: [ux-research, contextual-inquiry, field-study, ethnographic, workarounds]
---

# Contextual Inquiry Field Protocol — Clinical Research Coordinator

## 1. Study Focus & Contextual Inquiry Principles
- **Core Investigation Question:** How are clinical protocol deviations and patient adverse event notes documented between examination rooms and hospital databases?
- **Setting:** High-distraction shared coordinator bullpen with hospital pager alerts and frequent physician interruptions.

## 2. Environmental & Physical Artifact Inventory
- **Hardware:** Hospital-issued ThinkPad docked to single 24-inch monitor, badge-authenticated smartcard reader.
- **Physical Artifacts:** Laminated paper dosage reference cards, clipboards with carbon-copy consent logs.
- **Software Running:** Epic EHR, REDCap clinical database, Excel tracking spreadsheets.

## 3. Real-Time Observational Event Log
| Timestamp | Observed Activity | Tool Utilized | Observed Friction or Workaround | Participant Quote / Rationale |
|---|---|---|---|---|
| 10:30 | Patient trial check-in | Paper clipboard | Coordinator annotates side effects on margins | "The EHR interface is too rigid while talking with patients." |
| 11:05 | Transcription into REDCap | Hospital Desktop | Manually compares paper notes with trial criteria | "If I make a typo here, it delays FDA auditing sign-off." |
| 11:35 | Research meeting prep | Local Text Editor | Copies patient summaries without patient identifiers | "Cloud tools are completely banned under HIPAA here." |

## 4. Key Workarounds & Tacit Knowledge Discovered
- **Air-Gapped Note-Taking:** Coordinator relies on local text files to draft regulatory summaries before submitting them to the locked trial database.
- **Strict Data Sovereignty:** Absolute refusal to permit external servers to process voice recordings or trial summaries due to severe institutional IRB penalties.

## 5. Design & Workflow Opportunities
- [ ] Emphasize offline local Whisper transcription for regulatory and clinical environments.
- [ ] Provide private local Markdown templates for clinical trial protocols.
- [ ] Implement local audit-log exports for verifiable institutional records.

When to Use and When to Avoid

When to Use

• Use when developing software for specialized, complex domains (medical, legal, financial, engineering).
• Use to discover hidden workarounds that users forget to mention during remote video interviews.
• Use to understand the role of physical desktop environments and multi-tool workflows.

When to Avoid

• Avoid using when studying quick consumer self-service workflows like e-commerce checkout.
• Avoid using when remote screen sharing can capture 100% of the relevant software interaction.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the contextual inquiry field protocol:
1. Synthesize all observed physical and software workarounds into root-cause user needs.
2. Highlight environmental constraints (distractions, privacy regulations, hardware limits).
3. Generate three product concept briefs designed to replace the user's manual workarounds.
Output in structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.