In 2025, I led work at two associations on what I'd now call a member microlearning system. At the first association, I was on staff as Chief Marketing & Membership Officer. We had a webinar content archive that had been building for years. Members weren't using it. Staff couldn't keep up with surfacing it manually. I wanted to know if AI could help.

We did the work. We built the system. We launched it.

And I want to tell you what I learned, because it's not the lesson I expected to learn.

We did not build a chatbot. Chatbots are reactive: a member has a question, the bot answers. They're useful, especially for member service and just-in-time questions.

What we built was different. We took the association's existing content and transformed it into a microlearning system. By using AI tools in our pilot, the same webinar became a three-minute summary and a printable job aid. As always, we had the human subject matter expert review and approve all AI-generated materials.

We used Venngage for creating branded infographics quickly, and ChatGPT + Otter.ai to create the executive summaries.

The framing matters because it shapes what the engagement is actually for. A chatbot answers. A microlearning system teaches. Both move knowledge. They produce different kinds of learning.

I went into the work thinking the hard part was the build itself. That work can be hard, technically and editorially. But it was, in retrospect, the part of the work I was most prepared for. I'm an adult learning subject matter expert with years of instructional design experience, and I know how to create engaging learning experiences for working professionals.

By the time we launched, the system itself was good. The web page was up. The technical implementation worked. The first few member interactions were promising.

And then we hit the part I was less prepared for.

We promoted the launch. There was a web page. The monthly webinar emails mentioned the new system. Staff knew it existed. A handful of members tried it.

And then the energy faded.

Not all at once. Slowly. The web page sat there. The email mentions kept happening but became routine. We weren't tracking usage in any disciplined way. We weren't iterating based on what members actually did with it. The system existed. It just didn't grow into the thing we'd hoped it would.

That gap wasn't anyone's fault, exactly. The build was scoped well. The launch happened on schedule. But the operating rhythm that would have made the roadmap real didn't get built into the work, and once the initial push ended, the calendared follow-through didn't have an owner.

1. The 12-month roadmap is necessary but not sufficient

A roadmap is a list of activities. What's missing, almost every time, is the operating rhythm: who does each activity, on what calendar, and how is success measured? Without that layer, the roadmap describes a destination but doesn't build the road.

If I could redo that work, I would replace the 12-month roadmap with a 12-month operating plan. Same activities, but with named owners, calendared dates, and a quarterly review process.

2. The work should include a 30-to-60-day post-launch period

The first 60 days after launch are when the patterns get set: who promotes, what gets tracked, what gets iterated, who notices when usage flatlines. If those patterns aren't established with focused attention, they often don't get established at all.

3. Tracking should be designed into the work, not added later

We didn't capture good baseline data. We didn't set up usage tracking in a sustained way. By the time we wanted to know whether the system was working, we couldn't easily tell.

If I could redo it, tracking would be set up in week one, not week 12.

Each of these changes points to the same underlying principle: the work isn't about building a system. The work is about establishing the operating rhythm that makes the system actually used.

A microlearning effort that produces a working system and no operating rhythm has only done half the job.

My approach has evolved. If I were starting this work with your association tomorrow, the engagement wouldn't begin with a content audit. It would begin with members — structured conversations to understand their work, their pain points, and their priorities for what they need to learn next.

From those conversations, we'd identify two or three priority knowledge transfer needs. Then we'd design a pilot: a small, focused microlearning system built around those priorities, drawing from your existing content archive.

That sequence matters. Most content engagements start with the archive and ask "what could we do with this?" The better question is: "what do members need to do at work, and what in our archive could help them do it?"

→ Book a 30-minute consultation: Book time with Cathy to explore how we can help your association capture more member value from its resources.