Observation

Definition

Observation is a technique where the Business Analyst watches stakeholders perform their work in real time to understand actual processes, behaviors, and interactions. Unlike interviews or workshops, observation focuses on what people do rather than what they say they do — revealing workarounds, inefficiencies, and tacit knowledge that stakeholders may not articulate.

Inputs

• Existing process documentation to compare against observed reality
• Problem statements or hypotheses to guide observation focus
• Stakeholder availability and consent
• Compliance or audit findings that flag suspected process gaps

Outputs

• As-is process models reflecting actual (not documented) behavior
• Identified inefficiencies, workarounds, and undocumented steps
• Improvement opportunities and inputs to requirements or redesign
• Validated or contradicted assumptions from prior elicitation

When to Use

• Processes are manual, semi-automated, or suspected to have hidden workarounds
• Stakeholders struggle to explain their work in interviews or workshops
• The BA is new to the domain and needs grounded context
• Compliance and audit preparation requiring evidence of actual practice

When Not to Use

• When work is highly sensitive, confidential, or regulated such that observation would be inappropriate
• When observation could disrupt critical operations
• When the activity being studied is infrequent or event-driven
• When stakeholders are uncomfortable being observed — use interviews or document analysis instead