Last spring, a faith-tech leader pulled me aside after a conference session and confessed something that stuck with me: “Half my team is using AI every single day. I found out from a Slack message two months ago. We still don’t have a policy.” She laughed, but her eyes didn’t.
Here’s a number that should stop you cold: 73% of workers in tech-driven industries have already adopted AI tools for personal productivity, according to a 2025 Gartner report. But only 22% of organizations in the same report have a formal AI strategy in place.
That gap isn’t just a statistic. It’s a momentum killer. Individual team members are racing ahead with AI, while leadership lags behind, leaving faith-tech orgs fractured and unable to harness the very tools their people are already using.
I’ve seen this firsthand in my work with global discipleship platforms and curriculum tools. The disconnect between ground-level adoption and organizational vision doesn’t just stall progress—it risks alienating your most innovative team members. If leadership doesn’t close this gap fast, we’re not just missing opportunities; we’re actively pushing talent and ideas out the door.
This is the foundational misread that causes product teams and ministry leaders to fumble AI integration. They assume adoption happens organically because individuals are already experimenting with tools like ChatGPT or Midjourney. But without a deliberate strategy, these efforts fragment, creating silos instead of synergy.
To frame this problem, I’m turning to John Kotter’s 8-step change management model. Kotter, a Harvard professor who’s shaped how organizations navigate transformation, argues that lasting change starts with creating urgency and ends with anchoring new practices into culture. His framework isn’t about tech—it’s about people and systems. And right now, faith-tech needs both to align around AI before the gap becomes a chasm.
The Data Gap Between Workers and Leaders
I’ve sat in planning meetings for digital ministry tools where team members are quietly using AI to draft content or analyze user data. They’re not waiting for permission. They’re solving problems in real time.
But leadership often doesn’t even know this is happening. In one project I worked on for a children’s ministry curriculum platform, volunteers were using AI to adapt lessons for their specific contexts. Meanwhile, the org’s executives were still debating whether AI was “safe” for their mission. The people closest to the problem had already moved on. The people with the authority to support them hadn’t.
This isn’t just a communication failure. It’s a structural one. Workers are moving at the speed of necessity, while leaders are stuck in analysis paralysis. The result? Duplicated efforts, wasted resources, and a creeping frustration among team members who feel unseen.
Kotter’s first step—creating urgency—cuts through this. If leaders don’t see the 73% adoption rate as a call to action, they’ll keep treating AI as a future problem instead of a present reality. Urgency isn’t about fear; it’s about recognizing that your people are already ahead of you and deciding to lead from the front rather than manage from behind.
Why Faith-Tech Struggles with Strategic Alignment
Faith-tech organizations face a unique hurdle in AI adoption. We’re not just building products; we’re stewarding missions. That sacred responsibility can make leaders hesitant, fearing that AI might dilute the human or spiritual elements of ministry.
I’ve felt this tension myself. When working on a global Bible engagement app, I wrestled with how AI-driven personalization might feel mechanical to users who crave authentic connection. It’s a valid concern—but it often morphs into a permanent barrier that stalls progress long after the concern has been addressed.
Here’s where Kotter’s second and third steps—building a guiding coalition and developing a vision—come in. Without a coalition of trusted voices across the org, AI initiatives get stuck in endless debates. Without a clear vision, every decision feels like a threat to the mission rather than an expression of it.
I’ve seen faith-tech teams break through this by tying AI directly to their core purpose. One team used AI to analyze user engagement patterns, revealing which devotionals led to deeper spiritual practices. That’s not tech for tech’s sake—it’s tech for mission’s sake. When the vision is clear, the resistance softens.
Building Urgency for AI Implementation
Creating urgency isn’t about hype. It’s about showing what’s at stake. In faith-tech, I’ve watched organizations lose ground to secular competitors because they couldn’t move fast enough on digital tools—AI included.
Take a sermon resource platform I contributed to. Volunteers needed quick, adaptable content for their 7-minute prep windows. AI could have streamlined that process, but leadership hesitated, citing budget and “fit” concerns. Meanwhile, users drifted to faster, less mission-aligned alternatives. The lag didn’t just slow them down—it redirected their people somewhere else entirely.
Kotter’s model pushes for short-term wins—his sixth step. Pilot an AI tool for a single pain point, like automating email responses for volunteer inquiries. Show the time saved and the feedback gained. These wins build momentum and prove the case to skeptics more convincingly than any strategy document ever will.
Urgency also means addressing the human cost of lag. When team members see their AI experiments ignored, they disengage. I’ve been in rooms where the most creative minds quietly checked out because their ideas never made it past the brainstorming phase. Leadership lag doesn’t just lose ground on AI—it loses people.
Anchoring change—Kotter’s final step—means making AI a cultural norm, not a one-off project. It’s not enough to launch a tool; you have to celebrate its impact, train your people, and bake it into how you operate. Only then does the gap between individual adoption and organizational strategy finally close—and stay closed.
Your Turn: Apply This Today
- Survey your team this week to find out who’s already using AI tools—send a quick Google Form asking for specific examples and outcomes.
- Schedule a 30-minute meeting with key stakeholders by Friday to share the 73% adoption stat and discuss what inaction costs your org in momentum.
- Identify one pain point AI could solve—like content adaptation or user support—and commit to a 4-week pilot starting next month.
- Form a small coalition of 3–5 team members from different levels to champion this pilot and report weekly wins to leadership.
- Draft a one-page vision statement tying AI use to your mission—focus on outcomes like reaching more people or freeing up volunteer time—and share it at your next all-hands.
- Celebrate early results publicly—email the team or highlight a success in a meeting—to build buy-in and show this isn’t a passing fad.
The 51-point gap between how many workers are using AI and how many organizations have a strategy for it is not a technology problem—it’s a leadership problem. And leadership problems, unlike server outages, don’t fix themselves. The faith-tech teams that close this gap won’t just move faster; they’ll move together, with their most creative people finally feeling seen, supported, and unleashed to build what the mission actually needs.
If you’re wrestling with AI adoption gaps, check out my posts on AI Code Generation Won’t Fix Your Ministry’s Tech Debt—Here’s What Will and Internal AI Tools Need a Product Mindset to Stick in Faith-Tech Teams for more on navigating these challenges with a mission-first approach.
I consult with faith-tech product leaders and ministry innovators on closing AI adoption gaps, aligning tech with mission, and building urgency for change. Let’s talk.