About this block

Prioritization Criteria lays out the four questions every candidate roadmap item must answer. A centered header and lede sit above a two by two grid of criteria cards, evidence over enthusiasm, strategic fit, honest effort, and reversibility. Each card states the test in plain language, then shows a nested example box with a passed or failed verdict chip and a real item that met or missed the bar.

The criteria are one array of title, test, and an example with a passed flag that tints the verdict chip. Pairing every abstract test with a concrete accepted or declined item is the credibility device, a framework that names the CRM it turned down at 300 votes reads as a real filter, not a values slide. The closing line, that every no is written down, keeps the process accountable.

When to use

Reach for this block when buyers or your own team ask how the roadmap gets decided, and votes alone are not the answer you want to give. It turns prioritization from a black box into a published rubric, which builds trust with enterprise buyers who need to know a feature request has a real path. It pairs well with a voting board as the step that happens after an idea gets into the room.

A natural flow around it on a Marketing Pro page:

Before

• Roadmap board showing the items these criteria already sorted

After

• Feature request sections inviting ideas that will face the same tests
• Contact for buyers with a specific ask

What you can display

One strong use is the product prioritization rubric. Other frameworks:

• Partner criteria. The bar a tool must clear to join the ecosystem.
• Content standards. The questions an editorial pitch must answer for a media brand.
• Investment thesis. The filters a fund applies, each with a deal it took or passed.

Tip: use real passed and failed examples, a rubric with no declined item reads as decoration, not a filter.