Practice
An independent practice, built from operating the problem.
MONO360 is an independent practice for enterprise change, registered in Hong Kong. Twenty years of end-to-end delivery inside luxury and prestige retail — maisons, global beauty houses, heritage department stores — and UK public sector.
The method did not come from a framework. It came from running portfolios where the decision had already been made in a room, and having to live with what that produced. Most recently: a five-pillar enterprise PMO operating model, designed from scratch and delivered internally.
No certifications are claimed. The method comes from operating the problem, not from studying a framework — which is why it is specific about what a gate must be able to do, and unspecific about what it should be called.
THE ARC, STAFFED CONVENTIONALLY
Eight disciplines, staffed separately — and seven handoffs between them. Every gap is a place the reasoning can be dropped.
THE ARC, HERE
The same eight, held in one place. No handoff to lose the thread in — the reasoning that starts at strategy is the reasoning that reaches data architecture.
The rules
Three rules, and they apply here first.
01
Critical designs are not signed off by their author.
Every one is put to independent challenge before it is signed — including the designs behind Horizon PMO itself.
02
AI does the work inside the loop. It does not sign.
Reviews run as panels of several models, independently, against the same design. Direction, judgement and accountability stay with a person.
03
The challenge is kept.
Including the ones that changed our mind. A record that only contains agreement is not a record, it is a brochure.
The arc held in one place is one thread, not one opinion — which is exactly why the challenge has to come from outside it. Not a specialist in one layer of the arc. That is the point: the gaps between those layers are where portfolios fail.
The product
Horizon PMO — the method, productised.
A portfolio intelligence platform for enterprise change — one live view of every project, programme and investment.
It exists because the method needed somewhere to live: a register that can be compared, gates that can be failed, and a decision trail that survives the people who wrote it. The advisory work does not depend on it. The recommendation follows what the portfolio needs — often the tooling already in place, configured so that things can fail.
THE DECISION TRAIL
What was proposed, who challenged it, what changed, and who signed. Critical designs are never signed off by their own author.
Start here
Start with the portfolio you already have.
Bring the plan as it stands and the arguments you keep having about it.