Strategy driven priorities

Most teams treat prioritization as backlog grooming: clean the list, estimate a bit more carefully, move a few epics up, and call it done. That makes the backlog readable — it does not decide what should win. Feature scoring has the same gap: you can rate every epic on value and effort and still rank by negotiation skill instead of the outcome the business said it wanted this quarter.

Strategy driven priorities start from a different question: given the strategy we are pursuing right now, which Jira issues move that strategy forward fastest? Discovery, Market Penetration, and Growth will each pick a different winner — and the ranking should change when the strategy changes, not when the loudest stakeholder walks in.

A strategy is a choice of emphasis. Categories make that choice measurable — marketing impact, sales enablement, conversion, strategic differentiation, technical leverage, and whatever else your product cares about. Weights are how the active strategy says how much each category matters right now.

Change the strategy and the weights shift; change the weights and the ranking shifts. The backlog does not get a new speech — it gets a new objective order.

Scoring issues against those categories turns preference into a model the room can inspect. Write the result back with Jira Rank and PTIAS labels so "what is next" lives where teams already work — not in a workshop slide nobody opens afterward.

PI Planning is where that ranked work meets capacity. If the walk-in is still an unordered pile, the room invents priorities under time pressure. If it is already ordered by strategy, facilitators can stay on sprint load, dependencies, and commitment — executing strategy instead of rediscovering it.

Define strategies, set category weights, score Jira issues, and save Rank and PTIAS labels in Prioritizer: https://www.ptias.com/prioritizer

Then open that strategy-ranked backlog on the PTIAS PI Planning Board — capacity visible, Jira in sync: https://www.ptias.com/pi-planning