3.1. Business Analyst Roles and Responsibilities
💡 First Principle: "Owner," "manager," "product owner," and "product manager" all sound like generic leadership words, but on this exam each one names a distinct scope of accountability. The exam tests whether you can match a described responsibility to the correct title — not recite the titles from memory.
| Role | Owns | Typical Focus |
|---|---|---|
| Process owner | A specific business process's design and outcomes | "Is this process working as intended, end to end?" |
| Process manager | Day-to-day execution of that process | "Is the process running correctly today?" |
| Product manager | The product's overall strategy and lifecycle | "What should this product become, and why?" |
| Product owner | Prioritization of the backlog for value delivery | "What gets built next, and in what order?" |
Why roles and responsibilities need explicit identification. Skipping stakeholder identification is a common failure point — if a project doesn't clearly name who owns which decisions, requirements get approved by the wrong person, or nobody at all, and rework follows. Explicitly identifying roles up front is what lets a BA know who to go to for a decision versus who to go to for day-to-day process detail.
Internal vs. external roles. Internal roles sit inside the performing organization (an internal process owner, an internal product team). External roles sit outside it — a customer, a regulator, a vendor's own product manager. The distinction matters because external stakeholders typically can't be directed the way internal ones can; influence and negotiation replace direct instruction.
⚠️ Exam Trap: A scenario describing someone who "decides what features ship in the next release, ranked by value" is describing a product owner, not a product manager — even though "manager" sounds like the more senior-sounding title. Match the described behavior to the definition, not the title's apparent seniority.
Reassigning responsibility when an organization restructures. A common scenario pattern asks who should take on two related but distinct responsibilities after a reorg — say, redesigning an underperforming process versus running the redesigned version day to day once it's live. These map cleanly onto the process owner/process manager split: the process owner is accountable for the redesign's outcome, and the process manager takes over daily operation once it's implemented. The two roles can be held by different people, and often are — nothing about the definitions requires one person to do both, even though a scenario may tempt you to assume continuity of ownership by default.
When directing an external party backfires. A BA who treats an external vendor's team exactly like an internal team — issuing direct assignments rather than negotiating — often finds the relationship deteriorating over time, since the vendor has no organizational obligation to comply the way an internal team member does. Recognizing which engagement mode a stakeholder calls for, before choosing how to approach them, prevents this friction before it starts.
