Skip to main content

Chayil AI Adoption Series | Insight 01 of 05

Leadership and Readiness

Your Team Is Already Using AI. Are You Leading It Yet?

Your organization may have begun adopting artificial intelligence before leadership ever decided to adopt artificial intelligence.

Fredlena M. CosbyFounder and Principal Strategist, Chayil Advisory Resource8 min read

Artificial intelligence probably did not enter your organization through a strategic plan. There was likely no board resolution, no leadership retreat devoted to adoption, and no carefully designed implementation roadmap. It may have entered on an ordinary Tuesday afternoon when someone had an email they did not know how to answer, meeting notes that needed to become something useful, a grant deadline getting uncomfortably close, or a blank screen where tomorrow's communication was supposed to be.

So someone opened an AI tool and typed.

And just like that, your organization's AI journey may have begun. Leadership just may not have been in the room when it happened.

That possibility is no longer theoretical. Gallup reported in July 2026 that 52 percent of U.S. employees were using AI in their roles, while 47 percent said their organizations had integrated AI tools. Perhaps even more revealing, one in five employees did not know whether their organization had integrated AI at all.

Organizational AI Adoption

52%

U.S. employees using AI in their role

47%

say organization has integrated AI

20%

do not know whether organization has integrated AI

Source: Gallup, Organizational AI Adoption Jumps Six Points, July 2026

That last number interests me as much as the adoption numbers do.

Because this is not only a technology issue.

It is a leadership clarity issue.

You May Already Have an AI Strategy. You Just Did Not Design It.

If I were sitting with your leadership team, I would begin with a fairly simple question:

Do you know how your people are already using AI?

Maybe someone in communications uses it every day. Maybe an administrator has quietly figured out how to reduce repetitive work. Maybe a volunteer is experimenting with a tool leadership has never evaluated. Someone preparing a grant may use AI for research or drafting while another person refuses to touch it because no one has explained what it actually does.

None of that automatically means your organization has an AI problem.

It means leadership has something to understand.

And there is another layer leaders can miss. Some AI did not arrive because an employee deliberately opened a new tool. It arrived inside software the organization already uses. Email systems, meeting platforms, productivity software, donor systems, customer relationship tools, and other applications are increasingly adding AI capabilities.

So a leadership team can answer, "Which AI tools are we using?" and still be incomplete because the question they actually answered was, "Which AI tools do we knowingly open?"

That distinction matters.

Individual AI use is not the same as organizational AI adoption.

Access is not adoption. Experimentation is not strategy.

The Chayil Leadership AI Check

Chayil Framework | AI Adoption & Enablement
Leadership QuestionWhat We Are Trying to Understand
Where is AI already being used?Current behavior
What are people using it to accomplish?Actual use cases
What organizational information is entering AI systems?Information exposure
Where must human judgment remain?Responsibility and authority
What have we actually taught our people?Organizational preparedness

Not what we assume they know.

Not what we hope they understand.

What have we actually taught them?

That conversation gives leadership something more valuable than a list of popular tools. It gives leadership the truth about where the organization actually is.

What Went Into the System?

Most AI conversations naturally focus on the output.

Was the answer useful? Did it save time? Did the writing improve?

Those questions matter. But leadership also needs to ask what went in.

Churches, ministries, and nonprofits may hold donor information, personnel information, financial records, board matters, pastoral care details, information concerning children and families, client or beneficiary information, internal strategy, and intellectual property.

A large global study from the University of Melbourne and KPMG found that almost half of employees reported using AI in ways that violated company policies, including putting sensitive organizational information into free public AI tools. The study surveyed more than 48,000 people across 47 countries, so I would not treat it as a church specific statistic. I would treat it as evidence that employee AI behavior can move faster than organizational expectations.

This is where the conversation changes.

What did the convenience require from us?

The answer will vary by system, account type, contractual terms, information involved, and organizational environment. That is exactly why leadership should make these decisions intentionally rather than leaving them entirely to individual judgment.

Can AI Do This? Is Not the Same as Should AI Do This Here?

Artificial intelligence can do an extraordinary number of things.

But capability does not determine appropriateness.

I want leaders to become comfortable asking:

Should AI do this here?

The word here changes the conversation.

In this organization.

With this information.

For this purpose.

Serving these people.

Under these responsibilities.

A church may decide that AI can assist with routine administrative preparation while drawing a very different boundary around pastoral care. A nonprofit may use AI for communications or research while requiring stronger safeguards around beneficiary information. A leadership team may use AI to organize ideas while maintaining that humans carry the responsibility for the decision.

There is no prize for using AI everywhere simply because we can.

The goal is not to help an organization use AI faster. The goal is to help an organization use AI wisely.

Leadership Does Not Have to Master Every Tool

Some leaders already feel behind because they cannot keep up with every new model, feature, headline, or platform.

I would take that pressure off the table.

Leadership does not have to master every tool. It does need enough understanding to ask good questions.

Which tools are being used? What information are they receiving? What requires verification? Where does human judgment belong? Who remains accountable for the final work?

And perhaps most importantly:

Does this solve a problem we actually have?

For mission driven organizations, efficiency matters.

But efficiency is a servant of the mission, not the definition of it.

Try This Conversation

At your next leadership meeting, ask everyone to think about the last thirty days.

Which AI tools have you used for organizational work?

What did you use them to accomplish?

What kind of organizational information did you enter?

Then talk about the answers.

The point is not to catch somebody doing something wrong. The point is to understand the behavior that already exists.

You may discover your organization is further along than you thought. You may discover it is less prepared than you thought. You may discover that five people have five different ideas about what responsible AI use means.

Every one of those answers gives leadership somewhere real to begin.

And this is the question I would leave in the room:

If I asked five people in your organization today what your expectations are for using AI at work, would I receive the same answer five times?

If the answer is no, do not panic.

Pay attention.

You have just discovered where the conversation needs to begin.

Bring the Conversation Into the Room

Chayil's AI Adoption & Enablement work can begin with leadership education, a board conversation, an organizational readiness discussion, or a focused conversation around the AI use already happening inside the work.

We begin where your organization actually is.

Before We Leave This Conversation

Once leadership sees what is happening, someone will eventually say:

"Then we need to train our people."

I agree.

But train them to do what?

That question is harder than it sounds, and the answer changes what AI training has to accomplish.

That is where I want to pick up our conversation next.

Share this insightShare on LinkedInYour Team Is Already Using AI. Are You Leading It Yet? — Your organization may have begun adopting artificial intelligence before leadership ever decided to adopt artificial intelligence.

Next in the Chayil AI Adoption Series | Insight 02 of 05

Teaching People to Prompt Is Not an AI Adoption Strategy

What should your people actually know before they use AI on behalf of your organization?

Advisory

Bring the Conversation Into the Room.

Chayil helps leadership teams understand where AI belongs, how people should use it, how workflows may need to change, and what governance is required as adoption grows.

Leadership BriefingsBoard EducationTeam TrainingWorkflow EnablementAI GovernanceAI PolicyAgentic ReadinessStrategic Advisory
In Development

Companion Resource

The Chayil AI Readiness Conversation Guide

12 Questions Every Leadership Team Should Ask Before AI Becomes Part of the Work

A concise leadership resource designed to help organizations identify where AI is already touching the work and where leadership may need greater clarity around people, workflows, governance, and agents.

Be Notified When Available

Sources and Further Reading

Gallup

Organizational AI Adoption Jumps Six Points (July 20, 2026)

Gallup reports that 52 percent of U.S. employees use AI in their role, 47 percent say their organizations have integrated AI tools, and one in five remain unsure whether organizational integration has occurred.

Direct source ↗

University of Melbourne and KPMG

Trust, Attitudes and Use of Artificial Intelligence: A Global Study 2025

The study surveyed more than 48,000 people across 47 countries and examined workplace AI behavior, training, governance, and trust.

Direct source ↗