Decision-making domain: Who has the right to make decisions?
Brief
One decision domain is the area within which an individual, group, or organizational function has the authority to make decisions. The concept does not primarily deal with competence or knowledge, but with legitimate decision-making power. The question is not ”who can make the decision?” but ”who has the mandate to make the decision?”. Decision-making domains constitute one of the most fundamental, yet often least explicitly defined, components of organizations. They affect speed, accountability, innovation, risk management, conflict levels, and ultimately the organization’s ability to achieve its goals. In practice, decision-making domains can be:
- Strictly defined (e.g., only the finance manager can approve investments exceeding 1 MSEK).
- Shared or overlapping (several roles participate in the same decision).
- Indecisive or implicit (the decision is made by whoever happens to be the most senior, loudest, or most available).
When decision-making domains are clear, the uncertainty about who decides what decreases. At the same time, there is the risk that the organization becomes slow and bureaucratic. When the domains are unclear, greater flexibility and creativity often arise, but also conflicts, duplication of effort, and irresponsibility. A key insight in organizational design is that Responsibility and decision-making must be linked. It is difficult to hold someone responsible for an outcome if the person did not have the mandate to influence the decision. Similarly, problems often arise when people have the mandate to make decisions but are not held accountable for the consequences. The concept of decision-making domain occurs in several related areas:
- Organizational design
- Corporate governance (governance)
- Leadership
- Risk management
- System theory
- Military leadership
- Agile organizations
A useful way to understand decision domains is to view the organization as a network of interconnected decisions. Each organizational level exists in practice to handle certain types of decisions:
| Level | Typical decisions |
| Board of Directors | Strategic direction, risk appetite |
| Management | Priorities, investments |
| Middle management | Resource allocation, planning |
| Team | Operational decisions |
| Individual | Implementation and local elections |
The problem arises when this structure is not clear. Two extreme situations illustrate this:
Extreme 1: Centralization
No one is allowed to make decisions outside their domain. Any deviations must be escalated upwards. Results:
- Slow decisions
- Many bottlenecks
- Weak adaptability
- A small local initiative
Extreme 2: Full decision-making anarchy
Everyone considers themselves entitled to make all decisions. Result:
- Conflicts
- Conflicting decisions
- Political power struggle
- Unclear responsibility
Effective organizations therefore try to establish clear decision-making domains but at the same time create mechanisms for collaboration across domain boundaries. This article focuses specifically on three issues:
- What happens when decision-making domains are strictly allocated?
- What happens when decision-making domains are unclear or non-existent?
- What happens with responsibility and learning when something goes wrong, especially in unexpected events and so-called ”Black Swans”?
History
Decision-making domains have existed as long as people have organized themselves, but they were formalized only during industrialization.
Weber and the bureaucracy
The sociologist Max Weber In the early 1900s, he described how modern organizations are built around clear hierarchies and formal responsibilities. The basic idea was simple: Each role should have defined responsibilities, defined authority, and defined reporting channels. This created predictability and control.
Scientific Management
Frederick Taylor's ideas about division of labor reinforced the view that decisions would be made at higher levels while execution would take place at a lower level. The result was very clear decision-making domains but often low flexibility.
Knowledge organizations
In the late 20th century, the realization grew that employees are often closest to the knowledge. This led to:
- Delegation
- Self-governing teams
- Agile working methods
- Distributed decision-making
The focus shifted from control to ability.
Application
Strictly defined decision domains
When decision-making domains are very clear, everyone knows:
- who decides,
- who is consulted,
- who is informed.
Examples:
- The IT department decides on the technical architecture.
- Law determines the interpretation of agreements.
- The economic department decides on budget frameworks.
Advantages
- Quick allocation of responsibilities
- Lower level of conflict
- High predictability
- Unified decisions
Disadvantages
- Bottleneck
- Lower innovation
- Risk of silos
- Local problems must be escalated
Organizations can be robust but slow.
Indecipherable decision-making domains
Here often a phenomenon occurs that can be called:
”Mandate through initiative”
Whoever acts first becomes the decision-maker. Initially, this may seem effective, but in the long run, the result is:
- Conflicting decisions
- Two initiatives
- Internal conflicts
- Power struggle
A common symptom is that the same question is discussed repeatedly because no one really knows who owns the decision.
Responsibility diffusion
Psychologists talk about ”diffusion of responsibility”. When many people share responsibility, the result is often that no one feels full responsibility. The classic expression is:
”Everyone is responsible for the issue.”
which often means:
”No one is responsible for the issue.”
What happens when something goes wrong?
Here the decision-making domain becomes particularly important. Suppose a project fails, and then three questions arise:
- Who made the decision?
- Who had the mandate?
- Who had the information?
If these three people are the same individual, the responsibility is often easy to identify, but in many organizations they are different people.
Examples
- The management makes the decisions.
- The project manager implements it.
- The specialist is aware of the risks.
- When the project fails, blame games often arise.
The problem is that the decision-making domains and the information domains did not coincide.
Demand for responsibility
A mature organization distinguishes between:
- Responsibility for the outcome – You are responsible for the outcome.
- Decision-making responsibility – You are responsible for the decision.
- Process responsibility – You are responsible for how the decision was made.
Many conflicts arise because these three are confused.
- A decision may be well-founded but still lead to a bad outcome.
- A decision may be bad but may turn out to be a good outcome.
Accountability should therefore focus on decision quality rather than solely on results.
Black Swans and decision-making domains
The concept Black Swan, coined by Nassim Nicholas Taleb, describes events as:
- They are very rare.
- Has a great impact.
- Explained afterwards as if they were predictable.
Examples:
- The financial crisis of 2008
- Covid-19 pandemic
- Major cyberattacks
- Geopolitical shocks
Black Swans challenges the entire idea of decision-making domains. Why? Because no one can reasonably have full knowledge of an event that does not yet exist in the organization’s mental model.
The trap of hindsight
When a Black Swan occurs, there is often a demand to find the culprit. Organizations then begin to reconstruct the history. They identify:
- missed signals,
- warnings,
- alternative routes of action.
The result often becomes an illusion: That someone should have understood. But the very definition of a Black Swan means that the event was outside the normal decision-making framework. This creates an important principle: Not all extreme negative outcomes are the result of bad decisions.
Ecosystem
Decision-making domains are strongly influenced by several neighboring areas:
- Governance – Describes how decision-making is distributed.
- Risk Management – Defines which risks are acceptable.
- RACI models – Specify:
- Responsible
- Accountable
- Consulted
- Informed
- Sociotechnical systems – Studies how people and technology together shape decisions.
- Agile methods – Emphasizes local autonomy combined with common goals.
Practical examples
Example 1: Strict domain
A bank requires that all credit decisions over 10 million kronor be made by a special credit committee. Effect:
- Fewer erroneous credits.
- High traceability.
- Slower business.
Example 2: Unclear domain
A product company has no formal ownership of product prioritization. Results:
- The sales organization promises customer features.
- The development team prioritizes technology debt.
- Product management prioritizes strategy.
Consequence: Continuous conflicts and low delivery capacity.
Summary
Decision-making domains are ultimately about organizing power, responsibility, and the ability to act. A well-functioning organization is characterized not by maximal centralization or maximal freedom, but by a carefully considered balance between clarity and autonomy. The most important principle is:
The person held responsible should also have corresponding decision-making authority.
Strictly defined decision-making domains provide clarity, control, and traceability. They reduce conflicts and facilitate accountability. At the same time, they risk creating bureaucracy, bottlenecks, and slow adaptation. Unclear decision-making domains provide flexibility and initiative but tend over time to generate conflicts, duplication of effort, and the diffusion of responsibility. When something goes wrong, decision-making domains function as the organization’s ”forensic map.” They enable understanding:
- who made the decision,
- why the decision was made,
- what information was available.
In extreme or unexpected events, especially Black Swans, it becomes even more important to distinguish between:
- bad decisions,
- poor outcomes,
- genuine uncertainty.
An organization that punishes all negative outcomes risks creating fear and inaction. An organization that never holds anyone accountable risks instead a lack of accountability. The mature organization therefore focuses on the quality of the decision-making process rather than solely on the outcome.
Advantages
- Clear responsibility
- Higher decision quality
- Lower level of conflict
- Better risk management
- Easier learning after mistakes
Disadvantages, risks and limitations
- Excessive centralization
- Bottleneck
- Reduced innovation
- Warehouse behavior
- False security in the face of extreme events
Five readiness questions
- Is it clear who owns every critical decision in the organization?
- Does the decision-making mandate follow the same structure as the accountability requirement?
- Are there mechanisms in place to handle decisions that span multiple domains?
- Is major decisions documented so that they can be evaluated afterwards?
- Can the organization distinguish between bad decisions and bad outcomes in unexpected events?
Recommendation
In knowledge organizations and organizations driven by forces but innovation, the decision-making domain may be defined as:
A decision-making domain is not primarily a way to distribute power, but a way to create accountability in the face of uncertainty. Organizations rarely fail because decisions are made at the wrong level, but because no one knows who actually owned the decision when the consequences emerge.
