Goals & Scoring

Goals give portfolio work a “why”; scoring and prioritization decide what gets worked on first. All three sit on top of the same plan items the Roadmap visualizes.

Goals & Targets

A goal can nest under a parent goal, forming a hierarchy that rolls progress upward. Each goal owns one or more measurable targets.

Goal state	Typical next action
Draft	Activate
Active	Mark Achieved, Mark Missed, or Cancel
Achieved / Missed / Cancelled	Reopen

A target measures progress toward a goal as Maximize (percent complete = actual-vs-base progress toward a higher target), Minimize (progress toward a lower target), or Milestone (100% once reached or marked complete). Each target has its own state:

Target state	Typical next action
Draft	Activate
Active	Complete, or Cancel
Complete / Cancelled	Reopen

A target’s check-in frequency (Daily through Yearly) drives a recurring Planned-vs-Actual grid: each period is logged as a check-in record (Submitted, with a Revise action to correct it), and a goal’s overall percent complete is the weight-weighted average of its targets’ progress.

Scoring

Scoring is framework-driven and lives on the Portfolio Plan: each plan picks one of three frameworks, and every plan item scored under that plan is judged by the same formula.

Framework	Formula	Factors
WSJF	(Business value + Time criticality + Risk reduction) ÷ Job size	User business value, time criticality, risk reduction / opportunity enablement, job size
RICE	(Reach × Impact × Confidence%) ÷ Effort	Reach, impact, confidence (0–100%), effort
Value vs Effort	Value ÷ Effort	Value, effort

A score is never stored directly — it’s always computed from the underlying factor values, so changing a factor immediately re-ranks the grid. Value vs Effort additionally classifies each item into a quadrant — Quick Win (high value, low effort), Big Bet (high value, high effort), Fill In (low value, low effort), or Money Pit (low value, high effort).

Prioritization

Independent of the scoring formula, every plan item also carries a MoSCoW classification (Must have, Should have, Could have, Won’t have) and a manual rank. The Prioritization list is drag-rankable — dropping an item into a new position renumbers every item’s rank to stay dense and contiguous. The Prioritization Kanban board columns are the plan item’s lifecycle state (Draft through Done), with swimlanes by priority (Critical/High/Moderate/Low) — an item with no priority set lands in the Low lane rather than being hidden.