In BA work, missing information makes assumptions inevitable — but wrong assumptions lead to incorrect confirmations and rework. This article shows how to minimize risky assumptions and avoid jumping to conclusions.
In the BA world, encountering missing information or situations where gathering information is nearly impossible is a common occurrence. That's why making assumptions is inevitable. However, there are still cases where analysts, despite having collected and analyzed information, still make assumptions. Even I, while analyzing, sometimes make assumptions, leading to incorrect confirmations with clients and requiring rework.
So, how can we minimize this situation when making assumptions is unavoidable? Based on my experience, here are a few ways I can share with you:
1. Validate
This is the easiest and most effective way to determine if your assumption is correct. There are many ways to do this, and they're quite similar to the techniques used for requirement elicitation: interviews, surveys, Q&A sessions, etc. Validation is not only for determining whether an assumption is right or wrong but also to determine if it truly meets the client's needs. Remember, don't just focus on verifying right or wrong.
2. I/O Flow
Those of you who have taken my BA course are probably familiar with this technique. I/O flow helps verify the input and output information of an issue, specifically, in this case, an assumption. If the analysis results during the I/O flow process are unclear – where it's created, how it's used, whether it meets the initial requirements – then the assumption might be heading in the wrong direction.
3. Scenario
This involves outlining specific use cases for the assumption within the system. Use cases should be applied to different roles (different types of users on the system) in happy case, alternative, and exception scenarios. Use this analysis to assess the feasibility of the assumption.
4. Prototyping
Prototyping involves using design tools like Figma, Invision, or even coding a part of the software to give clients an initial visualization of the product – basically, a "sample product." By seeing this "sample product" and performing simple interactions, clients can easily verify if the BA's assumptions align with their expectations.
There are many other approaches depending on the specific case and the project/company. If you have any methods you'd like to share, feel free to leave a comment below!
