When Leaders Become the Decision System

Archive note: Originally published on LinkedIn on March 2, 2026. This article is preserved here as part of the evolution of our thinking on uncertainty, decision architecture, and the conditions under which leadership becomes the system itself.

Decisions are the foundation of every organization.

Strategy is not a document. Strategy is a sequence of decisions made under uncertainty. Structure is not an org chart. Structure is the pattern of who decides - and how.

Culture is not a set of values on a wall. Culture is the recurring way conflicts are resolved when certainty disappears.

That is why any serious analysis of an organization must begin with one question:

What is a decision - and how does it actually happen?

As early as the mid-20th century, management theory sought to systematize different levels of decision-making.

Robert N. Anthony (1965) distinguished between:

Igor Ansoff (1965) introduced a similar distinction between strategic, administrative, and operational decisions. Mintzberg, Raisinghani, and Théorêt (1976) differentiated between structured, semi-structured, and unstructured decisions. Herbert Simon (1960) distinguished between programmed and non-programmed decisions.

Across these models, the logic is consistent:

Operational Decisions

Routine, repetitive, with clear cause-and-effect relationships. Here, rationality is procedural. Rules exist. Standards exist.

Tactical Decisions

They translate strategy into action. They require expertise and analysis. Cause and effect are identifiable - but not trivial.

Strategic Decisions

They determine direction, positioning, and organizational identity. Their consequences are long-term, often difficult to reverse, and deeply intertwined with environmental uncertainty.

This classification is useful. But it conceals a deeper issue. Because categorizing decisions tells us nothing about how people actually decide.

Traditional rational choice theory rests on a simple assumption:

A decision-maker selects the alternative with the highest expected outcome.

James G. March articulates it clearly: “Decision makers are assumed to choose among alternatives on the basis of their expected consequences, but those consequences are not known with certainty.” (March, 1994)

In other words: We do not know the future. But we estimate probabilities. It is an elegant construct.

Yet Herbert Simon (1955; 1960) introduced the concept of bounded rationality.

Human beings:

Instead of optimizing, they “satisfice” - they choose an option that is good enough. In operational decisions, that is often sufficient. In tactical decisions, expertise can reduce uncertainty. But in strategic decisions, the problem is deeper. Because not only are probabilities unknown - the structure of the problem itself is often shifting.

Frank Knight (1921) made an early and critical distinction between:

Most strategic decisions do not live in the domain of risk. They live in the domain of uncertainty. This means that expected value models become insufficient. The decision is no longer a calculation. It becomes an interpretation.

Organizations do not decide. People do.

And people:

In strategic decisions, more than analysis is activated:

March and Olsen (1976) demonstrated that organizational decisions are often not the result of a linear rational process, but resemble a “garbage can model,” where problems, solutions, and participants enter the process at different times.

In other words:

Decisions are frequently the outcome of interaction - not calculation.

This is where modern organizations encounter a structural weakness.

Although they distinguish between strategic, tactical, and operational decisions, they often apply the same decision pattern to all three.

Operational decisions become overanalyzed. Tactical decisions become politicized. Strategic decisions are forced into analytical certainty. But certainty does not exist in the strategic domain. What exists is the capacity to move through uncertainty.

When this contextual difference is not recognized, organizations:

When we examine a single decision, we see an outcome. When we examine decision patterns, we see architecture. This is where complexity becomes a test. It does not test the intelligence of leaders. It does not test analytical capability.

It tests whether the organization can distinguish between:

And it tests whether the organization has a decision architecture that is context sensitive. Without it, every strategic decision becomes the personal burden of a leader. That is not a question of competence. It is a question of design.

Anthony, R. N. (1965). Planning and Control Systems: A Framework for Analysis. Harvard Business School.

Ansoff, H. I. (1965). Corporate Strategy. McGraw-Hill.

Kahneman, D., & Tversky, A. (1979). Prospect Theory: An Analysis of Decision under Risk. Econometrica, 47(2), 263–291.

Knight, F. H. (1921). Risk, Uncertainty and Profit. Houghton Mifflin.

March, J. G. (1994). A Primer on Decision Making: How Decisions Happen. Free Press.

March, J. G., & Olsen, J. P. (1976). Ambiguity and Choice in Organizations. Universitetsforlaget.

Mintzberg, H., Raisinghani, D., & Théorêt, A. (1976). The Structure of “Unstructured” Decision Processes. Administrative Science Quarterly, 21(2), 246–275.

Simon, H. A. (1960). The New Science of Management Decision. Harper & Row.

Simon, H. A. (1955). A Behavioral Model of Rational Choice. Quarterly Journal of Economics, 69(1), 99–118.