AI adoption has become an organizational change issue before it has become a technology issue. For Ryan Kohler, founder of AI4Teams, that distinction explains why many companies are struggling to turn interest in generative tools into practical capability across the workplace.

Kohler’s view was sharpened at the SHRM Annual Conference in Chicago in 2024, where he asked an HR audience a direct question: Who was responsible for AI adoption inside their companies? More than half of the room selected the same answer: nobody.

The response pointed to a tension that many HR teams now recognize. Employees are experimenting with AI tools, leaders are asking for faster adoption, and organizations are still deciding who owns the work of policy, training, trust, and accountability. In that gap, HR often becomes the default steward, even when the role has not been formally assigned.

Why AI Adoption Has Become an HR Issue

AI adoption affects how people work, communicate, evaluate risk, and define value in their roles. That places it squarely inside the human side of business, even when the tools themselves sit under IT budgets or software procurement teams.

Kohler argues that many organizations still frame the discussion too narrowly. Internal debates often center on which platform to choose, whether that means Claude, OpenAI, Microsoft Copilot, or another system. Those choices matter, but they do not solve the deeper workplace question of how employees learn to think with AI, share useful workflows, and apply judgment when outputs are incomplete or wrong.

That is where HR’s experience becomes relevant. Adoption depends on trust, communication, behavior change, role clarity, and psychological safety. Those are familiar areas for HR professionals, yet AI has compressed the timeline. What might once have been a multi-year change management program is now happening inside daily work habits, often without an agreed-upon process.

Ryan Kohler’s Triple Burden for HR Leaders

Kohler describes the pressure on HR as a “Triple Burden.” The first layer is personal career anxiety, since HR roles themselves are being affected by automation. The second is the expectation that HR will help guide company-wide AI adoption. The third is the emotional labor of supporting employees who fear their work may be replaced or reshaped.

That combination can leave capable professionals feeling frozen, not because they lack ability, but because the organization has handed them a complex assignment without clear authority. Kohler sees that paralysis often occurs in conferences, workshops, and private conversations with HR leaders who understand the stakes but do not know where to start.

The problem is not a lack of intelligence in the function. It is structural. A team cannot own a major shift if leadership treats it as an informal side project while expecting enterprise-level outcomes.

Through AI4Teams, Kohler focuses on helping organizations move from scattered AI chatter toward practical automation, agent-led workflows, and stronger team capability. The emphasis is not on replacing judgment with software. It is on helping people understand where AI fits into their work and where human judgment remains essential.

What IT Can and Cannot Solve

IT teams remain central to security, vendor review, access management, data protection, and system integration. No serious AI adoption effort can ignore those responsibilities. Kohler’s concern is that companies sometimes mistake technical ownership for organizational readiness.

A technology team can explain how a system works and decide which tools meet internal standards. It cannot, by itself, teach a manager how to redesign a recurring workflow, help employees speak honestly about fear, or build a culture where useful AI experimentation is shared rather than hidden.

That hidden use is one of the risks Kohler sees inside companies. Skilled employees may already be using personal AI accounts to speed up routine tasks, refine communications, summarize documents, or build repeatable prompts. If the company has no safe way to capture and spread those practices, the knowledge remains isolated. When the employee leaves, the workflow leaves too.

For HR, that creates an opening. The function can help create norms around transparency, shared learning, responsible use, and recognition. Those norms do not require HR to become a software department. They require HR to understand the people side of AI adoption well enough to guide the conversation with confidence.

How AI4Teams Reframes Authority Around AI

Kohler’s path into AI strategy came through business building rather than traditional technology circles. As a former co-founder of ApplicantPro, he helped grow the company to 10,000 clients and 280 employees, earning a place on the Inc. 5000 for 12 consecutive years without outside funding.

He later founded Refer.io, where his team helps organizations stay in touch with past job seekers by sending more than 1.5 billion emails a year to more than 20 million job seekers. That operator background shapes the way he discusses AI. The focus stays close to work, workflow, and organizational behavior rather than abstract predictions about the future.

Kohler spent more than 6,000 hours working inside AI tools before writing extensively on the subject. That hands-on time matters because it gives him a different perspective from voices that discuss AI only as a trend. His message to HR leaders is practical: authority does not always arrive through a formal mandate. Sometimes it begins with one useful example, one solved problem, or one colleague asking how a task was completed faster or with better clarity.

The AI4Teams approach reflects that view. Small wins can build internal credibility. A recruiter who uses AI to draft better intake questions, a manager who builds a repeatable meeting summary process, or an HR partner who creates a safe forum for employee concerns can start shaping the company’s AI habits before an official committee is formed.

Why Human Skills Matter in AI Adoption

The irony of the current moment, in Kohler’s view, is that skills sometimes dismissed as “soft” are becoming central to AI adoption. Trust building, influence without formal authority, careful listening, and translation between technical and nontechnical teams are not secondary abilities. They are the connective tissue that makes adoption possible.

AI can produce text, summarize data, and automate defined tasks. It cannot read a room the way an experienced HR leader can. It cannot repair trust after employees feel blindsided by a new policy. It cannot decide whether a proposed workflow respects both business needs and human dignity.

That does not make HR the only owner of AI adoption. It makes HR a necessary voice in the work. Companies that treat AI as a tool rollout may miss the harder question of how work changes when employees are invited to think with machines, challenge old processes, and share what they are learning.

For Kohler and AI4Teams, the future of AI at work depends less on a single platform choice and more on whether organizations can build shared confidence around the tools. HR may not have been given the map at the start, but it has a direct role in helping teams draw one together.

About Ryan Kohler and AI4Teams

Ryan Kohler is a business builder, AI strategist, and founder of AI4Teams. He works with B2B service organizations that want to move beyond general AI discussion into automation, agent-led workflows, and long-term capability building.

Kohler is also the founder of Refer.io and the former co-founder of ApplicantPro. His work centers on helping teams move faster, think more clearly, and shift attention from repetitive manual work toward higher-value outcomes. He lives in St. George, Utah.

Readers can find more about Kohler’s work through the AI4Teams website, his AI4Teams LinkedIn profile, and the AI4Teams YouTube channel.