Questions to Ask a COO
54 questions for half an hour with a chief operating officer, whether you have just met them or you work for them. The list opens with questions that need no inside knowledge of the company: the ones for an informational call, a conference introduction, a coffee arranged by a mutual contact, or an interview where the COO is the hiring manager. It then moves to the job itself and the split with the chief executive, and on to the operation: metrics, handoffs, single points of failure, what happens after something breaks. If this is a skip-level or a new-joiner introduction with your own COO, most of the list works as written, and you are in a position to act on the answers. The last three questions only make sense if you work there.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
What does your week actually look like? Which meetings are yours to run?
Why ask it
A calendar is harder to spin than a mission statement. If most of the week is unplanned escalation, the operation is running reactively whatever the strategy deck says about it.
How would you describe what the company is trying to get right this year, in one sentence?
Why ask it
The one sentence limit is the point. A COO who needs five initiatives and four minutes is describing an organisation without a clear priority, which explains a lot of the confusion further down.
How would you explain what the company actually does, operationally, to someone outside it?
Why ask it
The version a COO gives is about flows and constraints rather than the marketing story, which is the fastest way for an outsider to get oriented. Where they simplify tells you what they treat as incidental.
What is different about how the company works now compared with two years ago?
Why ask it
Comparing then and now gets you the trajectory instead of a snapshot, and it shows which changes stuck. Vague answers often mean growth happened to the company rather than being managed.
How do decisions get made when two teams want the same resources?
Why ask it
Resource conflict is the substance of the job. Listen for a named forum or process; if it is settled case by case, seniority is deciding it and you should know whose.
What is the last process you personally redesigned, and what prompted it?
Why ask it
Asks for one artefact rather than a philosophy of improvement. The prompt is the interesting half: a customer complaint, a bad quarter, an audit finding, a resignation.
What does the company do well that does not show up in the marketing?
Why ask it
Gives them something to be proud of that they are rarely asked about, which usually opens up the rest of the conversation. It also shows an outsider where the real capability sits.
What would surprise someone joining from a company twice your size?
Why ask it
Turns a vague culture question into a concrete comparison. The answer is usually about speed, formality, or how much ground one person is expected to cover, all of which matter if you are considering the move.
Which part of the operation are you leaving alone on purpose this year?
Why ask it
A deliberate not this year shows sequencing. A COO who says everything matters is describing a place where projects begin, compete for the same people and stall.
How much of your job would be the same at any company, and how much is specific to this one?
Why ask it
Separates the craft of the role from local circumstance, which is exactly what an outsider cannot see. It also tells you how far their advice will travel to your situation.
What is the last thing you changed your mind about?
Why ask it
Reversals show whether someone updates on evidence or on pressure from whoever complained loudest. No examples from a person making dozens of calls a week means outcomes are not being tracked.
When cost, speed and quality collide, which one usually gives here?
Why ask it
Every operation has a default tiebreaker and it is rarely written down anywhere. Knowing it explains most of the decisions you have already seen and predicts the next several.
What do you look for when you hire into operations?
Why ask it
A direct route to the thing you probably want to know, asked in a way that is easy to answer generously. Listen for the qualities they name unprompted rather than the qualifications they list.
What do you look at to tell whether a manager is doing well?
Why ask it
Tells you what actually gets rewarded. If the answer is only targets, expect turnover on the teams underneath the managers who hit them.
Which of your current risks worries you most: a vendor, a single person, a compliance exposure?
Why ask it
A COO who has mapped concentration risk answers with specifics and a mitigation attached. A general answer about risk management means the register exists but nobody is working it.
What is the hardest thing about working there that you would tell a candidate straight?
Why ask it
Frames honesty as fairness to a candidate rather than disloyalty to the company, so you usually get a real answer. Whatever they name is the thing you would be signing up for.
How do you keep a sense of what the front line is dealing with?
Why ask it
Reveals whether they still visit the warehouse, listen to support calls or read tickets. The answer also gives you a usable model if you want their job one day.
What did you have to unlearn when you moved from running a function to running operations?
Why ask it
Only someone who has made that move can answer with specifics, usually about giving up the work they were best at. It is one of the better questions for a mentoring conversation.
How did you end up in operations in the first place?
Why ask it
Almost nobody plans this career, so the route is usually accidental and worth hearing. It is the easiest question here to ask a stranger and the one most likely to produce a long answer.
What should I be paying attention to that I probably am not?
Why ask it
An open close that lets them raise whatever your questions missed. In practice this is where you hear about a coming reorganisation, a systems migration or a shift in the market.
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.
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.
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.
Which three numbers would tell an outsider whether this operation is healthy?
Why ask it
Forcing a short list reveals what the COO believes the operation is for. If all three are activity counts rather than outcomes, you have learned something before you open a single report.
Which operating metrics do you watch daily, and which can wait for the weekly review?
Why ask it
Separating heartbeat signals from review material shows whether the reporting cadence matches how fast the work moves. A COO who watches everything daily usually has a team that spends its mornings assembling numbers instead of using them.
What data do you wish you had and do not?
Why ask it
Instrumentation gaps are where decisions are currently being made on instinct. The gap they name is usually the highest-value thing you could go and build, and it is also a fair test of whether they know their own blind spots.
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 breaks first if volume goes up thirty percent?
Why ask it
Every operation has a known weak link, and COOs generally enjoy being asked about it. The named constraint is usually a person or a manual step rather than a system, which is worth remembering next time growth is announced.
Which processes here are ready to be simplified or retired?
Why ask it
A COO with a specific answer has been looking at cycle times rather than org charts. Naming a process nobody wants to defend is also the cheapest place for a new person to make progress in a first quarter.
What manual work still has no clear owner?
Why ask it
Unowned manual work is where capacity quietly disappears, usually into a spreadsheet maintained by one person who is now unable to take a holiday. The answer often identifies both an automation target and a single point of failure.
Which process here still depends on one person's memory?
Why ask it
Names the single-point-of-failure risk everyone tolerates. If the answer comes quickly, this has been on their list a while, and asking what has stopped it being fixed is the productive follow-up.
Where do handoffs between teams fail most often?
Why ask it
Work that leaves one team's definition of finished and arrives at another's is where delay and rework are created. Their answer tells you which two functions have an unresolved dispute, which is usually invisible from inside either one.
How do you stop functions from optimising against each other?
Why ask it
Sales booking what operations cannot deliver is the classic version. Listen for a shared metric or a forum where the trade is made explicitly, because goodwill between department heads is not a mechanism.
How do you decide whether to build a tool or buy one?
Why ask it
You are looking for the actual test they apply, such as whether the process is a differentiator or just table stakes. A COO who always builds is paying maintenance forever; one who always buys ends up gluing eleven vendors together.
How do you find out about a problem: a dashboard, an escalation, or a customer?
Why ask it
Ranks the detection systems honestly. A COO who mostly hears from customers has a monitoring problem, and one who mostly hears through escalation has a culture where bad news travels slowly.
What actually happens here after something breaks?
Why ask it
The shape of the postmortem tells you the culture: a written timeline and a change to the system, or a meeting that ends with a person's name. If actions from the last one were never closed, the ritual is theatre.
What have you tried to fix twice that's still broken?
Why ask it
The second attempt is where the real obstacle shows: budget, a person, an incentive, or a system nobody will replace. This question gets at institutional resistance in a way a question about challenges does not.
How do you replan when a quarter slips halfway through?
Why ask it
This tests whether replanning is a discipline or a panic. Good answers describe what gets cut and who is told; weak ones describe working harder, which is how the next quarter gets damaged as well.
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.
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.
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 deep is the bench if you lost two operations managers next month?
Why ask it
Key-person risk is the thing an outside reviewer misses most often, because it never appears on a process map. Push for names and cover plans rather than a general answer about succession.
What would you spend the next headcount on, and what does that person fix?
Why ask it
The next hire is the clearest statement of where an operation is short. More of the same role means the constraint is volume; a new capability means the constraint is design.
If you had to take ten percent out of the cost base, where would it come from first?
Why ask it
A COO who cannot answer quickly has not modelled it, which is itself the finding. The order they name things in tells you what they consider load-bearing.
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.
If you handed this operation to someone tomorrow, what would you warn them about?
Why ask it
Framed as a handover rather than a confession, so it gets the caveat that a direct question about weaknesses does not. Expect one system, one relationship and one deadline.
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.
Where does my team's work show up in what you look at?
Why ask it
Anchors a skip-level in something you can act on by Monday. Plenty of teams discover here that the number they optimise never reaches this desk at all.
What would you need to see before funding another person on my team?
Why ask it
Turns a request you were going to make anyway into a specification you can meet. Write down the evidence they name and bring back exactly that in a quarter.
What do people at my level worry about that you do not?
Why ask it
The gap between the two lists is where effort gets wasted, and only someone further up can see it. Expect at least one thing your team spends real hours on to be waved away.
Getting Value from Time with a COO
Practical guidance for the conversation itself
Know which conversation you are in
Time with a COO arrives in a few shapes: a skip level as a newer employee, an informational conversation while you weigh a move, a mentoring half hour, or a meeting where you are the one presenting. The same question lands differently in each. In a skip level, ask how the operation runs. In an informational conversation, ask about the company's trajectory. In a mentoring conversation, ask about their own transitions. Trying all three in twenty minutes gets you shallow answers to all of them.
Ask about mechanics, not values
- Operators give detailed answers about cadence, metrics, escalation and resourcing, and slogans about culture and mission.
- Anchor a question in something specific you have seen for yourself, from outside or from your own desk: a new market, a systems change, a hiring surge, a restructure.
- Ask for one example rather than a general approach. "What did you change last quarter" outperforms "how do you approach change".
- Do not ask anything answered in the last earnings call, the annual report or the company handbook.
How much time you actually have
- Twenty minutes realistically holds three questions plus follow ups. Choose them in advance and rank them.
- Lead with your best question rather than saving it, because these meetings get cut short far more often than they run long.
- Write the numbers down during the meeting. Metrics and headcount figures are the most durable thing you will take away.
- Send a short note afterwards that references one specific answer rather than thanking them in general terms.
If they are your own COO
- Know your own team's numbers before you walk in: throughput, error rate, backlog. Being able to answer a question about your own area is what turns one meeting into a continuing relationship.
- Do not spend the slot complaining about your manager. It is not the place to escalate unless the matter is serious and you have already tried the normal route.
- Hold the pitch. Ask what has already been tried, then send the proposal afterwards with that context in it.
- If you are raising a problem, bring a number, what it costs, and the one thing you need from them: a decision, a person, budget, or permission to stop doing something else.
What the answers tell you
- Specific figures recalled from memory suggest a leader close to the operation rather than to the reporting layer above it.
- A named broken process with a stated next step is a better sign than a polished account of continuous improvement.
- If nothing has gone wrong in the past year, either the organisation has been unusually lucky or you are being handled.
- If their stated priorities do not match what your own manager tells you, understand that gap before you plan your year around either version.