Prioritization Starts Before the Meeting
Using criteria to decide what actually moves forward
Visibility drives selection
In product and operations planning, everything is already on the table. Requests, bugs, stakeholder asks, you name it… along with a deadline that is starting to slip. Most of the time, the problem comes down to deciding what actually deserves attention now. It can be really tempting for a team to chase the sudden urgency of whatever is the loudest, or most recent, or whatever is easiest to talk about. And the pattern is simple. Visibility drives selection. Having everything visible and vying for attention at once turns prioritization into reshuffling the same list instead of making real decisions. This can cause important work to be delayed while low-impact work keeps resurfacing in the shuffle. It stays visible, so it keeps getting picked. The list may not even get better, just rearranged.
Define what qualifies first
But when indicators are defined for impact, urgency, and consequence, decisions stop being driven by what is most visible and start being guided by what actually matters. How those indicators are defined will vary by team, but the key is that they are defined before the planning session, not during it.
A simple starting point: before your next planning session, write down three questions your team will use to filter the list. Something like: Does this affect a core workflow or a customer commitment? Does it need to be resolved before something else can move? What happens if it waits another cycle? The exact questions matter less than the fact that everyone is working from the same ones.
Visibility becomes structured, and the reason something is prioritized is clear before the planning session even begins. This is a form of criteria-based prioritization. No complex system, just clear criteria set ahead of time. The discussion focuses on a filtered set, instead of reshuffling everything that happens to be visible.
Without it, the planning session becomes the point of prioritization. With it, the planning session becomes the confirmation step. Same meeting, different outcome. This shifts the work from debating items in the room to defining what qualifies before anything enters the room.
Getting the team to trust the criteria
The harder part is not defining the criteria. It is getting the team to trust them.
When a team is used to debating everything in the room, moving that filtering work upstream can feel like decisions are being made without them. The first few times you try this, someone will usually push back on something that did not make the filtered list. That is not a sign the approach is broken, it is a sign the criteria need a conversation, not just documentation.
Walking through the criteria together once, before anyone applies them, goes a long way. So does being explicit that the filter is a starting point, not a verdict. When the team helps shape the questions, they are much more likely to trust what comes out of them.
Keep the filter visible
Transparency that criteria has already been used to filter what is being reviewed is helpful. It helps clarify that the other items were considered even if they are not part of the immediate discussion, and prevents the assumption that they were missed or ignored.
One way to do this in practice: keep a simple “considered but not this cycle” section visible in whatever tool or doc your team uses for planning. It doesn’t need a lot of detail, just enough to show the item exists and was evaluated. That small move tends to reduce the re-litigation that happens when people assume things fell through the cracks.
Leave space at the end to surface anything that may have been missed or has changed in priority. It keeps things flexible without reopening everything. That keeps the process responsive without letting the planning session get pulled off track.
One of several approaches
Criteria-based prioritization is one way to bring structure to a noisy list, and it doesn’t require a scoring model or a new tool to get started. Three agreed-upon questions, applied before the meeting, can shift the whole dynamic from reshuffling to deciding.
Other teams may reach the same goal of structured prioritization through frameworks like WSJF (Weighted Shortest Job First), RICE (Reach, Impact, Confidence, Effort), MoSCoW (Must have, Should have, Could have, Won't have), or impact vs effort matrices; each just a different way of filtering what moves forward. The right choice depends on team size, planning cadence, and how much structure the work itself demands.
What tends to matter most is not which method you use, but whether the criteria exist before the room fills up.
Which approach do you rely on most when everything is competing for attention?