The governance framework that keeps a transformation decidable

Governance rarely gets budgeted, staffed, or designed the way technology and process do. It's treated as implicit — everyone assumes the right people will make the right calls at the right time — until a decision stalls for three weeks because nobody actually owned it, or a risk that was flagged once in a status meeting resurfaces as a cutover blocker nobody tracked.

That is why Governance sits as one of the six AMIGA dimensions rather than as a subset of Process. A process gap slows work down. A governance gap stops it from being decidable at all — the work is ready, but nobody with standing will say yes or no.

The four components here are deliberately minimal: a matrix, a tracker, a gate, and a path. None of them require new tooling or a governance office. They require someone to write down who decides what before the program needs that answer under pressure, not after.

This is a starter kit, not a full governance model — it is what you stand up in week one so decisions have a home. Programs from $12M to nine-figure implementations have run on some version of this structure; scale adds layers, it does not change the four things it is built from.