How should an operations leader evaluate COO jobs in India?

A company can use operations language for anything from plant performance to enterprise coordination. Ask which customer or economic consequence must change, where the constraint originates and why existing line leaders cannot resolve it through the current system. Treat that distinction as the first gate. Keep contrary evidence with its source. Do not let interview momentum settle it.

Frame the role around one operating equation: the constrained outcome, the few controllable drivers and the forum that reallocates resources. If interviewers cannot agree on that equation, the title is carrying unresolved organisational design. Do not accept a generic operational excellence brief as evidence that the company has chosen between stabilising today and redesigning tomorrow.

The COO title may describe an enterprise integrator, a manufacturing leader, a service-delivery executive, a transformation office or a deputy to the CEO. The contradiction begins when the organisation wants all five but cannot name the operating problem that unifies them. Ask which customer, margin, reliability or scaling outcome has resisted the structure and why a role is required now. Evidence should include the operating plan, recurring performance forum and a recent cross-functional failure with a named owner. Compare the CEO's diagnosis with those of business and functional leaders who will depend on the COO. The executive consequence is whether the role has a coherent system to improve or becomes the destination for every unresolved handoff. A broad remit may be viable when priorities and authority are sequenced. Stop if interviewers define the COO by activities rather than an enterprise outcome, if each sponsor assigns a different centre of gravity, or if the title is being used to postpone a necessary redesign of existing accountabilities.

Map control across supply chain, manufacturing, service delivery, technology enablement, procurement, quality and regional execution. Identify where business-unit leaders can opt out, where corporate functions retain vetoes and which metrics resolve competing priorities. Turn the gap into an authority question. Ask for one contested decision. Record who resolved it and how.

Use one recent service or delivery failure as a decision trace. Ask who saw the signal, who convened the response, which trade-off stalled and who had power to settle it; the trace reveals the real operating system. Direct reports are an incomplete proxy because enterprise throughput often depends on peers whose incentives and budgets sit beyond the COO hierarchy.

A COO can be accountable for delivery while lacking control over planning cadence, common measures, process ownership, investment and exception governance. This creates the appearance of an operating system without the means to run one. Select a recent service, quality or margin problem and reconstruct how information moved from the front line to enterprise action. Request the operating calendar, metric definitions, escalation thresholds and the forum that reallocates resources when performance misses. The role's consequence lies in whether the COO can alter the mechanisms producing the result, not whether teams provide updates. Shared dashboards do not establish shared accountability. Identify which businesses may opt out, which functions hold vetoes and who resolves conflicts between local optimisation and enterprise performance. Stop if the organisation expects common outcomes while allowing material units to reject the governing cadence, or if control of the measures, resource decisions and remediation owners remains outside the proposed role.

Clarify which appointments the COO can make, which are jointly owned and which are protected by history or stakeholder relationships. Explore whether performance consequences are applied consistently across corporate, regional and site leadership. Test the commitment under visible pressure. Record who accepts the cost. Name who can reverse the choice.

Prepare a capability hypothesis by role rather than by person: planning, plant leadership, field execution, data stewardship and transformation delivery. Ask sponsors which capability gaps they acknowledge and what intervention they would support. The candidate should not infer individual weakness from outside; only authorised assessment can establish whether a named leader should change.

An execution mandate may require replacing leaders, redesigning spans, building new capabilities or changing incentives, yet the COO may receive only an advisory voice over people decisions. The contradiction is accountability for a system whose leadership architecture is protected elsewhere. Ask for two examples of senior operating appointments, including who defined the specification, assessed candidates, approved the choice and managed a performance failure. Review workforce plans, succession depth and the approval route for structural change. The executive consequence is not limited to hiring speed. It determines whether the COO can create durable capability or must compensate personally for gaps the organisation will not address. Agree which appointments require concurrence, which budgets support capability building and how disagreement with business presidents will be resolved. Stop if incumbent protection is treated as non-negotiable while outcomes remain fixed, if talent decisions can be reversed without an accountable forum, or if the candidate is expected to promise transformation before seeing the capability baseline.

Test who owns the weekly operating rhythm, customer escalations, board performance narrative, strategic initiatives and decisions that span multiple business presidents. Ask how the CEO will respond when a powerful leader resists a common standard. Price the uncertainty before it compounds. Separate verified conditions from working assumptions. Give each gap an accountable source.

Draft a six-line CEO–COO compact with decision domains, escalation triggers and shared forums. Debate it during the process; disagreement now is cheaper than discovering two models of the role after appointment. Claims of complete trust are not a substitute for role architecture, especially when the COO is introduced into an established leadership team.

The CEO–COO relationship can fail even when both executives are strong because the division of enterprise leadership remains situational and private. The contradiction appears when the COO is described as empowered but every contested matter returns to the CEO without a known rule. Build a compact around strategy translation, operating review, external stakeholders, talent, capital and crisis response. Ask both parties to apply it to a recent decision and to a plausible future disagreement. Board material, meeting charters and prior deputy arrangements provide useful evidence of how the enterprise actually separates ownership. The executive consequence is whether teams receive one operating signal or learn to arbitrate between two centres of authority. Personal chemistry can support the compact but cannot define it. Stop if the CEO will not state which decisions leave their desk, if sponsors expect the COO to absorb conflict without authority, or if the arrangement depends on a future handover that has no timing, governance or board approval.

A mandate that expands after every interview, protected exceptions to common processes and refusal to name the CEO–COO boundary indicate unresolved design. Persistent dependence on personal influence also raises the execution cost beyond what the title suggests. Write the threshold before final-stage momentum. Reopen only on authorised evidence. Keep reassurance outside the proof record.

Define the minimum operating mechanisms required on day one and those that may be built in year one. Stop if sponsors will not distinguish between the two or cannot support the transitional disruption involved. These stop conditions assess mandate feasibility; they do not forecast the employer’s operating performance or criticise any current executive.

A structurally weak COO process often reveals itself through endless scope expansion, missing line authority and the promise that influence will follow delivery. Maintain a mandate ledger from the first conversation, noting the enterprise outcome, controlled mechanisms, direct accountabilities and sponsor commitments. Compare each addition with the resources and decisions already offered. The executive consequence of accepting a catch-all remit is asymmetric: every execution gap becomes the COO's problem while protected leaders and local exceptions remain beyond reach. Greater title, compensation or CEO access does not rebalance that contract. Require a current organisation view, forum charter and explicit position on leadership changes before final commitment. Stop if the role is expected to coordinate rather than decide, if the CEO continues to own every consequential operating forum, if sponsors cannot describe a precedent for cross-business authority, or if the process treats requests for operating clarity as a lack of flexibility.