What is Decision Intelligence?

Every company runs on decisions, yet the decision is the one thing enterprise software almost never stores. It stores transactions, tickets, contracts and timesheets. The reasoning behind the choices that shaped all of them evaporates, into slide decks, hallway conversations and the memory of whoever happened to be in the room. The organisation keeps the consequences and throws away the thinking.

Decision Intelligence is the discipline that fixes that. It treats a business decision as something you can structure, evidence, trace, challenge and learn from, rather than an event that happens on a Tuesday and is gone by Friday.

When a decision is captured as a Decision Object, with its evidence, its options, the choice and the outcome, it stops being a moment and becomes something the business owns.

Not analytics, and not a copilot

It is easy to confuse Decision Intelligence with two things it is not. Business intelligence tells you what happened: it reports the past well and stops there. An AI copilot hands you an answer and asks you to trust it. Decision Intelligence does the harder thing in between. It composes the available evidence into a recommendation you can interrogate, and it keeps the whole chain, so the decision can be challenged before it is made and scored after. A number you cannot trace back to its evidence is not intelligence; it is confidence without grounds.

What makes a decision intelligent

Five properties, and a decision needs all of them:

• Evidence with a quality state. Every fact carries whether it was measured, modelled, inferred, stated or unmeasured. An assumption is never allowed to impersonate a measurement.
• Options priced against the constraint that binds. Each option carries the earliest date it clears every requirement, not the date someone hopes for. The worst constraint decides, because the business experiences the constraint that fails, not the average.
• Confidence that is composed, not typed in. Business Confidence is computed from the published evidence and weighted by its quality. Nobody declares it; the system derives it, and names the dimension that binds.
• A recorded human choice. A person always decides. If they overrule the recommendation, the object records who, when and against what evidence. Overrides are allowed, and remembered.
• A scored outcome. When reality lands, it is compared with what was recommended and what was decided. That score is how the system learns.

One concrete example

No customer required. This is the shape of the thing:

A contract renewal is approaching. On the surface the account is healthy, every service level is green. But the value actually delivered is unmeasured, the relationship runs through a single sponsor, and the last three change requests were scoped below cost. A dashboard shows the green number and moves on. Decision Intelligence opens the renewal as a decision, not a date: it decomposes the health, names the dimension that binds, prices the options, renew as is, renegotiate scope, invest to save the relationship, and records which one the account owner chose. Months later, it scores whether that was the right call, and the next renewal with the same profile is recommended in light of it.

Why it compounds

A single intelligent decision is useful. A thousand of them is an advantage no competitor can buy. Because every outcome is scored against every recommendation, the organisation calibrates: if commitments with a certain profile consistently deliver below forecast, the next recommendation with that profile says so. This is the loop that turns a pile of decisions into enterprise intelligence, and the full philosophy behind it is set out in Enterprise Decision Intelligence.

The goal was never to take the decision away from the human. It was to make sure the human decides with everything in view, and that the organisation remembers what it learned.