Stack Ranking

Use stack ranking to give planned initiatives an explicit priority order.

Eligibility

Only initiatives with Planned status are eligible for stack ranking. Parent initiatives with at least one planned child are excluded until the child work is completed or moved out of Planned. This keeps the ranking focused on the work that can actually be compared now.

How ranking works

Each eligible initiative has a numeric rank. Lower numbers indicate higher priority. Drag an initiative by its handle to reorder it; the surrounding ranks adjust automatically.

Use stack ranking when the team has several planned initiatives and needs a visible answer to: what comes first?

What to check before ranking

Make sure each initiative has a clear title, useful description, owner, team, and taxonomy. Ranking works best when the items being compared are already well defined.

Use the same filters and column controls as the roadmap table to focus the ranking session. Filter by team, product, goal, or owner when one large workspace has several independent priority conversations.

Stack ranking is most useful after initiatives are defined; see Initiatives for the underlying roadmap record.