What to do with AI
This section is about where to begin, what to pilot, what to redesign, and what to watch carefully as AI becomes more capable.
The most useful way to read it is as a sequence of decisions: what one person can do today, what one office can pilot this quarter, what one department can redesign, and what the state should protect against before scale outruns control.
Choose one task this week: drafting letters, meeting minutes, form-filling, or document checking.
Before trusting output, make the system compare names, dates, fields, or source documents.
Ask where files stall, where inspection is weak, or where citizens struggle with forms.
Be explicit about what AI may assist with and what still requires human judgment.
Document the exact prompt, files, checks, and escalation rule so others can reuse it safely.
Track time saved, error rate, turnaround time, or citizen effort so adoption is evidence-based.
First, become a better operator.
The first level is not a ministry-wide platform. It is personal fluency. Learn how to direct an AI well, how to constrain it, and how to make it show its work before you ask it to touch larger systems.
The five habits below are practical habits of use, not theory.
Then use it on paperwork, language, and routine mechanics.
Administrative work is where AI becomes immediately practical. It is particularly strong where the job is repetitive, multilingual, document-heavy, and still dependent on people manually moving text from one format to another.
This does not mean “automate everything on day one.” It means finding processes where humans can dictate, lightly edit, verify, and approve while the system quietly carries the mechanical load.
Then redesign the process itself.
The real leap comes when AI is not only speeding up a workflow, but supervising it, surfacing bottlenecks, and helping rewrite the underlying rules. At that point, your department’s functioning becomes inspectable data.
This is where leadership matters most. These are not small productivity hacks. These are projects that change how a system notices delay, conflict, and preventable failure.
Then ask where India stands in the new economy.
The strategic story is not written yet. One narrative says a few giant model labs will win and everyone else will rent intelligence from them. But there is another possibility: a world of many models, routing layers, orchestration systems, and domain-specific agent stacks.
India should not think only in terms of catching up to a frontier snapshot. It should think about building systems that fit our scale, our institutions, our languages, our constraints, and our need to make citizens more capable.
Finally, keep the threat model in view.
A serious AI agenda has to hold two truths at once: these systems are increasingly useful, and they also create new harms at individual, institutional, and sovereign scale. If adoption accelerates, risk management has to mature with it.
The Indian risk surface includes a particular vulnerability: abundant cheap data, abundant attention, and large populations available to manipulation experiments at scale.
Closing
The path is simple, even if the technology is not.
Start personal. Move into administrative productivity. Redesign the process where the payoff is large. Think strategically about India’s position. And at every level, keep the risks visible.
The point is neither blind optimism nor blanket fear. The point is to become capable enough to use AI where it helps, shape it where it matters, and defend society where it threatens harm.
Resources
If you want to keep going, start here.
These are the books, essays, and trackers most worth reading after this talk. They give you a practical base: cyber risk, the history of modern AI, alignment and human values, beneficial abundance, and the state of local models you can run offline.