LEARN. PRACTICE. GROW.Concept and mechanism
Select an elicitation technique for a concrete question. If you need to understand a poorly documented operational sequence, authorized observation can reveal steps omitted during interviews. A prepared workshop helps areas compare examples when their interpretations differ. Documents and records help check statements, but may reflect another process version. Prepare purpose, scope, materials, and participants before the session. A meeting with managers does not automatically replace the experience of people doing the work. In an international environment, share terms and examples beforehand and specify time zones rather than assuming everyone interprets a local time identically.
Guided application
Imagine the procedure requires rejecting an incomplete file, but an operator demonstrates a manual recovery used at month end. Record the difference, confirm when it occurs, and involve the rule owner. Do not immediately turn observed behavior into an approved rule or dismiss it because it conflicts with documentation. After the session, return results and open questions to participants and compare them with other sources. Confirming that you recorded a need correctly differs from authorizing a solution. For communication, prepare an options-and-impact summary for the committee and exception details for implementers. Collaboration improves when each group can correct information, understand consequences, and identify decisions that remain open.
A discrepancy between procedure and execution is information to investigate.
Common pitfalls
Leading interview; silence treated as agreement; observation treated as authorization.
Related topics: Plan analysis and decisions · Life cycle, priorities, and changes · Current state, future state, and transition
Prepare, gather, confirm, and adapt communication to its audience.
Reference: Human-centred business analysis · Six-knowledge-area blueprint / handbook May 2026