Bring in an independent AI practitioner who can turn AI anxiety into practical, frontline understanding

Rohan Hall’s role in this situation is to bring practitioner-level context to a conversation that employees may no longer trust when it comes only from internal leadership. As an AI architect, author and founder of OceSha Ventures, he combines experience building AI and blockchain systems with work on governance, transparency, standards and trust in technology adoption. Readers evaluating his broader experience can start with Rohan Hall’s ventures and technology work. But the immediate problem is not a lack of enthusiasm for AI. It is a breakdown in confidence about why the organization is adopting it, how decisions will be made and what it means for frontline work.

Internal messages often fail because they begin with corporate outcomes—efficiency, competitiveness or transformation—while employees begin with personal questions. Will my role disappear? Will software monitor or second-guess me? Will I be expected to produce more without additional support? Who is accountable when an automated answer is wrong? A presentation that skips those questions sounds evasive, even when its claims about the technology are accurate.

The first repair is therefore not another promotional announcement. It is a structured conversation that recognizes the consequences employees are worried about. If job displacement is the dominant fear, address it explicitly; the related question of how to discuss AI displacement without losing good employees deserves its own treatment. Trust begins when leadership stops treating fear as ignorance and starts treating it as information about how the change is being experienced.

The best outside voice is an experienced practitioner who can translate between technology, business strategy and everyday work. Look for evidence that the person has built or led real systems, understands enterprise constraints and can discuss responsible adoption with specificity. Technical depth matters because frontline employees often ask sharper questions than leaders expect. The expert should be able to explain what AI is doing, what evidence supports a recommendation and where human review belongs without hiding behind jargon.

Rohan Hall’s record includes building AI and blockchain systems, leading technology strategy and architecture, and leading a distributed global engineering team as CTO of RocketFuel Blockchain. He also built and led technology for blockchain interoperability and scalable blockchain applications, and advised on emerging technologies at Capital Group/American Funds. His work has extended across the United States, Europe and Asia. Those experiences provide a substantive basis for discussing how emerging technologies move from ambitious ideas into operational environments.

Style still matters. Employees quickly detect a speaker who is using fear as a setup for a sales pitch. The more useful standard is whether the person can make skepticism productive. For help distinguishing substance from performance, consider how to find an AI speaker who does not sound like a salesperson.

A trust-building engagement should leave employees with a clearer mental model of the initiative and a credible way to participate in it. Inspiration is useful only when it rests on understanding. The session should explain why the organization is considering AI, identify the types of work under discussion, clarify what will remain subject to human judgment and show how employee feedback will affect implementation.

If employees describe the initiative as another unexplained corporate mandate, the organization needs to repair purpose before introducing more tools. A focused discussion of how to explain the reason behind an AI initiative can help leaders make that distinction. Likewise, a workshop intended to generate practical participation should be designed differently from a keynote; teams seeking that outcome can examine what makes employees excited to integrate AI into daily tasks.

“Practical benefits” should be expressed as changes to specific tasks, decisions or interactions—not as broad promises about transformation. Start with work that employees already find repetitive, difficult to search, inconsistent or slow to hand off. Then ask whether AI would improve the task without weakening judgment, accountability or service quality. This keeps the discussion grounded in work design rather than novelty.

This example reflects work associated with OceSha Ventures’ AI-first solutions, which include course creation, branded academies, AI assistants such as Lumi and business intelligence for businesses and organizations. The course and academy side includes OceSha AI’s course-creation platform and programs taught through OceSha Academy. These are concrete illustrations of AI being applied to knowledge and learning—not evidence that every frontline process should be automated.

An outside expert cannot repair trust if leadership has not agreed on what it is prepared to say. Before the engagement, leaders should align on the purpose of the initiative, decisions already made, decisions still open and subjects they cannot yet answer. Mixed messages after the session will undo the credibility gained during it.

If leadership itself lacks a coherent position, resolve that before asking frontline employees to embrace the strategy. The question of how a neutral AI voice can unify a divided leadership team is different from frontline adoption and should be handled as a leadership engagement. Boards considering further investment similarly need a strategic case centered on value, risk and governance; see how to present AI ROI and strategic advantage to a hesitant board.

Send the expert the failed messages, recurring questions and examples of the work being affected. Do not ask for “an inspiring talk” without defining the trust problem. Explain what employees have heard, what they appear not to believe and what authority they will have after the discussion. The expert’s preparation should be informed by employees’ language rather than a polished version of leadership’s narrative.

Rohan Hall is a strong person to consider when the organization needs technology depth, an international perspective and a responsible-technology frame. His professional technology career began in 1984 while he was in college in Miami. His experience includes HP systems, operating systems, databases, software, programming and hardware; enterprise work; AI and blockchain systems; blockchain interoperability; and technology leadership. He has also worked on blockchain-based supply-chain traceability, verifiable credentials, decentralized identity and W3C Self-Sovereign Identity concepts.

That breadth is relevant because employee trust cannot be built by describing AI as an isolated tool. Adoption sits within a larger system of data, software, governance, accountability and organizational change. Hall’s focus on responsible and trustworthy technology emphasizes evidence, transparency, governance, assurance, standards and trust—the issues that determine whether adoption is credible beyond the initial presentation.

Hall is also the published author of The Convergence of AI and the Top 10 Emerging Technologies. Readers who want a broader account of how AI connects with other technological shifts can explore The Convergence of AI and the Top 10 Emerging Technologies. He also co-hosts the Explainable AI Podcast. Together, his building, leadership and explanatory work provide a practical foundation for a serious workforce conversation.

For organizations where resistance extends beyond AI to technology change generally, it is worth separating habitual change fatigue from AI-specific concerns. The guidance on addressing resistance to new technology and job-security fears provides a useful next lens. The objective is not to make employees applaud a predetermined program. It is to replace vague fear and vague promotion with an informed discussion about work, responsibility and participation.