LEARN. PRACTICE. GROW.Concept and mechanism
Prepare elicitation with a purpose, participants, and the information needed. An interview can explore one person’s experience; a workshop can reveal differences among teams; existing documents and data help check the described process. Choose the technique according to the uncertainty to resolve. For a file-transfer service, merely asking whether the tool works may miss acknowledgment, resend, and reconciliation problems. Explore inputs, decisions, exceptions, and consequences. Distinguish an organizational rule from observed behavior. A rule may be current in a document but not followed in practice, or the document may be outdated. Record information origin and date.
Guided application
After gathering information, return a summary to confirm accuracy and understanding. Do not confuse interview confirmation with final approval of every requirement. Make vague expressions observable: fast needs an operation, load, boundary, and measurement method; available needs a window and conditions. Check whether the requirement is clear and whether it addresses the need. Prioritization should consider value, urgency, dependencies, and risk. A high-benefit requirement may depend on a less visible capability. When priorities conflict, prepare the comparison and involve authorized decision makers. Preserve the rationale so a context change can be reassessed.
An urgent request without an explicit reason needs clarification before bypassing dependencies.
Common pitfalls
Request treated as confirmed need; minutes treated as approval; priority determined by loudness.
Related topics: Need, value, and BACCM · Mindset, examples, and collaboration · Approach, change, and traceability
Gather, confirm, and structure needs before recommending priorities.
Reference: The Business Analysis Standard · 2025-07-21 / blueprint V1.1