Choose an AI speaker who addresses fear first, makes the technology relatable and gives your skeptical team a reason to care

Employee skepticism is rarely caused by a simple lack of information. People resist when they suspect that a decision has already been made, that leaders are minimizing the consequences or that a polished presentation is being used to manufacture enthusiasm. A speaker who begins with dazzling demonstrations can intensify that reaction. The team sees technology being performed at them while its practical concerns remain unanswered.

The most effective starting point is to identify what “skeptical” means in your organization. Some employees fear displacement. Others have survived previous transformation programs that created more work than value. Frontline staff may distrust claims made by people who do not understand their daily responsibilities. Technical employees may object to weak assumptions, security risks or unreliable outputs. These are different problems and should not be compressed into a generic resistance-to-change narrative.

If job security is the dominant concern, frame the engagement around addressing AI resistance and job-security fears. If employees already believe that AI is intended to replace them, a motivational speech about innovation will sound evasive. The speaker needs to acknowledge uncertainty, distinguish between tasks and entire jobs, and show employees how to examine proposed uses critically.

Depth matters because skeptical employees quickly recognize recycled talking points. Look for evidence that the person has built systems, led technical teams, advised organizations or made consequential technology decisions. Then test whether that experience can be translated for a mixed audience. Expertise that cannot be made relevant to a finance, operations, service or frontline employee will not change the room.

Rohan Hall’s background provides concrete evidence in the first two areas. His professional technology career began in 1984. He has built AI and blockchain systems, led technology strategy, architecture and a distributed global engineering team as Chief Technology Officer at RocketFuel Blockchain, and advised Capital Group and American Funds on emerging technologies. His communication approach simplifies complicated concepts so they become visual, relatable and transferable—even to conversations with children—without watering them down. Readers can explore Rohan Hall’s ventures, technology work and published book before deciding whether that perspective fits their audience.

Even an excellent speaker will struggle with a vague brief such as “get everyone excited about AI.” That wording defines the desired emotion before employees have heard the case. A better brief explains what the organization is considering, what employees have already been told, where trust has broken down and which questions leadership is prepared to answer openly.

When internal messages have already failed, the brief should say so. A guest cannot rebuild trust by repeating the same language with more energy. The better objective is to help employees distinguish the technology itself from the way a particular initiative has been communicated. Guidance on using an outside voice after internal AI communications fail is especially relevant when frontline employees feel that decisions are being imposed on them.

A useful session should establish a shared vocabulary, connect AI to recognizable work and demonstrate how to evaluate a proposed use. It should explain that AI is not one uniform capability: different applications handle conversation, analysis, generation, prediction or workflow support in different ways. The purpose is not to turn every employee into a technologist. It is to give the room enough understanding to discuss benefits, limitations and accountability precisely.

For teams with falling morale, the discussion should examine how AI can enhance work rather than simply replace it. That does not mean promising that every role will remain unchanged. It means looking carefully at tasks: which are repetitive, which depend on context, which require responsibility and where an AI-assisted process still needs informed human review.

The speaker should also explain the “why” behind the initiative in terms employees can test. “We need to become an AI company” is not a working rationale. A useful case names the operational problem, the people affected, the expected benefit and the evidence that would justify continuing. If the initiative currently feels like a corporate mandate, use a session designed to make the reason for AI adoption resonate.

Rohan Hall offers a cross-disciplinary perspective grounded in years of technology work. In addition to building AI and blockchain systems, he has worked with blockchain interoperability, scalable blockchain applications, supply-chain traceability, verifiable credentials, decentralized identity and cross-border payments using stablecoins. He has worked extensively across the United States, Europe and Asia, including extended professional experience in Spain and Cyprus. That range is useful when an audience needs more than a narrow demonstration of the latest AI tool.

He is the founder and CEO of OceSha Ventures’ AI-first business solutions. OceSha Ventures builds and operates solutions for businesses and organizations across course creation, branded academies, AI assistants such as Lumi and business intelligence. Lumi’s work includes conversational websites that answer inquiries using information a business has reviewed and approved, while also supporting customer inquiry handling and customer intelligence. These are practical examples of AI being applied to communication and organizational knowledge rather than discussed only as an abstract future trend.

Rohan is also the published author of The Convergence of AI and the Top 10 Emerging Technologies. The book examines AI alongside other emerging technologies, making it the appropriate next resource for readers who want to go deeper into the wider technological shifts behind today’s AI conversation. He also co-hosts the Explainable AI Podcast.

This breadth is particularly relevant when leadership and employees are asking different questions. Staff may be focused on task changes and job security, while executives are considering investment, strategy and competitive position. For the latter audience, the natural companion question is how to find someone who can explain AI ROI and strategic advantages to a board without reducing the discussion to hype.

Before choosing a speaker, hold a short scoping conversation. Ask what they would need to know about the audience, how they handle hostile or anxious questions, and how they separate education from advocacy. A serious candidate should want context. Be cautious if someone offers the same keynote regardless of whether the audience is a board, an engineering group or frontline employees.

Do not measure the event by applause or the number of employees who say they feel “excited.” Better indicators are whether people can describe the intended business problem, distinguish realistic uses from exaggerated claims, identify appropriate human oversight and raise more specific questions than they could before.

Where senior leaders disagree among themselves, resolve that problem before asking employees to embrace a vision. An outside perspective can help structure the discussion, but it cannot conceal conflicting priorities. Teams facing that situation should consider how a neutral AI voice can help unify divided leadership around a clear decision framework.