Categories
AI Today in 5

AI Today in 5: July 30, 2026, The Compliance Decision Fatigue Edition

Welcome to AI Today in 5, the newest addition to the Compliance Podcast Network. Each day, Tom Fox will bring you 5 stories about AI to start your day. Sit back, enjoy a cup of morning coffee, and listen in to AI Today in 5. All from the Compliance Podcast Network. Each day, we consider five stories from the business world, compliance, ethics, risk management, leadership, or general interest about AI.

Top AI stories include:

  1. Compliance decision fatigue in the age of AI. (JD Supra)
  2. BaFin to monitor AI use at banks and insurers. (Reuters)
  3. Can regs become machine-readable? (FinTech Global)
  4. Investment firms say AI is their top compliance concern. (Investment News)
  5. FDA rulebook for AI in drug trials. (The Clinical Trial Vanguard)

For more information on the use of AI in compliance programs, Tom Fox’s new book, Upping Your Game, is available. You can purchase a copy of the book on ⁠Amazon.com⁠.

To learn about the intersection of Sherlock Holmes and the modern compliance professional, check out Tom’s latest book, The Game is Afoot-What Sherlock Holmes Teaches About Risk, Ethics and Investigations on ⁠Amazon.com⁠.

Categories
Daily Compliance News

Daily Compliance News: July 30, 2026, The Milli Vanilli Edition

Welcome to the Daily Compliance News. Each day, Tom Fox, the Voice of Compliance, brings you compliance-related stories to start your day. Sit back, enjoy a cup of morning coffee, and listen in to the Daily Compliance News. All from the Compliance Podcast Network. Each day, we consider four stories from the business world, compliance, ethics, risk management, leadership, or general interest for the compliance professional.

Top AI stories include:

  • Defense lawyers claim DOJ FCPA case is a ‘Milli Vanilli’ offering.  (Law360) sub req’d
  • eBay and execs agree to pay $55.7 MM in settlement for harassment. (Law360) sub req’d
  • Teva can’t whine about agreed-to admissions. (Law360) sub req’d
  • 1st Circuit skeptical that hiring SW is a lie detector. (Law360) sub req’d

To learn about the intersection of Sherlock Holmes and the modern compliance professional, check out Tom’s latest book, The Game is Afoot-What Sherlock Holmes Teaches About Risk, Ethics and Investigations on Amazon.com.

Categories
Blog

The Final Frontier of Compliance Training: Five Lessons from Star Trek’s “Is There in Truth No Beauty?”

Corporate compliance is not just about rules, regulations, and policy manuals. At its core, compliance is about people—their perceptions, blind spots, willingness to communicate, and, above all, their ability to learn from each other in the face of risk and ambiguity. No franchise has dramatized the struggles of understanding, ethics, and communication better than Star Trek: The Original Series (TOS). And no episode is more apt for compliance professionals seeking to elevate their training and communications program than the third-season gem, “Is There in Truth No Beauty?”

Set aboard the USS Enterprise, the episode revolves around the arrival of Dr. Miranda Jones and the enigmatic Medusan ambassador, Kollos. The Medusans are a race of beings whose appearance is so alien that to gaze upon them causes madness. It’s a parable about the dangers and necessity of confronting the unknown, understanding difference, and building bridges across divides.

As compliance professionals, we can mine “Is There in Truth No Beauty? ” for powerful lessons on how to build a culture of effective training”forcommunications that prepares our teams for the uncharted territory of tomorrow’s risks. Today, we set our phasers to “inspire” and explore five key compliance training and communications lessons from this classic Trek tale.

Lesson 1: Embrace the Limits of Human (and Organizational) Perception

Illustrated by: The crew’s first briefing about the Medusan ambassador is laden with warnings: “No one may look upon a Medusan with the naked eye.” To the Medusan, human forms are equally incomprehensible, but they have developed technology, a protective visor, that allows safe interaction. Dr. Miranda Jones, specially trained and equipped, serves as a living bridge between the two species.

Compliance Lesson. Every organization has its own “Medusans” risks, regulations, and even people whose perspectives are so different they can seem incomprehensible. Too often, compliance training assumes everyone shares the same baseline understanding and comfort level. That is a dangerous assumption.

Your training must recognize the limits of perception, both cognitive and cultural. Not everyone will see risk the same way; not everyone will feel empowered to ask questions or speak up. Just as Dr. Jones brings specialized knowledge and equipment to the table, your compliance communications should equip employees with tools to recognize their blind spots and to bridge those gaps. This can mean scenario-based learning, peer-led discussions, or visual tools that help explain complex risks from multiple perspectives.

What should you do now? Acknowledge and proactively address the limits of human perception. Empower your team with adaptive tools and diverse viewpoints to “see” risk.

Lesson 2: Communicate Expectations—Don’t Assume Understanding

Illustrated by: Early in the episode, Captain Kirk assembles his crew for a detailed briefing. He explicitly warns, “You must not look upon the Medusan ambassador.” Spock and Dr. Jones reinforce the message, and the procedures for safe interaction are laid out.

Compliance Lesson. How many compliance failures begin with, “Well, I thought I understood what was required…”? In Star Trek, lives depend on explicit, repeated communication of expectations. In your organization, regulatory and reputational survival depends on it as well.

Effective compliance training requires more than a one-time email or a paragraph in the handbook. Clear, repeated, scenario-based communication is essential. Explain the “why” as well as the “what.” Don’t just say “do not do X,” but explain the risk, the rationale, and the real-world consequences. Use multiple formats, including live, digital, visual, and narrative, to reinforce the message.

What should you do now? Never assume understanding. Communicate expectations explicitly and often, and use stories, scenarios, and repetition to anchor key messages.

Lesson 3: Build Trust and Psychological Safety Before the Crisis

Illustrated by: The relationship between Dr. Jones and the crew is initially fraught. She is a telepath, guarded and secretive. Her sense of isolation is palpable. Yet as the episode progresses, Kirk and Spock earn her trust by inviting her into their confidence and acknowledging her unique expertise. This trust proves critical when disaster strikes.

Compliance Lesson. Effective communication is built on trust and psychological safety. If employees feel isolated, mistrusted, or afraid to speak up, no amount of “mandatory training” will make your compliance program effective. The Medusan can only safely interact through a trusted intermediary—just as employees will only engage with compliance if they feel respected and included.

Foster a compliance culture where people feel safe to voice concerns, ask questions, and share mistakes without fear of retaliation. Encourage managers to model vulnerability and openness. Use anonymous Q&A, “ask me anything” sessions, and real stories to build an environment of trust.

What should you do now? Trust is the engine of communication. Build psychological safety into your compliance training so that employees feel empowered to participate, especially when the stakes are high.

Lesson 4: Prepare for the Unexpected—And Practice the Protocols

Illustrated by: When Kollos’s container is accidentally opened, crew member Larry Marvick is exposed to the Medusan and descends into madness, nearly destroying the Enterprise. The emergency procedures are put to the test, and Spock’s preparation (and his use of the protective visor) is the difference between disaster and survival.

Compliance Lesson. Crises never unfold according to plan, but they reveal the effectiveness of your training and protocols. Star Trek demonstrates that it’s not enough to have a policy in the binder; you must train, rehearse, and test those protocols until they are second nature.

Use tabletop exercises, drills, and “what if” scenarios in your compliance training. Walk teams through incident response steps—debrief after near-misses or actual compliance failures. Emphasize not just the letter of the protocol, but the spirit, why each step matters, and how it protects the organization and its people.

What should you do now? Prepare, practice, and stress-test your compliance protocols. When the unthinkable happens, your team must be ready to act, not just recite policy, but live it.

Lesson 5: Embrace Diversity—and the Value of the Outsider’s View

Illustrated by: The Medusan, Kollos, is physically incomprehensible to humans, yet he is also a being of great intelligence and empathy. Spock, uniquely Vulcan and human, can serve as a bridge—merging with Kollos to save the ship. In the process, both gain insight from the other’s perspective.

Compliance Lesson:

Homogeneity is a hidden compliance risk. Diverse teams bring broader perspectives, challenge assumptions, and spot blind spots that a monoculture would miss. In Star Trek, survival depends on learning from the outsider; in compliance, innovation, and vigilance depend on the same principle.

Include voices from across your organization and beyond in your compliance training and communications. Seek out the vigilance, theys” who can question the status quo. Value the contributions of people from different backgrounds, departments, and experiences. Remember: your “Medusan” might hold the key to your next compliance breakthrough.

What should you do now? Diversity is your compliance superpower. Embrace the outsider’s perspective and make inclusion a pillar of your training and communications.

Final ComplianceLog Reflections

Is There in Truth No Beauty? “is a meditation on the limits of perception, the power of communication, and the necessity of embracing difference. For compliance professionals, it offers a road map for building training and communications programs that are clear, inclusive, practical, and resilient.

As you chart the course for your compliance initiatives, ask yourself:

  • Are we equipping our people to see risk from every angle?
  • Do we communicate expectations repeatedly and meaningfully?
  • Is trust the foundation of our compliance culture?
  • Are we truly ready for the unexpected?
  • Are we harnessing the power of diverse perspectives?

The universe of compliance is ever-expanding. Let’s train and communicate so our teams are ready to go where no one has gone before boldly.

Resources:

⁠⁠Excruciatingly Detailed Plot Summary by Eric W. Weisstein⁠⁠

⁠⁠MissionLogPodcast.com⁠⁠

⁠⁠Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance: Episode 60 – Unmasking Compliance Blind Spots: Lessons from ‘Is There in Truth No Beauty?’

No TOS episode is more apt for compliance professionals seeking to elevate their training and communications program than the third season gem, “Is There in Truth No Beauty?”

As compliance professionals, we can mine “Is There in Truth No Beauty?” for powerful lessons on building a culture of effective training and communications that prepares our teams for the uncharted territory of tomorrow’s risks. Today, we set our phasers to “inspire” and explore five key compliance training and communications lessons from this classic Trek tale.

Lesson 1: Embrace the Limits of Human Perception

Illustrated by: The crew’s first briefing about the Medusan ambassador is laden with warnings: “No one may look upon a Medusan with the naked eye.”

Compliance Lesson. Every organization has its own “Medusans” risks, regulations, and even people whose perspectives are so different they can seem incomprehensible. Too often, compliance training assumes everyone shares the same baseline understanding and comfort level. That is a dangerous assumption.

Lesson 2: Communicate Expectations—Don’t Assume Understanding

Illustrated by: Early in the episode, Captain Kirk assembles his crew for a detailed briefing. Spock and Dr. Jones reinforce the message, and the procedures for safe interaction are laid out.

Compliance Lesson. How many compliance failures begin with, “Well, I thought I understood what was required…”? In Star Trek, lives depend on explicit, repeated communication of expectations. In your organization, regulatory and reputational survival depends on it as well.

Lesson 3: Build Trust and Psychological Safety Before the Crisis

Illustrated by: The relationship between Dr. Jones and the crew is initially fraught. She is a telepath, guarded and secretive. Her sense of isolation is palpable. Yet as the episode progresses, Kirk and Spock earn her trust by inviting her into their confidence and acknowledging her unique expertise. This trust proves critical when disaster strikes.

Compliance Lesson. Effective communication is built on trust and psychological safety. If employees feel isolated, mistrusted, or afraid to speak up, no amount of “mandatory training” will make your compliance program effective.

Lesson 4: Prepare for the Unexpected—And Practice the Protocols

Illustrated by: When Kollos’s container is accidentally opened, crew member Larry Marvick is exposed to the Medusan and descends into madness, nearly destroying the Enterprise.

Compliance Lesson. Crises never unfold according to plan, but they reveal the effectiveness of your training and protocols. Star Trek demonstrates that it’s not enough to have a policy in the binder; you must train, rehearse, and test those protocols until they are second nature.

Lesson 5: Embrace Diversity—and the Value of the Outsider’s View

Illustrated by: The Medusan, Kollos, is physically incomprehensible to humans, yet he is also a being of great intelligence and empathy.

Compliance Lesson:

Homogeneity is a hidden compliance risk. Diverse teams bring broader perspectives, challenge assumptions, and spot blind spots that a monoculture would miss. In Star Trek, survival depends on learning from the outsider; in compliance, innovation, and vigilance depend on the same principle.

Final ComplianceLog Reflections

Is There in Truth No Beauty?” is a meditation on the limits of perception, the power of communication, and the necessity of embracing difference. For compliance professionals, it offers a road map for building training and communications programs that are clear, inclusive, practical, and resilient.

The universe of compliance is ever-expanding. Let’s train and communicate so our teams are ready to boldly go where no one has gone before.

Resources:

⁠⁠Excruciatingly Detailed Plot Summary by Eric W. Weisstein⁠⁠

⁠⁠MissionLogPodcast.com⁠⁠

⁠⁠Memory Alpha

Fiona is an AI generated voice

Categories
Blog

Connected Compliance: Part 4 – From Hotline to Trust

An effective compliance program is not a collection of disconnected policies, training modules, hotline reports, and investigation files. It is an operating system. Culture determines whether employees will use it. Risk assessment tells the organization where it must adapt. Investigations test whether the system responds credibly. Whistleblower programs reveal whether employees trust them enough to speak. In Blog Post 1, we considered communication as a compliance control. Blog Post 2 showed how operational signals create a dynamic risk radar. In Blog Post 3, we explained why every investigation is a test of governance and culture. This final installment examines the front door to the entire system: the reporting program.

A company can buy a hotline in an afternoon. It cannot buy employee trust. That distinction is the starting point for an effective whistleblower program. The platform, policy, telephone number, and case-management system are necessary infrastructure. They are not the program. The real program is the experience an employee anticipates before reporting and receives after doing so.

The answers do not come primarily from policy language. They come from what employees see happen to colleagues who raise concerns. A mishandled report can teach an entire workplace that silence is safer.

The First Report Is the Real Program Test

One of the easiest ways to discourage reporting is to do a poor job after a report arrives. An ignored allegation, confidentiality breach, unexplained delay, dismissive intake, or retaliation can do more damage than an outdated hotline poster.

This is why the reporting program and investigation process cannot be separated. Intake creates an expectation of action. Investigation determines whether that expectation is met. Follow-up determines what the reporter tells others about the experience. The process should begin with prompt acknowledgment. Whenever possible, a trained person should thank the reporter, gather clarifying information, explain next steps, and set realistic expectations. An automated receipt confirms that the technology worked. Personal contact demonstrates that the organization is listening.

What the DOJ Is Really Asking

The Department of Justice (DOJ) places confidential reporting within its evaluation of whether a compliance program is well designed. The 2024 Evaluation of Corporate Compliance Programs (ECCP) calls for an “efficient and trusted mechanism” for anonymous or confidential reports. The two words that matter most are efficient and trusted.

Efficiency requires accessible channels, proper routing, risk-based triage, qualified investigators, timely handling, documentation, and accountable remediation. Trust requires employees to believe that the company will take concerns seriously, limit information sharing, prevent retaliation, and respond consistently regardless of rank or commercial importance.

The DOJ asks whether employees know about the reporting mechanism, feel comfortable using it, and are willing to report misconduct. It also asks a difficult question: “Conversely, does the company use practices that tend to chill such reporting?” That directs compliance professionals beyond the hotline itself. Confidentiality agreements, manager behavior, performance systems, investigation delays, incentive structures, employment actions, and prior reporter experiences can all affect willingness to speak. The DOJ further asks whether the company tests hotline effectiveness by tracking a report from intake through disposition. This makes end-to-end testing a governance exercise, not a vendor-management task.

Design Channels Around the Workforce

A reporting system designed for headquarters may fail the people most likely to observe operational risk. Field employees, shift workers, remote personnel, contractors, and employees with limited computer access need channels that fit how they work. The answer is a meaningful choice. A mature program may include a telephone hotline, web portal, mobile access, email, QR codes, and in-person reporting to compliance, human resources, legal, internal audit, security, or management. Channels should be available in appropriate languages and accessible to employees with disabilities.

Placement matters. A QR code on an identification badge, break-room poster, or work-issued device may be more useful than a buried intranet link. A telephone line remains essential for employees who prefer to speak or lack reliable digital access. Many employees will first approach someone they trust. Compliance should analyze channel use by location, function, shift, language, and workforce type. A channel with no reports is not necessarily evidence that the location has no concerns. It may be evidence that the channel is unknown, inaccessible, or distrusted.

Make Speaking Up a Leadership Behavior

Tone at the top remains essential, but the employee’s immediate supervisor often controls the reporting climate. A chief executive may celebrate integrity while a frontline manager rolls their eyes, interrupts the employee, demands names, or warns that a report will hurt the team. The manager’s reaction becomes the company’s culture in that moment.

Managers need specific training. They should listen without investigating on the spot, avoid promises they cannot keep, preserve information, escalate promptly, and reinforce anti-retaliation expectations. A concern does not have to arrive through the hotline to require action. Leadership modeling should be visible. When leaders invite dissent, respond calmly to bad news, thank employees who identify risk, and communicate anonymized lessons, they show that speaking up protects the business. Regular field presence builds relationships, reveals access barriers, and provides context unavailable from a dashboard.

Tell the Truth About Confidentiality

Employees often use anonymity and confidentiality interchangeably, but they are different. An anonymous reporter does not disclose identity. Confidentiality means identity and related information are limited to people with a legitimate need to know. The company should never promise absolute secrecy when the facts make it impossible. In a small team, subject matter, timing, or witnesses may reveal who raised the concern. Overpromising creates a second breach of trust.

The better approach is candor. Explain that information will be restricted as far as reasonably possible, that some disclosure may be necessary to investigate fairly or meet legal obligations, and that retaliation is prohibited. Use role-based access, careful case notes, secure records, disciplined interview planning, and clear need-to-know rules. Confidentiality is not a slogan. It is an information-control process.

Communicate Without Compromising the Investigation

Silence during a long investigation can feel like indifference. Reporters do not need access to witness statements or confidential personnel decisions, but they do need evidence that the matter remains active. Set a communication cadence based on case risk and expected duration. Provide updates even when the update is that the review continues. Explain delays where appropriate, remind the reporter how to provide additional information, and repeat the anti-retaliation contact route.

At closure, confirm that the concern was reviewed and addressed as appropriate. Thank the reporter and reinforce anti-retaliation protection. The company may be unable to disclose findings or discipline, but it can close the human loop.

Treat Anti-Retaliation as an Active Control

An anti-retaliation policy is necessary, but it is not self-executing. Retaliation can be direct, such as termination, demotion, or loss of pay. It can also be subtle: exclusion from meetings, undesirable shifts, lost development opportunities, hostile supervision, damaged reputation, or social isolation. The company should assess retaliation risk throughout the matter. Compliance and human resources should preserve a baseline of the reporter’s role and treatment, monitor employment actions, schedule check-ins, and provide an escalation route outside the normal chain. Monitoring should continue after closure.

Protection does not mean immunity from legitimate performance management. It means employment decisions affecting a reporter receive appropriate review, are supported by contemporaneous evidence, and are not influenced by protected activity. When retaliation occurs, discipline should be prompt and visible enough, within confidentiality limits, to reinforce the rule.

Do Not Discredit the Difficult Messenger

Serial reporters and incomplete reports create operational challenges, but frequency, frustration, or poor drafting does not determine whether an allegation is true. Each concern should be assessed on its merits. A sparse report may still contain breadcrumbs. Investigators can review organizational charts, personnel changes, transactions, prior complaints, and control data before concluding that the matter cannot proceed. Multiple reports may reveal an unresolved environmental problem or weak earlier investigations.

Motivation can be relevant to credibility, but it should not replace evidence. Labeling someone a troublemaker is often an easy way to miss a difficult fact and an effective way to chill the next reporter.

Measure Trust, Not Just Volume

Hotline volume alone is a weak measure. A low number may reflect a healthy culture, a small risk population, inaccessible channels, fear, or lack of awareness. A rising number may reflect deteriorating conduct or growing confidence in the program. A useful dashboard combines volume with context: awareness and comfort survey results, reports by workforce segment, intake-to-acknowledgment time, triage time, case aging by risk, substantiation patterns, repeat allegations, reporter-update timeliness, retaliation concerns, remediation completion, and employee feedback after closure.

Compliance should test the entire system. Submit a controlled report, trace routing and access, review acknowledgments, confirm escalation rules, examine investigation handoffs, and verify closure and retention. Analyze whether reporting data changes risk assessment, controls, training, and resources. The objective is evidence that the program learns.

Closing the Connected Compliance Program

This four-part blog post series began with communication because employees cannot use a system they do not understand. It moved to dynamic risk assessment because organizations must recognize changing signals. It then examined investigations because allegations require independent facts, accountability, and remediation. Today we discussed whistleblower programs because none of those capabilities matter if people do not trust the company enough to speak. Join us tomorrow in our concluding Part 5 for a deeper discussion of how compliance truly is connected.

The connected compliance program is a loop. Communication builds awareness. Reporting supplies risk intelligence. Investigation converts allegations into reliable findings. Remediation improves controls. Feedback strengthens culture and makes future reporting more likely.

For the compliance professional, the final test is not whether the hotline exists. It is whether an employee facing a difficult choice believes that raising a concern will protect the organization, lead to a credible response, and not cost that employee a career. That is how a reporting channel becomes a trusted control and how culture becomes credibility.

Bonus Questions for Compliance Professionals

  1. Can every workforce segment access a reporting channel during the way and hours in which it actually works?
  2. Do employees know the available channels, understand external reporting rights, and say they feel comfortable using them?
  3. What happens during the first 24 hours after a report arrives, and who is accountable for acknowledgment, triage, and protection?
  4. Are managers trained to recognize and escalate concerns received outside formal reporting channels?
  5. Can the company show how reporter identity and case information are restricted to people with a legitimate need to know?
  6. How does the organization monitor direct and subtle retaliation during and after an investigation?
  7. Does the company communicate appropriately with reporters when an investigation is delayed and when it closes?
  8. Are serial, anonymous, and incomplete reports assessed on evidence and context rather than labels or assumptions?
  9. What reporting data has changed the risk assessment, controls, training, discipline, or resource allocation during the past year?
  10. Has the company recently tested one report from submission through routing, investigation, remediation, feedback, and retention?
Categories
Beyond the Label

Beyond the Label Podcast: Hope After the Flood: Surviving, Supporting, and Rebuilding Together

Co-hosts Tyler Townsend and Kelsi Wilmot of Beyond the Label pause their usual guest format to process the emotional toll of widespread flooding affecting all 19 counties, especially Kerr County, and to remind listeners that it’s okay not to be okay.

Tyler and Kelsi share lived experiences from last year’s floods and the recent July floods, including evacuations, work at reunification centers, deployments, volunteer coordination, and the lingering anxiety and “standby” stress that storms now trigger. They highlight community resilience, the importance of asking for help, and practical mental health resources, including 988, the crisis line (877-466-0660), free drop-in support at 819 Water Street, outreach teams, and therapist availability. They close by emphasizing hope, finding your “why,” avoiding isolation, and rebuilding together.

Key highlights:

  • Flooding Week Check-In
  • Hope and Holding On
  • Crisis Support Resources
  • Kelsi Flood Story
  • Tyler Response Journey
  • Aftereffects and Healing
  • Why We Do This Work
  • Find Your Why Helpers
  • Closing Together

Resources: 

Hill Country MHDD