The job is bigger than writing requirements
Business analysis is often reduced to a list of documents: BRD, FRD, user stories, process maps and so on. Those artifacts matter, but they are outputs of a much larger thinking process.
A strong BA helps an organization move from “something is not working” to a shared understanding of the problem, the desired outcome, the options available, and the requirements that make a solution possible.
Start with the decision that needs to be made
When a stakeholder says, “We need a new dashboard,” the first useful question is rarely “What should the dashboard look like?” It is “What decision are you trying to make that is difficult today?” That question changes the conversation from features to outcomes.
PMI describes business analysis as work that identifies needs, recommends viable solutions, manages stakeholder requirements and supports successful implementation.
BA and PM are connected, not interchangeable
| Question | Practical answer |
|---|---|
| Business analysis | What problem are we solving? What should the solution accomplish? |
| Project management | How do we organize people and work to deliver the agreed outcome? |
| Product management | What should we build, for whom, and why does it create value? |
| Engineering | How can we build the solution safely and effectively? |
What good BA work feels like
Try it
Take any familiar app or website. Write one feature request. Then ask “why?” three times. Your final statement should sound more like a business outcome than a feature.