Data as of Aug 25, 2026 · Based on 282 AI responses from ChatGPT, Google AI Overviews, ChatGPT Search and Google AI Mode · See how Parse measures this
Jama SoftwareYour brand can be here too.
Source | Citation share |
|---|---|
 Stakeholders who don't know what they want - Reddithttps://www.reddit.com/r/businessanalysis/comments/14kosvu/stakeholders_who_dont_know_what_they_want/ | 3.3% |
 12 Techniques for Requirement Gathering | Indeed.comhttps://www.indeed.com/career-advice/career-development/requirement-gathering-techniques | 3.1% |
 Best Business Analyst Training Institute,COEPDhttps://www.coepd.com/Blog/Essential-Elicitation-Strategies-for-Business-Analysts-1281 | 2.7% |
First time doing a requirements gathering meeting. How exactly do I ...https://www.reddit.com/r/businessanalysis/comments/ane2en/first_time_doing_a_requirements_gathering_meeting/ | 2.7% |
 Requirements Gathering: A Complete Step-by-Step Guide (2022)https://nmgtechnologies.com/blog/requirement-gathering-solve-biggest-problems-consulting | 2.5% |
A Guide to Requirements Elicitation for Product Teamshttps://www.jamasoftware.com/requirements-management-guide/requirements-gathering-and-management-processes/a-guide-to-requirements-elicitation-for-product-teams/ | 2.0% |
 How Business Analysts Gather Requirements? - Arsccom Learninghttps://arsccomlearning.in/how-business-analysts-gather-requirements | 1.7% |
 Beyond Requirements: The Real Work of a Business Analyst | by Sagar Taneja | Analyst’s corner | Mediumhttps://medium.com/analysts-corner/beyond-requirements-the-real-work-of-a-business-analyst-125369a09847 | 1.7% |
 Top 11 Practical Guide To Business Analyst Requirementshttps://businessanalyst.techcanvass.com/gathering-requirements-as-a-business-analyst/ | 1.7% |
 How to Elicit Requirements from Stakeholders Effectivelyhttps://plprojects.co.uk/eliciting-requirements-from-stakeholders/ | 1.7% |
A strong business analyst assumes that stakeholders do know what they need, but often don't know how to express it as requirements. The analyst's job is to uncover needs, constraints, and desired outcomes—not simply ask, "What do you want?" and write down the answer.
Some practical techniques:
Instead of asking:
"What system do you want?"
Ask:
People often struggle to describe solutions but can clearly describe frustrations and desired business outcomes.
Map the existing process ("as-is") before discussing the future state ("to-be").
Techniques:
When stakeholders see their current process visualized, they frequently identify gaps, pain points, and improvement opportunities they hadn't previously articulated.
People often describe how they think work happens, not how it really happens.
Spend time:
Observation frequently reveals requirements that never emerge in interviews.
Many stakeholders cannot evaluate written requirements but can react to something visual.
Show:
A common BA principle is that stakeholders discover what they want by reacting to examples. Visuals trigger much richer feedback than documents.
Rather than:
"What are your requirements?"
Ask:
Scenarios uncover business rules, exceptions, and hidden requirements.
Stakeholders often understand only their piece of the process.
Cross-functional workshops help expose:
Requirements emerge through discussion rather than individual interviews alone.
Requirements are usually discovered progressively.
A typical cycle is:
Experienced analysts expect requirements to evolve as understanding grows. Research and practitioner experience consistently show that requirements are often co-created through iterative conversations rather than simply extracted from stakeholders.
Sometimes stakeholders need help imagining possibilities.
For example:
"Would you prefer approvals via email, a workflow queue, or automatic rules?"
Providing alternatives often generates more useful feedback than asking open-ended questions. The goal isn't to lead them to an answer, but to stimulate thinking.
A common mistake is believing requirements gathering means "collecting requirements." In reality, business analysis is often a process of discovery and facilitation. Stakeholders typically provide fragments—problems, frustrations, goals, and ideas—and the BA helps transform those fragments into clear, testable requirements.
One of the most effective questions a BA can ask is:
"What decision are you trying to make, or what outcome are you trying to achieve?"
That question usually leads to better requirements than asking what features they want.
When stakeholders do not know what they want, a Business Analyst (BA) must shift from a passive order-taker to an active investigator who extracts needs through targeted problem-solving, visualization, and behavioral observation . Instead of asking stakeholders what software features they want, the BA focuses on identifying their daily frustrations, mapping their workflows, and presenting concrete concepts they can react to.
The following strategic framework allows a BA to guide uncertain stakeholders toward clear, actionable requirements:
Focus on Pain Points, Not Solutions
Stakeholders rarely know the technical solution they need, but they always know what makes their jobs difficult.
Shift from Interviews to Observation
If a stakeholder struggles to articulate their process during a structured interview, watch them do it live.
Give Them Something to Reject
People are notoriously bad at inventing ideas from scratch, but they are excellent at criticizing existing options.
Adopt an Iterative Agile Approach
When final requirements are highly ambiguous, executing a massive upfront discovery phase is dangerous and prone to failure.
Structure the Comparison of Elicitation Techniques
Different situations require different tactics. The table below outlines how to choose your elicitation method based on the stakeholder's exact behavior:
| Stakeholder Behavior[1][2][3][4][5][6] | Best Elicitation Technique | Why It Works |
|---|---|---|
| "I'm too busy to think about this right now." | Asynchronous Templates / Draft Artifacts | Allows them to review pre-made assumptions on their own time rather than starting from zero. |
| "I can't picture how this software helps me." | Low-Fidelity Prototyping / Wireframes | Converts abstract technical ideas into visual layouts they can easily click through. |
| "Our current process is just too complicated." | User Observation / Process Mapping | Bypasses verbal confusion by letting the BA visually track steps and find hidden gaps. |
| "I don't know what I want, but I'll know it when I see it." | Agile Iterations / Iterative Feedback Demos | Minimizes risk by testing small, working software pieces before committing to a final build. |
To help tailor this advice to your specific project, tell me:
To effectively gather requirements from stakeholders who do not know what they want, a business analyst must shift from passive note-taking to active elicitation, shifting the focus away from solutions and toward current business problems . When stakeholders lack a clear vision, asking them what features they want usually results in blank stares or shifting scope.
The following structured framework can be used to extract clear requirements from ambiguous feedback.
Stakeholders might not know what software or process they want, but they know exactly what frustrates them daily.
When stakeholders cannot visualize the future, begin by documenting their present reality.
People find it much easier to point out what they don't want than to describe what they do want.
Technical jargon and abstract business analysis terms can cause stakeholders to disengage.
Unsure stakeholders frequently request every feature imaginable once they start brainstorming, which quickly triggers scope creep.
To help tailor these strategies to your current situation, tell me a bit more about what you are working on:
Stakeholders who “don’t know what they want” usually do know their problems, frustrations, constraints, and goals — they just can’t translate those into clear requirements yet. A strong business analyst helps them discover and shape the requirements collaboratively, rather than expecting stakeholders to hand over a perfect specification.
Here’s what effective BAs typically do:
That question is often too broad.
Instead, ask:
This shifts the conversation from solutions to business outcomes.
People often struggle to explain processes abstractly, but their daily behavior reveals the real requirements.
Effective techniques include:
Many hidden requirements surface during observation rather than interviews.
Stakeholders react better to something concrete than to abstract discussion.
Useful tools:
A common BA trick:
Don’t ask stakeholders to invent the solution. Show them a draft and ask what’s wrong with it.
People are usually much better at reacting than creating from scratch. This is echoed frequently by experienced practitioners.
Requirements are often symptoms of deeper operational problems.
For example:
Stakeholder says:
“We need a dashboard.”
A good BA asks:
Sometimes the real requirement is:
The “5 Whys” technique is especially effective here.
Individual stakeholders usually see only part of the process.
Cross-functional workshops help expose:
Good BAs facilitate discussion between groups rather than acting as a passive note-taker.
Many stakeholders cannot define a future state until the current state is understood clearly.
A strong BA maps:
Once stakeholders see the process visually, future-state ideas emerge naturally.
Stakeholders often say things like:
The BA’s job is to clarify:
Good requirements become:
Requirements discovery is rarely one-and-done.
Strong BAs:
Research shows requirements are often co-created through iterative conversations, prototypes, and analysis — not simply “extracted” from stakeholders.
Stakeholders often propose solutions immediately:
“We need an AI chatbot.”
But the underlying need may actually be:
A BA should challenge assumptions respectfully and uncover the business objective underneath the requested solution.
Good analysts constantly confirm:
Requirements quality improves through repeated validation, not through a single interview.
A useful mindset is:
Stakeholders are domain experts.
The BA is the discovery and clarification expert.
The BA’s role is not merely documenting requirements — it’s facilitating understanding, reducing ambiguity, and guiding stakeholders toward clarity.
To gather requirements from uncertain stakeholders, a business analyst (BA) must pivot from asking "what do you want?" to uncovering "what problem are you solving?". Effective techniques include creating prototypes/mockups, mapping current ("as-is") processes, observing daily workflows, and using iterative, Agile feedback loops (e.g., MVPs).
Strategies for Eliciting Requirements from Indecisive Stakeholders:
By shifting the role from "order-taker" to "problem-solver," the BA provides structure to ambiguity, transforming vague ideas into actionable project requirements.
This is one of the core challenges of business analysis—and also where good analysts really differentiate themselves. The blunt truth: stakeholders rarely start with clear requirements. Your job isn’t to “collect” them—it’s to help discover and shape them.
Here’s how effective BAs handle that situation in practice:
When people don’t know what they want, it’s usually because they’re thinking in solutions instead of needs.
Start with questions like:
What’s not working today?
What’s slowing you down?
What would success look like?
Stakeholders often can’t define features, but they can describe pain points and desired outcomes.
👉 This reframes the conversation from vague ideas to concrete business value.
Before designing anything, map how things work today:
Processes
Workarounds
Bottlenecks
Dependencies
Understanding the current reality often reveals hidden requirements and gaps stakeholders didn’t articulate.
It also helps avoid solving the wrong problem.
People struggle with imagination—but react well to visuals.
Use:
Wireframes / mockups
Process diagrams
Prototypes
Sample reports
Seeing something tangible triggers feedback like:
“I don’t like this” or “this is close but missing X”
That’s gold. It’s far easier for stakeholders to react than to invent from scratch.
Requirements are discovered progressively , not defined in one session.
Good BAs:
Show early drafts
Get feedback
Refine continuously
Iteration works because requirements emerge through feedback cycles , not perfection at the start.
Stakeholders often:
Describe solutions instead of problems
Miss edge cases
Omit implicit assumptions
Your role is to probe and interpret , not just document.
Effective techniques:
“Why?” (multiple levels deep)
Scenario walkthroughs
Edge-case exploration
Contradiction checks
Because in reality, you’re extracting information , then turning it into requirements—not receiving them directly.
No single method works.
Combine:
1:1 interviews (depth)
Workshops (alignment)
Observation (truth vs what people say)
Document analysis (context)
Experienced BAs mix techniques to uncover the full picture.
If stakeholders are stuck:
Show similar systems
Compare alternative approaches
Use “would you want something like this?” prompts
People recognize what they want when they see options—even if they couldn’t describe them before.
Sometimes the issue isn’t confusion—it’s that you’re talking to the wrong people.
Include:
End users (day-to-day reality)
Decision-makers (strategic goals)
SMEs (deep knowledge)
Missing stakeholders = incomplete or misleading requirements.
A key mindset shift:
You are not a scribe—you are a facilitator of discovery.
Research shows requirements evolve through:
conversations
analysis
iteration
—not just initial stakeholder input.
When stakeholders “don’t know what they want,” it’s not a blocker—it’s the starting point.
A strong business analyst:
anchors on problems, not features
uses visuals and examples
iterates constantly
challenges assumptions
synthesizes scattered inputs into clarity
If you wait for stakeholders to hand you perfect requirements, you’ll never get them. If you guide them through discovery, you will.
If you want, I can walk through a realistic example (e.g., building a new internal tool) and show exactly how these techniques play out step by step.
A business analyst doesn’t wait for stakeholders to know what they want —because often they genuinely don’t. The job shifts from “collecting requirements” to facilitating discovery and shaping understanding.
When stakeholders are unclear, effective BAs use a mix of structured techniques to uncover needs, expose assumptions, and gradually co-create requirements.
Here’s how that actually works in practice:
Stakeholders often struggle to articulate requirements, but they can usually describe:
pain points (“this process takes too long”)
frustrations (“customers keep calling about X”)
goals (“we want faster onboarding”)
So the BA starts by anchoring on business problems, not solutions. Requirements are then derived from that.
Asking “What do you want?” is usually the least effective approach.
Better techniques:
Contextual interviews (“Walk me through how you do this today”)
Process mapping (visualizing current workflows)
Observation / shadowing (watching real work happen)
Document analysis (existing forms, reports, systems)
These help uncover implicit needs stakeholders can’t easily verbalize.
When people “don’t know what they want,” they often can’t visualize it yet.
So you give them something to react to:
Wireframes or sketches
Mockups / prototypes
Simple workflow diagrams
“What if…” scenarios
This is powerful because stakeholders are much better at:
reacting, correcting, and refining
than inventing from scratch.
Prototyping is one of the most effective ways to surface hidden requirements.
Instead of trying to “finish requirements” in one go:
Start with rough understanding
Validate early assumptions
Refine through repeated feedback loops
This works especially well in Agile environments where requirements naturally evolve through interaction.
A key BA skill is drilling into intent:
“Why is this important?”
“What problem does that solve?”
“What happens if we don’t do this?”
This separates:
stated solutions (“we need a dashboard”)
from
real needs (“we need visibility into delays”)
Often, the solution changes completely once the “why” is understood.
A critical but underrated point: stakeholders don’t “own requirements” in finished form.
The BA’s role is to:
synthesize conflicting inputs
resolve ambiguity
define clear, testable requirements
align them to business value
As one common principle in BA practice notes, requirements are co-created through analysis, not simply gathered.
When stakeholders are unsure, it’s not a failure condition; it’s normal.
Good BAs:
explicitly document assumptions
maintain a “decision log”
validate frequently
accept that early requirements are hypotheses, not truths
When stakeholders don’t know what they want, an effective BA:
focuses on problems, not requirements
uses observation + structured questioning
introduces visuals and prototypes to trigger feedback
iterates until clarity emerges
and ultimately translates messy input into precise requirements
If you want, I can also walk through a real example (like “stakeholder wants an app but has no idea what features”) and show exactly how a BA would progressively extract requirements step by step.
To gather requirements from stakeholders who are unsure of their needs, business analysts should focus on understanding the underlying problems rather than just collecting feature requests. Key strategies include defining the current "as-is" state, using prototypes and visuals for feedback, engaging in iterative discussions, and asking targeted questions about desired business outcomes.
Top Techniques for Eliciting Vague Requirements
Steps to Take with Uncertain Stakeholders
This is the normal situation, not an exception. Stakeholders rarely walk in with clear, complete requirements—in fact, uncovering what they really need (not what they say) is the core skill of a business analyst.
Here’s how effective BAs handle it in practice:
Stakeholders often jump straight to solutions (“we need a dashboard”) without defining the underlying need.
A strong BA reframes the conversation:
“What problem are we trying to solve?”
“What’s broken today?”
“What outcome would success look like?”
👉 This shifts from solution gathering → problem discovery , which is where real requirements come from.
Good elicitation is active. Stakeholders don’t know what they want because they haven’t thought deeply enough.
Techniques that work:
5 Whys to dig into root causes
Follow-up probing: “Can you give an example?”
Reframing: “So what you’re saying is…”
This turns vague input into concrete needs.
People react better than they invent.
Wireframes, mockups, or sample workflows
“Would something like this work?”
Why it works:
Requirements often emerge through iteration , not initial conversations
Stakeholders refine ideas when they see something tangible
What stakeholders say ≠ what they do.
Use:
Job shadowing
Process observation
System walkthroughs
This uncovers:
Hidden steps
Workarounds
Pain points stakeholders forgot to mention
Observation is a core elicitation technique for exactly this reason 10 Best Business Analysis Requirements Gathering Techniques.
One-on-one interviews are useful—but limited.
Workshops help:
Surface conflicting views
Build shared understanding
Trigger ideas through discussion
Experienced BAs combine multiple techniques (not just one) for full coverage Requirements Gathering Techniques: A Complete Toolkit for Business Analysts | Qualify Nation.
When people don’t know what they want, they usually don’t fully understand their own process.
So:
Map the current state (AS-IS)
Identify pain points
Co-create the future state (TO-BE)
This method naturally reveals requirements instead of forcing stakeholders to “invent” them.
Requirements are not discovered in one pass.
Effective BAs:
Run feedback loops
Validate assumptions early
Get partial sign-offs
This avoids the classic failure:
👉 “This isn’t what I wanted” after months of work
Stakeholders express needs , not requirements.
Your job:
Convert vague needs → clear, testable requirements
Separate:
Business need
User requirement
Functional requirement
This transformation is where BA value really shows.
No single method works alone. Common toolkit:
Interviews
Workshops
Observation
Prototyping
Document analysis
Combining them gives a fuller, more accurate picture.
If stakeholders “don’t know what they want,” it usually means:
They know their pain , not the solution
They haven’t articulated it clearly
Or they’re thinking in the wrong frame (solutions vs problems)
A good BA doesn’t wait for clarity—they create it.
Think of your role as:
🧠 Translator + Investigator + Facilitator
Not:
📝 Note-taker
If you want, I can walk through a realistic example (e.g., vague request → refined requirements step-by-step).
To gather requirements from stakeholders who are unsure of their needs, business analysts (BAs) must shift from passive "gathering" to active elicitation, focusing on uncovering underlying problems rather than just solutions. Effective techniques include mapping "as-is" processes, creating visual prototypes or Prototyping mockups, conducting one-on-one interviews, and asking open-ended questions about pain points.
Key Strategies for Unclear Stakeholders:
Techniques for Elicitation:
Ultimately, the goal is to guide stakeholders from "I don't know" to "That's not what I need," using the feedback to build the correct requirements.
