One of the COO's most valuable jobs is reducing organizational fog.
Fog appears when people are busy, meetings are frequent, updates are polished, and yet nobody is quite sure who can make which decision. Work moves, but decisions do not. Teams align, then realign. Leaders leave meetings with different interpretations. Escalations happen late. Tradeoffs are implied instead of chosen.
The company does not feel broken. It feels cloudy.
A great COO clears fog by designing decision flow.
Decision rights are operating infrastructure
Companies usually under-design decision rights because early-stage decision-making feels obvious. The founder decides. The small team discusses. The loudest context wins. Everyone knows who has taste, who has authority, and who must be consulted.
At scale, that breaks.
More functions have legitimate stakes. More decisions have second-order effects. More leaders own pieces of the outcome. More teams have partial information. More people can say no, delay, or reopen the issue. Authority becomes a social negotiation instead of an operating design.
Decision rights are not bureaucracy. They are infrastructure for speed. They also protect trust: people can accept hard calls more easily when they understand who had the authority to make them and how input was weighed.
A decision-rights system answers:
- Who owns the decision?
- Who must provide input?
- Who has veto rights, if anyone?
- What information is required?
- What tradeoff is being made?
- When does the decision need escalation?
- How is the decision communicated?
- How is follow-through inspected?
When these questions are unclear, the company pays a tax in meetings, politics, rework, and slow escalation.
The COO is not the decider for everything
A weak COO implementation centralizes decisions. People are unsure who owns something, so they bring it to the COO. The COO gets context, arbitrates, and moves the work forward. Everyone feels relieved.
Then it happens again.
Soon the COO is the organization's decision router. Nothing important moves without them. Leaders become less accountable because unresolved tradeoffs can always be elevated. The COO becomes overwhelmed, and the company mistakes dependency for operating discipline.
The COO's job is not to decide everything. The COO's job is to make the decision system legible enough that decisions happen at the right level.
Sometimes that means the COO decides. Sometimes it means the COO forces a functional leader to decide. Sometimes it means creating a forum. Sometimes it means clarifying that a decision is actually the CEO's. Sometimes it means removing a fake veto.
The goal is not COO control. The goal is decision throughput with accountability.
Map the recurring decisions
Decision-rights work should start with the decisions that repeatedly create drag.
Examples:
- Which customer commitments can sales make without product approval?
- Who decides whether an enterprise feature goes on the roadmap?
- Who owns pricing exceptions?
- Who decides hiring tradeoffs when headcount is constrained?
- Who can change launch dates?
- Who owns implementation scope when customer success, sales, and product disagree?
- Who decides whether a strategic initiative gets delayed?
- Who can approve exceptions to process?
- Who decides when to sunset a product, segment, or internal system?
- Who owns the tradeoff between margin and customer experience?
These are not abstract governance questions. They are where operating reality happens.
The COO should identify the top recurring decision bottlenecks and map them visibly. If a decision happens often, has meaningful consequences, and repeatedly creates confusion, it deserves design.
Separate input from authority
Many companies confuse being consulted with having decision rights.
A function may need to provide input because it has expertise, risk visibility, or implementation responsibility. That does not mean it owns the final call. When input rights become hidden veto rights, decisions slow down and accountability blurs.
The COO should make the difference explicit.
For each recurring decision, define:
- Decision owner: accountable for the final call.
- Required input: people or functions whose perspective must be considered.
- Approver: person or body with formal approval rights, if different from the owner.
- Escalation path: where the decision goes if tradeoffs exceed the owner's authority.
- Communication audience: who needs to know the decision and why.
This prevents the common pattern where everyone believes they were promised authority because they were invited into the conversation.
Escalation should be designed, not improvised
Escalation is not failure. Bad escalation is failure.
Healthy escalation happens early, with clear options, visible tradeoffs, and a decision request. Unhealthy escalation happens late, wrapped in politics, after teams have already committed to incompatible paths.
The COO should define escalation standards:
- Escalate when the decision crosses resource, customer, legal, brand, strategic, or executive-priority thresholds.
- Escalate when two accountable owners have a real tradeoff they cannot resolve inside delegated authority.
- Escalate with options, consequences, recommendation, and deadline.
- Do not escalate vague discomfort, preference conflicts, or work that the owner is avoiding.
- Do not escalate privately around the accountable owner.
A good escalation system protects both speed and judgment. It lets teams move independently until the decision genuinely belongs higher up.
Decision rights need maintenance
Decision rights age.
A decision that belonged to the CEO at 50 people may belong to a VP at 300. A decision that belonged to a function may become cross-functional as the product matures. A pricing exception that was rare may become common enough to require policy. A compliance threshold may change after enterprise customers arrive. A new executive may alter the boundary between functions.
The COO should treat decision rights as living architecture.
Review decision friction periodically:
- Which decisions are repeatedly escalated?
- Which forums debate but do not decide?
- Where do leaders claim unclear ownership?
- Where are decisions reopened after commitment?
- Where do teams wait for permission they do not actually need?
- Where are decisions being made by people without accountability for consequences?
- Which decisions have become too slow for the business environment?
Decision-rights maintenance is one of the least glamorous and highest-leverage COO practices.
Tradeoffs must be named
Most decision fog is really tradeoff avoidance.
The company wants speed and quality, customization and scalability, customer responsiveness and roadmap focus, hiring growth and burn discipline, autonomy and consistency, local optimization and company-level priorities.
The COO helps by naming the tradeoff instead of letting it hide inside process.
A clear decision conversation sounds like:
- “We can protect the launch date or include the enterprise requirement, but not both.”
- “We can accept margin pressure for this segment, or we can hold the model and lose some deals.”
- “We can give regions autonomy, or we can enforce global consistency. Which matters more for this decision?”
- “We can keep this initiative alive, but only by delaying one of the top three priorities.”
Once the tradeoff is visible, the right owner can decide.
Build a decision spine for strategic work
For each major priority, the COO should make the decision spine explicit:
- the few decisions that determine success;
- the accountable decision owner for each;
- required inputs and vetoes, if any;
- escalation trigger and escalation forum;
- deadline for the decision;
- communication path after the decision;
- owner for inspecting follow-through.
This prevents the common failure where an initiative has a named owner but no clear authority over the decisions that matter. Ownership without decision rights is theater.
The COO's decision-flow audit
A COO should be able to answer five questions about the company's decision system:
- What are the ten recurring decisions that most often slow execution?
- Who owns each one today?
- Which ones are being decided at the wrong level?
- Which ones lack clear input, approval, or escalation rules?
- Which tradeoffs are being avoided through ambiguity?
If those answers are unclear, the company is operating in fog.
Clearing that fog may not look dramatic. It may look like fewer meetings, cleaner escalations, faster tradeoffs, less triangulation, and more leaders taking real ownership.
That is COO work at its best: not making every decision, but making the company capable of deciding.
