Field Research Plan Template

What This Template Is For

Field research means observing users in their actual environment rather than a lab or a conference room. You see the interruptions, the workarounds, the sticky notes on monitors, and the reality of how your product fits (or does not fit) into a real workflow. These are insights you cannot get from surveys or analytics alone.

This template helps you plan a structured field study from defining research questions through synthesizing findings. It is designed for product managers and researchers who need to go beyond what users say they do and observe what they actually do. If you are working through a product discovery process, field research is one of the highest-signal inputs you can gather.

Pair this with a customer interview template for the conversational portions of your visits and an empathy map for synthesizing observations into actionable insights. Field research is most valuable in early discovery phases and when validating assumptions about user behavior.

When to Use This Template

• You are designing a product for a workflow you have never personally experienced or observed firsthand
• Analytics show unexpected usage patterns and you need to understand the real-world context behind the numbers
• Your team is building for a new market segment and needs to validate assumptions about user needs
• You are conducting a contextual inquiry as part of a broader research program
• A redesign is planned and you want to document the current state of user workflows before making changes
• Stakeholders disagree about user behavior and you need observational evidence to resolve the debate

How to Use This Template

Step 1: Define your research objectives. Be specific about what you want to learn. "Understand how users manage inventory" is too broad. "Identify the steps, tools, and workarounds users rely on when reconciling inventory discrepancies" is actionable.

Step 2: Recruit participants. Identify 5-8 participants who represent your target user segments. Field studies require fewer participants than surveys because the depth of observation compensates for breadth.

Step 3: Prepare your observation protocol. Define what you will observe, what questions you will ask, and what artifacts you will collect. Bring a note-taking framework so you capture data consistently across visits.

Step 4: Conduct field visits. Spend 2-4 hours per visit. Observe first, ask questions second. Record with permission. Capture photos of the physical environment, tools, and workarounds.

Step 5: Synthesize and share. Within 48 hours of each visit, write up your notes. After all visits, identify patterns across participants and create a findings report with prioritized recommendations.

The Template

Research Overview

Research Questions

Primary question: [The single most important question this research must answer]

Secondary questions:

1. [What tools and systems do users currently use to accomplish this task?]
2. [Where do users experience friction or create workarounds?]
3. [How does the physical environment influence how users interact with the product?]
4. [What triggers users to start this workflow, and what signals completion?]
5. [Who else is involved in this process, and how do they collaborate?]

Participant Criteria

Recruitment approach: [How you will find and screen participants]

Incentive: [Amount and form: gift card, donation, product credit, etc.]

Participant Roster

Observation Protocol

Before the visit:

• ☐ Confirm date, time, and location with participant
• ☐ Send a brief overview of what to expect (but do not reveal specific questions)
• ☐ Prepare recording equipment (camera, audio recorder, notebook)
• ☐ Review participant's company and role background
• ☐ Print consent forms and observation worksheets

During the visit:

• ☐ Arrive 10 minutes early, set up recording equipment
• ☐ Get signed consent for observation and recording
• ☐ Start with 5 minutes of rapport-building conversation
• ☐ Ask the participant to walk through their typical workflow as they normally would
• ☐ Observe silently for the first 15-20 minutes before asking clarifying questions
• ☐ Note: environment, tools, interruptions, workarounds, emotions, collaboration points
• ☐ Photograph physical artifacts (with permission): sticky notes, whiteboards, printed reports
• ☐ Ask follow-up questions using "Tell me more about..." and "Why did you do it that way?"
• ☐ Close with: "Is there anything I should have asked about that I missed?"

After the visit:

• ☐ Write up detailed notes within 24 hours while memory is fresh
• ☐ Tag observations against research questions
• ☐ Note any surprises or findings that challenge existing assumptions
• ☐ Send thank-you note and incentive to participant

Observation Worksheet (Per Visit)

Participant: [ID]

Date: [Date]

Location: [Office, home, warehouse, etc.]

Observer: [Name]

Environment notes:

[Describe the physical workspace. Lighting, noise, monitor setup, tools visible, interruptions observed.]

Workflow observations:

Key quotes:

• "[Direct quote from participant]" (context: [when/why they said it])
• "[Direct quote]" (context: [])

Artifacts collected:

• ☐ Photos of workspace
• ☐ Screenshots of tools/dashboards
• ☐ Documents or printouts shared by participant

Top 3 observations from this visit:

1. [Most surprising or impactful finding]
2. [Second finding]
3. [Third finding]

Synthesis Framework

Cross-participant pattern matrix:

Key findings (prioritized):

1. [Finding title]: [Description of the pattern, supported by specific observations from multiple participants]
2. [Finding title]: [Description]
3. [Finding title]: [Description]

Recommendations:

Filled Example: Warehouse Inventory Management Field Study

Research Overview

Research Questions

Primary question: How do warehouse managers currently reconcile inventory discrepancies between physical counts and system records?

Key Findings (After Synthesis)

1. Paper-first counting. 5 of 6 participants printed a spreadsheet and walked the warehouse with a clipboard despite having mobile scanning hardware. Reason: the mobile app crashed frequently on older devices and could not work offline in dead zones.

1. Dual-system workarounds. 4 of 6 maintained a personal spreadsheet alongside the official system to track adjustments because the system's audit trail was too slow to query.

1. Shift handoff gaps. All 6 participants reported that discrepancies were most common at shift changes. No standardized handoff protocol existed for in-progress counts.

Recommendations

Key Takeaways

• Observe first, ask questions second. The first 15-20 minutes of silent observation reveal behaviors users would never think to mention in an interview
• Five to eight participants is sufficient for field research. Patterns typically emerge by the fourth or fifth visit
• Write up notes within 24 hours. Field observations decay rapidly in memory, and details matter
• Photograph the physical environment. Sticky notes, printed spreadsheets, and dual-monitor setups tell you more about real workflows than any survey
• Tag every observation against your research questions during synthesis so patterns are traceable to evidence
• Share findings within two weeks of completing visits. Stale research rarely influences decisions