Field Ethnography & Contextual Inquiry

Template Overview

What users say in an artificial interview room rarely matches what they actually do at their desks. In formal interviews, people describe their idealized workflows; in reality, they use messy workarounds, copy data between sticky notes, fight with multi-monitor window management, and juggle interruptions.

Contextual inquiry and field ethnography bring researchers into the user’s authentic physical environment. By observing real work as it happens, researchers uncover the tacit habits and environmental constraints that dictate software adoption.

This template organizes ethnographic field observations: physical workplace context, observed digital artifacts, tacit behaviors, workaround hacks, and design implications.

Markdown Template Structure

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

---
title: "Contextual Inquiry: [Site / Participant ID]"
date: [YYYY-MM-DD]
participant_id: "ETHNO-03"
observation_site: "Home Office Setup (Remote Architecture Lead)"
researcher: "[[Lead Ethnographer]]"
environment_type: "Physical Desk Setup & Multi-Monitor Workspace"
observation_duration: "2.5 Hours Continuous Observation"
tags: [ethnography, contextual-inquiry, ux-research, fieldwork, observation]
---

# Contextual Inquiry: [Site / Participant ID] — [YYYY-MM-DD]

## 1. Physical Environment & Workspace Topology
- **Hardware Setup:** 16-inch M3 Max MacBook Pro docked to two 27-inch 4K displays; split ergonomic mechanical keyboard.
- **Physical Artifacts Present:** Spiral-bound dot-grid notebook open to left of keyboard; yellow sticky notes on monitor bezel tracking daily priorities.
- **Ambient Context:** Quiet home office; music playing on external speakers; Slack notifications muted on secondary display.

## 2. In-Situ Behavioral Observations
| Timestamp | Observed Activity | Environment / Screen State | Tacit Behavior / Workaround |
| :--- | :--- | :--- | :--- |
| 10:15 | Joined technical incident call | Zoom on primary display; terminal on secondary | Opened physical notebook to scribble down error codes before opening software editor |
| 10:35 | Copying code snippet | Terminal to scratchpad note | Switched between three different windows looking for previous week's configuration note |
| 11:05 | Documenting meeting consensus | Video call concludes | Copied temporary Markdown block from scratchpad into structured vault project directory |
| 11:30 | Filing task reminders | Reviewing notes | Transcribed handwritten sticky notes into task checkboxes in Markdown file |

## 3. Tacit Habits & Discovered Workarounds
- **Workaround 1 (Dual-Track Logging):** The participant habitually jots quick timestamps in their physical notebook during meetings because switching window focus to a note app feels disruptive to eye contact.
- **Workaround 2 (Scratchpad Ingestion):** The participant never writes directly in finished vault files; they maintain a messy `Inbox/scratch.md` file that they manually parse at the end of the day.

## 4. Physical vs Digital Friction Points
- Window tiling: Finding the note editor while screen sharing is awkward; participant frequently hid confidential notes to prevent accidental camera broadcast.
- Audio interruptions: When in-person family members entered the room, the participant muted the microphone but wanted ambient recording to continue locally.

## 5. Design Implications & Feature Inspirations
> [!IMPORTANT] Core Architectural Insight
> The participant desperately needs a distraction-free, floating mini-window capture widget that stays pinned on top without broadcasting during screen shares.

- [ ] Prototype floating mini-window capture interface for macOS.
- [ ] Add automated 'Scratchpad to Vault' organization wizard.

Filled Real-World Example

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

---
title: "Field Observation: ETHNO-03"
date: 2026-10-06
participant_id: "ETHNO-03"
researcher: "[[Kiran Shah]]"
tags: [ethnography, observation]
---

# Field Observation: ETHNO-03 — October 6, 2026

## 1. Context
Observed systems engineer working across multi-monitor setup.

## 2. Key Discovery
Engineer scribbles notes on physical paper during calls to avoid window switching. Validates demand for floating menu bar notes.

When to Use and When to Avoid

When to Use

• Use during in-situ contextual inquiry sessions and workplace ethnographic field observations.
• Use to document physical desk environments, multi-monitor ergonomics, and tacit workarounds.
• Use to discover unmet user needs that participants never think to mention in interviews.

When to Avoid

• Avoid using for remote mass quantitative surveys.
• Avoid using for formal engineering system architecture reviews.

On-Device AI Integration

Capture ethnographic field observations with Oyma on macOS:

Analyze the contextual inquiry field notes or recorded audio observation:
1. Synthesize the physical workspace topology, hardware fleet, and environmental ambient conditions.
2. Build the chronological observation table mapping activities, screen states, and tacit workarounds.
3. Detail unstated habits, physical-to-digital transition frictions, and window management behaviors.
4. Record key design implications and feature inspirations for the product team.
Output in structured, observational CommonMark.

Your ethnographic field notes and workplace observations remain securely on your private Mac.