Why great COOs say "no" more than you think

Executive overview

Most founders surround themselves with people who agree. A COO's real value is the opposite: saying no — or not now — to protect focus and reduce complexity.

Every "yes" consumes people, time, and money. The COO's job is to evaluate that cost against ROI: employee impact, customer impact, revenue, margin, and strategic fit. Anything that fails that test gets cut or deferred.

Leaders who say no protect the company's ability to work on the critical few, not the important many.

How to evaluate any idea

• Assess inputs: people required, time cost, money required.
• Assess outputs: employee impact, customer impact, revenue, margin, strategic alignment.
• If inputs don't produce the right outputs, the answer is "no" or "not now."
• "Not now" is a valid no — timing matters as much as merit.

The 1-800-GOT-JUNK French LMS example

• 2,800 field employees needed online training across ~10 modules.
• A training team was building out all content in French for the Quebec launch.
• Only 15% (300 people) had completed the English modules.
• The COO killed the French project: train the other 2,500 in English first.
• Surfaced a broader problem — too many miscellaneous projects running in parallel.

What happens when COOs can't say no

• They build permissive cultures where everyone's idea gets resourced.
• The company spreads effort across too many non-critical projects.
• Complexity grows; output shrinks.
• A COO who avoids conflict to be liked is a liability, not an asset.