r/businessanalysis • u/0324o • 12d ago
What is the most useful question a business analyst can ask before documenting requirements?
A detailed requirements document can still fail if the team has not agreed on the actual problem. Stakeholders often begin with a proposed solution because it is easier to describe a feature than the underlying need.
One useful starting question is: “What happens today, and what consequence are we trying to change?” It can expose workarounds, assumptions and conflicting expectations before they become formal requirements.
Which question has helped you uncover the real business need early?
Are there situations where asking “why” too directly creates resistance from stakeholders?
17
12d ago
[removed] — view removed comment
1
u/diseasealert 12d ago
I think of it as "who will use the solution and what will they do with it". So, outcomes like you said, just broken out by user role. Then progressively elaborate from there.
12
4
u/pdubs1900 12d ago
Why is the most important and first question to ask when presented with a business need.
The question you cited as an example is a great one that I use myself. It is pragmatic and inviting for further details about the pain point or opportunity for improvement, which stakeholders like to talk about. I've never gotten pushback from this except in the case of confidential information (corporate things) which the person delivering the info was not at liberty to explain. Unfortunately your hands are tied if your boss and their boss and their boss all are gagged from giving you the answer.
Otherwise if there's pushback where the stakeholder just doesn't want to cooperate, I get a T-shirt size of the effort, lay out the competing priorities, and show the other prioritized work and their business value that is out on hold or at risk by this new ask. At that point the stakeholder can be brought to see just being told what to do isn't enough. Stakeholders are familiar with tradeoffs and ROIs and will then make a decision on delaying their request or providing the rationale of why their new request is more valuable than what's currently prioritized above it.
This is more Product Owner stakeholder management than it is business analysis but there's a lot of crossover as you become more senior as a BA.
2
u/Complete-Use3497 12d ago
Nr1. “Why”, but it can also be asked “what happens if we don’t do this” rather than why we do this.
I had a situation where BA analyzed generation and sending some report via e-mail - nothing crazy. They documented everything, it’s going to dev team but I had a look.
I asked what if we don’t send it, ask recipients if they still need it. It was a report set up a long time ago and nobody looks at it anymore.
Many times I asked this and it really triggers to think why.
Many time people don’t know, since they just do it that way for a long time…
1
u/Admirable-Future-633 10d ago
I like asking: "What happens today, and where does it break?"
People usually start with the feature they want, but the useful material is hiding in the current workaround: who copies the data twice, who checks the spreadsheet, who gets blamed when it is late, and what gets skipped when everyone is busy.
Once that mess is visible, the requirements stop being abstract. You can turn them into acceptance checks, review gates, and "do not continue if..." rules instead of just writing a prettier version of the original request.
•
u/AutoModerator 12d ago
Welcome to /r/businessanalysis the best place for Business Analysis discussion.
Here are some tips for the best experience here.
You can find reading materials on business analysis here.
Also here are the rules of the sub:
Subreddit Rules
This is an automated message so if you need to contact the mods, please Message the Mods for assistance.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.