The Laundering Defence — Frameworks as Cover for Opaque Stakeholder Intent
Trigger
“Prioritization frameworks are just opinion laundering” — Jay Stansell, Product Coalition (Apr 2026). The “opinion laundering” framing. My instinct was to push back, not because the critique is wrong, but because it’s incomplete.
The Thought
The laundering critique assumes the PM knows why a stakeholder is pushing something and chooses to dress it up anyway. But that’s not always what’s happening. Sometimes the PM genuinely doesn’t have visibility into the reason — business constraints, partnership commitments, regulatory pressure, things that can’t be surfaced in an open roadmap discussion.
In that case, running a framework isn’t just providing cover. It’s buying time and legitimacy for the real work: finding out what’s behind the push. The framework creates a space where the PM can do the digging without the conversation collapsing into a power struggle.
This also reflects something the article undersells — PMs aren’t just accountable to users. They’re sitting at the intersection of user needs, business priorities, and internal constraints that often aren’t transparent. Part of the job is figuring out why something is being pushed, not just whether it scores well on RICE.
What lands / What I’d complicate
This defence has a clear failure mode. If the PM finds out the reason and it isn’t strategically sound, and still ships it anyway dressed in a framework score — that’s laundering. The defence only holds if the PM actually does the digging and acts on what they find. The framework as tool is different from the framework as alibi.
Possible connection
Links to the operating modes writing — the “navigating opaque stakeholder intent” dimension wasn’t directly addressed in the articles. Could also inform a future node on PM as internal translator vs. internal advocate.