The governed decision-intelligence layer for enterprise portfolios

Every decision, explained.

Horizon PMO connects the systems you already use to one reproducible record of what was decided, why, by whom and whether the decision proved sound.

Make the call. Preserve the evidence and challenge. See what changed. Carry the outcome into the next allocation.

Assess one decision ↗See the product ↓
Decision / HX-204Approved · version 4
Investment committee · 14 October
Fund Atlas. Defer Northstar.
Strategic alignmentRule: enterprise priority weighting v3
84
Decision evidenceSponsor 78 · DEI 61
−17
Challenge retained
Benefits confidence depends on two unvalidated adoption assumptions. Accepted by A. Chen with review at Gate 3.
8 sources$1.8m displaced2 dissenting reviews
Make the call•Explain the reasoning•Invite challenge•Retain the record•Learn from the outcome
The evidence layer

The data exists.
The governed view doesn’t.

Delivery lives in one tool, spend in another, risk in a spreadsheet and benefits in a deck. Horizon PMO reads the evidence where it lives, applies declared reconciliation rules to each evidence domain and keeps conflicts visible instead of averaging them away.

SP
SharePointPortfolios · business cases
$47.9m
X
ExcelBudgets · models
$49.1m
SAP
SAPActuals · commitments
$48.2m
O
OracleFinance · procurement
Live
SN
ServiceNowDemand · workflow
127 items
J
JiraEpics · delivery
31 programmes
ADO
Azure DevOpsReleases · dependencies
Live
SM
SmartsheetRAID · programme plans
6 at risk
SF
SalesforceBenefits · customers
Live
W
WorkdayCapacity · skills
214 people

No fixed source limit · Files · APIs · warehouses · documents · messages

HORIZON PMODecision evidence / HX-204Review now
Recommended posture

Review before releasing the next $2.1m.

Ten sources considered · five governed evidence domains

Financial truth$48.2m committedSAP · Oracle · Excel
Reconciled
Delivery evidenceReview before releaseDEI 61/100 · sponsor 78 · Jira · Azure DevOps · Smartsheet
−17 gap
Capacity impact11 over-allocatedWorkday · Azure DevOps
2 squads
Benefits evidence$2.8m not evidencedSalesforce · SharePoint
At risk
Why intervention is required

ERP actuals supersede the spreadsheet forecast. A delivery milestone moved. The benefits case still uses an unvalidated adoption assumption.

Owner · A. Chen · decide by 18 Oct4 conflicts retainedEvidence-readiness index—not a probability of success
Assembled by handBoard packs are already old when read.
A judgement, not a number“Are we on budget?” arrives without its rule.
Risk per projectCross-portfolio exposure is never added up.
Decided lateGovernance fires after commitment.
Fit

Built for complexity.
Not for everyone.

Horizon PMO matters where a portfolio decision nobody properly made at the front door is paid for later—in capital, capacity and confidence.

Most valuable where…
  • Many programmes compete for finite investmentand demand must be compared with what it displaces.
  • Multiple business units own different parts of the portfolioand no system holds the whole decision.
  • Financial, delivery and benefits records disagreeso executives cannot reproduce the number they back.
  • The PPM estate is operationally deep but executively denseso Horizon PMO can sit above it as the decision layer.
Probably not the right fit where…
  • The need is basic tracking or a single programme.
  • A spreadsheet still governs the portfolio reliably.
  • The PMO already preserves decision evidence and history effectively.
  • The requirement is maximum feature depth from one suite.
  • The buyer wants another dashboard without changing governance.
Enterprise pilot

Prove it on one decision.
Then decide whether to scale.

Horizon PMO starts with one consequential portfolio decision—not an enterprise-wide replacement. Test the evidence, governance and operating fit against a question your board already needs answered.

Assess one decision →
A contained first engagement
01

One live decision

Select a consequential approval, intervention or allocation question with a named executive owner.

02

Agreed evidence

Connect the relevant finance, delivery, capacity, risk and benefits sources—without replacing them.

03

Governed record

Declare the rules, retain conflicts and challenge, and show exactly why the resulting view can be trusted.

04

Scale decision

Leave with a working decision record and a written recommendation on readiness, requirements and next scope.

Product / One decision in motion

See the governance, not just the dashboard.

Evidence changes. MAIA exposes the conflict. A person makes the call. The outcome returns as learning.

Illustrative interface · fictional data

Decision / HX-204
Live portfolio · 09:42
Investment committee · version 4

Fund Atlas. Defer Northstar.

Approved
Strategic alignment84Priority weighting v3
Decision Evidence Index61Sponsor 78 · evidence gap −17
Capacity displaced$1.8mNorthstar · two squads
Proposed08 Oct
Challenged11 Oct
SignedA. Chen · 14 Oct
Which assumption changes this decision first?
MAIA · explained answer

Adoption confidence is doing more work than the evidence supports.

Atlas falls below the approval threshold if adoption is under 63%. Two sources still use the unvalidated 78% assumption.

Benefit model v6Adoption researchGate rule 3.2
Human decision requiredAccept risk · revise · defer
Outcome review · Gate 3

The promise returned to the record.

Learning captured
68%actual adoption
Original assumption78%

The programme delivered, but adoption was optimistic by 10 points. Future cases inherit the observed rate.

Rule updatedAdoption baseline: 78% → 68%Effective next allocation cycle
Why Horizon PMO is different

Not another system of activity.

PPM systems

Manage portfolio activity.

Plans, resources, workflows and delivery records.

BI tools

Render supplied data.

They visualise an answer after someone decides what is true.

AI assistants

Generate an answer.

Without governance, fluency can outrun evidence.

Horizon PMO

Governs the decision—and learns from the outcome.

Evidence, trade-offs, challenge, accountable approval and outcomes stay connected in one explainable record.

MakeExplainChallengeRetainLearn
The product surface

Govern every decision.
From evidence to outcome.

Four connected capabilities help the enterprise govern consequential decisions and preserve the evidence behind them.

01 / Govern

Control what enters and what can pass.

Demand, gates, approvals, exceptions and accountable history.

Make · challenge · retain
02 / Understand

See what the decision changes.

Map each decision to the business capabilities and value it enables—then trace its upstream dependencies and downstream impacts.

Map · explain · challenge
03 / Intervene

Model the choice while there is time.

Delivery, capacity, vendors and scenario trade-offs.

Make · learn
04 / Communicate

Publish the same truth for every seat.

Role views, MAIA answers, board packs and human approval.

Explain · retain
Product / From view to board

Build the view. Govern the report.

Configure the working view and publish the board narrative from the same governed record—with evidence and named approval.

Horizon PMOView builder / Executive portfolioDraft saved
Executive portfolio

What requires a decision?

Decision Evidence Index74
Sponsor 81 · DEI 74
Investment exposure$6.4m3 decisions account for 82%
Where attention goes first
  1. Atlas adoption−17 evidence gap
  2. Billing platform3 dependencies
  3. Cloud exit$1.2m exposed
Learning returned12assumptions updated
4 widgets · 6 governed sourcesEvery number keeps its rule
Horizon PMOReports / Q3 board packDrafted by MAIA
Q3 board pack

Ready for accountable review.

Portfolio reviewQ3MMXXVI · for the boardHorizon PMO
Executive summary

Committed spend is $48.2m. Six programmes require intervention; two share the billing dependency.

6 sources · 3 decisions
At a glance
$48.2mcommitted−1.2%variance6at risk74DEI
Attention
  • Atlas adoption −17
  • Billing platform 3 deps
  • Cloud exit $1.2m
MAIA · One dependency links three decisions.
Awaiting approvalNothing leaves without a named reviewer.

Illustrative interface · fictional data · no automated publication

MAIA governance

Answers with receipts.

MAIA explains approved portfolio views and cites the evidence. It does not invent a number it cannot point to—or become the accountable decision-maker.

Read-only viewsSource citationsTenant scopedHuman approval
Ask MAIAIllustrative portfolio · 09:42
1 / 4 · Dependency exposure
Which dependency creates the most portfolio exposure?
Billing platform requires intervention. It links three decisions and $4.1m of exposure. Confidence fell 17 points after the vendor milestone moved.
Sources: Exposure v7 · Delivery milestones · HX-204 · HX-221
Which business capabilities does approving Atlas affect?
Customer onboarding gains the value. Identity, data engineering and change adoption are the critical upstream dependencies; billing operations and service support are the downstream touchpoints.
Sources: Capability map v4 · Dependency register · Benefits case · Operating model
Which decision should the committee challenge first?
Challenge Atlas before releasing the next tranche. The case assumes 78% adoption while current evidence supports 63–68%. A named owner must validate the assumption, revise the tranche or defer.
Sources: Benefit model v6 · Adoption research · Gate rule 3.2 · HX-204
What changed after the outcome review?
Actual adoption settled at 68%—ten points below the approved case. The observed rate now informs future allocations, while the original assumption and accountable approval remain on the record.
Sources: Gate 3 outcome · Adoption telemetry · Decision HX-204 · Baseline rule v7
Enterprise assurance

Know the controls before you proceed.

Who can see the evidence. Who changed the record. Where MAIA stops.

Isolation

Keep each organisation’s evidence separate.

Identity-bound, tenant-scoped access is designed to isolate evidence, dashboards and answers.

Accountability

Retain a named history.

Approvals, budgets, risks and decisions are retained instead of overwritten by status.

AI boundary

MAIA explains. A person decides.

MAIA cites approved, read-only views. Approval remains with a named person.

Read assurance details →
Buyer questions

The questions worth answering early.

Evaluate Horizon PMO as a purpose-built decision-governance layer—including what must be proven in your estate and agreed in writing.

Does Horizon PMO replace our existing tools?+

It is designed to work above them, not require an estate-wide replacement. A pilot starts with the evidence already used for one decision and tests the connectors, access and operating changes needed in your environment.

Could we assemble this with Power BI and Fabric?+

Parts of it, yes. Power BI and Fabric can model governed data, surface lineage, provide AI-assisted answers and support write-back workflows. Horizon PMO is designed to package the decision-specific layer: evidence conflicts, the governing rule, challenge, named approval, history and outcome stay connected. The comparison is custom assembly versus a purpose-built operating model—not charts versus governance.

We already have a PMO—where does Horizon PMO add value?+

It is designed to give the PMO and accountable executives a reproducible chain from evidence and alternatives through challenge, decision, intervention and outcome. If your current operating model already preserves that chain reliably across tools, Horizon PMO may add limited value.

What does MAIA do—and not do?+

MAIA is designed to explain approved views and return source references within the user’s permitted scope. It does not approve decisions or silently change the record; a named person remains accountable. The interfaces and data shown on this site are illustrative.

How would an engagement start?+

Start with one consequential decision, a named owner, an agreed evidence set and explicit success measures. The pilot tests whether Horizon PMO can produce a reproducible governed record and credible evidence for—or against—wider adoption.

What happens if we do not continue after the pilot?+

No wider rollout should be assumed. The pilot agreement should state which outputs you retain, how your data is returned or deleted and how access is removed. Those exit terms are agreed in writing before the pilot begins.

Start with the question your board keeps asking

Know what changed. And why.

Assess one live decision, see the governed record and determine whether Horizon PMO is ready to scale across your estate.

Assess one decision ↗