Most PM advice assumes you're starting clean. New role, new team, fresh mandate, tidy process. Most PMs don't get that. They inherit projects, set up by someone else, running under unclear governance, with workstreams whose history nobody fully remembers.
In those projects, the role expands silently. Whatever's missing in the operating model (project management, business analysis, solution design, spec writing) quietly gets absorbed into the PM brief. The job description didn't change. The job did.
1 · The absorption pattern
Most often three roles collapse into one: product manager, project manager, business analyst or solution lead. Each absorbs work that should sit elsewhere.
The symptoms are recognisable:
- Working evenings or weekends on documentation that should have been someone else's deliverable.
- Explaining the same context to the same people, repeatedly, because nobody is logging decisions.
- Doing the thinking for tasks that should have owners.
- Being the only person who can answer questions about scope, schedule, and spec.
The most diagnostic question is the one that usually doesn't get asked: when your week runs out of hours, which part of the job actually gets dropped?
A mentee I work with answered that honestly the other week: 70% PM, 30% BA. The BA work is the part that gets skipped under pressure. That's not a healthy role split. It's a role with a hidden gap, and the gap is being filled silently.
2 · Where the gap is hiding
PM output is visible to leadership. Roadmaps, status updates, stakeholder communications all surface upwards.
BA work usually doesn't. Requirements, edge cases, specification quality, fitness-for-purpose checks only become visible when they fail.
So when capacity runs out, BA work gets sacrificed first. PM output keeps flowing. The org sees a PM on top of things. The cost lands later, as requirements stay implicit, scope drifts in implementation, and coordination quietly degrades.
The PM looks fine right up until they don't.
3 · Making the absorption visible
The fix isn't more hours. Most PMs in this pattern have already tried more hours.
The fix is producing the artefacts that make the absorption visible, and therefore negotiable. Same principle as PM as governance system: your leverage isn't doing more work; it's making the work legible enough that the org can coordinate around it.
A small number of artefacts do most of the work here:
- A RACI matrix forces the ownership questions that role-blur left implicit (covered in multi-team coordination).
- A decision log captures what's been agreed and stops re-litigation eating hours.
- A risk log surfaces what's being absorbed silently and gives leadership somewhere to push back if they want to.
None of this is bureaucracy. It's the mechanism that turns "the PM is doing too much" from a personal complaint into a structural conversation.
4 · When to name it (and when not to)
Naming the absorption to your manager works when you have artefacts that make the case. Without artefacts, "I'm doing too much" sounds like a complaint. With artefacts that lay out what falls under PM, what falls under project management, and what's currently unowned, it becomes a structural conversation about how the project is staffed.
Timing matters too. Naming the role-blur in the middle of a high-stakes delivery moment lands badly. Naming it at the start of a new quarter, or after a milestone, lands better. The artefacts are the same; the audience for them is different.
- Trying to fix it by working harder. Role-blur isn't a personal performance gap. Working harder absorbs more of it silently and makes the structural problem harder to surface.
- Treating it as a personal grievance. "I'm being asked to do too much" is weaker than "here's the structural absorption pattern in this project". The first invites an HR conversation that doesn't solve anything. The second invites a fix.
- Waiting for leadership to notice. They usually can't see it from where they sit. The absorption is the thing that makes everything look fine from above.
- Assuming you'll catch up next week. Catching up requires the artefacts. The artefacts require time. Without protecting time for them, the absorption compounds.