Your first 30 days as an AI enablement lead, week by week

The month, one line a week

Week 1: listen and count

Start with the boring data. List every AI tool the company pays for, how many seats each has, and who touched it in the last 30 days. Johnson Controls writes the reclaiming and review of licenses into the job. Harvard’s posting points to usage trends for renewals. Both start from a seat count, and so should you.

Then talk to people, and be careful how. In Deloitte UK’s survey, 64% of weekly generative AI users said they worry their managers will think AI can do their jobs (Ipsos UK fieldwork, May to June 2026). A new lead who asks “what are you using AI for?” is asking someone to take a risk. So ask for the task, the tool and what it saves. Say you will report by tool and team, never by person. Then find the people who are already good at it. Second Talent says every organization has some. Skip company-wide training, which Second Talent says produces broad, shallow adoption when a generalist runs it, and skip the questionnaire. There are five ways to find use cases that need no survey.

Week 2: pick three workflows and take a baseline

Three workflows, not thirty. Spectris asks its lead to keep one list of opportunities with a business owner, expected value, risk and status, and I would hold each of the three to that. No business owner, no place on the list. If you want a scoring sheet, the prioritization template scores by measured hours, with ease and risk beside them.

Then take the baseline, and do not ask for it. In METR’s trial, 16 experienced developers expected AI to make them 24% faster on their own real tasks, believed afterwards that it had made them 20% faster, and were measured 19% slower. The tools were from early 2025 and METR now calls the result out of date, so I cite it for the gap between belief and clock, not for what AI does today. Second Talent puts the same point bluntly: without a measurement of how long a task took beforehand, every claimed gain is an anecdote.

Skip scoring forty ideas, and skip promising that any of the three will work. A baseline is a measurement, not a commitment.

Week 3: write the rules and open a place to share

Second Talent warns that a program running ahead of policy collides with it, so write the policy before you run the program. One page, in front of security and legal, with three lists. Tools that are approved, in review and not allowed. What data may go into each. Who answers a request for a new tool, and in how many days. Pick the number of days and meet it.

Say what happens to people who used an unapproved tool before the page existed. I would say nothing happens. In PagerDuty’s survey (Wakefield Research, 1,250 office professionals, April 2026), 48% of workers who had used AI they thought was not allowed faced formal consequences such as a warning or disciplinary action. That is how you teach the next person to stay quiet. I would skip the ban too. In the Melbourne and KPMG survey, uploading company information to public AI tools was most common where the employer had banned generative AI: 67%, against 33% where there was no policy. That is an association in self-reports, not proof that bans cause it.

Then give the methods from week 1 somewhere to live. A folder, one card per method: what it does, who owns it, a version, a before-and-after check on 3 to 5 real past cases, and a status of draft, trusted or retire. The skill library template has the card. Keep it small. In SkillsBench, a lab benchmark, curated skills lowered the pass rate on 13 of 87 tasks, so a pile of untested skills is not a safe default.

Last, teach one habit to every manager you can reach. When someone shows a method, the first reply is a question about how it works. USC Marshall’s researchers, who surveyed 604 US employees who use AI daily, say people can tell within the first thirty seconds whether the supervisor is supportive. Skip the disclosure form, the detection tool and the big prize. All three arrive before the trust they need.

Week 4: show one result you can defend

You will be tempted to show a number that looks like savings. Don’t. After 30 days you can defend four things: what the company pays for and who uses it, a baseline for three workflows, a rule people can read, and a place where methods are collected.

If a champion already works a new way in one of the three workflows, you can add one line. Time ten of their cases the way you timed the baseline and put the median beside it. Label it plainly: ten cases by one person, not a rollout and not a gain you can multiply. Different people did the cases, so it is a comparison, not a measurement of AI.

Johnson Controls wants a lead who can tell activity from adoption. Logins, license counts and training attendance are activity. Spectris lists hours saved as a metric, and I would time a sample before I believed one. For days 31 to 90 I would track one pair: the share of the team still working the new way after 30 days, next to time per task against the baseline. You cannot report the first number in month one. Say so on the page, and give the date it arrives.

Then do one thing that shows judgment. Second Talent says the job includes running an intake and being willing to reject most requests, and Unity asks its lead to retire tools that do not earn their place. Turn one request down, in writing, with the reason.

Why I would not buy a tool in month one

It is the advice sponsors like least. You cannot write the requirement until you have the seat inventory and three baselines, and no product covers the whole job. In the platforms post I split the job into five parts: find use cases, track adoption and impact, govern tools, train people, share skills. From each vendor’s own pages, no product was rated full on more than three. Betts Recruiting lists different teams settling on different tools for similar tasks as a symptom of a missing lead, and one more tool will not cure that.

That post says to start with measurement when you do buy, and I stand by the order, not the date. There is one exception: a dashboard you already own. Microsoft’s page says the Copilot Dashboard needs neither a Viva Insights license nor a Copilot license to view, for customers with a qualifying Microsoft 365 subscription. It covers Microsoft Copilot only. For what the other tools measure, see the adoption analytics comparison.

The Friday review

At the end of each week, answer these before you leave. The first four are the same every week.

What I could not find

I found no posting or explainer with a 30-day plan, and no study that tested a first-month order or measured whether any order changes results. So this is judgment, built from what the postings ask for and what the studies say about estimates and fear. A lead who knows the company will change it.

Sources

1. The Betts Team. “What is a Head of AI Enablement?” Betts Recruiting, July 20, 2026.
2. “AI Enablement Lead: Key Skills & Responsibilities in 2026.” Second Talent, August 14, 2026.
3. “AI Enablement Lead (job posting).” Unity Advisory, via Ashby, accessed October 14, 2026.
4. “AI Enablement Lead (job posting 002871SR; expired).” Harvard University Information Technology, accessed October 15, 2026.
5. “AI Enablement Lead (job posting, Particle Measuring Systems).” Spectris, via Workday, published August 24, 2026.
6. “AI Enablement Leader (job posting).” Johnson Controls, accessed October 15, 2026.
7. “Head of AI Enablement (job posting R-100190; expired).” J.D. Power / Autodata, via London Tech Jobs, posted June 30, 2026.
8. “British workers spend nearly £1bn of their own money on GenAI for work, landmark Deloitte research finds.” Deloitte UK, September 16, 2026.
9. “PagerDuty Survey: 66% of Office Professionals Have Used AI Tools or Services at Work Despite Not Being Allowed Under Company Policies.” PagerDuty, survey by Wakefield Research, June 2026.
10. Nicole Gillespie, Steve Lockey, Tabi Ward, Alexandria Macdade and Gerard Hassed. “Trust, attitudes and use of artificial intelligence: A global study 2025.” The University of Melbourne and KPMG, April 2025.
11. Alexander Bernard. “Why Are Employees Reluctant To Disclose AI Use to Their Bosses?” USC Marshall School of Business, August 28, 2026.
12. Joel Becker, Nate Rush, Beth Barnes and David Rein. “Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity.” METR, July 10, 2025.
13. Xiangyi Li, Yimin Liu, Wenbo Chen, Bingran You and others. “SkillsBench: Benchmarking How Well Agent Skills Work Across Diverse Tasks.” arXiv (2602.12670, version 4), read October 16, 2026.
14. “Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers.” Microsoft Learn, accessed October 16, 2026.
15. “The system for AI enablement teams.” Nolli, accessed October 16, 2026.

Plain-text copy: /blog/first-30-days-as-an-ai-enablement-lead.md