DecisionOS — Decide · module

Portfolio

Which of the AI work already running should be scaled, sustained, merged, fixed or stopped — and what stopping frees up.

When you reach for it

Budget season, a new CIO's first sixty days, or the week after someone at board level asks how much is being spent on AI and what has come of it.

What it asks you

2 blocks, in this order. Each one exists for a stated reason, and the run tells you that reason as you answer it.

01
The inventory
One row per initiative that exists — running, funded, paused or stalled. Facts, all of them verifiable by someone, none of them rated.
02
The facts, per initiative
Nine facts and two judgements. Every one is something a person can establish, and 'don't know' is a real answer that routes the row to a conversation rather than to a verdict.

The method

How the result is produced

Every initiative is classified by an ordered rule set, evaluated top to bottom, first match wins. There is no scoring and no weighting: the rules are the model, and they are printed in full below so that a sponsor who disagrees can point at the rule rather than at the conclusion. Overlap is detected by grouping initiatives on their capability tag within a sponsoring function. Portfolio-level financial figures are computed from cost band midpoints, count only the initiatives that carry a band, and state how many were excluded — where no bands were given at all, the financial figures are suppressed rather than estimated.

What this is not

This is not an audit of your AI spend. The inventory is self-reported, and the module cannot see spend it was never told about.

This is not a verification of measured benefit. Where an initiative reports a number, the number was not checked.

This is not a completeness check. Whether an initiative is missing from the list cannot be established from inside this run, and the most common omission is the respondent's own.

Where it stops

Everything here is what you told us. Nothing was read, inspected, profiled or connected to.

There is no peer comparison behind any statement in this report, and none is implied. We will not show one until there is enough real data to state an n.

Financial figures come from band midpoints, not from reported figures, and count only the initiatives that carry a band.

The over-500,000 band has no upper bound, so a portfolio containing one very large initiative is understated by its total.

The coverage rule only fires where a Governance run has supplied a consequence level and coverage evidence. Without one, no initiative is flagged on coverage — not because none needs it, but because nothing has been established.

Mitigation for the completeness blind spot is procedural: circulate the classified list to function heads and ask what is missing.

What it connects to

Answers established elsewhere are carried in with their age shown, so a stale answer reads as stale rather than being silently reused.

Reads saved results from

Its results carry forward into

The rest of the Decide line

Use Cases

Which AI ideas do we do, in what order, and which are we explicitly not doing.

Open

ROI

What this initiative is actually worth, as a range, and which single assumption the answer depends on.

Open

Vendors

Which of these options to choose — including building it ourselves and doing nothing — and what the choice actually rests on.

Open

See what it costs All twelve modules