Enrich Business Analysis Experience for Your Stakeholders Using AI Tools

Disclaimer: The views and opinions expressed in this article are those of the author and may not reflect the perspectives of IIBA.

This article is part of AI Wednesdays, an ongoing 2026 series that explores how business analysis professionals are using AI in real, practical ways. Each article is written by a practitioner and shares experience-based insights to help you use AI with greater confidence—starting small, building familiarity over time, and applying it where it adds real value. 

This experience might sound familiar: During an elicitation or requirement validation discussion, you find that stakeholders aren’t aligned, or aren’t clear on how the requirements will help them meet their needs.

If it does, you’re not alone. 

This is exactly what I’ve seen and observed on several occasions throughout my career as a business solutions consultant. The challenge isn’t always about what we write; it’s about how well it’s understood.

Business analysis professionals invest enormous energy in gathering requirements, yet the disconnect between technical language and stakeholder expectations often persists right up to delivery. I’ve sat through workshops where perfectly valid requirements were disputed because they weren’t framed in a language the stakeholder could relate to.

Working at Appdirect over the past year, I’ve had the opportunity to change this dynamic with the help of AI. Through Appdirect’s own AI platform, I gained access to a broad portfolio of AI models, including Claude Opus, ChatGPT, and Google Gemini. 

What started as curiosity evolved into a structured practice that has meaningfully improved how I approach elicitation, requirement writing, and stakeholder communication. Keep reading to find out how!

The Problem with Traditional Elicitation (And Why AI Can Help)

A Guide to the Business Analysis Body of Knowledge (BABOK Guide) defines elicitation as the practice of drawing out information from stakeholders and other sources to understand business needs, requirements, and constraints. It’s a deeply human activity built on listening, probing, and interpreting.

Yet the documentation that follows elicitation is often where meaning gets lost.

When requirements are written quickly after a session, they tend to be sparse, jargon-heavy, or too technical for a business audience. When they’re written cautiously, they can become so wordy that stakeholders disengage. The sweet spot (where requirements are precise, clear, and complete) is really hard to hit consistently, especially under project timelines.

This is where AI, used thoughtfully, becomes a genuine partner in the analysis work.

I want to be clear about something important, which you’ve probably heard before but bears repeating anyway: AI doesn’t replace the business analysis professional. It doesn’t replace the conversation, the empathy, or the judgment. What it does do is remove the friction between capturing an idea and communicating it well.

Think of it as a very capable writing partner who never tires, never judges, and always has a suggestion ready.

How I Use AI in My Business Analysis Practice

Appdirect provides its employees access to a proprietary AI platform that sits on top of multiple leading AI providers. This means I can choose the right model for the right task. Claude Opus for deep reasoning and nuanced requirement writing, ChatGPT for quick drafts and user story generation, and Gemini for research-oriented queries.

Having this multi-model flexibility under one roof has been a significant productivity advantage. However, this variety is far from a requirement; you can use Claude Opus alone to perform all these activities together.

Activity 1: Structuring the Elicitation Process Using the BABOK Guide

Before any elicitation session, I ask Claude Opus to help me map the relevant BABOK Guide tasks to my specific engagement context. I provide a brief description of the project, the stakeholder types involved, and the phase we’re in. Claude then outlines the elicitation and collaboration tasks from the BABOK Guide that are most applicable, suggests techniques (interviews, surveys, prototyping, observation), and helps me formulate targeted questions.

What this gives me is a structured preparation checklist grounded in best practice, something calibrated to my actual engagement (and not generic). I’ve found that walking into a session with well-formed questions, aligned to BABOK Guide elicitation techniques, dramatically improves the quality of information. Also, since I’m aligned with the standard procedures of any business analysis process, my stakeholders are absolutely loving the elicitation process, and they’re well prepared to respond.

Activity 2: Generating and Enriching Business Requirements

Once I have my session notes and rough elicitation outputs, I use Claude Opus to transform them into well-structured business requirements. My prompt is typically something like this:

Here is a problem statement and a set of raw notes from a stakeholder session. Please generate formal business requirements in the format of SHALL statements, grouped by functional area, and include acceptance criteria for each.

The output isn’t final. I treat it as a strong first draft that I then review, validate, and adjust based on my own domain knowledge. But the time saved is considerable. What used to take me several hours of drafting and restructuring is now a matter of focused review and refinement.

More importantly, the enriched requirements are written in clear language, which makes validation discussions far more productive. This also gives me an edge in ensuring I’m not overlooking important aspects across technology, people, and business processes.

Activity 3: High-Level Swag and Cross-Customer Benchmarking

One of the more creative uses I’ve developed is asking AI to help me estimate the scope of a request by drawing on patterns from similar customer scenarios. In a SaaS business like Appdirect, many customer requests share common underlying requirements, even when the surface presentation differs. I describe the nature of the request to Claude and ask it to identify analogous use cases, estimate complexity levels, and flag common scope creep risks.

This gives me a high-level SWAG—an informed estimate I can use in early-stage conversations with product and delivery teams. It’s not a substitute for a proper estimation process, but it provides a valuable starting anchor that has, more than once, saved me from walking into a scoping conversation unprepared.

Activity 4: Validating Requirement Completeness With Use Cases

Perhaps the most impactful practice I’ve developed is using AI to generate use cases from my requirements and then cross-checking whether the requirements fully cover those use cases. This is a form of automated gap analysis.

I share a set of requirements with Claude and ask:

Generate the key use cases that these requirements should support. Then identify any scenarios where the requirements appear incomplete, ambiguous, or contradictory.

The response almost always surfaces at least two or three gaps I hadn’t noticed. In one recent project, this exercise caught a missing edge case in an approval workflow that would have caused a significant post-delivery defect.

This kind of validation is aligned with the BABOK Guide principle of requirement verification and validation, ensuring that requirements are correct, complete, consistent, and verifiable. AI accelerates this process without replacing the analyst’s judgment in deciding what to do about the gaps.

Practical Tips for Business Analysts Starting with AI

If you’re a business analysis professional looking to introduce AI into your practice, here are the principles that have worked for me:

• Start with a known problem. AI responds to the quality of your input. A vague prompt produces a vague output. Spend thirty seconds framing your context before you type.
• Always review and own the output. AI-generated requirements are a first draft, not a final answer. Your domain knowledge, stakeholder relationships, and professional judgment are irreplaceable.
• Ground AI prompts in the BABOK Guide. Referencing elicitation tasks, requirement types, or validation techniques in your prompts dramatically improves the relevance of the output.
• Use AI as a thinking partner, not a shortcut. The best outcomes I’ve had come from iterating with the AI, challenging its output, asking follow-up questions, and refining the result across multiple exchanges.
• Be transparent with your team. Using AI tools in a professional context is a practice decision that your organization should be aware of. Appdirect's proprietary AI platform provides this in a secure and governed way.
  
  

A Note on Ethics and the Human Element

I want to address something that I know is on many practitioners’ minds: Is it ethical to use AI in professional business analysis work? My answer is an unequivocal yes, as long as you're transparent, critical, and accountable.

The business analysis professional's core value is not in typing requirements but in understanding the business problem deeply enough to translate it into something actionable. AI accelerates the translation. It doesn’t manufacture the understanding. 

Every requirement I produce with AI assistance goes through my review, every gap identified by AI is confirmed by my judgment, and every stakeholder conversation is still driven by human empathy and professional rapport.

The risk I caution against is passive acceptance of AI output without critical evaluation. That is where quality degrades and where the analyst’s professional contribution is genuinely diminished. Used actively and critically, AI is simply the latest evolution in our professional toolkit.

Putting AI to Work in Business Analysis

Business analysis has always been about connecting stakeholders, problems, and solutions—and bridging the gap between what is said and what is meant. AI tools, when used thoughtfully and grounded in standards like the BABOK Guide, can meaningfully reduce the effort required to bridge those gaps and improve the quality of what we produce for our stakeholders.

Through using Claude Opus, I’ve found four activities that consistently deliver value: structuring elicitation preparation using BABOK Guide tasks, generating and enriching business requirements from raw session notes, estimating scope through pattern matching, and validating requirement completeness through use cases. Each of these activities keeps me in the driver’s seat while giving me the benefit of an always-available, highly capable thought partner.

My call to action for you is simple: pick one of these four activities. Try it on your next project. Evaluate the output critically. Adjust the approach and share what you learn with the community because that’s how we can all learn from each other and grow as professionals.

The future of business analysis will be shaped by humans and AI working together to deliver faster, higher-quality outcomes with greater clarity for stakeholders.

Explore the BABOK Guide to strengthen how you apply insight, judgment, and emerging tools like AI in your work. 

---

About the Author