Decision Governance

The discipline of confirming that the business still agrees with the decisions its systems help make.

Technology governance asks whether a system is secure, whether it performs, and whether it integrates. Decision governance asks who owns this decision, why this threshold is here, and whether we can defend it. Most organizations run the first list well and have never named, let alone managed, the second.

Where it came from

Every settlement in this space has the same bones: what data goes into the model, what it is allowed to output, which calls need a human, who inside the company answers for it, and what records prove any of it. That is a decision rights document.

The only real difference between a consent decree and a governance framework is who wrote it. One gets written by your team, on your calendar, in language that fits how your business runs. The other gets written by a regulator or a plaintiff's firm, on their calendar, in the shape of your worst quarter.

When to run this

After the Signature Audit has produced an inventory. Governance without an inventory is a committee.

The steps

Four things become standing practice rather than a project.

Identify every significant automated recommendation in the business.
Assign a named business owner to each decision it drives.
Put the assumptions behind it on a review schedule, the way you would any other operating number.
Write down when a threshold changes and why, the week it changes.

Review them on the same cadence as any other material policy. If pricing assumptions get looked at quarterly, so do the rules behind automated pricing.

What a bad answer looks like

The work landing with the wrong function. It cannot go to procurement, which is scoring vendors. It cannot go to IT, which answers for the system rather than the judgment inside it. It is not a compliance program either.

Every major operating metric already has an executive owner. Occupancy does. Bad debt does. Employee turnover does. Decision rights should too, and the owner is the executive whose numbers move when the decision goes wrong.

What to do with the output

The goal is not changing numbers more often. It is that changes happen on a calendar, in front of the accountable executive, with the reason written down the week it was decided.

None of it requires a data scientist. It requires an executive deciding these are business decisions and treating them the way the company already treats every other decision that matters.