observation-analysis
Installation
SKILL.md
Purpose
Discover requirements that stakeholders cannot articulate by observing them in their actual work environment. People are poor at describing their own routines -- they skip steps they consider "obvious," forget workarounds they have internalized, and underestimate how much time tasks actually take. Observation fills this gap.
This technique complements interviews (see skills/elicitation-interview/SKILL.md). Interviews reveal what people think they do; observation reveals what they actually do. The gap between those two is where unstated requirements live.
Key Concepts
Active vs. Passive Observation
| Aspect | Active (Contextual Inquiry) | Passive (Job Shadowing) |
|---|---|---|
| Interaction | Ask questions during the task | Watch silently, ask questions after |
| Disruption | Moderate -- may alter the workflow | Minimal -- natural behavior |
| Depth | High -- can probe reasons in the moment | Moderate -- explanations come later |
| Best for | Complex decision-making tasks | Routine, time-sensitive processes |
| Risk | Observer changes the observed behavior | Miss the "why" behind actions |
Rule of thumb: Use passive observation first to understand the flow, then switch to active observation for the steps that need explanation.