How Do You Measure a Company’s Decision Capacity?

05/08/2026

The KARAR-7 Management Scorecard

The general manager is facing another crowded agenda.

Sales is waiting for approval on a pricing exception. Procurement has escalated a supplier change. Operations is caught between capacity and a customer commitment. Human Resources is presenting a request for an additional position.

Everyone in the room is supposedly empowered. Yet almost every decision has arrived at the same desk.

The meeting runs long, the operation waits, and managers produce decision material instead of making decisions within their own domains. Meanwhile, the general manager spends time arbitrating daily issues rather than shaping the company's future.

"Is the company genuinely slow at making decisions, or has it concentrated its decision-making ability in the hands of a few people?"

Decision Speed Is Not Enough

Companies often measure decision capacity through elapsed time: How many days did the decision take? How long did approval wait? Did the meeting produce an answer?

These questions matter, but speed alone does not equal quality. A decision made with incomplete data, at the wrong organizational level, or outside defined authority can be extremely fast. It is equally misleading to measure a strategic investment and a routine purchasing exception against the same time target.

A fast decision and a rushed decision are not the same thing.

Decision capacity should be measured by whether decisions are made at the right level, with sufficient information, within defined authority, followed through in execution, and converted into organizational learning. Preparation time must also be separated from approval waiting time. The bottleneck is not always analysis; sometimes the decision is simply sitting in the queue of an executive who should not need to make it.

The Real Measure of Institutional Decision Capacity

In my earlier article, "If Every Decision Comes to You, Your Company Is Not Scaling," I argued that decision capacity cannot be built through task delegation or authority matrices alone. It requires a complete decision architecture: a decision inventory, decision levels, one accountable decision owner, authority corridors, decision data packages, escalation protocols, and a follow-up and learning rhythm.

When every decision reaches the owner, CEO, or general manager, the structure may appear tightly controlled. It may also reveal that the organization remains dependent on senior management.

Institutional decision capacity is not measured by how many decisions reach the top. It is measured by how many sound decisions can be made at the right level without reaching the top.

The objective is not to remove senior management from decisions. Strategic direction, major investments, high-risk matters, and irreversible choices should remain at the appropriate senior level. Repetitive, bounded, and reversible decisions should be resolved by the competent level closest to the work.

Decision Outcome and Decision Quality Are Not the Same

A well-prepared decision can produce a poor outcome because external conditions changed. A poorly prepared decision can produce a good outcome by chance.

A decision system therefore needs to be evaluated across three distinct layers:

Decision process: Was the decision made at the right level? Was there one clear owner? Were authority limits and required information defined?

Execution discipline: Did the decision become an action? Were ownership, timing, and resources clear? Was the decision diluted during implementation?

Outcome and learning: Did the expected effect materialize? Were the original assumptions valid? If the decision was reopened, was the cause poor analysis, weak execution, or a genuine change in conditions? Was the learning fed back into the system?

A strong decision system does not merely make decisions. It learns from them.

The Seven Areas KARAR-7 Must Measure

1. Decision Inventory

The recurring and critical decisions that shape company performance must be identified. The central question is simple: What proportion of our critical decisions is formally defined and classified?

2. Decision Level

Each decision should be resolved at the level appropriate to its strategic, tactical, or operational nature. When operational decisions repeatedly move upward, middle management becomes a communication layer rather than a management layer.

3. One Decision Owner

A decision may involve many contributors, but the final accountable owner must be clear. A structure in which everyone has a voice but no one has the final word produces meetings—not decisions.

4. Authority Corridor

The authority corridor defines the financial, commercial, operational, and people-related boundaries within which the decision owner can act. If the boundaries are unclear, managers either exceed them or escalate decisions they were already authorized to make.

As I emphasized in the Management Integrity Model, written authority and authority that can actually be exercised are not the same. Measurement must therefore examine where decisions are truly resolved and who can reverse them—not merely what the authority matrix says.

5. Decision Data Package

Authority cannot be delegated without access to information. The decision owner must be able to see the financial effect, cash impact, capacity implications, customer outcome, material risks, and genuine alternatives. The goal is not to collect the maximum amount of data. It is to provide the minimum reliable information capable of changing the decision, at the right time.

6. Escalation Protocol

Escalation should not become an escape route for managers who fear making a decision. It should activate when defined limits are exceeded, legal or ethical risk arises, strategic conflict appears, the effect is irreversible, or cross-functional dependencies cannot be resolved at the current level.

7. Follow-up and Learning Rhythm

Management does not end when a decision is announced. The decision must become action, be implemented, have its result verified, and generate learning. Otherwise, the decision is made in the meeting, altered in the field, and reopened a few months later.

Let's Pull a Rabbit Out of the Hat

Over the years, recurring decision bottlenecks, unnecessary escalations, unused authority, and meetings that produced no result led me to the same conclusion:

"A company's decision capacity cannot be measured only by the number or speed of its decisions."

That need led me to develop the KARAR-7 Management Scorecard.

The scorecard is not a replacement for KARAR-7. KARAR-7 designs the decision architecture; the KARAR-7 Management Scorecard measures the health of that architecture.

In my earlier article, "Not KPIs, but Decision Visibility," I argued that a metric becomes a management instrument only when it is connected to a chain of indicator, threshold, decision, action, and follow-up. The KARAR-7 Management Scorecard applies that principle to the company's decision architecture.

The scorecard evaluates all seven components together, but it does not surrender judgment to a single total score. A high aggregate score can hide a critical weakness. If decision ownership is unclear, information is unreliable, or outcomes are not followed through, strength elsewhere does not make the overall system healthy.

It therefore maintains two views:

System health shows how clearly the decision architecture is defined and how consistently it operates.

Decision-flow outcomes show how that architecture affects cycle time, escalation, execution, and senior-management workload.

The component weights, indicator formulas, scoring logic, alarm thresholds, critical entry conditions, and institutional implementation protocol form part of the detailed evaluation methodology and are not disclosed in this publication.

The purpose of the scorecard is not to grade managers. It is to make the bottlenecks in the company's decision system visible.

How Measurement Systems Break

When the scorecard becomes an individual performance contest, it begins to hide problems rather than expose them. Managers may stop escalating genuine risks, move faster with incomplete information, close decisions artificially, or optimize the score instead of improving the system.

Speed must therefore never be judged independently of decision level and information quality. Not every escalation is negative, and not every reopened decision represents failure. The instrument should improve the decision architecture, not punish the people operating inside it.

The First 90 Days

Days 0–30 — See the Decision Flow

Review the operational decisions escalated to senior management during the previous three to six months. Classify critical decisions as strategic, tactical, or operational. Separate preparation time from approval waiting time. Identify decisions that had no owner, had multiple owners, or were resolved at the wrong level.

Concrete output: A decision-flow map and the primary bottlenecks.

Days 31–60 — Build the Measurement System

Select a limited number of indicators for each KARAR-7 component. Define the data sources, ownership, and conditions that should trigger management attention. Build the first scorecard without confusing decision-process quality, execution discipline, and outcomes.

Concrete output: The first KARAR-7 Management Scorecard and the priority improvement areas.

Days 61–90 — Test Authority and Rhythm

Apply revised authority corridors in selected decision areas. Test the escalation protocol on real cases. Track the number of operational decisions reaching senior management, whether decisions are resolved at the right level, and whether they are executed as intended. Feed learning back into decision data packages, authority boundaries, and escalation rules.

Concrete output: A measurable, learning decision system with lower dependence on senior management.

"Which decisions can now be made reliably at the right level without reaching a senior executive?"

Conclusion

A company's scalability does not depend only on sales, production, talent, or financial capacity. Its decision system must also scale.

When every decision remains concentrated in a few hands, growth creates a new management bottleneck. Senior leaders work harder, but the organization does not become more capable of acting independently.

Real control is not approving every decision. It is being able to see the boundaries, information, and outcomes of decisions that do not pass through your desk.

That is the purpose of the KARAR-7 Management Scorecard: not to increase the number of decisions, but to make visible the system in which sound decisions can be made at the right level.

"A company does not scale at the speed of its leader. It scales at the speed of its decision system."

Editorial and Intellectual Property Note

This article is a general editorial management assessment. It is not an audit, valuation, or definitive performance assessment of any specific company, individual, executive, or governing body. It does not constitute legal, financial, tax, investment, technical, or organizational advice. Examples have been anonymized and generalized. External sources used are publicly available and were assessed as of the access date.

The KARAR-7 Scalable Decision Capacity Model—including its name, seven-component structure, sequence, definitions, relationships, and implementation design—was developed by Orkun Akçasarı.

The KARAR-7 Management Scorecard name, the mapping of measurement areas to the KARAR-7 components, the distinction between system health and decision-flow outcomes, the indicator architecture, component weights, formulas, scoring approach, alarm thresholds, critical entry conditions, and institutional implementation protocol are elements of an original body of work developed by Orkun Akçasarı. The full calculation and evaluation methodology is not disclosed in this publication.

Decision-making, governance, decision rights, authority, delegation, data quality, performance indicators, escalation, and organizational maturity are established concepts in management literature. No monopoly is claimed over abstract ideas or methods beyond what applicable law recognizes. Protection relates to the original text, arrangement, naming, classification, formulas, application design, and integrated presentation.

The article or any substantial part of the KARAR-7 Management Scorecard may not be reproduced, adapted, republished under another name, or used in commercial training, consulting, software, artificial intelligence systems, reports, presentations, assessment tools, or similar products or services without prior written permission.

Short quotations must identify the author, full article title, publication date, and active URL. Specialist legal advice should be obtained for registration, licensing, permissions, or intellectual-property disputes.

References

1. Rogers, Paul; Blenko, Marcia W. "Who Has the D? How Clear Decision Roles Enhance Organizational Performance." Bain & Company / Harvard Business Review, January 2006. Accessed August 5, 2026.

https://www.bain.com/insights/who-has-the-d-how-clear-decision-roles-enhance-organizational-performance/

2. International Organization for Standardization. "ISO 37004:2023 — Governance of Organizations — Governance Maturity Model — Guidance." November 2023. Accessed August 5, 2026.

https://www.iso.org/standard/65037.html

3. International Organization for Standardization. "ISO 37005:2024 — Governance of Organizations — Developing Indicators for Effective Governance." July 2024. Accessed August 5, 2026.

https://www.iso.org/standard/65038.html

Related Work by the Author

4. If Every Decision Comes to You, Your Company Is Not Scaling — Orkun Akçasarı

https://www.orkunak.com/l/yetki-devri-karar-alma-sistemi/

5. Not KPIs, but Decision Visibility: How to Build a Management Control System — Orkun Akçasarı

https://www.orkunak.com/l/kpi-degil-karar-gorunurlugu-yonetim-kontrol-sistemi/

6. The Powerless General Manager: The Management Integrity Model — Orkun Akçasarı

https://www.orkunak.com/l/yetkisiz-genel-mudur-yonetim-butunlugu-modeli/

7. The Seven Dimensions of Reading a Company — Orkun Akçasarı

https://www.orkunak.com/orkun-akcasari-nin-sirket-okuma-metodolojisi/

8. Management Notes — Orkun Akçasarı

https://www.orkunak.com/yonetim-masasindan-notlar/

Primary experiential basis: The personal experience, field observations, management assessments, and implementation results in this article are based on the author's professional experience, verified career records, and unpublished working files.