Stack Ranking

What is Stack Ranking?

Stack ranking is putting a set of items in a single order from most to least important, with no ties. In planning it is used to prioritize work; in HR the same term describes ranking employees against each other.

Updated November 2026 · 2 min read


Stack ranking in prioritization

In product and portfolio planning, a stack rank is one ordered list: item 1 matters more than item 2, which matters more than item 3, and so on. Ties are not allowed. That constraint is the point. Many prioritization methods produce scores where several items come out "high"; a stack rank forces a choice between them. Combined with a cut line, it shows exactly which work gets funded.

MethodOutputAllows ties?
Stack rankingA single ordered listNo
MoSCoWFour buckets: must, should, could, won'tYes
Weighted scoring modelA score per itemYes, often
WSJFA score that can be sorted into a rankRarely, but possible

How to build a stack rank

  1. Agree the criteria first, such as value, urgency, risk reduction and strategic fit
  2. Score or discuss items against those criteria to get a rough order
  3. Compare neighbors in pairs: "if we could only do one of these two, which?"
  4. Resolve every tie with a decision, not by averaging
  5. Publish the list and revisit it each planning cycle

An example

A product leader has 14 features marked "high priority" by different teams. Instead of debating labels, she asks the leads to build one stack rank in a two-hour session. Pairwise comparison quickly separates the top four, which all support the year's retention goal. The rest fall into place behind them. With capacity for six features, items 7 to 14 go below the line, and the teams leave knowing what they will and will not build.

Stack ranks and opportunity cost

Every position in a stack rank carries a hidden cost: whatever sits just below it. Moving an item up one place means moving another down. That makes opportunity cost visible in a way that scores and labels do not. Many teams find the conversation about two neighboring items more useful than the final list itself, because it brings out assumptions about value that were never written down.

Stack ranking employees

The same term has a second, more controversial meaning. In performance management, stack ranking (also called forced ranking) means ranking employees against each other and assigning set shares to top, middle and bottom groups. GE popularized the approach under Jack Welch with its "vitality curve." Microsoft dropped its version in 2013, and many companies have since moved away from it, citing harm to collaboration and morale. This entry focuses on prioritizing work; if you are reading about performance reviews, it is the HR meaning that applies.

Common pitfalls

  • Ranking items of very different sizes without considering cost; a high-value but huge item may deserve to sit below several smaller ones
  • Treating the rank as permanent instead of reviewing it as conditions change
  • Letting each team keep its own rank; the value comes from one list across the portfolio
  • Spending hours on precise positions far below the cut line, where order matters little

Frequently asked questions

What is stack ranking in product management?

It is putting features, epics or initiatives in a single ordered list from most to least important, with no ties allowed. Product teams use it to make trade-offs explicit and to decide what to build first when capacity is limited. It is often paired with a cut line showing what fits in the available capacity.

Is stack ranking the same as forced ranking?

In HR, yes: both describe ranking employees against each other and placing set shares into performance groups. In planning, stack ranking means ordering work, not people, and has nothing to do with performance reviews. The shared name causes confusion, so it helps to say which meaning you intend.

Why do teams use stack ranking instead of priority labels?

Labels such as "high" or "P1" let many items share the same priority, which pushes the real decision downstream to the people doing the work. A stack rank forces leaders to choose. It works well with WSJF or scoring models, which produce a first order that leaders then adjust and confirm.