Skip to content
Dr. Shiva Kakkar

For Indian CXOs, CHROs, L&D teams, and manager cohorts

For Indian CXOs asking where GenAI adoption should start.

Most organisations do not begin with a neat adoption strategy. They begin with a practical pressure: the CXO wants people trained, HR needs a credible programme, or a pilot has created interest without changing work.

I work on the sharper question underneath that pressure: which work should change first, who owns it, and what a manager will review after the session. The route is management education, product work at Rehearsal AI, and adoption design for Indian organisations.

Experience base

Management classrooms, product work, and implementation contexts.

Executive classrooms

2,000+

Managers and leaders trained across GenAI adoption, AI strategy, and management education programmes.
Institutional range

60+

Organisations and institutions across banking, healthcare, manufacturing, public sector, education, and professional services.
Academic route

IIM-A / XLRI

PhD from IIM Ahmedabad and former faculty experience at XLRI, brought into executive education rooms.
Product work

Rehearsal AI

Head of Product at Rehearsal AI, connecting the teaching to shipped AI-native learning systems.

Programme outputs.

A useful GenAI adoption programme should name the first workflows, identify owners, define review rules, and give employees practice on work that resembles their day. Otherwise the session creates interest, but not organisational movement.

Even when the request begins as employee training in AI, the test is more concrete: what people can now do differently, what managers can review, and which workflow can move without waiting for a large transformation programme.

Programme routes

Three common ways organisations begin.

01

CXO decision workshop

CXOs, business heads, senior managers

Name the first workflows worth changing, the owner for each move, and the review rhythm leadership can govern.

02

Employee GenAI re-training sequence

Managers, employees, HR, L&D

Turn tool familiarity into role-specific practice, verification habits, and manager-visible work products.

03

Stalled-pilot adoption sprint

Teams moving from pilot to deployment

Use the previous stalled pilot as evidence, then rebuild the workflow, review rules, and proof for the next phase.

Programme inquiries

Start with the work your team needs to change.

Share the audience, business function, and problem you want the programme to solve, then choose the right format: CXO conversation, workshop, employee cohort, or adoption sprint.

Email Dr. Shiva Kakkar