Before You Buy a Single AI Tool, Answer These Five Questions.

There is a pattern we see in organizations that have tried AI and quietly shelved it. They moved fast. They picked a tool that looked promising, rolled it out to their team, and waited for the results everyone was talking about.

The results didn’t come. Or they came briefly and then faded. And the conclusion the organization drew was that AI wasn’t ready for them, or wasn’t right for their industry, or needed more time to mature.

That conclusion is almost always wrong.

The tool wasn’t the problem. The foundation was. Specifically: five things that need to be true about your organization before AI can do anything more than impress people in a demo.

These are not technical prerequisites. You don’t need a software team or an IT department to answer them honestly. You need about fifteen minutes and a willingness to look clearly at how your organization actually operates today.

Question 1: Where does your team’s time actually go?

Not where it’s supposed to go. Not the job description version. Where does it actually go on a normal Tuesday?

Most leaders have a rough sense of this but have never mapped it with any precision. They know their office manager is busy, but they couldn’t tell you how much of that busyness is genuinely skilled work versus tasks that repeat themselves every week without requiring much judgment.

AI delivers its highest return in the second category. If you can’t identify where that work lives in your organization, you can’t aim AI at it. You’re just introducing a powerful capability into an undefined space and hoping it finds something useful to do.

What you’re looking for: the repeatable, time-consuming tasks your best people are doing that don’t actually require your best people.

Question 2: Is your most important knowledge written down, or does it live in someone’s head?

This question exposes something most organizations don’t want to admit: a significant amount of institutional knowledge exists only in the minds of the people who have been there long enough to absorb it.

How does your school handle a mid-year enrollment exception? Who approves a customer refund above a certain amount, and what are the actual criteria they use to decide? What does onboarding a new hire really involve, beyond the official checklist?

AI cannot operate on undocumented knowledge. It can’t interview your most experienced employee and absorb fifteen years of judgment. It works from what is written, structured, and accessible. Organizations that haven’t done the work of making their processes legible will find AI has nothing solid to stand on.

What you’re looking for: a clear picture of which processes are documented well enough that someone new could execute them correctly on day one.

Question 3: How does your team actually feel about change?

This is the question most AI implementation plans skip entirely, and it is the one that kills the most initiatives.

Technology isn’t neutral inside an organization. It lands differently depending on the culture it enters. A team that feels overworked and undervalued will interpret a new AI tool as evidence that leadership’s solution to their exhaustion is to automate them. A team that trusts leadership and understands the why behind a decision will engage with the same tool as an opportunity.

The difference between those two outcomes is not the tool. It’s the communication, the framing, and the involvement of the people whose jobs are actually changing.

What you’re looking for: an honest read on whether your team has the trust and psychological safety to engage with something new, or whether that foundation needs attention first.

Question 4: Can you point to one workflow that costs you the most and changes the least?

Organizations that try to transform everything at once with AI transform nothing. The scope becomes unmanageable, the wins are too diffuse to measure, and the initiative stalls before it demonstrates enough value to sustain itself.

The organizations that get AI right almost always start the same way: they pick one workflow. The one that is most expensive in time, most consistent in how it runs, and least dependent on edge cases and exceptions. They introduce AI there, measure what changes, and let that use case build the appetite for the next one.

For a school, that might be the process behind weekly parent communication. For a small business, it might be the intake process for new customers. The specific answer matters less than having an answer.

What you’re looking for: a single, high-friction, high-repetition workflow that is stable enough to be a reliable first target.

Question 5: Who in your organization will own this?

AI implementation without an internal owner is a project that belongs to everyone and therefore to no one. It gets deprioritized when things get busy, which is exactly when organizations need it most.

The owner doesn’t need to be technical. They need to understand the workflows that matter, have enough credibility with the team to lead a change, and have enough access to leadership to keep the initiative resourced and visible.

In a school, this is often an assistant principal or a department head with operational responsibility. In a small business, it’s frequently the operations manager or, in leaner organizations, the owner themselves. The title is less important than the commitment.

What you’re looking for: a specific name, not a committee.

What Your Answers Are Actually Telling You

If you worked through those five questions and found clear, confident answers, you are closer to meaningful AI adoption than most organizations at your size. The foundation is there. The next step is knowing where to build.

If the questions surfaced more uncertainty than you expected, that’s not a reason to wait. It’s a map. Every unclear answer points directly to the work that makes AI sustainable instead of just impressive for a month.

Either way, the questions have done their job. They’ve moved the conversation from “should we do AI” to “here is exactly what we need to do first.” That shift is where real progress starts.