TL;DR
Most internal AI surveys produce vibes data nobody acts on. The survey below produces decisions. Five categories (current usage, blockers, training gaps, sentiment, change management readiness), 10 to 15 questions, run pre-launch as a baseline, again at 90 days, then annually. Commit to three outputs before you launch: a leadership readout, a per-team action plan, and an updated training roadmap. Copy the question list inline.
- Five categories. 10-15 questions.
- Pre-launch baseline, 90-day re-survey, annual.
- Anonymous for sentiment, attributed for usage.
- Commit to outputs before launch.
In this article
Why most AI surveys fail
I have seen a lot of internal AI surveys at consumer brands. Almost all of them produce data that goes nowhere. The pattern is consistent. HR or comms launches a 40-question survey with vague Likert scales. The response rate is 35 percent. The results land in a deck nobody opens. Three months later, the same team is asking the same questions again because no one acted on the first set.
The failure modes are predictable.
- Too long. 40 questions kills response rate and dilutes the signal. 10 to 15 questions is the sweet spot.
- Too vague. "Do you feel positively about AI?" is unactionable. "Which workflows do you currently use AI for?" is.
- No commitment to outputs. The team launches the survey without agreeing what will be done with the results. The data lands and nothing happens.
- Wrong cadence. Monthly is fatigue. One-time is no trend line. Pre-launch / 90-day / annual is the right rhythm.
- Mixed anonymous and attributed. The team wants honest sentiment data but also wants to segment by department. The result is either dishonest answers or unusable data. Run two short surveys instead.
The survey below avoids all five. It is short, specific, action-oriented, and runs on a cadence that produces a trend line.
If you cannot name the three outputs the survey will produce, do not launch the survey.
When to run it
The survey runs three times in the program lifecycle. Skip any of the three and the data loses meaning.
Pre-launch baseline. Before any company-wide AI rollout, before any training program, before any tool is purchased for the whole org. The baseline captures where the team starts, so future surveys have a comparison point. The baseline is the most important run.
90 days post-launch. Three months after the first major AI rollout. This is where you find out what is actually working, what training gaps emerged, what blockers nobody told you about, and where adoption is fake (logged but not real). Most program corrections happen after this survey.
Annual thereafter. Once the program is in steady state, an annual run is enough to track sentiment, capability spread, and trend. Quarterly is overkill for most consumer brands. Monthly is survey theater.
The five categories that matter
1. Current usage
What is the team actually doing with AI today. Frequency, tools, workflows. Self-reported, but useful because it forces the respondent to name something specific.
2. Blockers
What is stopping more usage. Tooling, training, time, permission, trust, data access. The single most actionable category.
3. Training gaps
What the team feels they need to learn. Specific. Not "more training" but "I need to learn how to write a prompt for our CX system."
4. Sentiment
Do they trust AI in their workflow. Do they think it is making them more or less effective. Are they worried about their role.
5. Change management readiness
Do they see leadership support. Do they understand the strategy. Do they have an outlet for feedback. This category is what separates an AI program with momentum from one that is stalling. For the deeper treatment of this work, see AI change management for frontline teams.
The AI adoption survey (copy this)
Copy this. Run it pre-launch, then at 90 days, then annually. Keep the question wording consistent across runs so the trend line is real.
# AI Adoption Survey: [Company Name]
**Survey window:** [start date] to [end date]
**Run number:** [Baseline / 90-day / Annual]
**Estimated time:** 7 minutes
**Anonymity:** Anonymous for sentiment, team-level segmentation for usage
---
## Section 1: Current usage (attributed at team level)
**Q1.** Which team do you sit on?
- [List of teams]
- I prefer not to say
**Q2.** Which of these AI tools have you personally used for work in the
past 30 days? (Select all that apply.)
- [List of company-sanctioned tools]
- Other AI tool not on this list
- None
**Q3.** How often do you use AI tools for work?
- Daily
- A few times per week
- Once or twice per month
- Less often
- Never
**Q4.** For which of these workflows have you used AI in the past 30 days?
(Select all that apply.)
- Writing / editing
- Research / synthesis
- Data analysis
- Customer-facing communication
- Creative production
- Coding / engineering
- Internal communication
- Other: [free text]
- None
## Section 2: Blockers
**Q5.** What is the single biggest thing stopping you from using AI more
in your work? (Select one.)
- I do not know which tool to use for what
- I do not have access to the right tools
- I do not have time to learn
- I do not trust the output for my work
- My workflow is not a good fit
- My manager has not signaled support
- I have concerns about data or privacy
- Other: [free text]
- Nothing, I use AI as much as I want to
**Q6.** What would make you 2x more likely to use AI in your work?
[Free text, 1-3 sentences]
## Section 3: Training gaps
**Q7.** Which of these would be most useful to you in the next 90 days?
(Rank top 3.)
- A workshop on prompting for my specific role
- 1:1 office hours with someone fluent in AI
- A library of role-specific prompts and templates
- A clearer policy on what is and is not okay to do with AI
- A faster way to share what works across the team
- Examples of AI workflows from others on my team
**Q8.** On a scale of 1-5, how confident are you in your ability to use
AI effectively for your current role?
- 1 (not confident at all) to 5 (very confident)
## Section 4: Sentiment (anonymous)
**Q9.** AI tools are making me more effective at my job.
- Strongly disagree / Disagree / Neutral / Agree / Strongly agree
- I do not know
**Q10.** I trust AI output enough to use it in customer-facing work.
- Strongly disagree / Disagree / Neutral / Agree / Strongly agree
- Not applicable to my role
**Q11.** I am concerned about how AI will change my role over the next
12 months.
- Strongly disagree / Disagree / Neutral / Agree / Strongly agree
## Section 5: Change management readiness (anonymous)
**Q12.** I understand my company's AI strategy.
- Strongly disagree / Disagree / Neutral / Agree / Strongly agree
**Q13.** My manager has been clear about how AI fits into my work.
- Strongly disagree / Disagree / Neutral / Agree / Strongly agree
**Q14.** I have somewhere to share feedback about AI tools and policies.
- Yes, and I have used it
- Yes, but I have not used it
- No
**Q15.** [Optional] Anything else you want leadership to know about
how AI is landing on your team?
[Free text]
---
**End of survey. Thank you.**
A summary of results will be shared in [time frame, e.g. 2 weeks].
Specific actions and follow-ups will be communicated within 30 days.Fifteen questions. Seven minutes. Five categories. The wording is intentionally specific. "How often do you use AI tools for work" is answerable. "Do you embrace innovation" is not.
How to score and segment the results
The data is only useful if you commit to three outputs before you launch.
Output 1: One-page leadership readout. Top-line response rate, current usage frequency, top three blockers, top three training requests, sentiment score (Q9), strategy clarity score (Q12). One page. Sent to leadership within two weeks of the survey closing.
Output 2: Per-team action plan. For each team large enough to segment, the team lead gets a one-page memo with their team's results plus the top three actions they own. Action plans get reviewed at the next monthly leadership meeting.
Output 3: Updated training and enablement roadmap. The training requests in Q7 and the blockers in Q5 inform the training roadmap for the next quarter. The roadmap is published within 30 days of the survey closing.
If those three outputs do not happen in the 30 days after the survey closes, the survey was decorative. Commit to them in writing before launching, or do not launch.
For the broader program this survey sits inside, see the AI Transformation Playbook for Consumer Brands and the AI Transformation Roadmap Template. For the change-management work the survey feeds, see AI change management for frontline teams.
Surveys are a contract with your team. The contract is that you will act on what they tell you. Break it once and the next survey has half the response rate.
The bottom line
Most internal AI surveys produce vibes data nobody acts on. The survey above produces decisions. Five categories, 10 to 15 questions, run pre-launch as a baseline, again at 90 days, then annually. Anonymous for sentiment, attributed at the team level for usage. Three committed outputs: leadership readout, per-team action plan, updated training roadmap.
Copy the survey. Commit to the outputs. Run the cadence. The survey is only useful if the team trusts that telling you the truth will result in something changing.
FAQ
When should you survey employees about AI?
Three times. Pre-launch as a baseline, before any company-wide AI rollout. 90 days post-launch to measure adoption and surface blockers. Annually thereafter to track sentiment, training gaps, and capability spread. Surveys that happen on no fixed cadence produce data nobody acts on.
What questions matter on an AI adoption survey?
Five categories: current usage (frequency and tools), blockers (what is stopping more usage), training gaps (what they need to learn), sentiment (do they trust AI in their workflow), and change management readiness (do they see leadership support). 10 to 15 questions total. Anything more is a sign the survey is not focused.
How often should you run the AI survey?
Pre-launch as a baseline, then at 90 days post-launch, then annually. Quarterly is too frequent for most companies. Monthly is survey fatigue. The cadence has to match the speed of meaningful change in the program. Annually is the default for steady-state.
Should AI adoption surveys be anonymous or attributed?
Anonymous for sentiment and blocker questions. Attributed for usage and capability questions, because the data is more useful when you can segment by team. Run two short surveys instead of one long one if you cannot mix anonymous and attributed in your tooling.
What do you do with AI survey data?
Three outputs: a one-page readout to leadership, a per-team action plan owned by the team lead, and an updated training and enablement roadmap. If none of those three exist 30 days after the survey closes, the survey was decorative. Commit to the outputs before launching the survey.
How do you avoid bias in an AI adoption survey?
Three rules. Do not ask leading questions ("Do you agree that AI is transforming our work?"). Use balanced scales (equal positive and negative options). Allow "I do not know" as an answer. Pilot the survey with a small group first to catch confusing or biased wording before you push to the whole company.