Template Overview

True operational breakthroughs emerge from observing users in their natural workplace environments where interruptions, dual-monitor setups, physical paper notes, and communication tools intersect. The Contextual Inquiry Field Observation Log captures real-time environmental context, physical artifact ecosystems, and workflow breakdowns in sovereign Markdown.

Markdown Template Structure

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

---
title: "Contextual Inquiry: [[Participant Code / Role]]"
date: [YYYY-MM-DD]
field_researcher: "[[Senior UX Researcher]]"
participant_role: "Staff Software Architect"
work_environment: "Open-Plan Office / Dual 4K Displays + MacBook Pro"
observation_duration: "3 Hours (09:00 - 12:00)"
tags: [ux-research, contextual-inquiry, field-study, ethnographic, workflow]
---

# Contextual Inquiry Field Observation Log — [[Participant Code]]

## 1. Physical & Digital Workspace Ecosystem
- **Hardware Configuration:** 16-inch M3 Max MacBook Pro docked to dual 27-inch 4K displays. Mechanical split keyboard, wireless trackpad.
- **Physical Artifacts Present:** Physical bound paper notebook on desk for fleeting scratch notes; sticky notes on monitor bezel for temporary ticket IDs.
- **Active Digital Windows:** VS Code, Terminal (tmux with 6 panes), Slack, Obsidian vault, Zoom call window.

## 2. Chronological Observation Stream & Breakdowns
| Timestamp | Observed Activity | Environmental Context | Workflow Breakdown / Friction |
|---|---|---|---|
| **09:15** | Architecture standup call | Multi-tasking code while listening | Missed action item assignment; asked colleague in Slack |
| **09:42** | Writing technical RFC | Deep focus | Interrupted by 3 Slack DM notifications; lost flow state |
| **10:18** | Copying code into note | Pre-meeting prep | Formatted table manually in markdown; expressed annoyance |
| **11:05** | Retrospective call | Speaking without video | Scratched quick notes on physical paper because editor was hidden |

## 3. Unarticulated Needs & Latent Opportunities
- **The "Ephemeral Scratch" Problem:** Participant maintains paper sticky notes because opening a new digital note feels too permanent and adds vault clutter.
- **Meeting Audio Multitasking:** When active coding, participant relies on audio-only meeting presence and needs automated timestamped decision markers.

## 4. Synthesis & Research Insights
- [ ] [[UX Researcher]] Share field observations on split-screen meeting capture with design team.
- [ ] [[Product Designer]] Explore lightweight "scratch pad" floating overlay feature concept.

Filled Real-World Example

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

---
title: "Contextual Inquiry: Participant P-14 (Engineering Manager)"
date: 2026-10-10
field_researcher: "[[Dr. Mei-Ling Zhou]]"
participant_role: "Engineering Manager (Infrastructure)"
work_environment: "Home Office / Ultrawide Monitor"
observation_duration: "2.5 Hours"
tags: [ux-research, contextual-inquiry, field-study, ethnographic, workflow]
---

# Contextual Inquiry Field Observation Log — P-14

## 1. Key Workspace Observation
P-14 keeps their markdown vault open on the left third of their 38-inch ultrawide monitor while running Zoom on the right two-thirds. When calls conclude, P-14 immediately spends 10 minutes consolidating spoken commitments into their daily note.

## 2. Latent Need
P-14 explicitly stated they love local Whisper transcription because their previous cloud notetaker was banned by corporate infosec. Having summaries land directly in their existing local project folders saves them approximately 45 minutes daily.

## 3. Product Insight
Recommend building an option to auto-file meeting notes into specific folder paths based on calendar event titles.

When to Use and When to Avoid

When to Use

  • Use during on-site or remote observational field studies where users are observed doing real work.
  • Use to map physical and digital tool ecosystems, desk setups, and external interruptions.
  • Use to uncover latent user needs that participants fail to articulate in traditional interviews.

When to Avoid

  • Avoid for structured survey analysis.
  • Avoid for quantitative web analytics reviews.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Summarize the contextual inquiry field observation recording:
1. Outline workspace hardware setups, physical artifacts, and multi-window configurations observed.
2. Group observed workflow breakdowns, interruptions, and coping mechanisms chronologically.
3. Extract latent user needs and concrete product opportunities for the design team.
Output in clean, structured Markdown.

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

Frequently Asked Questions

What distinguishes contextual inquiry from standard user interviews?

Contextual inquiry observes users in their actual working environment while they perform real tasks, capturing unarticulated habits, interruptions, and physical artifacts.

Why document on-site observations in local Markdown?

Field observations capture proprietary workplace monitors, whiteboard contents, and confidential client interactions that must remain stored securely on the researcher's local device.

How does Oyma assist researchers conducting contextual inquiries?

Oyma transcribes field debriefs locally on your Mac with zero network egress, turning spoken observations into structured Markdown field notes.