LEARN. PRACTICE. GROW.Concept and mechanism
Elicitation seeks knowledge that may be incomplete, distributed, or implicit in work. Choose the technique according to the gap. Interviews clarify goals and explanations; observing a workflow may reveal waits and checks absent from the procedure. Use authorized examples and avoid copying real data without need and permission. A question already suggesting the preferred tool may prompt agreement. First ask which outcome fails, under which conditions, and with what consequence. If a manager reports five minutes and an operator one hour, they may be measuring processing and waiting rather than either person being dishonest.
Guided application
After the session, return results with examples and identified questions. Confirming that meaning was recorded correctly differs from approving a requirement for implementation. In an international team, adapt detail to the audience while retaining consistent concepts. Management may need impact and the decision; APS also needs states, failures, and responsibilities. When two teams dispute coverage after 18:00, explore capacity and interests before dividing tasks. To investigate low adoption, include people who do not use the portal; interviewing only frequent users may hide the main barrier. Keep hypotheses visible until sufficient evidence exists.
An informal duplicate-checking spreadsheet may reveal a need; its rules still need confirmation.
Common pitfalls
Leading questions; procedure as complete reality; notes as approval; samples excluding nonusers.
Related topics: Trace requirements and manage changes · Need, future state, and change strategy
Gather, confirm, and communicate meaning before treating it as agreement.
Reference: CBAP Competencies and Proficiency Levels · CBAP six-knowledge-area blueprint, May 2026 handbook