Two Stakeholders, One Quarter of Capacity: A PM's Real Conversation with Pictor
Every PM knows this one. Two stakeholders, two features, one quarter of engineering capacity — and no clean way to decide who wins.
Usually it gets resolved by whoever has the loudest voice, the most senior title, or the most persistence in follow-up meetings. Not exactly a business decision. So we asked Pictor for help with exactly this, and kept the conversation as it happened.
The Conversation
Me: Hey Pictor! I am a Product Manager and I have two stakeholders pushing for different features and only enough engineering capacity for one this quarter. Any ideas how to deal with this situation?
Pictor: Classic prioritization conflict. A few questions before I suggest anything useful: What does your organization use for prioritization right now — is there an existing framework, a roadmap process, or is it largely whoever pushes hardest wins? And do you know enough about the business value of each feature to make a case either way, or is that part of the problem?
Me: honestly we do not have sth concrete... or to be more specific any criteria that we use to prioritise...and about business value.. I think its more opinions...
Pictor: That's actually the core of the problem — and it's very common. Without shared criteria, every prioritization conversation becomes a political negotiation rather than a business decision. The stakeholders aren't really fighting over features; they're fighting because there's no agreed-upon way to settle the question.
One approach worth knowing about is WSJF — Weighted Shortest Job First — from SAFe (Dean Leffingwell, Scaled Agile Framework, 2011). You score each feature across business value, time criticality, risk reduction, and effort. The score creates a ranking that's defensible because everyone agreed to the criteria before any specific feature was on the table.
A simpler starting point: get both stakeholders in the same room and ask them to answer two questions for each feature — what problem does this solve for the business, and what happens if we delay it by a quarter? You'd be surprised how often that surfaces that one of the features doesn't have a strong answer to either question.
Me: I've heard about wsjf in the past... feels quite heavy now.. other options to start with?
Pictor: Good instinct — start lighter. Two options worth considering:
Impact vs. Effort (common lean/product thinking, no single definitive source) — score each feature on two dimensions only: business impact and effort. Anything high impact, low effort goes first. Simple, and it gets stakeholders talking about the same dimensions instead of just advocating for their own feature.
Opportunity Scoring (Ulwick, What Customers Want, 2005) — rate each feature on importance and current satisfaction with how that need is met today. Features that are important but poorly served are your highest opportunity.
Both work best facilitated together, not separately — separate conversations let each stakeholder optimize for their own feature.
Me: I will go for impact vs effort
Pictor: Good choice. A few things that will make it work in practice:
Define "impact" before you score — the most common failure mode is each stakeholder scoring impact relative to their own goals. Agree upfront what impact means here.
Score independently first, then compare — if one person anchors the group, everyone else adjusts to them instead of thinking independently.
The conversation after scoring is where the value is. If scores differ significantly, that gap is the useful signal — surface it, don't just average the numbers.
Me: I'll plan it for next week to go through the method and agree how to use it... would that be a good plan?
Pictor: Yes, that's solid. One suggestion: send both stakeholders a brief note before the meeting explaining what you're doing and why — something like "we're going to use a simple framework to make this decision together based on agreed criteria." That way they arrive expecting a structured conversation, not another negotiation.
What Actually Happened Here
Notice what Pictor never did: it never picked a winner between the two features. That was never the actual problem.
The real gap was that there was no shared way to decide — so it walked toward that, not toward "feature A vs. feature B." When the first suggestion (WSJF) felt too heavy, it didn't insist or repeat itself — it offered two lighter alternatives, one of them honestly flagged as having no formal source rather than being dressed up with a citation it didn't have. Once a method was chosen, the value shifted from "which framework" to "how do you avoid the framework becoming theater" — the tips about scoring independently before comparing, and treating disagreement as signal instead of noise to average away, are the kind of thing that separates a framework that works from one that becomes another meeting people tune out of.
By the end: a specific method, a session on the calendar for next week, and a plan for how to frame it so it doesn't just become another negotiation.
If you're staring down a stakeholder standoff with no criteria to fall back on, this is what working through it with Pictor looks like.
Questions about prioritization frameworks or how to run a session like this? Reach us at info@yourpaths.eu — or just ask Pictor directly.