Every company has a metabolism.
It is the rate at which the company senses reality, makes decisions, allocates resources, executes commitments, learns from outcomes, and adapts. Some companies metabolize quickly: signal moves, decisions happen, resources shift, and learning changes behavior. Others metabolize slowly: information pools in functions, risks surface late, decisions wait for meetings, plans age quietly, and resources stay attached to yesterday's priorities.
The COO is often the executive responsible for company metabolism. That responsibility is not about making the company busier. It is about shortening the distance between reality and response.
Not cadence alone. Not meetings alone. Metabolism.
Cadence is only one part of metabolism
Operating cadence matters, but cadence is not the same as metabolism. A company can have many meetings and still metabolize slowly. It can review dashboards weekly and still learn nothing. It can run quarterly planning and still fail to make real tradeoffs.
The question is not “Do we have a rhythm?” The question is “Does the rhythm move reality through the company fast enough to change decisions and behavior?”
A useful operating rhythm has five jobs:
- Surface reality.
- Interpret what it means.
- Decide what changes.
- Assign ownership and resources.
- Inspect follow-through.
If any step is missing, the cadence becomes theater.
The COO should look at every recurring forum and ask: what metabolism does this create? Does it speed up sensing, deciding, allocating, executing, or learning? Or does it simply let the organization perform attentiveness?
Reality sensing is the starting point
A company cannot metabolize what it cannot sense.
Reality sensing includes metrics, but it is broader than dashboards. It includes customer complaints, sales friction, support patterns, implementation delays, employee confusion, manager workarounds, product quality signals, financial variance, forecast misses, legal exceptions, churn narratives, and operational anomalies.
The COO's job is to make sure this signal reaches the right altitude without becoming noise.
Too little signal and executives are surprised. Too much raw signal and executives drown. The operating system needs filters that preserve meaning.
Good reality sensing asks:
- What changed?
- Why did it change?
- Is this a one-off, pattern, or structural issue?
- Who owns the response?
- What decision, if any, is needed?
- What should we stop believing?
A great COO is often the company's reality sensor. They notice when metrics and stories diverge, when leaders are overconfident, when a plan depends on assumptions nobody has tested, or when frontline workarounds reveal a broken operating model.
Decision speed determines metabolic speed
Signal without decisions creates frustration.
Many organizations are good at noticing problems and bad at deciding what to do about them. They escalate, discuss, document, align, socialize, and revisit. The issue becomes familiar before it becomes resolved.
The COO should inspect decision latency:
- How long does it take from problem detection to decision?
- Which decisions wait for the wrong forum?
- Which decisions require too many approvers?
- Which leaders avoid tradeoffs by asking for more analysis?
- Which issues get renamed instead of resolved?
Not every decision should be fast. Some decisions are consequential and deserve thought. But many operating decisions rot while waiting for ceremonial alignment.
The COO improves metabolism by matching decision speed to decision type.
Resource allocation is metabolism in numbers
The company reveals its real priorities through resources.
If strategy changes but people, budget, roadmap capacity, executive attention, and incentives do not, the metabolism is blocked. The company has intellectually accepted a new direction without physically moving toward it.
The COO should connect operating reviews to resource movement. When signal shows that a priority is under-resourced, the question should not be “Who can work harder?” It should be “What are we willing to move, stop, delay, or de-scope?”
This is where COOs must be willing to create discomfort. Resource allocation is tradeoff made visible. Teams will often prefer aspirational overload to explicit subtraction.
A strong COO keeps asking: if this matters, what changes?
Operating debt slows metabolism
Operating debt is the accumulation of decisions, processes, systems, meetings, roles, reports, workarounds, and assumptions that once helped but now slow the company down.
Examples:
- a planning process designed for 80 people still used at 800;
- approval rules created after one bad incident and never removed;
- dashboards nobody trusts but everyone maintains;
- meetings that exist because of historical anxiety;
- custom customer commitments that break scalability;
- role boundaries built around former employees;
- internal tools that require manual reconciliation;
- parallel metrics used by different functions;
- escalation paths that depend on personal relationships.
Operating debt is dangerous because it feels like normal work. People adapt to it. They create rituals around it. They stop noticing the drag.
The COO should run periodic operating debt reviews. Ask leaders: what slows us down that no longer creates enough value? Which process exists because we do not trust the system? Which meeting would we not create again? Which exception has become the business model? Which manual workaround is hiding structural failure?
Then retire, redesign, or reassign the debt.
Operating debt has signatures
Operating debt is the accumulated cost of decisions the company did not make, systems it did not build, interfaces it left vague, and exceptions it normalized. It shows up as:
- recurring escalations with no root-cause owner;
- metrics that are debated more than acted on;
- planning commitments that everyone knows are overstuffed;
- customer exceptions that become the real process;
- executives using private channels to get decisions unstuck;
- resources attached to priorities the company no longer believes;
- managers inventing local workarounds because the official operating model is too slow.
The COO should treat operating debt like product debt: not all of it must be fixed now, but the company should know which debt is slowing metabolism and which debt is becoming dangerous.
Metabolism changes by stage
At 30 people, metabolism is mostly proximity. The risk is chaos, not bureaucracy. The COO should add just enough rhythm to prevent avoidable misses.
At 300 people, metabolism depends on cross-functional flow. The risk is fragmentation. The COO should design forums, decision rights, metrics, and initiative ownership that connect functions without centralizing everything.
At 3,000 people, metabolism depends on enterprise architecture. The risk is slow governance, stale plans, and layers of filtered reality. The COO should simplify decision paths, preserve local ownership, and ensure executive forums receive honest signal rather than sanitized narratives.
The same process can be discipline at one stage and debt at another.
The metabolism audit
A COO can audit company metabolism with six questions:
Sensing: How quickly do important signals reach accountable leaders?
Interpretation: Do forums distinguish noise from pattern and symptom from cause?
Decision: Are decisions made at the right level with enough speed?
Allocation: Do resources move when priorities or reality change?
Execution: Are commitments translated into owners, dates, dependencies, and standards?
Learning: Does the company change behavior based on outcomes, or merely discuss them?
If the answer is weak in any area, the COO has work to do.
The goal is not to make the company frantic. High metabolism is not constant motion. It is the ability to absorb reality and respond with appropriate speed.
A great COO designs the company so reality does not have to scream before it is heard.
