Decision debt

Engineers have a word for the cost of a shortcut that is paid later, with interest: technical debt. A choice made quickly, under pressure, leaves something unresolved in the code, and every later change pays a little more for it until someone stops and pays it down. The word is useful because it turns a vague unease into a line item. Once a thing has a name, someone can be asked to own it.

The way organizations decide needs the same word.

Decision debt is the future work created when a decision’s reasons, responsibilities or conditions are lost, unclear or out of date. Competent teams with clear goals accumulate it too.

It is created the moment a decision leaves the room with its reasoning behind it. What each person meant stays in their head. What the leader actually decided stays in the leader’s. Who accepted the work, and on what conditions, was never said, so it is nowhere. The decision goes forward as a line in the notes, and everything that made it a decision stays in the people who were present.

The familiar handoff

Email introduces the question. Meetings explore it. Notes summarize what was said. Email records the outcome. Tasks execute it. Each handoff is a place where a reason, a responsibility or a condition can fall out, and the question nobody in the chain is paid to answer is the one that matters most: when circumstances change, who reconnects the pieces?

The answer, in most organizations, is whoever was in the meeting. That is the debt.

How it accrues

The debt has the structure of any debt. The principal is the reasoning that left the room: the reservation nobody voiced, the constraint nobody wrote down, the fact that one person held and the group never heard. In a typical six-person meeting two people do most of the talking; the other four absorb the direction, and whatever they knew stays absorbed. [3]

The interest is the meeting that schedules another, because a meeting that does not produce a recorded decision produces a mandate to meet again. Three-quarters of knowledge workers say that is how their meetings frequently end. [2] The managers know the rate they are paying: in a McKinsey survey of 1,259 of them, 61 percent said most of their decision-making time was used ineffectively, and deciding was more than a third of their week. [1]

The debt compounds when the sponsor leaves, because the context leaves with them. The successor inherits the decision and none of the reasons, and the organization can no longer tell which of its precedents were sound. This matters more than most analysis budgets assume: across 1,048 decisions, the process by which a decision was made mattered six times more to the outcome than the analysis behind it. [4]

And it defaults when the decision is acted on without its conditions, by a ticket, a signature or an agent that carries it forward at speed and does not know the acceptance had a condition attached.

A balance sheet nobody keeps

The same McKinsey survey put a number on the carrying cost: for an average Fortune 500 company, roughly 530,000 days of managers’ time a year, about 250 million dollars of labor, spent on decision-making that the people doing it describe as ineffective. [1] The figure is an estimate and should be read as one. What matters more than its size is where it sits, which is on no balance sheet at all. Nobody is assigned to pay down a debt the books do not show.

This is why the debt looks like ordinary work. Rework, re-litigation, the second launch meeting, the hire that has to be explained again to the new director: none of it is labeled as the cost of a decision that was not recorded. It is labeled as the job.

Three systems of record, and the one that is missing

Capital and resources are secured in the ERP. Customer relationships are secured in the CRM. Code and tasks are secured in the repository and the tracker. The most consequential asset of all, how the company actually makes its choices, has no system of record. It lives in a system of ephemera: chat threads, call transcripts and human memory. When a vice president leaves, the context behind three years of choices leaves with them.

The tools around the decision are good at their jobs. None of them has the decision as its job. They sit downstream of it and carry whatever the meeting produced: the decision when there was one, apparent agreement when there was not. Typing speed is not business velocity. A bad decision made faster is not productivity; it is debt issued at a higher rate.

A system of ephemera issues the debt. A system of record pays it down.

Sikizana is the system of record for judgment. As a CRM takes a customer relationship out of a salesperson’s private memory and makes it a corporate asset, Sikizana takes the reasons, reservations and conditions out of individual heads and makes the company’s judgment a kept, versioned and reusable asset. It records decisions, never people. The channels, the boards and the AI then inherit a decision instead of inventing one.

Paying it down

Naming the debt does not shrink it. It makes it something a leader can decide to stop issuing. The first decision you record is the first one you stop paying interest on: each person thinks it through privately before the room forms a view; the leader decides explicitly, with reservations answered in their own words; each owner accepts the work and names what the yes depends on; and the reasoning, the forecast and the outcome stay together, so the organization learns from its own calls. AI does the clerical work. People make the decision.

Sources

1. McKinsey (2019) · Decision making in the age of urgencySurvey fielded February 2018; 1,259 respondents in 91 countries. The dollar and day figures are McKinsey’s estimates for an average Fortune 500 company.
2. Atlassian (2024) · State of Teams5,000 knowledge workers; 77% said they frequently attend meetings that end by scheduling another.
3. Thompson, Kellogg School of Management · How brainwriting can neutralize the loudmouthsA research summary: in a typical six-person meeting, two people do more than 60 percent of the talking.
4. Lovallo and Sibony (2010) · The case for behavioral strategy, McKinsey QuarterlyAcross 1,048 decisions, the decision process mattered more than the analysis by a factor of six.

The surveys report workplace experience; the research explains group-decision mechanisms. Neither measures Sikizana, whose benefits are objectives for evaluation against a baseline.