In business analysis, the methodology you choose is not just a process—it’s a lens that determines how you see problems, gather requirements, and deliver value. Using the wrong methodology can lead to analysis paralysis, missed deadlines, or solutions that solve the wrong problem.

This is less a full methodology and more a rigorous modeling standard. BPMN maps end-to-end processes; UML (use case, activity, sequence diagrams) specifies system behavior.

The BA works like a researcher. You empathize with users, define pain points, ideate, prototype, and test—before writing a single functional requirement.

Here, analysis is continuous. Instead of a 100-page BRD, you write user stories, acceptance criteria, and maintain a backlog. The BA (or Product Owner) refines requirements just before they are developed.