Operations Manager Assessment

Why Operations Managers are hard to hire well

Operations is judged on the absence of problems, which makes it almost impossible to read from a CV. A manager who inherited a well-designed process and kept it running looks identical on paper to one who rebuilt a failing operation, and often better, because the second one presided over a period of visible disruption while the fixing was happening. Stability is the output, and stability has no artefact. The candidate who tells you their site hit its targets every month for three years may have been the reason, or may have been fortunate in what they inherited.

The promotion pipeline creates a second problem. Most operations managers were the best operator on the floor, and the qualities that earned the promotion are precisely the ones that limit them afterwards. Someone who is fast, capable and willing to pick up whatever is failing will, once promoted, keep picking up whatever is failing. The team learns that escalation is efficient. The manager is busy and well regarded, the metrics are propped up by their personal effort, and the underlying process is exactly as broken as it was on their first day. This is the single most common failure pattern in the role, and interviews reward the behaviour that produces it.

There is also a scale and mode problem that hiring processes routinely ignore. Running a stable operation and turning round a broken one are different jobs requiring different instincts, and so are running an operation of thirty and an operation of three hundred. The first pair differ in tolerance for disruption; the second pair differ in whether you manage the work or manage the people who manage the work. A candidate who has only ever done one of these can be excellent and still be wrong for what you have, and nothing in the job title distinguishes them.

What separates the best from the rest

The best operations managers fix the process rather than the instance. Given a failed order, a missed SLA or an angry customer, the weak response is to resolve it personally and move on, which is satisfying, visible, and leaves the failure rate untouched. The strong response is to resolve it and then ask what in the system allowed it, which is slower, less visible, and the only thing that changes the numbers. You can identify this in about ten minutes of the right questions, and almost never from a CV, because both types of manager report having handled the escalation.

They are also genuinely comfortable with variance rather than averages. A team hitting 96% on average with a spread from 88% to 100% has a different problem from a team sitting flat at 96%, and only one of those problems is solved by capacity. Weaker managers watch the headline number, react when it dips and relax when it recovers, which produces a permanent cycle of intervention and drift. Stronger ones look at the shape of the distribution, know which stations, shifts and product lines sit in the tail, and target the tail.

The third difference is how they make a change survive. Anyone can improve a process while they are standing next to it. The test is what happens on the night shift six weeks later, and that is a question about documentation, coaching, and whether the new way is genuinely easier than the old way rather than merely mandated. Managers who skip this step accumulate a drawer of improvement projects that all worked at the time. It is the least glamorous part of the role and the part that decides whether any of the rest of it compounds.

Why interviews alone fall short

Operations interviews reliably produce good answers, because the correct answers are well known and unobjectionable. Ask about continuous improvement and you will hear about root cause analysis and standard work. Ask about a difficult team member and you will hear about clear expectations, documented conversations and support. These answers are correct. They are also what every candidate says, including the ones who resolve every issue personally and have never held a difficult performance conversation to a conclusion.

The credentials do not help as much as they appear to. Lean and Six Sigma certifications establish that someone has been taught DMAIC and can construct a control chart, which is worth something, and they say nothing about whether the person will apply any of it to a live operation under time pressure with a director’s initiative implicated in the data. Certification is a floor, not a signal, and treating it as a differentiator mainly filters for who had an employer willing to pay for the course.

The deeper limitation is that this job is made of many small decisions taken quickly, and interviews sample large decisions recalled slowly. Whether to hold the line on a standard when the shift is short-staffed, whether to escalate a supplier problem now or give it another week, whether the dip is signal or noise: these are made in minutes, dozens of times a month, and they determine performance far more than any single restructuring. Situational scenarios put every candidate in front of the same set of them and make the reasoning comparable.

Common hiring mistakes in operations recruitment

• Promoting the strongest operator without testing whether they can change what other people do - throughput as an individual predicts very little about performance as a manager
• Mistaking firefighting energy for capability - the manager who is always in the middle of a crisis may be the reason the crises recur
• Reading stability as evidence of skill - a well-designed operation runs itself for a while, and the CV cannot tell you who designed it
• Treating a Lean or Six Sigma certificate as a differentiator - it establishes training, which the qualification already established
• Ignoring the difference between running and turning round - the tolerance for disruption required by each is close to opposite
• Not testing data literacy honestly - a manager who reads averages and ignores variance will keep solving the wrong problem with more headcount
• Overlooking how changes are sustained - an improvement that lasts only while the manager stands next to it has not improved anything

The work this role is assessed against

• Monitor KPIs and dashboards, triage exceptions, and run incident war rooms when needed
• Build and adjust schedules, forecasts, and staffing plans based on demand signals
• Conduct Gemba walks, audits, and Kaizen events, and implement and verify corrective actions
• Run daily standups and weekly business reviews, communicating status, risks, and mitigations
• Negotiate vendor terms, manage inventory and logistics constraints, and coordinate change rollouts

Tools and outputs this role works with

Microsoft Excel and Google Sheets, SAP S/4HANA or Oracle NetSuite for ERP, Microsoft Dynamics 365, Salesforce, Power BI or Tableau for reporting, Jira or Asana for initiative tracking, Microsoft Project or Smartsheet for planning, Microsoft Visio or Lucidchart for process mapping, Miro for collaboration, Slack or Microsoft Teams, SQL at basic querying level, WMS and TMS platforms such as Manhattan or Blue Yonder, and Google Workspace or Microsoft 365.