Feature Priority Engine — Decide What to Build Next

Outcome: Reliable checkout. No capacity, impact counts or effort estimates supplied.

A — Checkout error fix: Evidence state documented problem, but frequency, severity, affected users and root cause are unknown. Provisional state: Needs estimate and impact validation; assess whether it meets an urgent reliability or contractual obligation. Do not fabricate a priority score.

B — Dashboard redesign: Evidence of one request, not proof that the proposed solution solves a customer problem. Provisional state: Needs discovery. Clarify user job, current pain and connection to strategic outcomes.

Sequence proposal: Investigate the checkout defect first because it directly relates to the supplied outcome; this is a provisional judgment, not a committed delivery order. Mandatory risk findings could change urgency.

Evidence plan: A—reproduce issue, measure actual scope, assess workaround and obtain engineering range. B—validate problem with legitimate user evidence and explore smaller solutions.

Capacity and dependencies: Confirm available team capacity, existing commitments, technical dependencies and operational readiness before scheduling. Unknown values stay unknown.

Decision log: A advanced to investigation; B held for discovery; rationale is outcome alignment and evidence difference. Owner approval, review date and commitments remain pending.

Review triggers: New impact evidence, confirmed mandatory risk, estimates or changed strategy.

Execution: Prioritization brief only. No tickets changed, roadmap committed, score invented or delivery guaranteed.