When we’re trying to solve a problem or add value to our organization with a change, one of the first steps after we initiate a project is understanding the requirements of the users and business. Requirements are qualities or functionality that a product or solution must have to be considered successful. Without knowing these basic needs, it would be difficult to understand how to drive value for the users or organization as a whole.
But how do we discover these requirements? How can we draw out the information we need to get a detailed picture of what the solution needs to be or do? That’s where requirements elicitation techniques come in.
Let’s dive into these core techniques that every business analysis professional should master.
What is Requirement Elicitation?
Requirement elicitation is the process of identifying the needs of stakeholders to ensure a project or initiative delivers the right solutions. It’s one of the most critical steps in business analysis because incomplete or misunderstood requirements can derail a project, leading to costly delays, scope creep, and unmet needs.
In fact, 60% of projects fail because requirements are incorrect or incomplete.
Mastering requirement elicitation techniques will help you uncover clear, accurate, and actionable requirements. By using proven approaches, BAs ensure that they truly understand stakeholders’ needs and align project goals with business objectives.
What Are the 6 BIG Elicitation Techniques?
There is no one-size-fits-all method for gathering requirements, but these six techniques are some of the most widely used and effective approaches in business analysis. Depending on the nature of your project and stakeholders, you may use one or a combination of these methods:
1. Document Analysis
Document analysis involves reviewing existing documentation to gather requirements. This could include business plans, process flows, policies, manuals, or previous project reports. Although it’s a simple technique, it’s very powerful. Document analysis provides vital and detailed information about a topic, product, or process – enabling you to grasp concepts more quickly. This saves time and effort in explanation, giving you some background information and context.
When to use this method:
- When historical or organizational information already exists.
- To gain insights into the current state and identify gaps.
Benefits of document analysis:
- Saves time by leveraging existing knowledge.
- Provides a baseline for further elicitation activities.
Despite the simplicity of document analysis, it’s still important to plan your analysis session to ensure that it provides the value and insights you’re looking for. Planning will help you set goals, organize any participants who may be joining you, and block off time for the session to ensure that you have the time dedicated to that task.
2. Observation
Observation, also known as job shadowing, involves watching stakeholders perform their tasks to understand workflows and identify pain points. Many people find it difficult to explain how they complete a task, but observing them allows you to see first-hand the steps they take when completing a process or working with a product.
When to use this technique:
- When stakeholders struggle to articulate their processes.
- For projects involving manual, complex, or repetitive tasks.
- When you’re unfamiliar with a process or industry.
Benefits of observation:
- Provides firsthand insights into the actual work environment or process.
- Highlights inefficiencies or unspoken requirements.
Observation, coupled with your experience and knowledge, can provide you with new insight into potential requirements. You’ll be able to see things that may not be obvious to the user who performs that task frequently, including challenges, bottlenecks, and workarounds that they may use to deal with those issues. You can then take those observations and use them to inform potential user needs or requirements.
3. Brainstorming
Brainstorming is a collaborative technique that encourages stakeholders to generate ideas and discuss potential solutions in a free-flowing manner. We can also use this method to come up with a consensus on a solution or idea to solve a problem.
Brainstorming can be done in three formats: solo (by yourself), one-on-one with another person, or in a group. I like conducting them in a small group to get ideas flowing and build on one another’s ideas. Often, it’s best to keep brainstorming groups relatively small, around three to eight people.
When to use this technique:
- When creative solutions are needed for complex problems.
- To explore a wide range of ideas in a short time.
Benefits of brainstorming:
- Encourages stakeholder participation and engagement.
- Brings together diverse stakeholders, potentially from different departments, for well-rounded input on a solution.
- Fosters innovative thinking and identifies unexpected requirements.
While you won’t dig into the details of the ideas generated in a brainstorming session, this is an excellent method for getting the pot bubbling and getting creative with the potential solutions and opportunities available.
4. Questionnaire/Survey
A questionnaire or survey is a static set of questions designed to collect input from a large group of stakeholders quickly. There are many survey formats that offer you flexibility in the medium you choose, including old-fashioned pen and paper and telephone. These days, though, there are a lot of free and premium online services that make survey distribution, collection, and response analysis much more efficient.
When to use questionnaires and surveys:
- When you need input from a geographically dispersed or large audience.
- To collect quantifiable data for analysis.
Benefits of this method:
- Cost-effective and efficient.
- Provides measurable results and stakeholder trends.
Sometimes, surveys can be used as a springboard to generate a few ideas for needs or requirements, which can be further investigated through other elicitation techniques.
5. Interviews
Interviews are sessions with stakeholders to ask questions and explore their needs, concerns, and expectations. Interviews can be structured (with the interviewer having a list of detailed questions that need to be answered) or unstructured (with the interviewer having a general idea of the questions they want to ask but leaning more toward a conversational exchange between themselves and the interviewee).
When to use interviews:
- When in-depth understanding is required.
- To clarify complex or sensitive topics.
Benefits of using interviews for elicitation:
- Builds trust and rapport with stakeholders.
- Uncovers rich qualitative information and insights.
Interviews can include one or more interviewers and one or more interviewees. Regardless of the number of participants in the session, Business Analysts need to ensure that participants build on each other’s answers rather than swaying their responses or becoming agreeable.
6. Requirement Workshop
A requirement workshop may sound complex but at its core, it’s a structured meeting where stakeholders come together to discuss a topic or set of topics to define customer and user requirements. It actually has a similar look and feel to other corporate meetings.
When to use requirement workshops:
- For initiatives requiring consensus from multiple stakeholders.
- When the change needs to move forward quickly with purpose and clear direction.
Benefits of this elicitation method:
- Promotes teamwork and immediate feedback.
- Aligns stakeholders on priorities and key decisions.
Defining a few discussion topics in advance and using visuals helps keep the conversation flowing and the participants focused. These workshops also help build relationships with stakeholders because they are able to voice their ideas, helping them feel seen and heard.
How to Choose the Right Requirement Elicitation Technique
Selecting the best technique depends on a number of factors, including the context of your change initiative, your stakeholder needs, and available resources. In many cases, a combination of techniques is appropriate and even necessary. For example:
- You might start with document analysis to understand the present state.
- Follow up with interviews or surveys to gather more stakeholder input.
- Host a requirement workshop to gain consensus and finalize priorities.
Combining techniques ensures you include different perspectives, minimize gaps, and validate requirements effectively. But when considering the best technique – or combination of techniques – for your organization and change, try keeping these tips in mind:
- Consider stakeholder availability and communication preferences.
- Evaluate the complexity and size of the project.
- Identify time, budget, and resource constraints.
Looking for some more detailed learning? Our Understand and Elicit Requirements course is designed to help you confidently understand and elicit requirements, driving your solutions towards valuable outcomes. Through practical strategies and real-world scenarios, you’ll learn:
- The building blocks of requirements elicitation.
- How to select the proper elicitation techniques.
- Effective communication techniques with stakeholders.
- How to validate and prioritize requirements.
Whether you’re a new business analysis professional or looking to sharpen your skills, this course will help take the guesswork out of this essential task.
Gaining Insights with Requirements Elicitation
Requirement elicitation is an art and a science—it requires the right mix of techniques, stakeholder collaboration, and analytical thinking. By mastering these six big techniques, Business Analysts are equipped to deliver impactful solutions.
Are you ready to level up your elicitation techniques? Check out our Understand and Elicit Requirements course today, and take a confident step toward delivering additional value!
Jeremy Aschenbrenner
The BA Guide
