Elicitation and Collaboration in Business Analysis

Elicitation and Collaboration is an important area of Business Analysis. It focuses on how Business Analysts obtain information from stakeholders, confirm their understanding, communicate Business Analysis information, and work with stakeholders throughout an initiative.

A Business Analyst does not simply ask stakeholders what they want and write down their answers. Elicitation involves exploring needs, understanding problems, investigating the current state, identifying the desired future state, and developing a shared understanding of what needs to change.

Collaboration is equally important because Business Analysis involves people with different responsibilities, knowledge, interests and expectations. The Business Analyst brings these perspectives together and helps stakeholders reach a common understanding.

The BABOK® v3 Knowledge Area, Elicitation and Collaboration, contains five tasks:

1. Prepare for Elicitation
2. Conduct Elicitation
3. Confirm Elicitation Results
4. Communicate Business Analysis Information
5. Manage Stakeholder Collaboration

The process is iterative. A BA might gather information during an interview, identify unanswered questions, discuss those questions in a workshop, review existing documents, and then return to stakeholders to confirm the findings.

1. Prepare for Elicitation

Good elicitation starts before the BA meets the stakeholders.

The BA needs to understand what the elicitation activity is intended to achieve. This includes understanding the scope, identifying relevant stakeholders, selecting suitable elicitation techniques, preparing supporting information and considering practical issues such as time, location and resources.

Stakeholder identification is particularly important. The BA needs to determine who has useful knowledge about the business problem and who will be affected by the proposed change.

For example, suppose an organisation wants to replace its customer relationship management system. The BA might need to involve sales staff, customer service teams, managers, IT specialists and other users of the existing system.

Each stakeholder provides a different perspective.

The BA also needs to select an appropriate elicitation technique. Interviews might work well when detailed information is required from an individual stakeholder. Workshops might be more appropriate when several stakeholders need to discuss a process together. Observation might be useful when the BA needs to understand how work is performed in practice.

BABOK® Task: Prepare for Elicitation

The purpose of this task is to determine the appropriate approach for obtaining information from stakeholders and other sources.

The BA considers:

• Scope of the elicitation activity
• Stakeholders who need to participate
• Elicitation techniques
• Available resources
• Timing
• Location
• Supporting materials
• Potential risks

The BA should also consider the Business Analysis approach and the characteristics of the stakeholders.

Key Output

The main output is an Elicitation Activity Plan.

This plan describes how the elicitation activity will take place.

A simple example:

Elicitation objective:

Understand problems with the current customer onboarding process.

Stakeholders:

Customer service, compliance, sales and IT.

Technique:

Workshop followed by interviews.

Duration:

Two hours.

Location:

Online.

Expected result:

Identify current process problems and stakeholder needs.

2. Conduct Elicitation

Once the BA has prepared, the elicitation activity takes place.

The BA engages with stakeholders and gathers information relevant to the business need.

The information might relate to:

• Business problems
• Current processes
• Existing systems
• Stakeholder needs
• Business rules
• Constraints
• Opportunities
• Future-state expectations
• Potential requirements

The BA should listen carefully and ask appropriate questions.

Suppose a stakeholder says:

"Our current process takes too long."

This statement does not provide enough information to define a requirement.

The BA needs to investigate further.

Questions might include:

• Which part of the process takes too long?
• How long does the process currently take?
• Who performs the activity?
• Which systems are involved?
• Where do delays occur?
• What causes the delays?
• What would an acceptable process look like?

The BA moves from a general statement towards a clearer understanding of the problem.

This is one of the reasons elicitation requires analysis and collaboration rather than simple note-taking.

BABOK® Task: Conduct Elicitation

During this task, the BA performs the planned elicitation activity.

The BA:

• Engages stakeholders
• Asks questions
• Listens to stakeholder responses
• Observes processes where appropriate
• Records information
• Identifies additional questions
• Investigates areas requiring clarification
• Identifies new information and potential requirements

The BA should remain open to information that was not expected during preparation.

Key Outputs

The main outputs are:

• Elicitation results
• Unconfirmed information
• Additional questions
• New information requiring further investigation

An important point is that elicitation results are not automatically final requirements.

The BA needs to confirm the information before treating it as reliable.

3. Elicitation Is Iterative

Elicitation rarely happens once.

A single interview might reveal new questions. A workshop might identify conflicting information. Document analysis might reveal information that stakeholders did not mention during an interview.

The BA therefore repeats elicitation activities as the understanding of the problem develops.

A typical cycle might look like:

Interview → Review information → Identify gaps → Workshop → Confirm findings → Follow-up interview

This iterative approach helps the BA develop a more complete understanding of the business need.

It also helps stakeholders refine their own understanding.

4. Elicitation Techniques

Business Analysts use different techniques depending on the situation.

Common techniques include:

• Interviews
• Workshops
• Observation
• Surveys
• Document analysis
• Interface analysis
• Data mining
• Market analysis
• Benchmarking

The choice of technique depends on the objective, stakeholders, available resources and project context.

For example, observation might help when stakeholders struggle to explain a process because they perform the work automatically as part of their daily routine.

An interview might be more appropriate when the BA needs detailed information from a subject matter expert.

A workshop might be useful when several stakeholders need to discuss a process and reach agreement.

The BA therefore needs to choose the technique rather than applying the same approach to every situation.

5. Confirming Elicitation Results

Information gathered during elicitation should not automatically be treated as final.

The BA needs to review and confirm the information.

This helps identify:

• Missing information
• Errors
• Contradictions
• Assumptions
• Misunderstandings
• Information requiring further investigation

For example, suppose Finance says that every refund requires manager approval.

Customer Service says refunds below £50 do not require manager approval.

The BA should investigate the difference rather than simply choosing one statement.

The BA might review existing business rules and speak with the appropriate stakeholders to determine the correct process.

Confirmation therefore helps establish a reliable understanding of the information gathered.

BABOK® Task: Confirm Elicitation Results

The purpose of this task is to check whether the information obtained during elicitation is accurate and useful.

The BA reviews the information with stakeholders and checks for:

• Accuracy
• Consistency
• Completeness
• Understanding
• Relevance

The BA also compares new information with existing information.

If differences appear, the BA investigates them.

Key Outputs

The outputs include:

• Confirmed elicitation results
• Updated information
• Identified issues
• Additional elicitation requirements

The key idea is:

Elicitation produces information.

Confirmation establishes shared understanding of that information.

6. Communicating Business Analysis Information

A Business Analyst also needs to communicate information effectively.

Different stakeholders need different levels of information.

A senior manager might need a high-level summary of the business problem, expected benefits, costs and risks.

A developer might need detailed functional and non-functional requirements.

An end user might need information about how a new process will affect their daily work.

The BA therefore needs to consider the audience when communicating Business Analysis information.

Possible communication formats include:

• Requirements documentation
• User stories
• Use cases
• Presentations
• Workshops
• Reviews
• Dashboards
• Models

The purpose is to make sure stakeholders understand the information relevant to their role.

BABOK® Task: Communicate Business Analysis Information

The BA selects an appropriate communication method and format.

The BA considers:

• Who needs the information?
• What information do they need?
• How much detail do they need?
• When do they need it?
• What communication method is appropriate?

For example:

Senior management:

Business objectives, costs, risks and expected value.

Developer:

Detailed requirements and business rules.

End user:

Process changes and expected system behaviour.

Key Outputs

Communication produces:

• Shared understanding
• Stakeholder feedback
• Decisions
• Agreed information
• Updated Business Analysis information

Communication is therefore more than distributing documents. The BA needs to determine whether stakeholders understand the information.

7. Managing Stakeholder Collaboration

Business Analysis depends heavily on stakeholder collaboration.

Stakeholders might have different priorities, levels of influence and views of the problem.

Some stakeholders might be highly engaged. Others might have limited availability or little interest in the initiative.

The BA needs to manage this collaboration throughout the initiative.

This involves encouraging participation, addressing concerns, clarifying responsibilities and helping stakeholders reach agreement.

For example, a new system might benefit the organisation but change how employees perform their daily work. Some employees might therefore have concerns about the change.

The BA needs to understand those concerns and ensure relevant information reaches the appropriate stakeholders.

Collaboration does not end after requirements have been documented. Stakeholders continue to provide information and feedback as the initiative develops.

BABOK® Task: Manage Stakeholder Collaboration

The BA works with stakeholders throughout the initiative to maintain effective engagement.

The BA:

• Encourages stakeholder participation
• Builds relationships
• Manages communication
• Clarifies roles and responsibilities
• Addresses stakeholder concerns
• Resolves conflicts
• Encourages agreement
• Monitors stakeholder engagement
• Maintains ongoing collaboration

The BA also needs to identify situations where stakeholders are not sufficiently engaged.

For example, a critical SME who repeatedly misses requirements workshops creates a risk because important business knowledge might be missing.

The BA needs to address the issue and find an appropriate way to obtain the required information.

Key Outputs

The results of stakeholder collaboration include:

• Stakeholder engagement
• Stakeholder agreement
• Decisions
• Issues requiring resolution
• Feedback
• Improved communication
• Ongoing stakeholder participation

8. Understanding Current and Future States

Elicitation helps the BA understand both the current state and the desired future state.

Consider a manual customer onboarding process.

The current state might involve:

• Customers completing paper forms
• Staff manually entering information
• Multiple approval steps
• Processing taking several days
• Errors caused by manual data entry

The future state might involve:

• Digital forms
• Automated data capture
• Automated validation
• Faster approvals
• Reduced manual entry

The BA uses elicitation to understand the gap between these two states.

Understanding this gap helps establish what needs to change and what the proposed solution needs to achieve.

9. The Role of Stakeholders

Different stakeholders contribute different types of information.

A Domain Subject Matter Expert provides knowledge about the business area.

For example, a finance specialist might explain how invoice approvals currently work.

An Implementation Subject Matter Expert provides knowledge about implementing the solution.

A Project Manager provides information about delivery considerations such as scope, schedule, resources and risks.

Customers provide information about their needs and expectations.

End users provide information about how processes and systems work in practice.

The BA needs to bring these perspectives together.

No single stakeholder is likely to have the complete picture.

10. Elicitation and Requirements

Elicitation and requirements are closely connected, but they are not the same thing.

Elicitation is the process of obtaining information.

Requirements represent what the organisation, stakeholders or solution need.

For example, during an interview a stakeholder might say:

"Customers keep calling us because they don't know whether their refund has been processed."

The BA investigates the problem.

The underlying need might be:

"Customers need visibility of their refund status."

This could then lead to a solution requirement such as:

"The system shall allow customers to view the status of their refund."

The BA has therefore moved from stakeholder information to an understood need and then towards a defined requirement.

11. The Importance of Shared Understanding

One of the central purposes of elicitation and collaboration is shared understanding.

A project becomes difficult when different stakeholders have different interpretations of the same requirement.

For example:

The business believes a report should show monthly sales.

The developer believes the report should show calendar-month sales.

Finance expects financial accounting periods.

These differences need to be identified and resolved.

The BA helps stakeholders clarify terminology, expectations, assumptions and requirements.

The objective is to create a common understanding before the solution is implemented.

12. BABOK® Tasks and Outputs at a Glance

The five tasks provide a useful structure for revision.

BABOK® Task	Main Purpose	Key Outputs
Prepare for Elicitation	Plan how information will be obtained	Elicitation Activity Plan
Conduct Elicitation	Obtain information from stakeholders and other sources	Elicitation results, unconfirmed information
Confirm Elicitation Results	Check and validate information	Confirmed elicitation results, updated information
Communicate Business Analysis Information	Present information in an appropriate format	Shared understanding, feedback, decisions
Manage Stakeholder Collaboration	Maintain stakeholder engagement and agreement	Stakeholder engagement, decisions, feedback, issues

A useful memory sequence is:

Prepare → Conduct → Confirm → Communicate → Collaborate

13. The Complete Elicitation and Collaboration Cycle

The overall process can be remembered as:

Prepare → Conduct → Confirm → Communicate → Collaborate

First, the BA prepares by understanding the objective, stakeholders, techniques and resources.

Second, the BA conducts elicitation and gathers information.

Third, the BA confirms the information with stakeholders.

Fourth, the BA communicates the information using an appropriate format.

Finally, the BA continues collaboration with stakeholders throughout the initiative.

The process repeats as new information emerges.

14. Key Points to Remember

Elicitation is more than collecting requirements. It involves investigating needs, problems, opportunities, current states and future states.

Preparation is important because the BA needs to understand the purpose of the activity, identify stakeholders and select suitable techniques.

Elicitation is iterative. New information often creates new questions.

Elicitation results need to be reviewed and confirmed.

Different stakeholders require different communication approaches.

Stakeholder collaboration continues throughout the initiative.

Conflicting information needs to be investigated and resolved.

The BA's role is to help stakeholders develop a shared understanding of the business need and the change required.

The five BABOK® tasks are:

1. Prepare for Elicitation
2. Conduct Elicitation
3. Confirm Elicitation Results
4. Communicate Business Analysis Information
5. Manage Stakeholder Collaboration

A useful way to remember the topic is:

Prepare the conversation.

Elicit the information.

Confirm what you learned.

Communicate the results.

Collaborate with stakeholders.

Repeat the process as the understanding develops.