Let me say something that most AI conversations skip right over: the organizations getting real value from artificial intelligence are not the ones with the most sophisticated tools. They are the ones with leadership that decided intentionally, clearly, and early what AI was going to mean for their mission.

I work with associations and mission-driven organizations every day. And in the last two years, I have watched AI go from a curiosity to a board agenda item to a source of very real pressure. Staff are experimenting on their own. Vendors are showing up with demos. Board members are asking why you haven't moved faster. And somewhere in the middle of all that noise, the question lands on someone's desk (usually the IT Director) and it gets treated like a systems question.

It is not a systems question. It is a leadership question.

Why This Keeps Getting Handed to IT

There is a pattern I see across organizations of every size. When something involves technology, it gets routed to the person who is most comfortable with tech. Maybe that's your IT Director. Maybe it's a staff member who has become the unofficial go-to because they can coax the printer back to life and figure out why Zoom isn't connecting. They get handed the AI question because, it's a tool, isn't it?

But AI isn't a tool in the way a new accounting platform is a tool. Selecting AI (real AI, applied with intention) requires answers to questions that IT simply cannot answer alone:

• What outcomes are we trying to drive for our members?
• Where is operational friction costing us capacity we can't afford to lose?
• What are we willing to change about how we work and what is off the table?
• The Why. What problem are we actually solving? Not what AI can do in general, but what does our organization need it to do for us? If the answer is "stay current" or "because the board asked," that is not a Why. That is pressure. A real Why is specific: reduce the hours spent on manual reporting, improve how we onboard new members, give our team time back for the work that requires human judgment.
• The Guardrails. Governance is not an IT function. Decisions about what data AI can touch, how staff are expected to use it, what review processes exist before AI-generated content goes to members; these are leadership decisions. Without clear guardrails set from the top, you get inconsistent adoption, staff anxiety, and real risk.
• The Culture Signal. How leaders talk about AI sets the tone for everyone else. If leadership is dismissive, staff won't engage. If leadership is uncritical, staff won't push back when something isn't working. The organizations I have seen use AI well have leaders who are visibly learning alongside their teams. They are asking questions, setting expectations, and treating AI as a collaborator, not a silver bullet.

Those are strategy questions. They belong in the CEO's office, the leadership team's retreat, and the board's governance conversation. When they get delegated down the org chart, something important gets lost and you usually don't realize it until you're six months into a tool adoption that isn't delivering.

What AI Actually Requires from the Top

Here is what I tell every executive team before they start an AI conversation in earnest: AI is not a vending machine. You do not drop in the right prompt and get a flawless result. You do not buy a platform and walk away. AI requires active leadership: before, during, and long after go-live.

Specifically, leadership needs to own three things:

The Question That Changes the Conversation

I work with a lot of leadership teams that come into the AI conversation asking, “What should we be using?” It is a reasonable question, but it is usually the wrong starting point.

The better question is: “What would need to be true about how our organization works for AI to actually help us?”

That question surfaces things like: whether your data is clean enough to be useful, whether your processes are documented well enough to be automated, whether your staff has the capacity to learn something new right now. It brings the real constraints into the room before a vendor does.

A good strategist will help you ask that question honestly, and they won't push you toward a specific platform until you have answered it. The tool selection comes last. The strategy comes first.

What This Looks Like in Practice

Imagine instead of handing AI off to your IT team and hoping for the best, your leadership team spends a focused half-day identifying the two or three operational pain points that are costing you the most capacity; and defining what success would actually look like.

Imagine instead of reacting to a vendor pitch, you walk into the demo with a clear set of requirements rooted in your mission, and you know which questions to ask because leadership has already aligned on the answers.

Imagine instead of staff quietly experimenting without guidance, your team has a clear framework for how AI fits into their work; including what can accelerate it, where human judgment is non-negotiable, and how to flag concerns without feeling like they're slowing things down.

None of that happens without leadership driving it. And with it right approach, all of this is achievable for an association of any size.

Final Thought

Moving forward, AI will shape how associations operate. The organizations that navigate it well won't necessarily be the ones with the biggest budgets or the most sophisticated technology stacks. They will be the ones where leadership decided to lead, to ask the hard questions, set the right guardrails, and stay engaged through the learning curve.

This isn't about replacing your team with software. It isn't about chasing every new model that comes out. And it isn't about hoping someone figures it out below the leadership line.

It is about making intentional, mission-aligned choices before the pressure makes them for you.

Daniel is a technology strategist and Principal at Strategico Consultants, where he advises associations and mission-driven organizations on technology strategy, AI adoption, and organizational change.