Name the business problem before naming the tool.
In CXO conversations, the first confusion is rarely about whether AI matters. It is about where to begin: customer work, HR work, finance work, compliance work, sales work, or internal productivity.
I am Dr. Shiva Kakkar: PhD, IIM Ahmedabad; ex-faculty, XLRI; and Head of Product at Rehearsal AI. If you are here, you are probably asking the question I hear from leaders most often: where do we start with GenAI adoption, and how do we identify the use cases inside our organisation that are actually worth pursuing? That is the work I help leadership teams structure.
I teach GenAI transformation to executives, managers, and faculty from organisations across India.
The useful starting point is the work itself: where it repeats, who can change it, what evidence shows the problem, and what risk has to stay visible while the team experiments.
In CXO conversations, the first confusion is rarely about whether AI matters. It is about where to begin: customer work, HR work, finance work, compliance work, sales work, or internal productivity.
Many organisations already have a dead proof of concept, unused ChatGPT subscriptions, or a workshop that created interest but no operating change. That history is not a failure to hide. It is the adoption data.
A good GenAI use case is not just exciting. It has a clear owner, accessible data, reviewable output, manageable risk, and a team that can absorb the change. This is the framework for deciding where to start.
Once the first use cases are chosen, re-training can become specific: what employees will do differently, what managers will review, what evidence is required, and what the next 30 days should prove.
Executive classrooms
Public artifacts
Product work