On a recent episode of the Leading Learning podcast, JD Dillon made a point that should land hard with anyone planning AI training for an association staff. Courses and conferences, he argued, don’t fit how most people actually work. His alternative is simple: reliable access to information at the point of need, learning from peers, and short, frequent practice. In his words, “three minutes a day actually matches how we work as people in terms of our memory, especially if we’re able to apply that information quickly.”
Dillon was talking about frontline workers. But he also made the case that these principles carry over to desk-based teams. We think that’s especially true for AI.
Here is how AI training usually goes at an association. Someone books a lunch-and-learn or a half-day workshop. Attendance is good. People leave energized. Then Monday comes, the renewal campaign is behind, and the new prompting technique sits unused until it’s forgotten.
A few months later, leadership looks at adoption and sees the same handful of enthusiasts doing interesting things while everyone else uses AI the way they did before, or not at all. The board asks what the AI plan is, and the honest answer is “we did a training.”
The issue isn’t the quality of the session. It’s the shape of it. A single event asks people to absorb a lot at once and then apply it later, on their own, under deadline pressure. That’s the opposite of how skills stick.
Structured learning still matters. Your staff need shared vocabulary, a sound mental model of what AI is good at, and clear rules about safe use. That foundation is worth real time.
But the foundation is the start, not the finish. What turns knowledge into fluency is the daily rhythm afterward: small, repeated moments where someone uses AI on real work, gets a result, and adjusts. We made a related argument in The Fluency Trap: classroom training alone creates false confidence. The question this piece answers is what the day-to-day rhythm should actually look like.
None of these require a budget or a new tool.
1. Build a shared answer bank. Dillon’s first principle is reliable access to information when someone needs it. For AI, that means a single, easy-to-find place with your approved tools, your AI policy in plain language, and a growing set of prompts and examples that worked on real association tasks. A shared document or an intranet page is enough to start. When a staff member is staring at a blank screen before a board report, they shouldn’t have to remember a workshop slide. They should be able to look it up in thirty seconds.
2. Make peers the teachers. Every association has a few staff members who figured out something useful with AI on their own. Give them a standing ten minutes at the weekly staff meeting to show one real task, start to finish, including what didn’t work. Rotate departments so the events team sees what finance is doing and vice versa. Peer examples are more credible than vendor demos because they come from the same inbox, the same members, and the same deadlines.
3. Ask for three minutes, not three hours. Instead of blocking a quarterly training day, ask every staff member to try AI on one real task each day, even a small one: summarizing a long member email, drafting a first pass at a session description, cleaning up meeting notes. Keep it inside your policy, and keep it low stakes. The goal is repetition. If you want to go further, pick one narrow, repeatable task per department and focus there first, which we covered in Stop Automating Everything.
Sidecar’s AI Learning Hub for Teams gives your staff the foundation and the rhythm. The core courses build shared vocabulary and safe practice. Department pathways for events, finance, fundraising, governance, HR, marketing, membership, and operations keep the learning tied to each person’s actual job. Every learner works toward the Association AI Professional (AAiP) certification.
After the courses, the rhythm continues. A use case library gives staff a place to find examples when they need them. Office hours give them a place to bring real questions. Quarterly continuing education keeps skills current as the tools change. And because every tier includes unlimited users, you can bring the whole staff along, not just the early adopters.
More than 30,000 association professionals are already part of Sidecar’s AI learning community.
One great training session won’t make your staff fluent in AI. A few minutes of real practice every day, with good information close at hand and peers to learn from, will. Start the habits this week, and give them a strong foundation to build on.
Ready to build AI fluency across your team? Explore the AI Learning Hub for Teams at sidecar.ai, or book a call with our team.
Is a one-time AI workshop enough for association staff?
Rarely. A workshop can build awareness, but skills fade without regular practice on real work. Pair structured learning with short, daily use and easy access to examples.
What is microlearning for AI skills?
It means short, frequent learning moments, often a few minutes, tied to a real task. For AI, that could be trying a new prompt on a member email or reviewing a colleague’s example.
How do we keep staff AI use safe while encouraging daily practice?
Publish a plain-language AI policy first, list approved tools, and set clear rules on what member data never goes into consumer AI products. Then encourage practice inside those limits.