How to get deliverables from teams you don't manage
In a matrix organization, your progress depends on teams that have their own managers and priorities. Getting the necessary resources requires constant haggling and begging, and communicating the resulting delays is often dismissed as finger-pointing. Because these other departments don't suffer the consequences of a messy launch, project managers become exhausted human shock absorbers just trying to get things done.
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.
- 1Endlessly escalating issues to upper management and screaming into the void via reports.Did this help you?
- 2Carefully wording status updates and risk communications to avoid the optics of assigning blame.Did this help you?
- 3Accepting that dealing with politics is the entire job rather than actual project execution.Did this help you?
- 4Leaving the company to escape the personal toll of being a human shock absorber.Did this help you?
- 5Escalating priority conflicts directly to the intersecting management chain of both teams.Did this help you?
- 6Treating cross-team dependencies as formal commitments with a named owner and delivery date.Did this help you?
- 7Creating a single intake queue with visible weekly capacity for shared specialists.Did this help you?
- 8Having all teams expose their sprint goals publicly to forecast clashes.Did this help you?
- 9Establishing formal working groups with representatives from each business area to review schedules.Did 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.
“It's exhausting. All I want is to simply get stuff done and manage my team doing their work. Instead I'm constantly busy haggling with other departments, fighting for visibility or escalating to upper management because risk is not being taken seriously.”source ↗
“me communicating risks and delays for my project has been called "finger pointing" or is simply brushed off because not part of product launch KPIs”source ↗
“When your work depends on another team, your progress partly depends on decisions you do not control. They have their own manager and priorities.”source ↗
“This is depressingly common in matrix orgs where service teams are treated as an afterthought rather than actual stakeholders. The "free resources" line hit close to home, nothing like having another PM treat your team as spare capacity they can just absorb whenever convenient.”source ↗
“I've had a job like this, stayed about 3 years, and it took a massive personal toll on me. Google "human shock absorber." I'm a high achiever and after years of "stakeholder managing" without meaningful change, I started to lose it.”source ↗
“The root of the problem is that the product team is not going to suffer the consequences of the mess they are launching, my team is.”source ↗
“i’m a matrix pm and sometimes people don’t like the optics of communicating risks and issues - and yes, i have to be careful about how i word them to not assign blame.”source ↗
“At my current company (well, I just resigned) we might launch a UX A/B test for an important page, like a Contact Experts hub (e.g. where you go to use or purchase a number of services), in a quarter. We will test maybe three or four variations of this page. That test will take a quarter to go live, then another few weeks to bake, and we'll have a full turnaround in 4-5 months.”source ↗
“My company is exactly like this, and I work on the services side as well. It's obviously not normal or ideal, but it's exactly what I've been dealing with. As far as I know, at my company, the job of PMO is primarily to deal with these politics so the teams don't have to. Honestly, I don't even do much else.”source ↗
“The amount of time I prep Ressource deployment with other departments and then have to renegotiate, hassle and beg because something went wrong somewhere on the other and those ressources necessary for my project are not available....I do not want to think about it. Ist's how it is.”source ↗
“The cross-functional idea sounds nice in theory but I've seen it fall apart when that one database person gets stretched thin anyway because suddenly every team needs them at same week. At that point you're back to negotiating priorities, just with extra steps.”source ↗
Where this came up
People with this problem also raised
- 2Why is my entire day eaten up by meetings and micromanagement?
- 8How to survive a completely mismanaged project with terrible leadership
- 5How to delegate tasks without micromanaging
- 2How to limit project visibility to assigned resources
- 12How do you keep track of clients, projects, deadlines, and follow-ups?
- 43How to deal with uncooperative coworkers who don't do their work