COOs are often asked to “create more accountability.”

It sounds simple. It is not.

In many companies, accountability becomes bureaucracy wearing a serious face. More status meetings. More dashboards. More reporting templates. More approvals. More check-ins. More process around why work is late. Everyone becomes better at explaining work, not necessarily better at doing it.

A great COO creates accountability without turning the company into a compliance machine.

The goal is not to make people feel watched. The goal is to make commitments clear, tradeoffs visible, ownership real, and follow-through reliable. Accountability is an operating design problem before it is a performance-management problem.

Accountability starts before the commitment

Most accountability systems fail because they begin after people have already committed to too much.

The company sets ambitious goals, funds too many initiatives, keeps pet projects alive, lets every function define success differently, and then demands accountability when the plan slips. That is not accountability. That is wishful thinking followed by pressure.

The COO should create accountability at the point of commitment.

Before a team commits, ask:

  • What outcome are we actually promising?
  • Who owns it?
  • What resources are required?
  • What dependencies must hold?
  • What tradeoffs are we accepting?
  • What work is being stopped or deprioritized?
  • What risks are known now?
  • What evidence will show progress?
  • What decision rights does the owner have?

A clear commitment is easier to hold than a vague aspiration.

Visibility is not accountability

Dashboards are useful. They are not accountability by themselves.

A company can have beautiful dashboards and weak accountability if nobody owns the result, nobody changes behavior when the metric moves, or every miss becomes a narrative exercise.

Visibility answers: what is happening?

Accountability answers: who owns the outcome, what are they doing about it, what tradeoff is required, and what happens if the pattern continues?

The COO should be suspicious of visibility systems that do not change decisions. If a report is reviewed every week but no resources move, no commitments change, no risks escalate, and no behavior improves, the report may be ritual rather than operating tool.

Bureaucracy grows when trust is replaced by proof-of-work

When leaders do not trust execution, they often ask for more reporting. The request is understandable, but it can create a bad loop.

Execution is weak, so leadership asks for more visibility. Teams spend more time reporting. Work slows. Leadership sees more slippage. Reporting increases again.

The COO's job is to diagnose why trust is low.

Is ownership unclear? Are goals unrealistic? Are leaders hiding bad news? Are dependencies unmanaged? Are teams under-resourced? Are standards inconsistent? Are there consequences for missing commitments? Are executives changing priorities casually? Are metrics unreliable?

If the underlying issue is unclear ownership, more reporting will not fix it. If the issue is unrealistic planning, more dashboards will only document the fantasy. If the issue is executive churn, teams will learn to wait out commitments.

Accountability requires truth at the source, not paperwork at the top.

Make tradeoffs visible

A COO creates accountability by making tradeoffs impossible to hide.

When a leader says yes to a new initiative, the COO asks what moves down. When a team misses a milestone, the COO asks whether the miss came from execution quality, dependency failure, resource mismatch, unclear decision rights, or changed priorities. When a function claims a goal is critical but assigns weak ownership, the COO points out the contradiction.

This can feel uncomfortable, but it is not punitive. It is operating honesty.

The sentence “we are accountable” means nothing unless the company is willing to name the choices accountability requires.

Use standards, not surveillance

Strong accountability depends on clear standards.

Examples:

  • A launch is not green unless enablement, support readiness, customer messaging, and rollback plans meet defined criteria.
  • A strategic initiative is not on track unless milestones reflect outcome progress, not activity completion.
  • A hiring plan is not approved unless role clarity, budget, interviewer capacity, and onboarding ownership exist.
  • A forecast is not credible unless it is supported by evidence, not optimism.
  • A customer escalation is not resolved until ownership, customer communication, internal root cause, and prevention path are clear.

Standards let teams self-manage. Surveillance makes teams perform for management.

The COO should prefer standards that help owners know what good looks like before executive review.

Follow-through is where accountability becomes real

Many organizations are strong at commitment and weak at follow-through.

Decisions are made, but nobody checks whether they landed. Owners are assigned, but dependencies are not reviewed. Risks are named, but no action is taken. Misses are explained, but patterns are not addressed. Meetings end with agreement, and the same topic returns two weeks later unchanged.

The COO should design follow-through into the system.

Every material decision should produce:

  • owner;
  • action;
  • due date or milestone;
  • communication path;
  • dependency;
  • review point;
  • escalation trigger if off track.

This sounds basic because it is. Many companies do not fail from lack of sophisticated management theory. They fail because the operating system does not close loops.

Consequences do not have to be theatrical

Accountability eventually requires consequences. Not punishment theater. Consequences.

A missed commitment may lead to reallocation, scope reduction, leadership intervention, a change in owner, a revised plan, coaching, performance management, or a decision to stop the work. The key is that repeated misses cannot become normalized.

The COO should help the executive team distinguish between:

  • a good plan disrupted by new reality;
  • a weak plan that was never credible;
  • a capable owner blocked by dependencies;
  • an owner avoiding tradeoffs;
  • a resource mismatch;
  • a performance issue;
  • a strategy issue masquerading as execution failure.

Different causes require different consequences.

Diagnose misses before adding process

When commitments slip, the COO should separate four causes:

  • bad commitment: the goal was vague, overstuffed, or never truly resourced;
  • bad ownership: nobody had enough authority to deliver the outcome;
  • bad system: dependencies, decisions, or handoffs made success unlikely;
  • bad performance: the owner had the right conditions and still did not execute.

These require different responses. Adding reporting to a bad commitment only documents fiction. Treating a system failure as individual weakness creates cynicism. Treating a performance failure as a process issue creates avoidance.

Keep accountability close to the work

The more accountability moves away from the work, the more bureaucratic it becomes.

A board-level dashboard cannot substitute for manager judgment. An executive review cannot substitute for functional ownership. A COO cannot personally inspect every commitment in the company.

The COO should push accountability downward and outward through clear ownership, good standards, decision rights, and operating forums. The executive layer should inspect the health of the system and intervene where stakes or patterns require it.

The COO's accountability checklist

A practical accountability system answers:

  • Are priorities few enough to be real?
  • Does each important outcome have one accountable owner?
  • Are commitments resourced?
  • Are tradeoffs explicit?
  • Are decision rights clear?
  • Are standards defined before review?
  • Is progress measured by outcome evidence, not activity?
  • Are risks escalated early?
  • Does follow-through close loops?
  • Are repeated misses diagnosed and acted on?

If the answer is no, do not add a heavier reporting process first. Fix the operating design.

The best accountability system is not the one with the most process. It is the one where people know what they own, have authority to act, surface reality early, and cannot hide unresolved tradeoffs inside vague activity.

That is accountability without bureaucracy.