“I need someone to run the business” is not enough
It is understandable. The founder is in every meeting, every escalation, every approval, and at least three Slack threads that should have ended yesterday. The company wants an operator. Everyone starts saying COO.
But what does running the business mean here? Owning day-to-day operations? Translating strategy? Leading the executive team? Fixing delivery? Integrating finance, people, sales, and operations? Building the next management layer? Becoming the founder's eventual successor?
If the COO mandate is “take everything the founder hates,” the company has not designed an executive role. It has created a very expensive junk drawer.
Start with the operating constraint
Name what the business cannot do reliably today. Decisions may stall at the founder. Functions may work hard without working together. Revenue may grow faster than delivery. The leadership team may need stronger standards. Strategy may change more often than the operating plan can absorb.
Define the current state, the business consequence, the change required, and the conditions the COO will inherit. “Build an operating system that lets a founder-led $100 million consumer company scale across channels without every cross-functional decision returning to the CEO” is a mandate. “Help us scale” is a wish wearing business casual.
Define the COO mandate in six parts
Translate
Turn strategy and founder intent into priorities, operating plans, decisions, owners, and a rhythm the company can execute.
Integrate
Connect functions that currently optimize their own work while the customer, margin, or deadline absorbs the disagreement.
Scale
Build the structure, systems, leadership, and accountability required for the next stage without creating process theater.
Decide
Clarify which enterprise and operating decisions the COO owns, shares, recommends, or escalates.
Lead
Raise the quality of the leadership team, surface problems early, and make the company less dependent on founder intervention.
Deliver
Produce measurable business outcomes, not merely a calmer calendar and an impressive collection of recurring meetings.
Not every COO needs identical scope. That is the point. The role should reflect this company's business model, stage, leadership team, founder, and next set of problems.
Write the first-year outcomes, recurring accountabilities, decision rights, reporting lines, team, and boundaries. Then decide whether the work truly requires a COO or a different leader.
COO, Chief of Staff, President, or VP of Operations?
A Chief of Staff often works through the founder, increasing leverage across priorities, information, special projects, and coordination. A VP of Operations may own a defined operating function. A President may carry broad business, commercial, or external leadership. A COO typically has recurring enterprise authority and accountability, but the title is not regulated by the hiring police.
Use my guide to Chief of Staff vs. COO and the Director, VP, or Head of calibration. If a less senior or narrower role can solve the problem, that is not thinking small. It is refusing to buy a C-suite title before the work needs one.
The founder handoff is part of the job
A COO cannot own what the founder keeps reclaiming. Before outreach, decide which decisions move fully, which remain shared, which require consultation, and what the founder will genuinely stop doing.
Then tell candidates the truth. If the founder changes priorities quickly, wants to remain close to product, reviews major hires, or holds final authority over spending, say so. Strong operators can work with involved founders. They need an honest map.
Interview the founder-company fit in both directions. The candidate must be able to challenge, influence, repair disagreement, and operate without constant permission. The founder must be able to receive pushback, share information, and let another executive lead without treating independent judgment as a small coup.
Interview for ownership
Turn operator language into evidence
| Candidate says | Ask next | Listen for |
|---|---|---|
| “I scaled the company.” | What broke, what did you personally change, and what became possible afterward? | Specific operating choices and measurable outcomes. |
| “I was the CEO's right hand.” | Which decisions did you own without the CEO, and where did you disagree? | Real authority, trust, backbone, and repair. |
| “I built process.” | Which business problem required it, who adopted it, and what work became faster or better? | Useful systems rather than ceremonial meetings. |
| “I led cross-functionally.” | Describe a conflict where functions had rational but competing goals. | Enterprise judgment and decision mechanics. |
| “I transformed the team.” | Who did you develop, hire, reorganize, or exit, and how did standards change? | Talent judgment and leadership courage. |
| “I am very strategic.” | Show how one strategic choice changed priorities, resources, and weekly execution. | The bridge between deck and delivery. |
Do not confuse large-company scope with small-company operating range
A candidate may have managed enormous scale with mature systems, specialized teams, established processes, and powerful brand gravity. That experience can be valuable. It does not automatically prove they can build the missing infrastructure, get close to the work, or make tradeoffs with fewer resources.
Ask what they inherited, what they built, how large the support system was, and what they did when the answer could not be delegated. Test whether the candidate can move between enterprise decisions and operational detail without either micromanaging the team or floating several floors above reality.
The guide on whether an executive can operate in a smaller company gives you a deeper assessment path.
Look for systems that changed behavior
COO candidates often describe operating rhythms, dashboards, planning cycles, and accountability systems. Ask what behavior changed. Did decisions happen faster? Did priorities become more stable? Did forecast accuracy improve? Did functions stop surprising one another? Did the founder leave meetings and stay gone?
A system is useful when the company can make better decisions repeatedly. More meetings and a handsome dashboard may be ingredients. They are not the result.
Use a work sample that exposes tradeoffs
Give the candidate a realistic operating problem with incomplete information. Growth is strong, delivery is slipping, leaders disagree about priorities, the founder is still approving too much, and the company cannot fix everything this quarter.
Ask what they would diagnose, what they would stabilize first, which decisions require the founder, how they would set the operating cadence, and what they would deliberately delay. Strong COOs should reveal judgment, sequencing, and the ability to make uncertainty usable.
Do not ask candidates to redesign the whole company as free interview homework. You are hiring an operator, not running a small unpaid consulting tournament.
Build the scorecard before chemistry takes over
Founder-COO chemistry matters because the relationship carries trust, conflict, proximity, and shared decisions. It is still not the entire hiring decision.
Score the evidence for the actual mandate: enterprise judgment, execution, operating range, financial fluency, systems building, cross-functional influence, talent leadership, founder partnership, change leadership, and first-year outcomes. Record evidence before the debrief, then use the executive hiring scorecard and the guide to founder executive interviews.
Prepare the company to receive a COO
The search is not ready until the company can explain the mandate, authority, resources, compensation, risks, founder handoff, and first decisions. The leadership team also needs to understand what changes when another executive begins connecting work that previously lived in separate rooms.
If the founder wants leverage but not a change in decision rights, say that plainly and reconsider the role. A capable COO cannot create an operating company while remaining an unusually senior project coordinator.
My guide to executive onboarding in the first 90 days can help turn the hiring promise into an actual landing plan.
When you should call me
Call me when the founder knows the company needs stronger operational leadership but the role keeps expanding every time another executive joins the discussion. Call me when you are debating COO, President, Chief of Staff, or VP of Operations and everyone is using the same words to mean different jobs.
I have recruited senior leaders across operations, finance, legal, marketing, partnerships, technology, sports, consumer brands, and founder-led businesses. I know how to separate big scope from personal ownership and executive presence from the operating evidence beneath it.
Bring me the business plan, leadership team, founder calendar, decision bottlenecks, and the responsibilities nobody can agree on. I will help you define the mandate, map the market, and build an assessment process that can survive chemistry.
Frequently asked questions
When should a founder hire a COO?
Hire a COO when the company has a material enterprise operating mandate that needs sustained executive ownership, the founder can define what must be handed over, and the business is ready to provide the authority, information, resources, and compensation required. Founder overload alone does not define the job.
What should a COO own?
COO scope varies widely. The role may own company operations, strategy execution, cross-functional performance, specific business units, financial and operating cadence, people leadership, customer delivery, or a transformation. Define decisions and outcomes explicitly instead of relying on the title.
What is the difference between a COO and Chief of Staff?
A Chief of Staff often increases the founder's leverage through priorities, information, special projects, and coordination. A COO usually carries broader line authority and recurring accountability for operating results. Company stage and mandate matter more than a generic title definition.
Should a COO be the founder's opposite?
Complementary strengths can help, but hiring an opposite is not a mandate. Choose the capabilities the business needs and test whether the working styles can create productive tension, clear decisions, and trust. Chemistry without operating evidence is not enough.
What questions should a founder ask a COO candidate?
Ask what enterprise problem they inherited, which decisions they owned, how they translated strategy into execution, where they changed the organization, how they handled founder or CEO disagreement, what they stopped, how results changed, and what the team would say became clearer.
How do you evaluate a COO candidate from a larger company?
Test operating range. Ask what infrastructure they inherited, how close they were to the work, what they built with limited resources, how they made decisions without complete data, and whether they can operate without a large staff, mature systems, or brand power.
Should a COO candidate complete a case study?
A bounded work sample can test diagnosis, questions, priorities, decision rights, and communication. Give enough context to reason but do not ask finalists to solve the company's full operating model for free. Assess judgment and assumptions, not slide volume.
When should we use an executive search firm to hire a COO?
Use a search partner when the mandate is difficult to calibrate, the role is confidential or business-critical, the strongest candidates are not actively applying, the founder needs market intelligence, or the company needs deeper assessment than a résumé screen and chemistry-heavy interview process.
Do not hire a COO to absorb the chaos.
Hire the executive who can change how the company operates.
Define the mandate, founder handoff, authority, and evidence before looking for a second-in-command.
Talk to Rachel about the search