Independent practice · Hong Kong
Decided before
it is built.
MONO360 is the independent practice of Van Le. Two decades running portfolios and PMOs at enterprise scale — advising on how change gets chosen, governed and proven in the AI era.
Practice
Independent. One practitioner, the full arc.
Method
Two tiers, 22 gates, a written decision trail.
Product
Horizon PMO — the method, productised.
01 — The problem
Most portfolios are decided in a room and governed in a spreadsheet.
Demand arrives from everywhere and nowhere — a steering committee, a corridor, a board paper someone has already promised. Capacity is asserted rather than measured. The plan that comes out is a negotiation, not a decision.
Two questions almost nobody can answer at the same time: what earned its place in the plan, and what proved it deserved to stay there.
SIX DOORS IN · NO GATE
CAPACITY VS COMMITTED
The pivot
A review after the build is a report. A review before it is a decision.
Governance that exists as a document is not governance. It has to be a gate something can fail.
02 — The model
Two tiers, one governed system.
Demand decides what earns a slot in the plan. The lifecycle decides how it gets built and proven. Same method, two altitudes — and nothing skips either.
TIER 01
Demand
What earns a slot in the plan. Once a quarter, every ask through one front door, committed to capacity that actually exists.
TIER 02
Lifecycle
How it becomes proven software. Eight stages, twenty-two gates, and a written decision trail you can audit.
03 — The demand tier
Every ask, through one front door.
Six steps between an idea and a committed slot. An ask that cannot survive all six was never a plan item — it was a preference with a sponsor.
MANY ASKS IN · FEW COMMITMENTS OUT
01
Strawman
Someone wants something. Written down before it is argued about.
02
Captured
Into the register, in a shape that can be compared with everything else.
03
Scored
Against declared criteria, not against who is asking.
04
Challenged
Independently. The sponsor does not mark their own homework.
05
Committed
To capacity that actually exists, for a period with an end.
06
Handed over
Down to the lifecycle, business case attached.
The number that matters
11 of 22 gates fire before a line of code is written.
Exactly half. The expensive mistakes are caught at design, where they are cheap to fix — not in production, where they are not.
04 — The method
Reviewed before it is built, not after.
Most software is built fast and checked later. This is the other way round: every feature passes review gates before a line of code is written — so what reaches your environment is deliberate, reviewed and predictable.
01
Is it worth it?
The business case, feasibility and budget are confirmed before any design work begins.
02
Agree the “what”
A clear, testable definition of what the feature must do — signed off before design starts.
03
Design & review
Independently reviewed for soundness, security and knock-on impact — then a build plan is approved.
04
Build & release
Built to the plan, verified against it, tested on a staging copy, released only on your sign-off.
THE DECISION TRAIL
What was proposed, who challenged it, what changed, and who signed. Critical designs are never signed off by their own author — they are stress-tested by independent reviewers, on the record.
05 — The practice
One practitioner, the full arc.
Twenty years of end-to-end delivery inside luxury and prestige retail — maisons, global beauty houses, heritage department stores, and UK public sector. Operating the problem long before building anything to solve it.
Most recently: a five-pillar enterprise PMO operating model, designed from scratch and delivered internally, without Big Four support. That is where this method comes from — not from a framework, from having to run one.
No certifications are claimed. The track record is the credential.
THE ARC, STAFFED CONVENTIONALLY
Eight disciplines, eight specialists — and seven handoffs between them.
THE ARC, HERE
One practitioner across all eight. No handoff to lose the thread in.
Not a specialist in one layer of the arc. That is the point — the gaps between those layers are where portfolios fail.
06 — The alternative
The large firms now sell governance too.
The major integrators have named delivery systems with governance built into them — AI-native, agentic, promising compressed time-to-market. Take that seriously. It means governed change is now something enterprises buy on purpose rather than assume they already have.
GOVERNANCE INSIDE THE FLOW
GOVERNANCE ABOVE IT
Their gate controls how. It cannot control whether.
A governance stage inside a delivery flow governs work that is already in the plan. It has no view on what earned a place there — because the firm was engaged to deliver what you had already chosen. The expensive decision was made before they arrived.
A firm that designs, builds and reviews is marking its own homework.
The one rule this method will not bend is that critical designs are never signed off by their own author. An integrator cannot honour that on its own work, however good its process is. It is a structural conflict, not a failure of intent.
The argument
This is not an argument against large firms. It is an argument about who reviews them.
Plenty of change genuinely needs their capacity. The question is who decides what belongs in the plan before anyone is engaged to build it — and who checks the work of the firm that built it.
07 — Horizon PMO
The method, productised.
Horizon PMO is a portfolio intelligence platform for enterprise change — one live view of every project, programme and investment. It is a product you license, not a rollout I bill for. That distinction is deliberate: advisory work is about your portfolio and your governance; the product stands on its own.
08 — Contact
Start with the portfolio you already have.
A first conversation is diagnostic, not a pitch. Bring the plan as it stands and the arguments you keep having about it.