Prioritisation as Capital Allocation

Trigger

“Prioritization frameworks are just opinion laundering” — Jay Stansell, Product Coalition (Apr 2026). The closing argument reframes prioritisation from feature-ranking to capital allocation.

---

The Thought

Most prioritisation frameworks optimise for the go decision. RICE, ICE, MoSCoW — they help you pick what to build next, but they don’t account for what you’re taking on after you ship. Every feature adds maintenance burden, security surface, and complexity that compounds quietly.

The capital allocation reframe makes the full cost visible: expected return, risk profile, and maintenance cost that extends years past launch. That’s a different conversation than “what has the highest impact-to-effort ratio.” It forces you to think about what it costs to be wrong, not just what you stand to gain if you’re right.

---

What lands / What I’d complicate

The reframe is right directionally. Where I’d complicate it: “capital allocation” is a frame you need to earn the right to use. If the PM doesn’t hold the budget or isn’t seen as a strategic voice, framing roadmap decisions as capital allocation can land as overreach. The more useful question might be: does this framing change how you think about the roadmap even if you can’t say it out loud in the room?

---

Possible connection

Could seed a node on what a PM is actually doing when they prioritise — not frameworks, but the underlying act. Possible link to operating modes work if the mode shapes what “good prioritisation” looks like in that context.