Independent practice · Hong Kong
Decided before it is built.
MONO360 is an independent practice for enterprise change — the advisory, the operating model it produced, and the platform and agents that run it.
01 · THE GROUND
One governed system.
Demand and delivery are usually governed separately — one committee decides what to fund, another decides how it gets built, and nothing joins the two. The overlap is where a portfolio is actually decided, and it is usually the part nobody owns.
02 · THE GAP
Decided in a room.
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. A portfolio needs two auditable answers: what earned its place in the plan, and what proved it deserved to stay. Most cannot produce either.
THE TWO ANSWERS A PORTFOLIO OWES
What earned its place in the plan?
What proved it deserved to stay?
03 · THE PIVOT
Before, not after.
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 — and it has to sit where the work is still cheap to change, not after the money is spent.
WHERE THE GATES SIT
Gates on both sides of the plan. The left-hand ones decide whether.
04 · THE MODEL
Two altitudes.
Demand decides what earns a slot. Delivery decides how it gets built and proven. AI works inside both — drafting, scoring, challenging, every step recorded — and stops at the point where something has to be signed.
05 · THE RECORD
A trail that survives.
A decision trail outlives the people who wrote it: what was proposed, who challenged it, what changed, and who signed — held as data rather than as a folder of documents. It is the difference between a portfolio you can explain and one you can only defend.
THE DECISION TRAIL
What was proposed, who challenged it, what changed, and who signed. Critical designs are never signed off by their own author.
Where the expensive decisions are still cheap to change.
Gates fire before a line of code is written, not after. The mistakes that cost the most are caught at design — not in production, where they are not.
Clients we work with
Not published — client engagements are under confidentiality until named consent is on record.
Case study
View the gapsA portfolio read as it actually was — what a gate caught, and what changed.
Standing up one front door for demand inside an organisation that had six.
Not published — written and cleared before it appears here.
On our mind
The practiceWhy capacity is asserted rather than measured, and what it costs.
A gate something can fail: the difference between a document and a decision.
Inside the loop, never on the gate — where an agent stops.
Not published — the writing section is being built.
Start here
Start with the portfolio you already have.
A first conversation is diagnostic. Bring the plan as it stands and the arguments you keep having about it.