India's mission-mode programmes are led by officers titled CEO, Chairman, or Director General. The titles are borrowed from corporate vocabulary; the architecture beneath them is bureaucratic. The officer cannot hire their own team. Cannot deploy capital without Finance Ministry concurrence. Rotates on the same cycle as a generalist Secretary. The title sets up expectations the architecture cannot fulfil. What does the title actually authorise?
The CEO of a major government technology mission may be named among the most influential people in the relevant domain globally. The appointment may carry genuine institutional credibility, with the officer having served at the crossroads of digital governance and institutional innovation for over a decade. Yet the constraints this officer operates under reveal why the mission CEO designation, however earned, does not translate into the execution authority the title implies. A multi-year tenure at the parent ministry is, by the system's own standards, an exceptional accommodation. The observation is not about any individual officer; it is that even an officer whose programme had received global recognition is not exempt from the rotation architecture.
The appointment itself reveals the first structural constraint. The ACC does not evaluate "who is the best person to lead India's AI programme." It evaluates which officer at the appropriate seniority level is available for posting. Domain expertise may be a consideration; it is rarely a requirement. The officer arrives at the mission the same way they would arrive at any ministry: through the cadre allocation and seniority matching process. The mission does not select its leader; the system posts one.
The budget is not a corpus. It is an annual allocation subject to the fiscal calendar compression that governs all central expenditure. The CEO cannot deploy capital at will; every significant expenditure requires Finance Ministry concurrence, and the fiscal year's rhythm, not the mission's urgency, determines when funds are available.
The mission does not exist as an independent institutional entity. It operates as a division within its parent ministry, subject to the same HR policies, procurement rules, and administrative procedures. The CEO who wants to hire a domain expert from industry cannot bypass UPSC norms. The CEO who wants to fast-track a procurement cannot bypass GFR rules.
The fourth constraint is career incentive. The officer's Annual Confidential Report is written by the Secretary of the parent ministry. The officer's next posting, empanelment as Additional Secretary or Secretary, and career trajectory depend on this assessment, not on whether the mission delivered its targets. The rational institutional behaviour is to keep the Secretary satisfied, manage inter-ministerial relationships smoothly, and avoid audit observations. These are coordination priorities, not execution priorities. The officer optimises for what the system rewards, which is process management, not outcome delivery.
The result is that the office, regardless of its designation, gravitates toward secretariat behaviour: convening meetings, processing files, preparing notes for the Empowered Committee, coordinating with state governments, managing compliance reporting. An officer who exercises bold judgment and succeeds is noted. An officer whose bold judgment yields adverse outcomes is audited. The institutional incentive is unambiguous.
This is not to diminish the coordination itself. India is a federal democracy of twenty-eight states, eight union territories, twenty-two scheduled languages, and economic conditions that vary by an order of magnitude between districts. Coordinating a national programme across this diversity; aligning state governments with different political dispensations, reconciling central eligibility norms with local industrial conditions, managing disbursements through state treasuries with different fiscal calendars; is genuinely complex work that most private-sector CEOs would find unfamiliar. The officer performing this coordination is doing the job the institution actually designed for them; the job is coordination, not execution. The problem arises when the same institutional model is applied to deploying risk capital, building technology programmes, or racing against global competitive timelines. The mindset of the office remains administrative and distributive; a remnant of the era when the state's role was to allocate, regulate, and control, not to compete, invest, and iterate.
The government now funds like a capitalist but thinks like an administrator; the officer in the chair inherits both the fund and the thinking.
The Smart Cities Mission, Startup India, the Atal Innovation Mission, GeM, ONDC; each has been led by officers whose tenure is determined by the posting cycle, not the programme's lifecycle. When the officer moves, the programme does not pause. But it decelerates. The incoming leader spends months understanding the terrain, rebuilding relationships with industry partners, and developing the domain fluency that the predecessor carried out the door. The programme's external partnerships, often built on personal trust between the officer and the counterpart, must be re-established. The institutional memory of what was tried, what did not work, what was quietly shelved, and what was about to break through is not captured in any handover note.
ISRO succeeds where most government technology programmes struggle because it operates with long-tenure leadership, autonomous institutional structure, and political protection across governments. It has had launch setbacks and mission setbacks. But the institution was allowed to try, iterate, and learn. The system gave ISRO institutional room to learn through setbacks. It does not extend the same room to most other technology programmes.
The companies and partners engaging with these programmes need to understand what the office actually is, beneath the title. The CEO they met last quarter may not be the CEO next quarter. The strategic direction they were assured of may shift with the new leader's institutional reading. The partnership framework they negotiated was built on a relationship that the system's own rotation logic may dismantle. Planning for this is not cynicism. It is institutional realism.