COO vs operations manager: the same operation, two different reasons to change

If the COO deploys a programme across several sites and it does not scale, the company faces a broad execution problem. Costs increase, service deteriorates and leadership must explain why an improvement initiative weakened delivery. This is why the profile explicitly asks who will embed the change in operational management.

For the operations manager, the consequence is immediate and local. New training, an additional manual step or a fragile integration falls on people already stretched by absence and staffing gaps. A failure can stop the day. They are not more or less committed to quality; the losses they must personally manage are different.

The COO profile centres on an operation that cannot keep pace with ambition and costs too much per unit. Meaningful metrics might include throughput, first-time-right quality, OEE and rework costs. These metrics are not interchangeable. Choose the ones connected to the customer commitment and cost structure.

A strong case establishes a baseline, demonstrates measured improvement and shows how results will be sustained across departments. The source profile mentions failed lean programmes without lasting adoption and consultants who disappeared after presenting. That makes a clear ownership model, rollout sequence and accountability just as important as the potential return.

The operations manager does not lack ideas for improvement. According to the source card, repeated incidents, staff shortages and unfit systems leave little capacity to act. A solution that eventually saves time may be unacceptable if it first requires a difficult migration, extra tasks or extensive training.

Show the actual change on the floor. Who has to do what, how long is training, who provides support and what happens if a shift cannot use the new process? Then measure a relevant outcome: unexpected downtime, rework or handover delays. Visible results in a similar department and peer references are explicitly part of the source profile.

BIS and BAS are separate 0-10 profile scales. The k parameter is neither a percentage nor a conversion probability. It describes a relative preference for earlier versus later outcomes within the model. None of these values predicts the decisions of an individual person. They support the distinctions already present in the source-card pains, fears and evidence requirements.

The COO has k 0.12; the operations manager has k 0.30. In these profiles, this fits annual investment and improvement programmes for the COO and a strong need to reduce interruptions during the current working week for the operations manager. This does not mean the COO rejects early results or the operations manager has no strategic view.

Structure a rollout to serve both horizons. The operations manager should see a meaningful early result without excessive workload. The COO should see how the test can become a controlled, repeatable programme with measured cost and quality outcomes.

Consider a system that distributes staffing and capacity more intelligently. The COO asks whether it remains reliable across six sites during peak demand and helps reduce total cost per order. The operations manager asks whether tomorrow’s late shift will still know which tasks come first if a colleague calls in sick.

Both need contingency planning and support. But lead with repeatability and governance for the COO and with understandable steps, shift resilience and hands-on support for the operations manager. The order matters because attention follows responsibility.

For the COO, open with a relevant sector case showing baseline, productivity, quality, cost per unit and implementation approach. Add how the result was embedded in operations and, ideally, a peer COO reference. For the operations manager, start with a concrete shift or workflow before and after implementation. Show reduced interruptions and how little strain adoption placed on the team.

A product demo proves a feature works in a demo. A site trial can show it works in one environment. Only a carefully supported rollout case can justify broader repeatability. Do not quietly turn one of those statements into another.

“Has this worked at our scale?” asks whether the COO can responsibly roll out the solution, not whether they dislike innovation. “We have no time” often means the operations manager lacks the staffing capacity to absorb another initiative. The profiles explicitly link that objection to a stretched team.

For the COO, add scalable cases, unit economics and a plan for ownership. For the operations manager, show a low-burden trial, on-site support, simple recovery options and proof from a comparable department. More feature slides will not resolve either problem.

Keep the same honest product claims while changing the first question and the first evidence.

• Start the COO conversation with scale: what constrains growth and what is the cost per unit?
• Start the operations-manager conversation with the next shift: which interruption consumes the most time?
• Bring two case views: operational results across sites and a credible floor-level workflow.
• Show the implementation burden: training, fallback, support and interruption risk.
• Connect measurements: how does less downtime at one site translate into repeatable productivity?
• Check decision rights: the job title alone does not establish budget or approval authority.
• Follow up differently: share a scalable business case with the COO and an easy trial plan with the operations manager.

Illustrative scenario, not a measured customer response. You sell a platform that coordinates staffing and capacity across locations: “Fewer interruptions, better planning and more output with the same resources.”

The operations manager asks how long planners need to learn it, what happens during downtime and whether the team will notice fewer rota problems next week. The COO asks how rollout across locations works, whether cost per order falls and who keeps the process embedded after launch.

The appropriate first demonstration shows a real shift and a manageable trial. The strategic follow-up separates what the trial demonstrates from what still requires validation at scale. It includes the cost, ownership and risk of rollout.

To the COO: “As sites grow, inconsistent planning can make unit costs and service quality harder to control. I can share a case showing measurable capacity improvements and how operational leaders kept the process in place. Which KPI would show you that the change really scales?”

To the operations manager: “If staffing changes and last-minute requests keep disrupting the plan, a new tool only helps if it creates less work. I can show a short demonstration from a comparable team, including training and support. Which disruption would you most like to remove first?”

Neither message claims outcomes that have not been established. Each invites a discussion about a problem supported by the relevant source profile.

The operations manager may know whether the process genuinely works for the people using it; the COO may need to decide whether the improvement matters across the business. But a job title is not a formal mandate map. An operations manager may control a departmental budget, and a COO may still need finance or board approval.

Create a shared measurement plan for early reliability, team load, disruption risk, quality and cost per unit. State who collects each metric, over which period and what else might explain the change. This allows an operational trial to become defensible evidence rather than a win for one stakeholder.

First define exactly what your product changes: planning, maintenance, safety, capacity, staffing or something else. Identify who experiences the problem and who must approve the investment. Then explore associations around the current process, the proposed change and the feared downside.

Ask the COO which scaling claim is relevant, what return threshold matters and who would own the new process. Ask the operations manager which step creates the most friction, what training burden is realistic and which proof would be credible to the team. Turn the answers into one evidence architecture: a small, dependable test that could responsibly be expanded. Link the output to a tailored communication strategy.

The mistake is not promising efficiency. The mistake is assuming efficiency means the same kind of proof at every level of operations. The operations manager needs confidence the next working day will run better without crushing the team. The COO needs confidence that the improvement can survive growth and appear in operational unit economics.

A strong B2B business case connects the immediate operational proof to the organisation-wide consequence. Start with what people can actually deliver, not a generic claim of productivity.