Business Analysis 101: Elicitation and Collaboration - Elicitation Techniques, Interviews, Workshops, Observation, Document Analysis

What This Is

Elicitation is the systematic gathering of information from people, documents, and observations to discover what the business really needs. It sits early in the Requirements Life Cycle Management knowledge area and feeds the analysis, specification, and validation phases.

Real?world example: A financial services firm wants a new CRM system to track client interactions. The BA must interview sales reps, run workshops with marketing, observe call?center agents, and review existing sales?process documents to uncover functional and non?functional needs before any design work begins.

Key Terms & Techniques

• Interview – One?on?one or small?group conversation to extract detailed information; belongs to Elicitation (BAK1) and produces Stakeholder Requirements and Assumption logs.
• Workshop – Structured, time?boxed collaborative session with multiple stakeholders; part of Elicitation (BAK1) and yields Requirements Documentation, Prioritization matrices, and Consensus decisions.
• Observation (Job Shadowing) – Watching users perform their tasks in the natural environment; falls under Elicitation (BAK1) and results in Process models, Pain?point lists, and Implicit requirements.
• Document Analysis – Reviewing existing artifacts (policy manuals, system specs, contracts) to extract relevant requirements; a Elicitation technique that creates Baseline requirements, Gap analysis, and Traceability matrices.
• Stakeholder Map – Visual representation of who is impacted and who can influence the solution; used in Stakeholder Management (BAK2) to plan elicitation activities.
• Elicitation Plan – Document that outlines which techniques, participants, and schedule will be used; an output of Business Analysis Planning & Monitoring (BAK1).
• Facilitation Techniques – Methods such as Brainstorming, Affinity Diagram, Nominal Group Technique that help groups generate and organize ideas during workshops.
• Active Listening – BA skill of paraphrasing, probing, and confirming to ensure accurate capture of stakeholder intent; essential across all elicitation techniques.
• Probing Questions – Open?ended, follow?up questions that dig deeper into “why” and “how”; a core interview skill.
• Non?verbal Cues – Body language, tone, and facial expressions observed during interviews or workshops; helps uncover hidden concerns.

Step?by?Step / Process Flow

1. Identify & Prioritize Stakeholders – Use a stakeholder map and influence/interest matrix to decide who must be involved in each technique.
2. Develop the Elicitation Plan – Choose the right mix of interviews, workshops, observation, and document analysis; schedule, logistics, and required artifacts are documented.
3. Execute the Techniques
4. Conduct interviews (prepare questions, record responses).
5. Run workshops (facilitate activities, capture ideas on whiteboards or digital tools).
6. Perform observation (shadow users, note steps, capture screenshots).
7. Perform document analysis (catalog existing artifacts, highlight gaps).
8. Document Elicited Information – Convert raw notes into Stakeholder Requirements, Process Models, Assumption logs, and Traceability entries.
9. Validate & Refine – Review the documented outputs with the same stakeholders (or a validation meeting) to confirm accuracy and completeness.
10. Baseline & Communicate – Obtain formal sign?off, update the Requirements Management Plan, and circulate the baseline to the project team.

Common Mistakes

Certification Exam Tips

1. Know the Input/Output Model – For each technique, remember that Elicitation is the input (e.g., “Stakeholder needs”) and the output is Requirements (functional, non?functional, transition). The exam often asks “What does the BA produce after a workshop?” – answer: Requirements Documentation (or a Prioritization matrix).
2. Technique?to?Goal Matching – ECBA/CCBA questions frequently pair a scenario with the best elicitation technique. Remember:
3. Interview-detailed, individual insight (e.g., “What does the sales rep need to capture on a call?”).
4. Workshop-consensus, prioritization, or conflict resolution.
5. Observation-uncovering hidden workarounds or inefficiencies.
6. Document Analysis-when legacy specs or contracts exist.
7. Facilitation vs. Elicitation – The BA facilitates workshops but elicits information. If a question asks who “leads the discussion,” the answer is the BA (facilitator), not the stakeholder.
8. Remember the “E” in BABOK – Elicitation is an activity, not a deliverable. Don’t select “Elicitation” as a requirement artifact. The artifact is the output (e.g., “Stakeholder Requirements”).

Quick Check Questions

1. Scenario: After a requirements workshop, three senior managers disagree on the priority of a new reporting feature. Which technique should the BA use next?
   Answer: MoSCoW prioritization (or a Voting/Ranking technique).
   Justification: MoSCoW provides a structured way to reach consensus on Must, Should, Could, Won’t items.

2. Scenario: The BA needs to understand why users are manually entering data into two separate systems. Which elicitation technique is most appropriate?
   Answer: Observation (Job Shadowing).
   Justification: Watching the users in their natural environment reveals the actual workflow and hidden pain points.

3. Scenario: The project sponsor hands over a legacy system specification document. What should the BA do first?
   Answer: Document Analysis.
   Justification: Analyzing existing documents uncovers current functionality, gaps, and assumptions before any new elicitation.

Last?Minute Cram Sheet (10 One?Liners)

1. Elicitation = activity; Requirements = output.
2. Interviews-produce Stakeholder Requirements and Assumption logs.
3. Workshops-deliver Requirements Documentation, Prioritization matrices, and Consensus decisions.
4. Observation-yields Process models, Implicit requirements, and Pain?point lists.
5. Document Analysis-creates Baseline requirements, Gap analysis, and Traceability matrices.
6. Elicitation Plan belongs to Business Analysis Planning & Monitoring (BAK1).
7. Stakeholder Map is a tool of Stakeholder Management (BAK2).
8. Facilitation techniques (Brainstorming, Affinity Diagram, NGT) are used inside workshops.
9. Active Listening + Probing = essential skill for all elicitation techniques.
10. Validation of elicited information must occur before baselining; otherwise the BA risks “requirements creep.”

Good luck – you now have the practical toolbox and exam?ready shortcuts to ace the elicitation portion of any IIBA certification!