How a COO builds independent problem-solvers instead of answering questions

Executive overview

A COO who answers every question trains dependency, not capability. The role is to grow people's skills and confidence so they can act without you.

When someone brings a problem, redirect it: "What do you think?" If they don't know, send them to think. If they have an answer, let them run with it.

The COO's job is to make themselves unnecessary, not indispensable.

Redirecting questions to build ownership

• Default response to any question: "What do you think we should do?"
• If they don't know, send them away to think and return with an answer
• If they have a tentative answer, push back with the same question — don't validate prematurely
• Four-question filter before acting: Is it within your responsibilities? Within core values? Within budget? Are you willing to own the outcome?

The skills-and-confidence ladder

• Visualise every employee climbing two parallel ladders: skills on the left, confidence on the right
• Growth requires both — skills without confidence stalls execution; confidence without skills creates errors
• Every conversation with a direct report should ask: What are you working on? Why? Who can you delegate it to?
• "They can't do it" is not a reason to keep it — delegate and train anyway
• Stand beside them, show your work, transfer the knowledge

Why managers default to hiring instead of developing

• At ~30–40 employees, the reflexive answer to any problem is headcount
• More people doesn't solve a flood of questions — stopping the flood does
• The real solution: build the team's ability to self-direct, not absorb more requests