AI Readiness Has No Finish Line 

Written by Sara Spalt 

When associations start an AI readiness effort, they often frame it the same way they’d frame a software implementation. There’s a scope, a timeline, a set of deliverables. When the deliverables are done, the project closes. The team moves on. 

That framing is understandable. Associations run on project-based work, and it’s natural to apply that structure to something new. But in nearly every engagement I’ve been a part of, the organizations that treated AI readiness as a project found themselves revisiting the same ground six to twelve months later — re-educating staff, re-explaining policies, re-doing work they thought was finished. 

The problem wasn’t poor execution. It was the assumption that “done” was a meaningful destination. 

Where Most Organizations Actually Are 

When we start working with an association on AI, one of the first things we do is try to understand where the organization sits on the readiness spectrum — and that spectrum is wider than most leaders expect. 

On one end are organizations where AI hasn’t been formally acknowledged at all. Staff may be using tools quietly, without any guidance or governance, because no one has said anything one way or the other. On the other end are organizations that have policies, training programs, and dedicated internal resources actively driving adoption. Most associations fall somewhere in between: some awareness, some use, limited structure. 

What becomes clear quickly is that where an organization sits isn’t fixed. Staff turn over. Tools evolve. Use cases that didn’t exist six months ago become relevant. A policy written for 2024 may already be strained by what tools can do in 2026. Readiness is a moving target — which means maintaining it requires ongoing attention, not a one-time push. 

What a Practice Looks Like 

The organizations I’ve seen build durable AI capability share a few habits. 

They take regular pulse checks. Instead of relying on a single baseline survey, they return to their staff periodically to understand how usage has changed, where friction points are, and what questions have surfaced since the last check-in. This doesn’t have to be elaborate. Even a short annual survey combined with a few informal conversations can surface things that leadership wouldn’t otherwise see. 

Their governance evolves. An acceptable use policy isn’t a document you write once and file away. Associations with mature AI programs treat governance as living infrastructure — something that gets reviewed when tools change, when staff voice concerns, or when something unexpected happens in the broader environment. 

Training is embedded, not episodic. A single all-staff training session, however well-designed, has a short half-life. The organizations making real progress on adoption have found ways to fold AI into onboarding, into team meetings, into the normal flow of how work gets talked about — so that building capability doesn’t depend on people remembering what they learned at a launch event eight months ago. 

Champions stay active. Many associations launch with an internal champions program — a group of willing staff who help drive adoption across teams. The ones that sustain momentum treat those champions as an ongoing resource, not a launch mechanism. They give them visibility, support, and updated guidance as things change. 

The Bigger Question 

The question worth sitting with isn’t whether your organization has completed an AI readiness effort. It’s whether you’ve built the habits to keep up as AI becomes more embedded in how your team works. 

The associations making the most progress aren’t necessarily the ones that invested the most upfront. They’re the ones that built a rhythm — small, consistent actions that keep readiness current as the landscape around them continues to shift. 

That’s a harder goal than closing out a project plan. But it’s also a more honest one.