What does it mean that distributed decision-making?

Moving decisions to the people closest to the information improves both speed and quality. Centralized decision-making creates a fundamental information problem: the person with the authority to decide is not the person with the best information about the situation. Every level of hierarchy that a decision must traverse adds delay (the decision waits in someone's queue), distortion (the information is simplified or filtered as it moves upward), and distance (the decision-maker lacks the contextual nuance that the person closest to the situation possesses). Distributed decision-making solves this problem by moving authority to where the information already is — but it requires infrastructure to maintain coordination.

Example: An e-commerce company, Relay, processed all pricing decisions through a central pricing committee — three senior leaders who met weekly to review and approve pricing changes for the company's 12,000 products. The process was thorough but slow: pricing requests waited an average of 9 days for committee review, and 40% were sent back for additional analysis because the committee lacked the product-specific context to evaluate the request. Meanwhile, competitors adjusted prices in real time. The company redesigned decision rights by creating three tiers. Tier 1 (automated): algorithmic pricing for commodity products based on competitor data and margin rules — no human decision required. Tier 2 (distributed): product managers could adjust pricing within defined parameters (margin floor, maximum discount percentage, competitive positioning rules) without approval. Tier 3 (committee): only strategic pricing decisions (new product launches, market-entry pricing, bundle strategies) required committee review. The result: average pricing decision time dropped from 9 days to 4 hours, pricing accuracy improved (product managers had better market knowledge than the committee), and the committee focused its attention on the strategic decisions where its cross-product perspective added genuine value. Total decisions processed by the committee dropped from 200 per week to 15 — but those 15 were the ones that actually needed centralized judgment.

Try this: Audit one week of decisions in your team or organization. For each decision, record: (1) Who made the decision? (2) Who had the most relevant information? (3) How long did the decision take from request to resolution? (4) How much of that time was active analysis versus waiting in queues? (5) Was the decision sent back for revision? If so, why? After the audit, categorize each decision into three tiers: Tier 1 — decisions that could be automated or rule-based (clear criteria, low variability, low risk). Tier 2 — decisions that could be distributed to the person with the best information (moderate complexity, bounded risk, clear parameters). Tier 3 — decisions that genuinely require centralized judgment (cross-cutting impact, strategic significance, high ambiguity). Calculate the percentage of current centralized decisions that could move to Tier 1 or Tier 2. In most organizations, this percentage is above 70%.