What is DecisionOps?

Nico Izcovich, founder of Learning NodesIn development since November 2025. First published 6 February 2026.

DecisionOps is the practice of running business decisions the way good engineering teams run deployments: every decision has an owner, the evidence it rested on, the reasons it was made, and a record that later decisions can cite. It covers the whole path from a messy situation to a committed decision, and it keeps that path open to questions afterwards.

What it changes day to day

A situation is written down in plain words before anyone asks for analysis.
The questions a decision depends on are made explicit, each with the person who can answer it.
Numbers in an answer come from a query anyone can read, with the data and the row count beside them.
The decision is committed as a record that stays as written. A correction is a new record that points to the old one.

The loop

ASK: describe the situation. The system reads it against the decisions already on record and proposes the business questions that expose the gaps, along with the decision you appear to be facing.

DECIDE: work the case. Answer the questions, test the claims the decision rests on, and see what decides each option.

ACTIVATE: commit. The decision becomes a Decision Record with its owner, evidence and reasons, and the next situation can cite it.

Why it needs a name

DevOps made deployments traceable and repeatable. DataOps did the same for data pipelines. Decisions are what both exist to serve, and they had no practice of their own. DecisionOps is that practice.

Where to go next

Read the guide from the start, or try the loop on a situation of your own at workstation.learningnodes.com.