Why AI Governance and Clean Data Matter More Than the Demo cover image

Why AI Governance and Clean Data Matter More Than the Demo

Why AI Governance and Clean Data Matter More Than the Demo

Listen for free

View show details

This Season's Biggest Deal | 0.99 €/mo for 3 months + 15 € Audible bonus

6.99 €/month thereafter - terms apply. Cancel monthly.
Summary
As HR technology moves from AI-powered recommendations to agents that can execute multi-step workflows, the risks around employee data, privacy and accountability are becoming harder to ignore. A November 2026 report from employment law firm Littler notes that agentic AI can act across workplace systems, while governance frameworks are struggling to keep pace: only 13% of organizations surveyed believed they had the right governance in place. The report underscores why access controls, human oversight and clear accountability need to be designed into workplace AI. At HR Tech in Las Vegas, RPI Tech Connect host Chris Arey speaks with Melissa Olson and Jackie Dudas about what they heard on the conference floor. Their conversation moves beyond the latest AI demonstrations to the questions HR and technology teams need to ask: what data is feeding the system, what can an agent access or disclose, how should its behavior be governed, and where does human judgment still matter? In this episode, Melissa Olson and Jackie Dudas share their takeaways from HR Tech 2026, including why clean data, shared definitions, security controls and careful testing should come before broad AI deployment. They also discuss the importance of looking beyond vendor demonstrations and keeping the employee experience human. Show notes What should HR teams check before adopting AI agents? HR teams should understand the data, permissions and governance behind an AI tool before allowing it to interact with employee information or carry out workplace processes. The discussion highlights how conversational AI can introduce risks that are easy to miss in a polished demonstration, including employees entering sensitive or unrelated information, agents exposing details they should not disclose, and inconsistent data producing unreliable answers. Melissa points to the work that happens behind the scenes: cleansing and normalizing data, agreeing on organizational terminology, and applying consistent metadata tags. These foundations help an AI system retrieve the right information and operate within intended guardrails. Jackie raises a related concern about how much an employee might share in a conversational exchange and what the system could learn or reveal across the organization. The conversation also makes a case for asking vendors what actually powers a branded AI assistant, rather than accepting its name or demonstration at face value. Organizations need to understand the underlying software, security model and data protections. The practical approach is to define the business outcome first, then prototype, test and verify the technology before expanding its authority. Key takeaways - AI is becoming a standard part of the HR technology conversation. Melissa describes the conference message as an evolution from AI-first and AI-native software toward agentic capabilities. Jackie observes that AI use has become so widespread that, in conference sessions, nearly everyone raises a hand when asked whether they use it. The challenge for HR teams is shifting from whether AI is relevant to understanding where it belongs and what it should be allowed to do. - Conversational AI creates new questions about employee information. An employee might use an AI assistant to begin a leave process, but the same open-ended conversation could invite unrelated or sensitive disclosures. Jackie asks whether information shared by one employee could influence responses elsewhere in the organization, or whether an agent might reveal confidential details such as a pending promotion. Those risks make data access, disclosure rules and governance essential design questions. - Data preparation is a major part of AI implementation. Melissa stresses that organizations need to cleanse, normalize and rationalize their data before expecting AI to work reliably. Teams across the business also need to agree on terminology and metadata tagging so information can be found and interpreted consistently. This is not simply an IT task: shared definitions across departments help improve search, analytics and the quality of AI outputs. - Vendor demonstrations should be followed by questions about what is under the hood. A polished AI assistant may have a memorable name, but buyers still need to understand the actual software behind it, how it accesses data and what protections are in place. The conversation points to questions about security architecture, personal information, governance layers and safeguards against unauthorized access. HR and IT teams should evaluate the underlying system, not just the experience shown on stage. - AI adoption should be deliberate, and it should not erase the human experience. Melissa advocates moving slowly, prototyping and testing before giving AI broad access or responsibility. Jackie reinforces the need to identify the outcome an organization wants before choosing a tool. Both also recognize that technology should improve employees’ ...
adbl_web_anon_alc_button_suppression_t1
No reviews yet