user-context-fieldwork

Investigate real user workflows, constraints, and workarounds through observation-first fieldwork.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill user-context-fieldwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-context-fieldwork
Source: https://github.com/NlightNFotis/skills/tree/main/user-context-fieldwork
Command: npx skills add https://github.com/NlightNFotis/skills --skill user-context-fieldwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid designing for imaginary users by uncovering how people actually work in their real environments, with their real constraints, habits, vocabulary, and workarounds.

Core Features & Use Cases

  • Contextual workflow analysis: Maps what users actually do, not what teams assume they do or what users say they do in abstract.
  • Workaround and constraint discovery: Surfaces hidden friction, unofficial processes, missing features, local norms, and trade-offs that make surprising behavior rational.
  • Evidence-based research framing: Guides fieldwork through observation, triangulation, bias checks, glossary capture, and jobs-to-be-done synthesis.
  • Use cases: Useful for redesigning onboarding or CLI flows, understanding why a shipped feature is ignored or misused, investigating contradictory support reports, and grounding surveys or experiments in real user behavior.

Quick Start

Ask the user-context-fieldwork skill to investigate a specific user group and produce a fieldwork report covering observed workflows, workarounds, constraints, vocabulary, and design implications.

Frequently Asked Questions about user-context-fieldwork

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I uncover user workarounds and hidden workflows during contextual inquiry?

Contextual inquiry uncovers hidden workflows by prioritizing direct observation over user statements, triangulating evidence across sources to separate actual behavior from abstract claims and map real operational constraints.

Why does user behavior contradict what they say in UX research surveys?

UX research surveys often capture stated intent rather than actual behavior; observation-first fieldwork triangulates evidence and separates stated versus observed actions to reveal the real workarounds users rely on.

What is the best way to investigate contradictory user support feedback?

The best way to investigate contradictory support feedback is fieldwork that observes users in their actual operating environment, identifying local norms and constraints that make surprising or conflicting behavior rational.

How do I translate fieldwork observations into jobs-to-be-done design constraints?

Translate fieldwork observations by synthesizing vocabulary, workarounds, and hidden friction into jobs-to-be-done frameworks, converting real environmental constraints into actionable design requirements.

When do I need contextual inquiry for product discovery instead of standard analytics?

You need contextual inquiry for product discovery when making decisions affecting users whose operating environment is not shared by the team, requiring observation to understand real constraints and unofficial processes.

How do I check for bias and sampling gaps in user research fieldwork?

Check for bias in user research fieldwork by triangulating across multiple evidence sources, separating stated from observed behavior, and validating that captured workflows represent actual work rather than abstract assumptions.