Why BA work becomes more about structure than requirements in real delivery environments
I’ve worked in delivery environments as a BA and Product Manager for sometime now, I keep seeing the same pattern across different organisations.
Most teams do not struggle because of lack of skill or effort. They struggle because of structure.
Common issues:
• stakeholders are too senior to give detailed input
• unclear ownership of requirements
• constant priority changes
• limited access to SMEs
• discovery happens too late in delivery
What stands out to me is that BAs often end up compensating for gaps in operating model design, instead of just doing analysis work.
In many cases, success in discovery depends less on the BA and more on how the organisation structures decision making and access to information.
In some environments, you naturally have product owners or operational SMEs who sit closer to the detail. In others, everything is centralised at senior level, which makes even basic clarification work slow and fragmented.
In those cases, I have found that shifting from “requirements gathering” to structured validation helps a lot. Instead of trying to extract everything upfront, you work with partial understanding and progressively refine it through short focused check-ins.
Curious how other BAs or Product people handle these situations where clarity and stakeholder access are limited from the start of a project.