How should an industrial leader evaluate manufacturing COO jobs in India?

Ask which customer or economic outcome is constrained, how long the issue has persisted and which prior intervention failed. Determine whether the first task is restoring control, enforcing common decisions or creating a different production system. Treat that distinction as the first gate. Keep contrary evidence with its source. Do not let interview momentum settle it.

Frame three horizons with entry and exit evidence: stabilise, standardise and redesign. Test sponsor willingness to delay visible transformation activity until the reliability foundation is sufficient. A demand for immediate step-change across all dimensions indicates unresolved sequencing, not necessarily an ambitious mandate.

A board may describe the appointment as transformation while plant leaders are still managing unstable schedules, repeat quality escapes and overdue maintenance. That contradiction matters because redesign consumes the same supervisory attention needed to restore control. Ask for twelve months of on-time delivery, scrap, unplanned downtime, premium freight and customer complaint trends by site, then compare them with prior improvement launches and cancelled actions. The pattern will show whether the first horizon is stabilisation, network standardisation or genuine operating-model redesign. For the incoming COO, choosing the wrong horizon turns every missed milestone into a leadership problem even when the sequence was impossible. Establish entry and exit evidence for each horizon, including the sponsor who can defer visible automation or footprint announcements. Stop if the board insists on simultaneous reliability, cost, inventory and capacity step-changes before it will disclose the baseline or acknowledge which intervention has already failed.

Map formal and informal authority across business units, plants, procurement, logistics, quality and product engineering. Identify exceptions that have local economic reasons and those protected only by history. Turn the gap into an authority question. Ask for one contested decision. Record who resolved it and how.

Trace a network allocation decision through evidence, debate and execution. Compare the actual mechanism with the enterprise accountability assigned to the role. Direct ownership of selected plants does not establish the ability to optimise an interconnected network.

The apparent attraction of a multi-plant COO mandate can conceal a structural contradiction: enterprise accountability sits at headquarters, while plant managers, procurement leaders and engineering teams retain local vetoes protected by business-unit history. Test authority through a real network allocation decision rather than an organisation chart. Review who supplied the demand data, who compared landed cost and changeover capacity, who approved the customer promise, and whether the chosen plant actually complied. Add recent examples involving supplier substitution, quality containment and engineering standards to expose informal power. The executive consequence is severe because one weak site can determine service, working capital and reputation across the network, yet the COO may be able only to convene. Require a written mechanism for resolving local exceptions, changing site leadership and enforcing shared standards without destroying justified local economics. Stop if sponsors call the role network-wide but refuse to identify a decision in which the incoming leader's judgement would prevail over a business-unit president.

Ask how bottlenecks are validated, how lifecycle cost competes with short-term output and whether committed projects can be stopped. Explore post-investment learning and who owns benefits after commissioning. Test the commitment under visible pressure. Record who accepts the cost. Name who can reverse the choice.

Create a constraint-to-capital ledger that records alternative interventions, expected operating consequence and review point. Use it to resist attractive technology that does not change the limiting condition. A capital envelope is not equivalent to authority when projects, suppliers or locations are predetermined.

Manufacturers often approve an impressive capital envelope while leaving the real investment choices untouched. The contradiction is a COO expected to remove constraints even though projects, vendors or locations were selected before diagnosis. Examine the last three capacity or automation proposals from bottleneck evidence through commissioning and benefits review. Maintenance backlog, overall equipment effectiveness by constraint, changeover loss, cash conversion and post-investment variance provide a stronger evidence base than a project presentation. Ask who could have stopped each proposal and whether a lower-capital operating intervention was considered. For the incoming executive, inherited spending can lock the network into the wrong footprint while future misses are attributed to execution. Make a constraint-to-capital ledger a condition of the first operating cycle, with alternatives, assumption owners and review dates. Stop when management will disclose the approved budget but not the evidence that selected the project, or when committed investments are declared irreversible regardless of what diligence reveals.

Ask how many major changes sites are already carrying and whether leaders can release time for learning and problem solving. Examine how standards are reinforced without assuming anything about current workforce performance. Price the uncertainty before it compounds. Separate verified conditions from working assumptions. Give each gap an accountable source.

Build a change-load map by site and leadership layer. Sequence interventions so that operating control, learning loops and local ownership mature before additional complexity is introduced. Candidate interviews cannot establish safety, labour or capability conditions; those require authorised site and specialist diligence.

The change programme may promise higher productivity while sites are already absorbing supervisor vacancies, new quality requirements and labour-relations pressure. That is the central contradiction: the workforce is treated as implementation capacity rather than as a constrained operating system. Request authorised site-level evidence on overtime, attrition, training completion, safety leading indicators, temporary labour, open leadership roles and the number of concurrent initiatives. Pair the data with listening sessions involving plant heads and frontline supervisors, because aggregate dashboards can hide where standards are no longer reinforced. The COO consequence is practical and immediate. Excess change load converts improvement work into workarounds, raises operating risk and makes local resistance look cultural when it is actually capacity. Agree a site-by-site sequence that protects daily control, releases learning time and names which programme will pause. Stop if sponsors demand a single network launch date, prevent direct site diligence, or treat questions about safety and industrial relations as evidence that the candidate lacks transformation ambition.

Warnings include protected local exceptions, a transformation timeline fixed before diagnosis and pressure to promise cost while reliability evidence is unavailable. A role may also conceal routine firefighting that leaves no capacity for redesign. Write the threshold before final-stage momentum. Reopen only on authorised evidence. Keep reassurance outside the proof record.

Set gates for network scope, baseline evidence, capital governance, people authority and sponsor tolerance for sequence. Decline if the organisation wants transformation language without accepting its operating choices. The decision assesses mandate feasibility, not the operational condition of any employer or facility.

A final-stage process can celebrate the COO's transformation credentials while narrowing the decisions that made those credentials valuable. The contradiction becomes visible when cost, delivery and inventory commitments are fixed, yet plant leadership, capital sequencing and customer exceptions remain dispersed. Assemble a mandate feasibility pack from site baselines, reserved-matter schedules, approved projects, customer penalty exposure and the first-year decision calendar. Reconcile it with separate accounts from the CEO, business-unit heads and board sponsor rather than accepting a blended narrative. The executive consequence of unresolved fragmentation is not merely slower progress. It creates personal accountability for a network that cannot be governed as a network and encourages short-term cost actions that damage reliability. Convert each dependency into a pre-appointment gate with a named owner and date. Stop if critical authority is promised informally, the timeline predates diagnosis, or the organisation asks for an unconditional savings commitment before providing operating and contractual evidence.