A portfolio of bets
kept honest

Intake, scoring, capacity, gates and value tracking operated as one program. The portfolio of work stays legible to the board, engineering stops being the bottleneck that kills bets silently and outcomes get measured against the hypothesis that funded them.

Portfolio topology: intake, stage-gate lanes, bets moving through discovery, delivery, launch and scale portfolio.graph bets 24 / wk 16 intake · discover · deliver · launch · scale Intake Discover Deliver Launch Scale · run Bet 12 Bet 04 · killed Bet 11 Bet 07 · hot Bet 09 Bet 15 Bet 02 Bet 01 · live Bet 03 · live

CAPABILITIES

Six portfolio surfaces under one governance body

Intake, capacity, gates, value tracking, investment shape and exec reporting — wired together so bets are accepted, measured and retired in the open.

01

Portfolio intake

Single pipeline across business units, scoring rubric, bias-aware ranking, duplicate detection, killed-bet graveyard.

02

Capacity planning

Team capacity modelled in weeks, commitment vs. buffer, key-person risk, vendor mix, quarter-by-quarter reshuffles.

03

Stage-gate governance

Discovery → delivery → launch → scale with kill / scale / pivot decisions at each gate, signed by accountable owners.

04

Value tracking

Hypothesis → expected outcome → actual outcome; honest post-mortems; lessons fed back into the scoring rubric.

05

Investment shape

Horizon 1 / 2 / 3 balance, run / grow / transform mix, tech-debt allocation, discretionary vs. committed ratios.

06

Executive reporting

Single dashboard for board and ExCo with bets, status, spend, expected return and confidence band — no slide deck.

SCORING RUBRIC

A scoring rubric with weighted dimensions

The default weighting we use to rank incoming bets. Numbers land in a single spreadsheet column each quarter, debated openly, and the losers go into the killed-bet graveyard with a named reason.

DimensionWeightRubric
Strategic fit25%Alignment with the top 3 strategic bets for the year
Value (conf. banded)25%Expected benefit × confidence, not max-case "hockey-stick"
Cost to value20%Engineering + ops + ongoing run cost vs. value
Risk (tech + market)15%Shared dependency, novel tech, regulatory exposure, lock-in
Time to first signal10%How quickly we learn if the bet is working — short is better
Reversibility5%One-way doors weighed against two-way doors
Kill it or scale it

A portfolio without kills is a backlog with a budget line. Gates are the point where a bet must survive evidence or die — and the graveyard is the most valuable asset the program has.

Open product strategy ↗

STACK

Intake · capacity · value · exec

Default toolkit across the four portfolio lanes. Substitutions driven by the work-management incumbent and the reporting cadence the board expects.

Intake · scoring

  • Productboard · Aha! · Jira Align
  • Notion / Linear intake with templates
  • Weighted shortest job first
  • RICE + confidence bands

Capacity · plan

  • Linear · Jira · Asana
  • Capacity in weeks + named owners
  • Commitment vs. buffer budgets
  • Quarterly rebalance retros

Value · evidence

  • Outcome dashboards
  • Pre- / post-mortems
  • Feature flags + experiment backing
  • Lessons library + rubric update loop

Exec · board

  • Single dashboard (no slides)
  • Horizon 1/2/3 mix visuals
  • Spend + run cost per bet
  • Confidence-banded value curves

Adjacent disciplines

Intake · gate · kill · scale

Run the portfolio like it is on the cap table

Share your current intake pipeline, last-quarter spend, the three bets the board is asking about and the two things nobody wants to kill. We come back with a rubric, a capacity reshuffle sketch and a 90-day governance proposal inside ten working days.