I get asked this fairly often, usually by people deciding which direction to move in. The honest answer is that the boundary depends heavily on the organisation, and anyone who gives you a clean universal definition is simplifying.
But there is a real difference underneath the overlap, and it is roughly this: a Product Manager is mostly accountable for choosing what to build. A Business Analyst is mostly accountable for making sure the thing being built is properly understood.
Different centres of gravity
Both roles ask why. Both talk to users. Both write things down. The difference is where the weight sits.
- A PM tends to work outward: market, positioning, roadmap, trade-offs between opportunities, what to say no to.
- A BA tends to work inward: process, rules, edge cases, dependencies, what a decision actually implies once you follow it through the system.
In a small startup, one person does both and the distinction is academic. In a larger enterprise setting, the depth required on the inward side is genuinely a full job, which is why the role exists separately.
The question each role is answering
I find it useful to think of it as two different questions. The PM is asking: of all the things we could do, which one is worth doing? The BA is asking: now that we have chosen, what does it actually mean, precisely, including all the parts nobody has thought about yet?
Neither question is more senior than the other. They fail in different ways. A team without the first builds well-specified things nobody needed. A team without the second builds the right idea in a way that falls apart on contact with real data.
Why I am not in a hurry to pick a label
I am early in this. What I have noticed is that the skills that make me better at Business Analysis (understanding users, thinking in outcomes, being rigorous about what done means) are not a different set of skills from product thinking. They are a subset of it, practised in more detail.
So I am less interested in which title I end up with than in getting genuinely good at the part they share: understanding a problem well enough that the solution becomes obvious to everyone, not just to me.