MONO360 Contact

Practice

An independent practice, built from operating the problem.

MONO360 is an independent practice for enterprise change, registered in Hong Kong. It draws on years of work on the ground in luxury and prestige retail — maisons, global beauty houses, heritage department stores.

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.

Eight governed stages run as a continuous loop, a gate between every pair, with multi-AI peer review at the centre and a person signing. EIGHT STAGES · ONE GOVERNED LOOP 1 STRATEGY 2 DISCOVERY 3 DESIGN 4 BUILD 5 VERIFY 6 UAT 7 RELEASE 8 OPERATE MULTI-AI PEER REVIEW MODELS CHALLENGE A PERSON SIGNS A GATE BETWEEN EVERY STAGE A LOOP, NOT A ONE-WAY ROADMAP

The record

The five, applied here first.

A person sits above the loop and supervises it; AI runs inside the loop beneath, with every layer under the decision above it. A PERSON SUPERVISES AI inside the loop EVERY LAYER RUNS UNDER THE DECISION ABOVE IT
Governance
A gate said no to our own roadmap. One product direction rested on a premise five independent reviews could not prove, and it was stopped before any build began.
Accountability
Nothing here is signed off by its author — including the designs behind Horizon PMO, and this website. The site was reviewed independently, graded amber, and published as it stood.
Process redesign
Our own demand enters through one front door and is ranked on evidence, with a mandatory contrarian challenge before anything is committed.
Data
Ask the eight questions of this portfolio and the answers exist in writing: what earned its place, what was refused, what a review changed, who challenged what, and who signed.
Workforce readiness
AI does much of the drafting here and none of the signing. Reviews run as panels of several models, independently — one opinion repeated is not corroboration.

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.

And the limit of it, stated plainly. A practice that governs itself is not proof it can govern you: your portfolio has a scale and a politics ours does not. What this record proves is narrower — that the model has been run, that it refused things, and that the refusals were kept. Inspectable evidence from client work is the one finding still open, and it is named here rather than left for you to notice.

We ran it on ourselves →  ·  How this site was reviewed →

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.

horizonpmo.io →

THE METHOD, RUNNING AS SOFTWARE

THREE OF THE LIVE VIEWS · SCROLL →

PORTFOLIO
GATES & DECISIONS SIGNED PROPOSED · CHALLENGED · SIGNED
CAPACITY COMMITTED VS REAL

ONE LIVE VIEW · NOTHING FAILS OFF THE RECORD

Start here

Start with the portfolio you already have.

Bring the plan as it stands and the arguments you keep having about it.

The first read ends in writing: which of the gaps are live in your portfolio, and the first gate that would expose them.