Questions to Ask COO
Twenty-two questions about the job rather than the operation: what a COO's day is made of, how the decision split with the chief executive got settled, what they got wrong in their first year, and which parts of the role they find genuinely unpleasant. Written for a profile or podcast interview, a mentoring call with someone who holds the job you want, or research before your company hires one. If you want the operating detail instead of the person, the diagnostic questions for a COO cover metrics, constraints and vendor risk.
The questions
Open any question for the note
Which functions report to you, and which ones did you have to argue for or give up?
Why ask it
The title carries no fixed scope, so the answer defines the job. The negotiation is the interesting part, since which functions a chief operating officer was denied usually maps exactly onto where the chief executive still wants control.
How is the job different from what you expected when you took it?
Why ask it
Most people arrive expecting to improve systems and find the work is largely about people and about the executive relationship above them. The specific surprise tells you what the role demands that no job description mentions.
What does a normal Monday look like?
Why ask it
A concrete walk through one day cuts past the abstractions. Listen for how much is scheduled by other people, how much is spent in review meetings, and how little is left for the improvement work the role is nominally about.
Which meeting on your calendar could you not cancel?
Why ask it
The uncancellable meeting is the operating system of the company, usually a weekly review or a leadership session. Ask what happens in it and how commitments are tracked between one and the next, since that mechanism is the most portable thing they do.
What do you look at before anything else in the morning?
Why ask it
The first thing checked is the true measure of what the role is accountable for: a queue, a plant report, cash, service levels, an incident channel. It also tells you what they no longer trust to reach them through normal reporting.
How do you and the chief executive split decisions in practice, and how did you settle that?
Why ask it
Ask how it was agreed, not just where the line sits. Pairs that wrote it down tend to survive; pairs relying on instinct usually describe a period of collisions first. This is the single most predictive thing about whether the role works anywhere.
How much of your week goes on things nobody would call operations?
Why ask it
Legal disputes, an office move, a departure, a board request, one large customer. The proportion is usually higher than expected, and it explains why the improvement projects on their list move slowly regardless of intent.
What is the smallest detail you still watch personally, and why that one?
Why ask it
Every good operator keeps one or two things at a level of detail that looks disproportionate. The reason is usually a past failure. That story tells you where the company's real fragility lies better than any risk register.
How do you tell a process problem from a people problem?
Why ask it
Getting this wrong in either direction is expensive: replacing someone who was set up to fail, or rewriting a process to avoid a difficult conversation. Look for a specific test they apply, such as whether a capable replacement would hit the same wall.
When a number moves the wrong way, what is your first move?
Why ask it
Useful answers are unglamorous: check whether the measurement changed, go and look at the work, talk to the person closest to it. Anyone whose first move is a meeting with their peers is likely to be managing the report rather than the operation.
What do you do when a leader reporting to you is not going to make it?
Why ask it
The honest answer includes how long they waited and what that delay cost. This is where operating executives most often admit to being slow, and hearing the reasoning is more instructive than any framework about managing performance.
How do you decide what to stop doing?
Why ask it
Operations accumulate reports, meetings, and checks that once had a purpose. A specific example of something removed, and what happened afterward, shows whether they can subtract. Most cannot, which is why their calendars look the way they do.
What did you get wrong in your first year in this role?
Why ask it
Common answers are moving too fast on structure, trusting the reported numbers, or underestimating one function. The specific error is worth more to anyone about to take a similar job than a list of things that went well.
Which improvement looked good on paper and did not survive contact with the operation?
Why ask it
The reason it failed is the lesson: a step that only worked when one experienced person was present, a system that assumed clean data, a target that pushed work into the next queue. These stories are where operating judgment actually comes from.
How do you keep the numbers you receive from being managed for your benefit?
Why ask it
Anyone senior gets a filtered view, and good operators build routes around it: skip-levels, sitting in on calls, reading raw tickets, unannounced visits. If they claim their reporting is simply accurate, they are describing a company they have not tested.
How do you tell a team that is genuinely running well from one that is quietly heroic?
Why ask it
The difference matters because heroic teams look excellent until one person leaves. Listen for indicators they actually use: overtime, single points of failure, whether the process runs when the manager is on holiday.
What happens when the chief executive commits publicly to something you know is not deliverable?
Why ask it
This is the defining tension of the role. Answers involving a private renegotiation, a staged commitment, or an early warning to the customer describe someone with authority. Answers about making it work regardless describe someone absorbing the cost quietly.
What do you wish the rest of the company understood about your constraints?
Why ask it
Usually something concrete: lead times, a contract, a regulator, the cost of switching a system. Hearing it explains decisions that look arbitrary from the inside, and it is the most immediately useful answer for anyone working under them.
What part of the job do you find genuinely unpleasant?
Why ask it
Restructurings, telling people no repeatedly, being the person who slows things down. Anyone who claims to enjoy all of it is performing, and the honest answer is the best information available to someone deciding whether they want this role.
What skill did you have to build that none of your earlier roles taught you?
Why ask it
Frequently something like reading a balance sheet, handling a board, or communicating in a downturn. It points directly at the gap most candidates for the role have, which makes it the most actionable answer for someone aiming at the job.
How do you decide between bringing in outside help and building the capability internally?
Why ask it
Look for a rule rather than a preference: whether the work is recurring, whether the knowledge needs to stay, how quickly it is needed. Operators without a rule tend to accumulate either dependence on consultants or teams they cannot keep busy.
For someone who wants this job in five years, what should they be doing now that most people are not?
Why ask it
Better than asking for career advice, because it forces a comparison. The answers tend to be specific and slightly unwelcome: take a job with a profit and loss statement, spend a year somewhere unglamorous, learn the finance rather than the tooling.
Getting a useful hour with an operating executive
Practical guidance for the conversation itself
How to use the time
Bring one topic, and say what you want from it
Chief operating officers spend their days deciding things, and they respond well to a stated purpose: you want to understand how decision rights were divided, or how they judge a struggling team. A general request to pick their brain gets you a general conversation.
Ask about a specific episode rather than an approach
How do you handle change management produces a speech. What happened when you moved the second shift to the new process produces the real material, including who objected and what it cost. Anchor every question you care about to an event.
Come with data if you are raising a problem
If you work for them, a problem presented with numbers, a timeframe, and one proposed action gets treated as work. The same problem presented as a complaint gets treated as noise, and you will not get another meeting for a while.
Ask what they would want to know in your position
A good closing question, because operating executives see the parts of the company that individual teams do not, and this gives them room to raise something they would not volunteer unprompted.
What the answers tell you
- A described weekly cadence with tracked commitments means the operation is run to a rhythm rather than by escalation.
- Knowing the smallest detail they personally watch tells you where the company has been burned before.
- An explicit division of decisions with the chief executive is the strongest single sign that the role is real rather than titular.
- Willingness to name what they left unfixed indicates triage; claiming everything is being addressed indicates a smaller operation or a less candid answer.
- Specific routes around their own reporting, such as skip-levels or reading raw tickets, suggest they know how filtered a senior view is.
What goes wrong
Asking about operational excellence
The phrase invites the prepared answer, and you will hear about continuous improvement for ten minutes. Ask what a specific number was, what they changed, and what it is now.
Using the meeting to pitch your project
If you want a decision, ask for one explicitly and bring what is needed to make it. Disguising a request as a learning conversation wastes their time and yours, and it is transparent from the second question onward.
Going around your own manager
A skip-level that surfaces a problem your manager has not heard about creates trouble for you afterward. Raise it with your manager first, then use the time with the chief operating officer for the pattern rather than your particular case.
Only asking about strategy
Most of this role is cadence, staffing, and tradeoffs, and that is where the transferable knowledge is. The strategy questions are comfortable for both sides and produce answers you could have read in the company update.
Not writing anything down
These conversations produce a handful of specifics worth keeping: a metric, a rule for a decision, a mistake to avoid. Without notes, an hour of good material turns into a vague sense that it went well.