AI literacy for GCC leadership teams: where to start

Across India’s GCCs, the same request is arriving from headquarters: tell us how AI will change your centre. Leadership teams are expected to answer with confidence, set direction for thousands of people and make the case for investment. Many are not yet equipped to do it.

That is not a criticism of leaders. Most have spent their careers building and running delivery organisations, and AI has moved faster than anyone’s development plan. But it does mean the gap needs closing quickly, because AI decisions made without understanding tend to be either too cautious or too careless.

What AI literacy means for a leader

AI literacy for a site leader or director is not the same as AI skill for an engineer. Leaders do not need to build models or write prompts all day. They need enough understanding to make good decisions and ask the right questions.

In practice, that means being able to explain in plain language what current AI tools do well and where they fail, recognising which parts of the centre’s work are likely to change, understanding the risks around data, security and quality, and judging whether a proposal is realistic.

It also means having a shared language across the leadership team. When every leader has a different mental model of AI, priorities conflict and decisions slow down.

---

Five questions every GCC leadership team should be able to answer

A useful way to test AI literacy is to ask whether the leadership team can answer five questions together.

Five leadership questions on AI

2. 1Where does it change our work?Automate, augment, untouched
3. 2Which roles change first?And how we support people
4. 3What are the guardrails?Data, IP, quality
5. 4How will we measure it?Baselines and outcomes
6. 5What is the case for HQ?Capability and ownership

A credible AI plan for HQ

Where will AI change our work?

Map the centre’s portfolio into three groups: work AI is likely to automate largely, work it will augment, and work it will barely touch. This map is the foundation for every other decision.

Which roles change first, and how do we support people?

Some roles will change sooner and more deeply than others. Leaders need a view on which, and a plan for reskilling, redeployment and career paths, so people see AI as an opportunity rather than a threat.

What are our guardrails?

Clear rules on approved tools, data use, intellectual property and review of AI output protect the centre and give teams confidence to experiment. They should align with HQ policy rather than work around it.

How will we measure impact?

Without baselines, AI investment cannot be justified. Leaders should agree a small set of measures for each pilot before it starts.

What is our case to HQ?

Finally, the leadership team should be able to explain how AI adoption strengthens the centre’s capability and supports a bigger role in the global organisation. This is what turns AI from a cost-saving exercise into a growth story.

---

How to build AI literacy in a leadership team

Generic AI awareness sessions, with impressive demonstrations and little connection to the centre’s work, rarely change how leaders decide. A more practical approach works on the leadership team’s own portfolio.

Generic awareness

Portfolio-based literacy

• Impressive demosYour own work, mapped together
• Individual learningShared view across the team
• Ends with inspirationEnds with decisions and owners
• No link to governanceGuardrails agreed with HQ policy
• Hard to measureLiteracy assessed before and after

A focused leadership workshop typically covers a plain-language view of AI capabilities and limits, a mapping exercise on the centre’s real portfolio, a discussion of role redesign and talent, a session on governance, and the outline of a business case for HQ. It ends with priorities, owners and the first experiments for each area.

Follow-up matters. Short sprints where individual teams redesign one workflow end to end, and report the results back to the leadership team, keep the momentum going and build real evidence.

---

Start now, start small

Leadership AI literacy does not need a year-long programme to begin. A single, well-designed day with the leadership team, followed by a few targeted experiments, can shift a centre from waiting for direction to setting it.

HQ is asking the question either way. Centres whose leaders can answer it clearly, with a shared view and a credible plan, are the ones that will be trusted to lead AI-driven change across the wider organisation.

---

Common mistakes leadership teams make with AI

Even well-informed leadership teams tend to fall into a few predictable traps. Recognising them early saves months.

Delegating AI to a single function. It is tempting to hand AI to the CTO, a CoE or an innovation team and move on. But AI changes work across every function in the centre. If the wider leadership team is not involved, adoption stays narrow and the centre’s AI story to HQ stays thin.

Starting with tools instead of work. Buying licences is easy. Deciding which workflows to change, and how, is the real work. Centres that start with the portfolio map and then choose tools make better use of their budget.

Treating governance as a brake. Some leaders see guardrails as something that slows experimentation. In practice, clear rules speed things up, because teams stop waiting for permission and security teams stop blocking pilots they do not understand.

Waiting for perfect information. AI capabilities are changing quickly, and there will never be a moment when everything is clear. Leadership teams that set a direction, run small experiments and adjust every quarter make far more progress than those waiting for certainty.

Forgetting the people story. Employees hear about AI in the news and wonder what it means for their jobs. If leaders do not explain the plan, rumours fill the gap. A clear, honest message about how roles will change, and how the centre will support people through it, builds trust and makes adoption easier.

A useful habit is to review these five traps at the end of each quarterly AI discussion. If the leadership team recognises one of them in its own behaviour, that is the next thing to fix.