Business Analysts and Project Managers often work side by side on the same initiative. Both engage stakeholders, attend workshops, manage issues and help projects move forward.
Because of this overlap, the two roles are sometimes confused.
But they have fundamentally different areas of focus.
A simple way to think about the distinction is:
The Business Analyst focuses on what the organisation needs and why. The Project Manager focuses on how the initiative will be delivered, when, and with what resources.
Both perspectives are important. A project can be delivered on time and within budget but still fail if it solves the wrong problem. Equally, excellent requirements have limited value if the project cannot successfully deliver them.
What Does a Business Analyst Do?
A Business Analyst (BA) works to understand business needs and translate them into clearly defined changes, requirements and outcomes.
The BA typically asks questions such as:
- What problem are we trying to solve?
- Why does this problem exist?
- Who are the stakeholders?
- What does the current process look like?
- What should the future state look like?
- What business capabilities are required?
- What are the functional and non-functional requirements?
- How will we know the solution meets the business need?
The Business Analyst therefore concentrates heavily on business needs, processes, requirements, stakeholders and solution outcomes.
A useful representation is:
Current State → Problem → Future State → Gap → Requirements → Solution → Business Outcome
What Does a Project Manager Do?
A Project Manager (PM) focuses on organising and controlling the delivery of the initiative.
Typical questions include:
- What needs to be delivered?
- What is the project schedule?
- What resources are required?
- What is the budget?
- What are the dependencies?
- What risks and issues could affect delivery?
- Who is responsible for each activity?
- Are milestones being achieved?
- Is the project still on track?
The Project Manager creates the structure needed to move the initiative through delivery.
A simplified view is:
Scope → Plan → Resources → Schedule → Risks → Delivery → Closure
The Key Difference: Business Outcome vs Project Delivery
The easiest way to understand the difference is through their primary focus.
| Business Analyst | Project Manager |
|---|---|
| Focuses on the business need | Focuses on project delivery |
| Understands the problem | Organises how the work will be delivered |
| Defines requirements | Manages scope and schedule |
| Analyses processes | Coordinates activities and resources |
| Facilitates business discovery | Facilitates project planning |
| Manages requirement changes | Manages project changes |
| Supports solution validation | Monitors delivery progress |
| Focuses on business outcomes | Focuses on project objectives |
Neither role is more important than the other.
They solve different but complementary problems.
An Example: Implementing a New ERP System
Imagine an organisation decides to replace its existing ERP platform.
The Business Analyst might:
Analyse existing business processes and pain points.
Interview Finance, Procurement, HR, Operations and other stakeholders.
Map current-state processes.
Identify opportunities for process improvement.
Define future-state business processes.
Develop functional and non-functional requirements.
Document business rules and integration requirements.
Support vendor evaluation.
Validate that the proposed ERP solution meets the organisation’s requirements.
The Project Manager might:
Develop the overall implementation plan.
Establish project governance.
Manage the budget.
Coordinate internal teams, vendors and implementation partners.
Manage the project schedule and milestones.
Track risks, issues and dependencies.
Report project progress to executives.
Coordinate testing, deployment and implementation activities.
Both people are working on the same ERP initiative, but they are looking at it through different lenses.
The BA asks:
“Are we implementing the right solution?”
The PM asks:
“Are we delivering the solution successfully?”
Where Do Their Responsibilities Overlap?
There is naturally some overlap between the roles.
Both may facilitate meetings, engage stakeholders, identify risks, manage change, communicate with delivery teams and contribute to governance.
The distinction is usually found in why they are performing those activities.
For example, both may run workshops.
A Project Manager might facilitate a workshop to establish:
Activities → Owners → Dependencies → Milestones → Delivery Plan
A Business Analyst might facilitate a workshop to establish:
Problems → Processes → Stakeholders → Requirements → Future State
The technique may look similar, but the intended outcome is different.
Who Owns the Requirements?
Requirements are generally a core responsibility of Business Analysis.
The BA works with stakeholders to elicit, analyse, document, prioritise, validate and manage requirements.
The Project Manager needs visibility of those requirements because they affect scope, schedule, cost and resources.
For example, if stakeholders introduce a significant new requirement halfway through delivery:
The BA asks:
What is the business need? Is this genuinely required? What processes or existing requirements does it affect?
The PM asks:
What will this change do to scope, schedule, budget and resources?
Together, these perspectives support a better change decision.
Who Owns the Project Scope?
This is where the distinction can sometimes become blurred.
A Business Analyst helps define what the business and solution need to achieve.
A Project Manager manages the approved project scope and the impact of changes to it.
Consider a stakeholder requesting a new reporting capability.
The BA analyses the requirement:
Why is it required? → Who needs it? → What information is needed? → What business decision does it support?
The PM considers the delivery implications:
How much effort? → What does it cost? → Does it affect the timeline? → Does another deliverable need to change?
The decision is stronger when both perspectives are considered.
What Happens When There Is No Business Analyst?
On some projects, the Project Manager may also perform Business Analysis activities.
This can work for relatively small or straightforward initiatives.
However, on larger or more complex initiatives, combining the roles can create challenges.
The Project Manager may naturally concentrate on:
Schedule → Budget → Resources → Risks → Milestones
while detailed analysis of:
Business Needs → Processes → Stakeholders → Requirements → Business Rules
receives less attention.
The result can be a project that is well managed from a delivery perspective but poorly defined from a business perspective.
What Happens When There Is No Project Manager?
The opposite problem can also occur.
An initiative may have excellent Business Analysis, clearly documented requirements and strong stakeholder alignment, but lack delivery coordination.
Without effective project management, the initiative can experience unclear responsibilities, missed deadlines, unmanaged dependencies, budget issues and poor communication.
Strong requirements do not automatically create successful delivery.
Do Agile Projects Still Need Both?
Agile delivery changes how responsibilities are organised, but it does not eliminate the need for either Business Analysis capability or delivery management capability.
The titles may change.
Business Analysis responsibilities may be shared between Business Analysts, Product Owners, Product Managers and subject matter experts.
Traditional Project Management responsibilities may be distributed across Delivery Managers, Scrum Masters, Product Owners and programme leadership.
The important question is therefore not simply:
“Do we have someone called a Business Analyst and someone called a Project Manager?”
A better question is:
“Do we have clear ownership of both business analysis and delivery management responsibilities?”
BA vs PM: Which One Does Your Project Need?
Many substantial initiatives benefit from both.
If the primary challenge is understanding the problem, defining requirements, improving processes or aligning stakeholders, Business Analysis capability is likely to be important.
If the primary challenge is coordinating resources, managing schedules, budgets, dependencies and delivery risk, Project Management capability is likely to be important.
For complex transformation initiatives, system implementations and cross-functional projects, the strongest model is often:
Business Analyst + Project Manager + Business Stakeholders + Delivery Team
Each brings a different perspective to the initiative.
Two Roles, One Successful Outcome
Business Analysts and Project Managers should not be viewed as competing roles.
They are complementary.
The Business Analyst helps answer:
Are we solving the right problem and building the right solution?
The Project Manager helps answer:
Can we successfully deliver it within the agreed constraints?
Together, they connect business need with successful execution.
A well-managed project needs more than a schedule and budget. It also needs clearly understood problems, aligned stakeholders, well-defined requirements and measurable business outcomes.
That is why strong Business Analysis and strong Project Management often work best together.