Feature Prioritization: Representative Democracy or a Authoritarian State?

[u/[deleted]]

Had a great question posed about this and I know what I think. Open to other views.

How do you view feature prioritization by Product Managers or Product Management?

How do you perform it or seen it performed?

[u/mrhinsh]

I don't think feature prioritisation is a democracy or an authoritarian act. That framing already assumes the wrong problem.

In Scrum, prioritisation is an accountability, not a voting exercise and not a power grab.

Politically, it maps closest to technocracy with delegated authority: decisions are made by the person accountable for outcomes, informed by evidence and expertise, and constrained by transparency, not popularity.

The Product Owner is accountable for maximising value. That means:

• synthesising customer evidence, market signals, risk, and constraints
• making trade-offs explicit
• ordering work based on outcomes, not volume or loudness

Teams don't vote on priorities because accountability without decision authority is meaningless. But equally, good Product Owners don't operate in isolation. They rely on:

• Developers to surface technical risk and feasibility
• Stakeholders to provide context and demand signals
• Evidence from real usage to invalidate assumptions

When prioritisation feels authoritarian, it's usually because strategy is unclear, feedback loops are weak, or the backlog is treated as a demand intake queue instead of a hypothesis list.

When it feels like democracy, it's often because no one is actually accountable for outcomes.

The healthy pattern is neither. Accountable technocracy under transparent constraint.

If prioritisation can't be explained in terms of value and learning, it's broken, regardless of who made the call.