Decision as Communication

Niklas Luhmann articulated an idea that fundamentally shifts how decisions in organizations are understood: Decisions are not mental acts that occur inside the head of an executive. They are communicative events within the social system. A decision exists only once it is communicated — and it takes effect only in the way it is communicated.

Strategic Relevance

For leadership teams, this perspective carries far-reaching consequences. The quality of a decision is not measured solely by the rigor of the analysis that preceded it. It is measured by whether the organization recognizes the decision as such, understands it, and can process it in a connectable way. A brilliant strategic decision made within the leadership circle but never clearly communicated is organizationally ineffective. It simply has not happened.

This explains a phenomenon familiar to many leadership teams: the conviction that a decision was made long ago — while the organization continues to wait, interpret, or work in different directions. The reason is not a lack of execution capability but the confusion of opinion-forming with deciding. As long as a preference is not communicated into the organization as a decision, it remains without consequence.

Common Misconceptions

A widespread oversimplification is to think of decisions as moments — as the single instant when someone internally says yes or no. In reality, organizational decisions are communication processes that unfold across meetings, documents, and conversations. The supposed decision moment is often merely the point at which communication becomes condensed.

Equally misleading is the assumption that decisions must primarily be rationally justified in order to be effective. In systems theory, what matters is not the rationality of the justification but the connectivity of the communication. A decision that is organizationally understood and processed further is more effective than one that is logically unassailable but communicatively disconnected. The notion that better arguments automatically lead to better decisions underestimates the role of decision premises — the structures that determine which communication even qualifies as a decision.

Decision Architecture Perspective

From the perspective of decision architecture, the question is not only who decides but how decisions are communicatively produced. What formats exist to make decisions visible? Are there clear distinctions between discussion, opinion-forming, and decision? Do all participants know when a decision has been made — and when it has not?

Designing this communicative infrastructure is a central lever against decision gridlock. Organizations that lack clear formats for decision communication systematically produce ambiguity: meetings end without a recognizable decision, minutes document discussions rather than commitments, and the organization is left guessing what now applies. Decision design therefore begins not with analytical tools but with the question of how an organization makes decisions visible as communication.

Distinction

Decision as communication is neither a technique nor a framework. It is a theoretical perspective that directs attention to what actually happens in organizations — as opposed to what org charts and process descriptions suggest. The concept differs fundamentally from psychological decision models such as System 1 / System 2, which locate decisions as cognitive processes within the individual. It is not an action guideline but an analytical tool — and precisely for that reason strategically relevant.