Can one person really be both the project manager and the business analyst?
It’s a question that resurfaces every few months on LinkedIn—and every time, the comment section lights up. It’s not hard to see why.
Companies everywhere are trying to consolidate roles. AI is shifting how we define job boundaries. And in that swirl, leaders are experimenting: one role, two roles, hybrids, handoffs. Most of us have seen at least one version fail badly.
But the deeper I go into this debate—in client rooms, hiring conversations, and org design work—the more I notice something strange: the people most confident in their answer are usually reacting to the scar tissue of a past failure. And the trouble with scar tissue is that it narrows your range of motion.
Our experiences matter—but they’re also limited. Most of us haven’t seen every flavor of project, team, or constraint. And as a colleague of mine likes to say, it’s hard to read the label from inside the bottle.
If all we use is personal experience, our data set is too small. To make better decisions, we have to zoom out—and look at the structure of the problem, too.
Everyone Thinks the Answer is Obvious.
Spend five minutes in the comments section of a “PM/BA hybrid” post, and you’ll start to see the two camps form.
On one side: Why not combine them? If the PM truly understands the business, why not let them own the requirements too? One role means fewer handoffs, tighter communication, and leaner teams. It’s faster, cheaper, and arguably smarter—especially in smaller companies or projects where budget and headcount are tight.
On the other side: This is a false economy. Business analysis is a craft. It requires specialized skills in facilitation, elicitation, documentation, and prioritization—especially in technical or regulated environments. Combine the roles, and something important will get dropped. Usually, it’s quality. Sometimes, it’s the project.
Here’s the thing: both positions are strong. They’re clear. They’re well-reasoned. And they’re often shaped by real experience.
But that’s also what makes them incomplete.
Why It’s Not So Simple
When we debate whether the PM and BA should be the same person, we tend to argue as if the roles are fixed—as if there’s a single “right” way to divide the work, and our job is to figure out which side wins.
But the truth is, roles have always flexed. They evolve with the work, the team, the context, and the tools available. The boundary between PM and BA isn’t a line etched in stone. It’s a design choice—one that’s shaped by capacity, clarity, and risk tolerance.
And companies will always be experimenting. Sometimes for efficiency. Sometimes out of necessity. And as AI continues to automate pieces of both jobs, that experimentation is only going to accelerate—not settle into consensus.
That’s why it’s worth stepping back—not just to ask whether the roles should be combined, but to rethink the assumptions baked into the debate itself.
Here are four reasons the question is more complex than it looks.
- All Roles Are Made Up
It’s easy to forget, but job roles—especially in knowledge work—aren’t natural laws. The PM/BA split that feels obvious today was once someone’s invention. A useful choice. Not a permanent truth.
That means we can reinvent it. Especially when the work shifts, or the tools change, or the people in the room bring a different blend of strengths. Holding too tightly to yesterday’s structure risks missing tomorrow’s opportunity.
- Most Teams Don’t Get to Choose
The hybrid PM/BA isn’t always a strategy. Sometimes it’s survival.
Small and mid-sized orgs often can’t afford a two-person team for every project. They need people who can stretch—and who won’t let gaps stall progress. For these teams, debating whether a hybrid “should” exist misses the point. It already does. The real question is how to support it.
- AI Is Already Coming for the Job Split
This isn’t theoretical. AI is already eating the admin-heavy parts of both jobs—drafting requirements, documenting decisions, flagging conflicts, prepping status updates.
That doesn’t make PMs or BAs obsolete. But it does mean both roles require less time to execute well. Which means more leaders will ask: if the tools can do 30–40% of both jobs, why can’t one person do the rest? That’s not an attack—it’s an inevitable design question. And the sooner we answer it with intention, the better.
So Where Does That Leave Us?
There’s no one right answer—just tradeoffs.
Every project is a design decision. Do you want depth at the risk of disconnection? Or range at the risk of missed nuance? Most teams don’t get to maximize both.
Think of it like a slider. On one end: deep specialization. On the other: broad generalization. Where you place it depends on the work, the people, and the moment.
The smartest PMOs don’t argue about where the slider should be. They move it on purpose—and design roles to match.
Here are four reasons the question is more complex than it looks.
- All Roles Are Made Up
It’s easy to forget, but job roles—especially in knowledge work—aren’t natural laws. The PM/BA split that feels obvious today was once someone’s invention. A useful choice. Not a permanent truth.
That means we can reinvent it. Especially when the work shifts, or the tools change, or the people in the room bring a different blend of strengths. Holding too tightly to yesterday’s structure risks missing tomorrow’s opportunity.
- Most Teams Don’t Get to Choose
The hybrid PM/BA isn’t always a strategy. Sometimes it’s survival.
Small and mid-sized orgs often can’t afford a two-person team for every project. They need people who can stretch—and who won’t let gaps stall progress. For these teams, debating whether a hybrid “should” exist misses the point. It already does. The real question is how to support it.
- AI Is Already Coming for the Job Split
This isn’t theoretical. AI is already eating the admin-heavy parts of both jobs—drafting requirements, documenting decisions, flagging conflicts, prepping status updates.
That doesn’t make PMs or BAs obsolete. But it does mean both roles require less time to execute well. Which means more leaders will ask: if the tools can do 30–40% of both jobs, why can’t one person do the rest? That’s not an attack—it’s an inevitable design question. And the sooner we answer it with intention, the better.
What Does This All Mean for PMs?
If you’re a PM right now, this debate isn’t just theoretical. It’s about your future—and how you grow in a world where job boundaries are blurring, not solidifying.
The takeaway isn’t that you must become a hybrid. It’s that you need to understand how business analysis works—deeply enough to recognize when it’s missing, when it’s weak, and when your project’s success depends on it.
That doesn’t mean going back to school. It might mean asking better questions. Shadowing a BA. Practicing requirements elicitation in your next kickoff. Expanding your toolkit—not to replace someone else’s job, but to make your own more effective.
Because here’s the truth: as tools absorb the mechanical parts of the PM role, the value shifts to the human parts—connecting the dots, resolving ambiguity, translating what the business needs into something a team can deliver. Those aren’t skills any one role owns. But they’re the ones PMs need most to stay relevant, resilient, and trusted.
If You Only Do One Thing
Pair up your PMs and BAs—and get them in each other’s heads.
Have them shadow each other for one meeting. Afterward, ask: What did you notice? What did you track that I missed? What could we have made easier for each other?
Then swap roles. New meeting, new observer.
This isn’t about merging responsibilities. It’s about growing thinking range. The more your team understands how adjacent roles approach the work—their questions, instincts, blind spots—the easier it becomes to flex and collaborate when the model inevitably shifts.
You don’t need to reorg to prepare for change. You just need to create the conditions where shared fluency can grow.