
AI Adoption
About this brief
What is the ECLC? The Executive Council for Leading Change (ECLC) is a global, peer-led community of more than 1,200 enterprise transformation leaders. Members meet in regular virtual roundtables of around 4545 executives, held under Chatham House rules, to share what is working, what is not, and how they are handling change.
How Tigerhall fits. ECLC is convened by Tigerhall, the transformation delivery platform for a world of always-on change. Tigerhall turns a companyโs strategy into personalized change journeys for each employee, delivered in the flow of work (Teams, Slack, Outlook, mobile) in 33 languages, with real-time data on where the change is landing and where it is stalling. Leaders own the strategy and the plan; Tigerhall runs the delivery, so a team of two or three can deliver what used to take fifteen to twenty.
What is an executive brief? An ECLC executive brief is a short, anonymised write-up of a single roundtable. It captures what the room discussed, where leaders agreed and differed, and what to do next. Each opens with a summary, then themed sections, then eight key takeaways.
Executive Summary for Closing the AI Leadership Gap
An AI transformation lead designing an executive training program asked members what leaders need to decide, build and model to lead AI transformation. Members covered strategic decisions, new skills, change-agile culture and readiness.
The consensus was that the leadership gap is less about technical knowledge and more about judgment: aligning on outcomes beyond cost savings, designing work end to end, knowing when not to use AI, and creating the safety and incentives that let people learn.
Strategic Decisions for Executives
Members named the decisions they see rising to the top.
Agree the outcome. Leadership needs alignment on the value they want, beyond cost savings, and a picture of what the organization should look like in 18 to 24 months.
Prioritize where to invest. Decide how ideas make the cut and how they will be resourced; low-hanging fruit first.
Plan the change. Early adopters will find AI changes peopleโs capacity and priorities, and change management is a core decision, not an afterthought.
Fix the data foundation. Layering AI on poor data and unoptimized systems wastes value; redesign work before deploying.
Set guardrails and cost controls. A surprise usage bill can arrive quickly.
Insist on ROI. Access for everyone is not a return on investment.
Choose tools and stewardship bodies such as responsible-AI councils and task forces.
The hostโs own team is building a toolkit for taking an agentic use case to launch, partly to show how much effort and how many partners that takes.
Measuring Return and Adoption
Use a balanced scorecard. Track sentiment, adoption, meaningful use, and proficiency, and define what each looks like.
Define meaningful use. Look past compliance logins to people redesigning work and building time-saving tools.
Separate personal productivity from building. Individual uplift is assumed and hard to measure; agents that replace human effort in measured workflows have a before and an after.
Focus on the small builder group. One organizationโs AI innovation team, under one percent of staff, builds tools removing 10 to 20 percent of hours from everyday jobs; value follows a Pareto pattern.
Do not judge by adoption alone. Adoption takes time; one member argued for judging transformation by direct, trackable financial impact.
Split governance in two: financial operations (limits, credits, routing to models) and data governance.
Central Control or Experimentation
Too much centralization slows adoption. One member encourages experimentation within policy, then runs a return analysis only on ideas with promise.
Federated models allow speed but demand clarity on decision rights and more communication.
Control the content. Build a prioritized graph of the data the model should use, and secure data-retention terms; one organization changed AI vendors because the preferred one would not agree to its terms.
Enterprise assistants are a common default because they keep data in the environment.
Skills Leaders Need
Design thinking. Without it, AI initiatives become automation that hard-codes existing behavior; value comes from reimagining work end to end. Pilot purgatory and a small initial productivity bump are common outcomes otherwise.
Openness to change in every direction, which builds credibility and surfaces resistance and excitement.
The courage to challenge. Fear of missing out pushes teams to start from the technology and look for a problem; leaders must ask if AI is the right answer, and sometimes to turn a project off.
Evaluation. Judging output is straightforward in objective tasks such as coding and hard in judgment-heavy work.
Systems thinking. Anticipate second- and third-order effects rather than react.
Inclusive leadership. Under pressure leaders default to command and control; bringing in more voices produces better solutions and buy-in.
Empathy, contextual understanding and resilience, plus tailoring the approach to each businessโs stage.
Building a Change-Agile Culture
The host noted rising skepticism: a golden-hammer mentality, environmental concerns, intimidation from a widening gap between super users and hesitant users, and change fatigue.
Resistance is not rejection. It is a human reaction and a form of feedback; quiet colleagues may be a bigger risk than vocal ones.
Work with the willing, and do not spend long converting those who reject.
Brainstorm with teams on their terms. Small-group sessions on pain points and automation opportunities reduced resistance.
Create psychological safety. Make it acceptable to experiment and make mistakes, and equip leaders at every level with talking points.
Show vulnerability. Leaders who say they are learning alongside the team encourage exploration.
Democratize, do not document. Starting by documenting everyoneโs job descriptions puts people on the defensive; empowering the business with low-code tools builds engagement.
Encourage peer learning so it is less top-down.
Redesign incentives. A change that fights the business model fails; one teamโs need for protected learning time collided with a utilization-driven model.
Tokens, Mandates and Cost Anxiety
Moving from subscription to usage-based pricing created anxiety. Teams worried about being monitored; the fix was to say it is acceptable to exceed budget while learning.
Allocation is hard, particularly when budgets are distributed across the business.
Run a representative pilot. One firm gave a mixed group free use for 60 days to measure usage and set allowances and cost guidelines.
Think beyond mandates. Usage requirements are reactive; one idea was to treat token allowances as an employee benefit.
Readiness for Transformation at Scale
Members disagreed on how to judge readiness.
Adoption threshold first. One view: true transformation, which redesigns workflows and how managers lead people and AI, cannot happen until a large majority, around 80 percent, uses AI in everyday work. It can be reached within a single function.
The cost: an adoption threshold may take around 18 months, a hard conversation with finance leaders.
Impact first. A counter-view: judge success by measurable financial impact, since adoption will have its own curve and should not be the primary test.
Key Takeaways
Align on outcomes beyond cost. Define the 18-to-24-month picture.
Fix data and process before layering AI.
Measure with a scorecard, and measure builders separately from everyday users.
Let people experiment inside clear guardrails. Add governance when something shows promise.
Develop design thinking and the confidence to say no.
Treat resistance as feedback and listen for the quiet colleagues.
Build psychological safety through leaders who model learning.
Align incentives and cost policies with the behavior you want.



