Six findings.

Each finding is stated with the evidence behind it and where it is published. Together they explain why a mature market of portfolio tools still cannot tell an executive what the next dollar buys.

1

Ranking is a heuristic, and it fails exactly where portfolios live.

Sorting by score and cutting at the budget is optimal only when every item is small and divisible. Real portfolios are lumpy, so rank-and-cut falls short of the best available set and quietly drops the large, focused strategic bet. With no units of value the field has no marginal analysis and no prices, so it scores where it should solve.

How we know
A proof, set out in Method Note 02 · The wrong foundation
Discipline
Economics · allocation
2

The pipeline sets the ceiling. The optimizer only decides how close you get.

No selection can fund a priority that nothing in the pipeline serves. Most organizations source candidates bottom-up only, which clusters supply on familiar work and starves the strategic priorities. Adding top-down candidates drawn from capability gaps raises value and alignment at every budget, which no amount of extra money can do.

How we know
The same budgets solved against three pipelines, in Method Note 03 · Pipeline supply
Discipline
Economics · opportunity supply
Bottom-up only+ top-down+ asset lifecycle
The same budgets solved against three pipelines. Bottom-up only stops gaining near $9M, with alignment near 50% at every budget; adding ten top-down candidates lifts alignment to about 77% at $10M. Illustrative synthetic data; the shapes are the point.
3

Every limit has a price, and only the binding ones matter.

A budget, a mandate, a floor, a business-unit split and a scarce skill are each a limit on the solution, and each has a measurable cost. With whole projects the marginal value of money is a staircase, not a rate: nothing until +$340K, then this project. Five prices answer an executive's real questions: the option given up, the next dollar, each limit, the people we lack or leave idle, and the distance from the strategy. Effort spent negotiating a limit that does not bind is waste.

How we know
Prices computed across the decision chain; the Decision Inventory, a working paper, chapters 8–9
Discipline
Economics · scarcity
4

A portfolio boundary is a zone, not a line.

Ordering projects by how far the world must move before their decision changes shows which commitments are settled and which are one estimating error from reversing. That is where review effort belongs, and a ranked list hides it.

How we know
Projects ordered by distance to flip, in Method Note 01 · Distance to flip
Discipline
Governance and law
5

Value is asserted, not measured, and the loss happens where no one sees it.

On a real 50-project register, the 50 initiatives took only 23 distinct value scores, so most ties were being broken on cost without anyone saying so. Weights typed into a scorecard are never tested against the strategy they claim to represent. Ratings also drift upward over cycles, because rating a project as touching every priority costs nothing.

How we know
A real 50-project register, anonymized; the Decision Inventory, a working paper, chapter 7
Discipline
Behavior
6

A decision can be automated exactly as far as its rule is explicit and its result reversible.

Every vendor is adding agents, and none says which decisions an agent should make. An inventory of about 120 decisions across the chain answers that question. Each decision is typed and has an owner and a mode: Autopilot, Supervised or Manual. Automation rises down the chain, from a strategy end that is almost all judgment to a capacity end that runs mostly on autopilot. The machine never ratifies its own output.

How we know
118 decisions classified by mode; the Decision Inventory, a working paper, chapters 3–6
Discipline
Automation
AutopilotSupervisedManual
Share of each module's user decisions by mode.

Models of reality

Built from models of how the organization actually works.

Most portfolio tools reduce the organization to an abstraction they can compute easily: one score per project, one budget line, one number for "resources". The decision then gets made against the abstraction, and reality only shows up later as delays, contractors and re-plans. The IQ Suite models what is really there and solves against that.

From a weighted score to an exchange rate

What leadership actually believes, measured.

Priorities are elicited as ratios between business drivers, at corporate and business-unit level, and published with a range rather than one false-precise number. Importance and urgency are kept apart.

  • Drivers or OKRs
  • Corporate and business-unit levels
  • Disagreement shown, not averaged away
403525
Typed weightsMeasured, with range

From one budget line to every real limit

The walls the decision actually lives between.

Cash across years, capital and subscription costs, people per skill per quarter, points per train, business-unit floors, mandates and in-flight commitments are each modelled as the limit they are, and each one is priced.

  • Cash, internal capacity and agile capacity as separate pools
  • Multi-year cost, not a single number
  • Mandates and floors with their price
budget
One budgetEvery binding limit

From "resources" to people, skills and quarters

Who is available, when, and at what rate.

Capacity is modelled skill by skill and quarter by quarter, internal or bought, with the lead time to hire and the time to become productive. A funded plan the organization cannot staff shows up at approval, with its price.

  • Shortfall at the contractor rate, idle time priced
  • Hiring, development and release on the company's clock
FTE: 40
A headcountSkills × quarters

From a given list to a pipeline with sources

What is on offer, where it came from, and what is missing.

Candidates are traced to their source: the people who run the business, the capability gaps the strategy exposes, and the assets that need replacing. The pipeline is valued, so the company can see what a stronger one would buy.

  • Bottom-up, top-down and asset lifecycle
  • Transform or improve incrementally
A listThree sources, one offer

From a one-off plan to a standing decision

Planning repeated with what actually happened.

Spend, progress and forecasts flow back into the same models that made the decision. Whether to hold, rebalance, trade or realign is decided again with today's data, and the record carries why.

  • One engine for planning and managing
  • Every departure priced and recorded
plan v1re-decide
An annual planA decision kept current