How Many People Have to Say Yes Before Anything Gets Done?

There is a question worth asking in your next leadership meeting, and it is deceptively simple: how many individual approvals does it take to launch a new initiative at your company? Not a major acquisition. Not a regulatory filing. A standard, mid-level business decision — a new vendor contract, a revised pricing structure, a change to an existing workflow.

For many organizations, the honest answer is uncomfortable. Four people. Six. Sometimes more. And buried inside that number is one of the most underappreciated competitive disadvantages in business today.

Speed is a strategic asset. When your internal decision-making machinery runs slower than the market moves, you do not just miss opportunities — you cede ground to competitors who have figured out how to move faster. The approval bottleneck is rarely the result of bad intentions. It is typically the accumulated consequence of risk aversion, organizational politics, and process design that was never revisited after it was first established.

Where Decisions Actually Go to Die

Before any organization can fix its approval process, it needs an accurate picture of where decisions stall. The instinct is to blame individuals — the executive who sits on emails, the department head who demands to review everything. But the root cause is almost always structural.

Consider these diagnostic questions:

• Who has formal authority versus who has informal veto power? In many companies, these are entirely different people. A decision may technically require three sign-offs, but in practice, a fourth stakeholder's objection can restart the entire process.
• At what point in the review cycle do decisions most frequently pause? Track actual timelines, not estimated ones. The gap between the two is usually illuminating.
• How many of your approvals are additive versus redundant? If two different reviewers are evaluating the same risk from the same information set, one of those reviews is not adding value.
• What happens when a decision-maker is unavailable? If the answer is "it waits," you have a single point of failure embedded in your operations.
• Are approval thresholds documented and consistently applied? Ambiguity about who can authorize what creates a gravitational pull toward over-escalation.

The answers to these questions will typically reveal that the bottleneck is not located where leadership assumes it is.

The Real Cost of Slow Sign-Offs

It is worth quantifying what approval delays actually cost, because organizations rarely do this with any rigor.

First, there is the direct cost of delayed execution. A vendor contract that takes six weeks to approve instead of two represents four weeks of unrealized value — whether that is operational efficiency, revenue, or risk reduction.

Second, there is the opportunity cost of the decision-makers themselves. Every hour a senior leader spends reviewing a decision that falls below their appropriate authority threshold is an hour not spent on strategy, client relationships, or organizational development. Multiply that across a year and the number becomes significant.

Third, and perhaps most damaging, is the cultural cost. When employees learn that decisions move slowly regardless of urgency, they stop treating speed as a value. Initiative atrophies. People wait to be told rather than acting with confidence. The organization becomes reactive by default.

What Streamlined Looks Like in Practice

One mid-sized logistics firm in the Midwest recognized that its procurement approvals were running an average of 23 business days — nearly a full month — for contracts under $50,000. After mapping its actual approval chain, the team discovered that four of the seven required sign-offs were duplicative: different stakeholders reviewing identical information with no differentiated perspective to add.

The company redesigned its approval matrix by first establishing clear dollar thresholds tied to defined authority levels, then eliminating review steps that lacked a distinct evaluative purpose. Within one quarter, average approval time dropped to eight business days. More importantly, the senior leaders who had been pulled into routine reviews were freed to focus on decisions that genuinely warranted their attention.

A regional healthcare technology company faced a different version of the same problem. Its product team was losing feature releases to competitors consistently — not because of development capacity, but because the internal sign-off process for go-to-market decisions involved stakeholders from seven different departments. The company implemented a tiered decision model: a small, empowered core team could approve standard releases autonomously, while a broader coalition was reserved for decisions with cross-functional risk. Release cycles accelerated by 40 percent within two quarters.

Neither of these outcomes required a dramatic organizational restructuring. They required an honest audit and the willingness to act on what the audit revealed.

Distinguishing Necessary Oversight from Bureaucratic Weight

Not all approvals are waste. Some oversight is genuinely necessary — legal review of contracts, financial authorization for capital expenditures, compliance checks in regulated industries. The goal is not to eliminate accountability. It is to ensure that accountability is applied at the right level, by the right people, with a clear purpose.

A practical framework for making this distinction involves three questions for each approval step in your process:

1. What specific risk does this review step mitigate? If the answer is vague or amounts to "general awareness," the step may not be earning its place in the process.
2. Is this person uniquely positioned to evaluate that risk? If the same risk is being assessed by multiple reviewers without differentiated expertise, consolidation is likely possible.
3. What is the cost of removing this step if something goes wrong, versus the cost of maintaining it if nothing does? This is a straightforward expected-value calculation that most organizations skip entirely.

Applying this lens systematically to your existing approval workflows will surface both the steps worth keeping and the ones that exist primarily out of habit.

Building an Organization That Can Actually Decide

The companies that move fastest are not the ones that take the most risks. They are the ones that have designed their internal processes to match the tempo of their markets. Approval velocity is a discipline, not an accident.

Start with a complete map of your current decision pathways — not the official org chart version, but the real one, reconstructed from how decisions actually move. Identify the three or four decisions your organization makes most frequently and measure how long each step takes. Then ask whether that timeline is a function of necessary diligence or accumulated procedural inertia.

The answer will tell you more about your competitive position than most strategy documents ever will.