Part of Work Architecture

Decision Systems

Somewhere in your company a person signs off on a machine's recommendation several times a day, and nobody has told them what signing means.

Decision Systems is about how a company makes up its mind. Who gets to call it. How much process the call deserves. And whether anyone, a year later, can still work out why it went the way it did.

This became its own subject when machines started handing people answers faster than anyone could check them. A model suggests a price. It flags a candidate. It drafts the policy. A person still approves it, but the approval has never been defined. Is it a review, or a rubber stamp? Most companies have never had that conversation, because until recently there was nothing to have it about.

The old tools do not help. RACI and RAPID sort out who does what among people. Neither has a box for a machine that offers an opinion.

So this domain holds what you need once a model is in the room. Who decides. What gets written down. Which calls are worth slowing down for. And when a machine should stop and wake someone up.

It is not about making the right call. It is about the machinery the call travels through.

What is coming

  • The Decision Record Stack
    Framework in development, v0.2

Nothing in this domain is published yet. Each item below carries the month it is due.