Helping your staff adopt AI: role-based training, champions and fear
When nonprofits plan for AI, most of the energy goes into data and tools, like which platform to pick and whether the CRM is clean enough. Those questions matter. When I see a rollout stall, though, the cause is usually on the people side.
Most often staff got training that didn’t fit their job, or nobody knew who to ask when they got stuck, or people were quietly worried about what AI meant for them and never said so. You can plan for all of that the same way you plan for the tech.
Why generic training doesn’t stick
The biggest failure point I see in any new tech rollout is generic training. Giving a fundraiser the same AI prompt guide as your accountant won’t work. Their days look nothing alike, so the examples won’t land for either of them.
People pick up a tool when it fixes a problem they had this morning. So AI training has to be specific to the role and practical right away. Here’s where I’d focus for each group:
- Fundraisers. Using AI to summarize a donor’s history before a cultivation call.
- Program staff. Using AI to pull themes out of client feedback for an impact report.
- Admin staff. Using AI to draft internal documentation and clean up data.
When people see AI handle a specific pain point in their own day, they come back to it the next morning. That’s when adoption really takes off.
Someone has to own the questions
The second gap is support. When a staff member has an AI question, like which prompt works best or whether they’re allowed to paste in a donor’s details, who do they ask?
In a lot of organizations the honest answer is nobody. So people guess, or they give up.
Every nonprofit needs a designated AI champion, or a small task force if you’re bigger. The champion’s job has three parts:
- Set policy. Make the rules on data use and privacy clear, and keep them current.
- Provide support. Be the go-to person for prompting help and troubleshooting.
- Share what works. Pass good examples from one department to the others.
Pick someone curious who colleagues already go to when they’re stuck. They don’t need a tech background. This small support system ends up being the backbone of your change management.
Fear is the biggest hurdle
The number one thing that keeps staff from adopting AI is fear. Some people worry they’ll look incompetent with a new tool. A lot of them worry about their jobs.
The framing that helps most is AI as a co-pilot. Its job is to take on the shovelling work, the manual and repetitive tasks, so your team has more time for thinking work like strategy and building relationships. Your staff stay in charge. They decide what the AI works on and check what it produces.
Focus your training on the human work AI makes room for. Once people can see the time it gives back, the fear starts to ease.
How to roll it out
- Name your champion first. Before any training, pick the person staff will go to with questions, and tell everyone who it is.
- Write the basic rules down. Have the champion draft a short page on what data can go into which tools. People experiment more freely once they know where the lines are.
- Train by role, in small groups. Run separate short sessions for fundraising, programs and admin. Build each one around a task from that team’s real week.
- Use people’s own work. Ask everyone to bring something from their desk, like a donor file or a stack of feedback forms. They’ll remember what they did with it far better than a demo.
- Talk about the fear openly. Ask people what worries them, and answer honestly. Telling staff plainly that AI is there to take work off their plate does more than any slide deck.
- Share wins every month. Have the champion collect examples of time saved and pass them around at staff meetings.
For leaders: put the people side in the plan
It’s easy to put all your planning into data and tools and hope the people side sorts itself out. The rollouts I’ve seen work had a leader who planned for the people using the tools just as carefully as the tools themselves.
A few questions to ask before you roll anything out:
- Is our training built around each role’s actual work?
- Who’s our AI champion, and does everyone know?
- Have we told staff plainly what AI means for their jobs?
- How will good ideas get from one department to the next?
If you’re not sure what the quick wins are for each team, my free Nonprofit AI Readiness Roadmap looks at fundraising, programs and admin separately and gives you quick wins for each. That makes a good starting list for role-based training.