A prioritization brief explains a proposed work order using evidence, dependencies and capacity, with deferred work and the decision owner made explicit.
You review the facts and access. Nothing is published without your approval.
The method behind the prioritization briefAsk your agent for an evidence-led proposed order, not invented scoring or an implied staffing commitment.
How can an AI agent help explain product priorities?
Give your agent the candidate work, supporting evidence, dependencies and real capacity constraints. Ask for a proposed order with a reason for each choice, explicit deferred work and questions that could change the recommendation. Let the decision owner approve priorities in your existing planning process.
What to give your agent
Candidate work and the goal it supports.
Dated customer observations or other authorized evidence; distinguish requests from validated needs.
Supplied effort estimates, capacity constraints and prerequisite work.
Decision owner, current commitments and conditions for revisiting the order.
Agree what the order should optimize
Name the outcome and constraints before discussing attractive features. A fixed deadline, a prerequisite and a preference are different kinds of input. Ask for missing constraints rather than creating numerical weights that make the choice look objective.
Put evidence beside each candidate
Keep the source and its limits visible. Several support notes may justify investigating a problem without proving how many customers have it. Separate evidence of a problem from confidence that a proposed solution will fix it.
Check what each choice displaces
Show effort as an estimate, identify prerequisite work, and name what will wait if this item comes first. Do not confuse a high-value idea with work that is ready to begin. Never count uncertain availability as committed capacity.
Share a recommendation, not a silent roadmap change
Lead the HTML brief with proposed order and rationale, then evidence, dependencies and deferred items. Include the decision still needed and a supplied review trigger. Record approval and scheduling in the planning tool; a readable page does not allocate people.
Create a prioritization brief from only my supplied or authorized candidate work, evidence, dependencies and capacity constraints. Ask for missing essentials. Separate problem evidence from solution confidence; preserve estimate units and uncertainty. Show a proposed order, what each choice displaces, prerequisite work, deferred items and conditions that could change the order. Do not invent scores, weights, customer prevalence, staffing, dates or approved commitments. Use static HTML with no scripts or forms and my saved style if available. Show the draft and unresolved questions. Keep priority approval and scheduling in our existing planning workflow. Do not publish or change access without separate explicit approval.
Check before you shareAccuracy, clarity, and permission
Does each priority connect to a supplied goal and evidence?
Are dependencies and capacity constraints visible?
Are estimates distinct from booked resources?
Does the reader see deferred work and the decision owner?
When HTML fits
A dated explanation stakeholders can read before a planning discussion, with detail below a short proposed order.
When another format fits better
Use the backlog or planning system to assign work and maintain live priorities. A brief does not optimize capacity automatically or replace the accountable decision-maker.
What we started withThe same facts, as a wiki page
Fictional team wiki
Alder Reports — proposed priority for this cycle
Goal and capacity
Prepared September 7, 2026, by Rowan for Priya. Goal: make report labels easier to understand. Priya allows capacity for one small improvement this cycle; no end date, approved choice or schedule is supplied.
Candidates
A: revise the glossary, estimated by Rowan at two editor days. Twelve selected support notes mention confusing labels, but they are not representative or a unique-customer count. No revision result is measured. B: custom report labels, estimated by the delivery team at five developer days. Developer availability is unknown, and consistent meanings require a settled glossary first. C: color refresh, estimated at one designer day, with no supplied evidence connecting color to label understanding.
Proposed order
Rowan proposes glossary first, custom labels after definitions and developer availability are settled, and deferring the color refresh for lack of problem evidence. Priya must decide; this proposal reserves no staff and authorizes no work. Effort across roles is not interchangeable, and no numerical weights or scores are agreed.
Revisit conditions
Revisit if evidence or capacity changes. Actual priorities and dates belong in the existing planning board; this snapshot does not update it.
Inspect the HTMLOne self-contained file
The example is sanitized and isolated from this site. No scripts, forms, or live data.
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Alder Reports · Priority proposal</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f5f8fc;color:#182e46;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#23486b;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Alder Reports / September 7, 2026 / Fictional planning brief</p><h1>Fix the meanings before adding more labels.</h1><p class="intro">One small improvement fits this cycle. Rowan proposes the glossary revision; Priya still needs to decide.</p></header><aside class="lead"><h2>Proposed first: the glossary.</h2><p>Two editor days estimated. Twelve selected support notes mention confusing labels. No choice is approved or scheduled.</p></aside><section><h2>Three candidates, different reasons to wait</h2><div class="grid"><article class="card"><h3>Glossary revision</h3><p>Directly addresses the supplied label-confusion evidence. A beneficial result has not yet been measured.</p></article><article class="card"><h3>Custom labels</h3><p>Five developer days estimated. Needs a settled glossary first; developer availability is unknown. Defer until both are resolved.</p></article><article class="card"><h3>Color refresh</h3><p>One designer day estimated. No supplied evidence connects it to label understanding. Proposed deferral.</p></article></div></section><section class="warning"><h2>What the evidence does not tell us</h2><p>Twelve notes are not a representative sample or a count of unique affected customers. The estimates use different roles and cannot be treated as interchangeable capacity. No scoring weights are agreed.</p></section><section><h2>The decision belongs in planning</h2><p>Priya must approve the priority through the existing planning board. This proposal reserves no staff and gives no delivery date. Revisit if new problem evidence or changed capacity is supplied.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>
The original worked scenarioThe source scenario, step by step
The prerequisite comes before the attractive feature
Fictional reporting-team planning notes; no priority has been approved.
The original notes
Capacity allows one small improvement this cycle. Twelve supplied support notes mention confusing report labels; that is not a customer prevalence estimate. A glossary revision is estimated at two editor days. Custom labels need a settled glossary and are estimated at five developer days; developer availability is unknown. A color refresh takes one designer day but has no supplied problem evidence. Recommend the glossary first, defer custom labels until definitions and capacity are confirmed, and defer the color refresh. Priya must decide; nothing is scheduled.
Proposed first
Glossary revision: two editor days estimated; twelve support notes indicate label confusion, not customer prevalence.
Dependency
Custom labels need a settled glossary; five developer days estimated and developer availability unknown.
Deferred
Color refresh: one designer day, but no supplied problem evidence.
Decision
Priya must decide within capacity for one small improvement. Nothing is scheduled.
The order follows evidence and readiness, not a made-up composite score.
Questions, adaptations & sourcesGo deeper when you need to
Do I need a scoring framework?
No. A clear rationale can be more honest than an unsupported score. If your team supplies a validated scoring method, preserve its inputs and uncertainty instead of inventing weights.
What if the evidence is weak?
Say what is missing and consider a bounded investigation if that is an actual option. Do not turn a request into proof of widespread demand.
Is the first item now committed?
Only if the authorized decision process says so. Label a recommendation as proposed and leave dates unconfirmed until agreed.