Why do project managers and business analysts always overlap?
Business analysts define what the business needs, while project managers determine how the work is organized and driven forward. When BAs expect project plans and timelines to answer requirements, or when the two roles misunderstand which input comes first, responsibilities clash and ownership gets blurred.
Core Friction Pattern
Analysis of 2 peer accounts across online developer and community forums reveals that “Why do project managers and business analysts always overlap?” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+2 alternative community-tested workarounds cataloged below.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
Why do project managers and business analysts always overlap?
- 1Escalating role disputes to leadership and sponsorsDid this help you?
- 2Running discovery phases independently without analyst inputDid this help you?
- 3Working around uncooperative team members using alternative process workstreamsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“My understanding is pretty simple: As a BA, your role is to identify and define what the business needs to reach a solution for the <problem>. Opposite of that, I as the PM determine how the work is organized and drive it forward towards a solution for said business need.”source ↗
“BA: "Well, we need the Project Plan & Timeline to answer those questions. Can you get it done please?"”source ↗
“Their role is the major input into ours and when they don’t understand that or think it’s the other way around, it then causes situations like this.”source ↗
Where this came up
People with this problem also raised
Related community dilemmas clustered by discussion consensus
How to balance workloads for different mock trial roles
Building a project from the ground up requires defining rubrics, prep, and research for every distinct part to ensure a balanced workload. This often leaves teachers unsure if they are over-complicating the activity, especially when trying to assign enough basic research to passive roles like jurors.
Why does management give us arbitrary deadlines without explaining why?
When managers hide financial deadlines and project goals, employees are left guessing what matters most and are punished when they guess wrong. This lack of transparency causes high stress and prevents teams from planning effectively, making the pressure feel entirely arbitrary.
Why is Scrum being forced onto non-Agile teams?
Newly integrated teams are forcing a rigid Scrum approach onto projects requiring traditional or hybrid methods, refusing feedback from existing staff. This creates friction, hostility, and widespread frustration instead of productivity, resulting in excessive meetings that stall work.
How do I know what my job actually is with no communication?
A total lack of communication from leadership leaves new staff guessing about their duties and wondering if they should just stop helping altogether. Without clear boundaries, colleagues end up taking over lessons and paperwork, making it impossible to establish an actual role.
Why is tech support doing project work without extra pay?
Technical support staff are being pulled into project implementation and scope creep without a role change, pay bump, or clear departmental boundaries. Because incoming standard tickets and project requests get blurred, staff are forced to absorb extra workload without the necessary capacity or staffing.
Doing manager work without the title
Employees manage direct reports and advanced tasks while stuck under junior titles like coordinator, specialist, or processor. When applying for equivalent roles, they are rejected for supposedly lacking "management experience." This leaves them trapped at a lower wage ceiling, unable to get the career bump their actual work deserves.