Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 17 – Compliance Lessons from The Squire of Gothos

In this episode of Trekking Through Compliance, we consider the episode The Squire of Gothos, aired on January 12, 1967, Star Date 2124.5.

Story Synopsis

The Enterprise encounters a rogue planet previously hidden from their sensors. As Sulu attempts to enter a course around the planet, he suddenly vanishes from the bridge, and Kirk vanishes a moment later. The Enterprise then receives a strange message on a viewscreen in blackletter writing: “Greetings and Felicitations!” followed by “Hip hip hoorah. Tallyho!” Spock orders Chief Medical Officer Dr. McCoy, Lt. DeSalle, and geophysicist Karl Jaeger to form a landing party and conduct a search.

The landing party beams down and unexpectedly finds itself in a lush and breathable environment, a medieval castle. They find Captain Kirk and Lt. Sulu immobilized and a humanoid who identifies as “General Trelane, retired.

Trelane suggests that Kirk be prey for a royal hunt, and Kirk agrees in return for the release of his ship. Two beings appear and call out to Trelane, ordering him to “come along” and lecturing him for his misbehavior. He then disappears, and the two beings follow after apologizing to Kirk, who returns to the ship.

Commentary

The story follows the crew of the Enterprise as they encounter the playful and powerful alien Trelane, who underestimates human progress and ethics. The episode explores themes of technological superiority, hidden motives, information asymmetry, adaptive adversaries, and the courage to speak truth to power. Fox draws valuable parallels to modern compliance challenges through these themes, offering insightful lessons for compliance professionals.

  • Mysterious Planet and Disappearance
  • Encounter with General Trelane
  • Trelane’s Trial and Resolution
  • Fun Facts and Behind the Scenes
  • Compliance Lessons from The Squire of Gothos

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

 

Categories
Compliance Tip of the Day

Compliance Tip of the Day: The Master Data Plan

Welcome to “Compliance Tip of the Day,” the podcast where we bring you daily insights and practical advice on navigating the ever-evolving landscape of compliance and regulatory requirements.

Whether you’re a seasoned compliance professional or just starting your journey, our aim is to provide you with bite-sized, actionable tips to help you stay on top of your compliance game.

Join us as we explore the latest industry trends, share best practices, and demystify complex compliance issues to keep your organization on the right side of the law.

Tune in daily for your dose of compliance wisdom, and let’s make compliance a little less daunting, one tip at a time.

In today’s episode, we explore how a Master Data Plan can be used to make your use of data more efficient, more transparent and more encompassing.

For more information on the Ethico ROI Calculator and a free White Paper on the ROI of Compliance, click here.

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 15 – Compliance Lessons from Shore Leave

In this episode of Trekking Through Compliance, we consider the episode Shore Leave, which aired on December 29, 1966, with a Star Date of 3025.3.

This is one of the most fun and beloved TOS episodes. It begins with the Enterprise discovering  Omicron Delta, which appears to be the ideal location for rest for the Enterprise crew. However, strange things soon start to happen to the landing party. McCoy sees Alice and a white rabbit; Sulu finds an antique Police Special gun; Don Juan and Esteban Rodriguez accost Yeoman Barrels; and Angela sees birds. Kirk cancels shore leave for the rest of the crew but is confronted with practical joker Finigan from Starfleet Academy on the one hand and his former girlfriend Ruth on the other.

Spock reports from the Enterprise that he has detected a sophisticated power field on the planet that is draining the Enterprise’s energy. Spock beams down to help investigate, just as communications with the ship are becoming impossible. After asking Kirk what he was thinking about before encountering Finigan, Spock realizes that the apparitions are being created out of the minds of the landing party. The planet’s caretaker appears with McCoy. The caretaker apologizes for the misunderstandings and offers the services of the amusement park planet to the Enterprise’s weary crew.

Commentary

In this episode of Trekking Through Compliance, host Tom Fox delves into the beloved Star Trek episode ‘Shore Leave.’ The story follows the crew of the Enterprise as they encounter strange phenomena on a seemingly perfect shore leave planet, leading to various bizarre and surreal experiences. Fox extracts valuable compliance lessons from the episode, emphasizing the importance of incorporating fun and games into training for better engagement. He also discusses leadership principles such as leading by example, fostering integrity, clear communication, distributed leadership, and adaptability. The episode is a blend of adventure, whimsical elements, and practical insights for compliance professionals aiming to cultivate a culture of trust and ethical behavior in their organizations.

Key Highlights

  • Strange Happenings on the Planet
  • Kirk’s Encounters and Investigations
  • The Planet’s Secrets Revealed
  • Fun Facts and Behind the Scenes
  • Compliance Lessons from Shore Leave

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 14 – Compliance Lessons from Balance of Terror

In this episode of Trekking Through Compliance, we consider the episode Balance of Terror, which aired on December 15, 1966, Star Date 1709.1

Enterprise investigates the lack of response from Earth outposts 2 and 3, monitoring the Neutral Zone between planets Romulus and Remus and the rest of the galaxy. The Earth outposts were constructed on asteroids and were authorized by a treaty following the atomic war with the Romulans more than a century earlier. No human or Romulan, however, has ever seen the other.

As the Enterprise communicates with Outpost 4, Commander Hansen reports an attack underway by an unknown weapon from a spaceship, which subsequently vanished. The Romulan commander questions his mission of starting a war and discusses it with his Centurion—the Enterprise and Romulan ship exchange fire. The Enterprise then sits motionless, hoping the Romulan ship will make a move and reveal itself. They do so, and the Romulan ship is rendered inoperative, and its captain self-destructs.

Commentary

In this episode of Trekking Through Compliance, host Tom Fox explores the first appearance of the Romulans in the original Star Trek series episode ‘Balance of Terror.’ The Enterprise investigates attacks on Earth outposts near the Romulan Neutral Zone, uncovering themes of trust, loyalty, and the ethical dilemmas compliance officers face. The episode’s tension, akin to a World War II submarine movie, highlights the importance of principled decision-making, transparency, and balancing security and civil liberties. Key compliance lessons include the necessity for robust risk assessment, clear communication, and an understanding of diverse organizational cultures.

Key Highlights

  • The Enterprise’s Mission and Encounter
  • The Cat and Mouse Game
  • The Final Confrontation
  • Compliance Takeaways from Balance of Terror

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 13 – The Conscience of the King

In this episode of Trekking Through Compliance, we consider the episode The Conscience of the King, which aired on December 8, 1966, with a Star Date of 2817.6.

Dr. Thomas Leighton calls the Enterprise Planet Q. Leighton suspects Anton Karidian, the leader of a Shakespearean acting troupe currently on the planet, is Kodos the Executioner, the former governor of the Earth colony of Tarsus IV. Kodos ordered that half the population of 8,000 be put to death during a food shortage. Both Leighton and Kirk were eyewitnesses.

Kirk arranges to ferry the acting troupe to its next destination. Spock learns the history of the massacre, Kirk’s connection to it, and that seven of the nine witnesses had died in each case when Karidian’s troupe was nearby. Kirk confronts Karidian with his suspicions. Karidian does not admit to being Kodos.

Karidian, overhearing, is disturbed, and Lenore tries to reassure him by revealing that she has been killing the witnesses to his crimes. Kirk moves to arrest them both. Lenore snatches a phaser and accidentally kills Karidian.

Commentary

The episode recounts Captain Kirk’s confrontation with Kodos the Executioner, who has been living under the alias of actor Anton Karidian. While investigating a string of murders tied to Karidian’s acting troupe, Kirk grapples with the ethical dilemma of justice versus mercy. The narrative challenges viewers to question whether Karidian’s past atrocities should overshadow his subsequent years of apparent redemption. Tom Fox connects these themes to compliance, reflecting on how professionals might balance institutional justice and mercy within their organizations. This episode explores moral guilt, redemption, and the intricate balance between justice and leniency.

Key Highlights

  • Plot Summary: Conscience of the King
  • Shakespearean References and Performances
  • Ethical Dilemma: Justice vs. Mercy
  • Implications for Compliance Professionals
  • Conclusion and Next Episode Preview

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Blog

AI in Compliance Week: Part 5 – Continuous Monitoring of AI

This blog post concludes a five-part series I ran this week on some of the keys intersecting AI and compliance. Yesterday, I wrote that businesses must proactively address the potential for bias at every stage of the AI lifecycle—from data collection and model development to deployment and ongoing monitoring. In this final blog post, I deeply dive into continuously monitoring your AI. We begin this final Part 5 with some key challenges organizations must navigate to accomplish this task.

As we noted yesterday, data availability and high data quality are essential. Garbage In, Garbage Out. Robust bias monitoring requires access to comprehensive, high-quality data that accurately reflects the real-world performance of your AI system. Acquiring and maintaining such datasets can be resource-intensive, especially as the scale and complexity of the AI system grow. However, this is precisely what the Department of Justice (DOJ) expects from a corporate compliance function.

How have you determined your key performance indicators (KPIs) and interpretation? Selecting the appropriate fairness metrics to track and interpret the results can be complex. Different KPIs may capture various aspects of bias, and tradeoffs between them can exist. Determining the proper thresholds and interpreting the significance of observed disparities requires deep expertise.

Has your AI engaged in Model Drift or Concept Shift? Compliance professionals are aware of the dreaded ‘mission creep. AI models can exhibit “drift” over time, where their performance and behavior gradually diverge from the original design and training. Additionally, the underlying data distributions and real-world conditions can change, leading to a “concept shift” that renders the AI’s outputs less reliable. Continuously monitoring these issues and making timely adjustments is critical but challenging. Companies will need to establish clear decision-making frameworks and processes to address model drift and concept shift.

Operational complexity is a critical issue in continuous AI monitoring. Integrating continuous bias monitoring and mitigation into the AI system’s operational lifecycle can be logistically complex. This requires coordinating data collection, model retraining, and deployment across multiple teams and systems while ensuring minimal service disruptions.

Everyone must buy in or in business-speak – Organizational Alignment must be in place.  Not surprisingly, it all starts with the tone at the top. Your organization should foster a responsible AI development and deployment culture with solid organizational alignment and leadership commitment. Maintaining a sustained focus on bias monitoring and mitigation requires buy-in and alignment across the organization, from executive leadership to individual contributors. Overcoming organizational silos, competing priorities, and resistance to change can be significant hurdles.

There will be evolving regulations and standards. The regulatory landscape governing the responsible use of AI is rapidly growing, with new laws and industry guidelines emerging. Keeping pace with these changes and adapting internal processes can be an ongoing challenge. Staying informed about evolving regulations and industry standards and adapting internal processes will be mission-critical.

The concept of AI explainability and interpretability will be critical going forward.  As AI systems become more complex, providing clear, explainable rationales for their decisions and observed biases becomes increasingly crucial. Enhancing the interpretability of these systems is essential for effective bias monitoring and mitigation. This will be improved by developing robust data management practices to ensure the availability and quality of data for bias monitoring. The bottom line is that companies should prioritize research and development to improve the explainability and interpretability of AI systems, enabling more effective bias monitoring and mitigation.

A financial commitment will be required, as continuous bias monitoring and adjustment can be resource-intensive. It requires dedicated personnel, infrastructure, and budget allocations and investing in specialized expertise, both in-house and through external partnerships, to enhance the selection and interpretation of fairness metrics. Organizations must balance these needs against other business priorities and operational constraints. Companies must allocate the necessary resources, including dedicated personnel, infrastructure, and budget, to sustain continuous bias monitoring and adjustment efforts.

Organizations should adopt a comprehensive, well-resourced approach to AI governance and bias management to overcome these challenges. This includes developing robust data management practices, investing in specialized expertise, establishing clear decision-making frameworks, and fostering a responsible AI development and deployment culture.

Continuous monitoring and adjusting AI systems for bias is a complex, ongoing endeavor, but it is critical to ensure these powerful technologies’ ethical and equitable use. By proactively addressing the challenges, organizations can unlock AI’s full potential while upholding their commitment to fairness and non-discrimination.

By proactively addressing these challenges, organizations can unlock AI’s full potential while upholding their commitment to fairness and non-discrimination. Continuous monitoring and adjusting AI systems for bias is a complex, ongoing endeavor, but it is a critical component of responsible AI development and deployment.

As the AI landscape continues to evolve, organizations prioritizing this crucial task will be well-positioned to navigate the ethical and regulatory landscape, build trust with their stakeholders, and drive sustainable innovation that benefits society.

Categories
Blog

AI in Compliance Week: Part 4 – Keeping Your AI – Powered Decisions Fair and Unbiased

As artificial intelligence (AI) becomes increasingly integrated into business operations and decision-making, ensuring the fairness and lack of bias in these AI systems is paramount. This is especially critical for companies operating in highly regulated industries, where prejudice and discrimination can lead to significant legal, financial, and reputational consequences. Implementing AI responsibly requires a multifaceted approach beyond simply training the models on large datasets. Companies must proactively address the potential for bias at every stage of the AI lifecycle – from data collection and model development to deployment and ongoing monitoring.

Based upon what the Department of Justice said in the 2020 Evaluation of Corporate Compliance Programs, a corporate compliance function is the keeper of both Institutional Justice and Institutional Fairness in every organization. This will require compliance to be at your organization’s forefront of ensuring your AI-based decisions are fair and unbiased. What strategies does a Chief Compliance Officer (CCO) or compliance professional employ to help make sure your AI-powered decisions remain fair and unbiased?

The adage GIGO (garbage in, garbage out) applies equally to the data used to train AI models. If the underlying data contains inherent biases or lacks representation of particular demographic groups, the resulting models will inevitably reflect those biases. It would help if you made a concerted effort to collect training data that is diverse, representative, and inclusive. Audit your datasets for potential skews or imbalances and supplement them with additional data sources to address gaps. Regularly review your data collection and curation processes to identify and mitigate biases.

The composition of your AI development teams can also significantly impact the fairness and inclusiveness of the resulting systems. Bring together individuals with diverse backgrounds, experiences, and perspectives to participate in every stage of the AI lifecycle. A multidisciplinary team including domain experts, data scientists, ethicists, and end-users can help surface blind spots, challenge assumptions, and introduce alternative viewpoints. This diversity helps ensure your AI systems are designed with inclusivity and fairness in mind from the outset.

It would help if you employed comprehensive testing for bias, which is essential to identify and address issues before your AI systems are deployed. By Incorporating bias testing procedures into your model development lifecycle and then making iterative adjustments to address any problems identified. There are a variety of techniques and metrics a compliance professional can use to evaluate your models for potential biases:

  • Demographic Parity: Measure the differences in outcomes between demographic groups to ensure equal treatment.
  • Equal Opportunity: Assess the accurate favorable rates across groups to verify that the model’s ability to identify positive outcomes is balanced.
  • Disparate Impact: Calculate the ratio of selection rates for different groups to detect potential discrimination.
  • Calibration: Evaluate whether the model’s predicted probabilities align with actual outcomes consistently across groups.
  • Counterfactual Fairness: Assess whether the model’s decisions would change if an individual’s protected attributes were altered.

As AI systems become more complex and opaque, transparency and explainability become increasingly important, especially in regulated industries. (Matt Kelly and I discussed this topic on this week’s Compliance into the Weeds.) It would help if you worked to implement explainable AI techniques that provide interpretable insights into how your models arrive at their decisions. By making the decision-making process more visible and understandable, explainable AI can help you identify potential sources of bias, validate the fairness of your models, and ensure compliance with regulatory requirements around algorithmic accountability.

As Jonathan Marks continually reminds us, corporations rise and fall on their government models and how they operate in practice. Compliance professionals must cultivate a strong culture of AI governance within your organization, with clear policies, methods, and oversight mechanisms in place. This should include:

  • Executive-level Oversight: Ensure senior leadership is actively involved in setting your AI initiatives’ strategic direction and ethical priorities.
  • Cross-functional Governance Teams: Assemble diverse stakeholders, including domain experts, legal/compliance professionals, and community representatives, to provide guidance and decision-making on AI-related matters.
  • Auditing and Monitoring: Implement regular, independent audits of your AI systems to assess their ongoing performance, fairness, and compliance. Continuously monitor for any emerging issues or drift from your established standards.
  • Accountability Measures: Clearly define roles, responsibilities, and escalation procedures to address problems or concerns and empower teams to take corrective action.

By embedding these governance practices into your organizational DNA, you can foster a sense of shared responsibility and proactively manage the risks associated with AI-powered decision-making. As with all other areas of compliance, maintaining transparency and actively engaging with key stakeholders is essential for building trust and ensuring your AI initiatives align with societal values, your organization’s culture, and overall stakeholder expectations. A CCO and compliance function can do so through a variety of ways:

  • Regulatory Bodies: Stay abreast of evolving regulations and industry guidelines and collaborate with policymakers to help shape the frameworks governing the responsible use of AI.
  • Stakeholder Representatives: Seek input from diverse community groups, civil rights organizations, and other stakeholders to understand their concerns and incorporate their perspectives into your AI development and deployment processes.
  • End-users: Carsten Tams continually reminds us that it is all about the UX. A compliance professional in and around AI should engage with the employees and other groups directly impacted by your AI-powered decisions and incorporate their feedback to improve your systems’ fairness and user experience.

By embracing a spirit of transparency and collaboration, CCOs and compliance professionals will help your company navigate the complex ethical landscape of AI and position your organization as a trusted, responsible leader in your industry. Similar to the management of third parties, ensuring fairness and lack of bias in your AI-powered decisions is an ongoing process, not a one-time event. Your company should dedicate resources to continuously monitor the performance of your AI systems, identify any emerging issues or drift from your established standards, and make timely adjustments as needed. You must regularly review your fairness metrics, solicit feedback from stakeholders, and be prepared to retrain or fine-tune your models to maintain high levels of ethical and unbiased decision-making. Finally, fostering a culture of continuous improvement will help you stay ahead of the curve and demonstrate your commitment to responsible AI.

As AI is increasingly embedded in business operations, the stakes for ensuring fairness and mitigating bias have never been higher. By adopting a comprehensive, multifaceted approach to AI governance, your organization can harness this transformative technology’s power while upholding ethical and unbiased decision-making principles. The path to responsible AI may be complex, but the benefits – trust, compliance, and long-term sustainability – are worth the effort.

Categories
Trekking Through Compliance

Trekking Through Compliance: Episode 11 – Ethical Lessons from Menagerie, Part 1

In this episode of Trekking Through Compliance, we consider the episode The Menagerie (Part One), which aired on November 17, 1966, Star Date 3012.4.

Story Synopsis

This was the original pilot episode presented to NBC. Set in 2267, the Enterprise arrives at Starbase 11 in response to a subspace call Spock reported receiving from the former captain of the Enterprise, Christopher Pike, under whom Spock had served. Pike cannot move or communicate other than answering yes/no questions with a device operated by his brainwaves. Pike refuses to communicate with anyone except Spock.

Spock, meanwhile, commandeers the Enterprise using falsified recordings of Kirk’s voice and orders the ship to depart under the computer’s control. After several hours, upon learning from the computer that the shuttlecraft does not have enough fuel to return to the starbase, Spock brings them aboard and then gives himself up, confessing to mutiny. Mendez convenes a hearing, at which Spock requests immediate court-martial, which requires three command officers. The tribunal begins, and Spock offers as his testimony what seems to be video footage of the Enterprise’s earlier visit to Talos IV in 2254.

In 2267, the scene is interrupted by a message from Starfleet Command, which reveals that the images they have been viewing are transmitted from Talos IV. Mendez is placed in command of the Enterprise, but Spock begs Kirk to see the rest of the transmission.

Commentary

In this episode of Trekking Through Compliance, host Tom Fox delves into the first part of ‘The Menagerie,’ a pivotal Star Trek episode derived from the original pilot, ‘The Cage.’ The episode follows the Enterprise’s detour to Starbase 11 after Spock receives a message supposedly from former Captain Christopher Pike, only to find Pike severely injured and unable to communicate. Spock’s subsequent actions lead to a gripping courtroom drama and examination of ethical dilemmas. Tom highlights key ethical lessons, including informed consent, disability rights, truthfulness, ethical decision-making, and whistleblowing, showing how these can be applied within compliance programs to foster a more moral and just organizational environment.

Key Highlights

  • Plot Summary of The Menagerie Part 1
  • Behind the Scenes and Fun Facts
  • Ethical Lessons from The Menagerie Part 1

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Compliance Tip of the Day

Compliance Tip of the Day: AI Powered Internal Controls

Welcome to “Compliance Tip of the Day,” the podcast where we bring you daily insights and practical advice on navigating the ever-evolving landscape of compliance and regulatory requirements.

Whether you’re a seasoned compliance professional or just starting your journey, our aim is to provide you with bite-sized, actionable tips to help you stay on top of your compliance game.

Join us as we explore the latest industry trends, share best practices, and demystify complex compliance issues to keep your organization on the right side of the law.

Tune in daily for your dose of compliance wisdom, and let’s make compliance a little less daunting, one tip at a time.

In today’s episode, we begin a weeklong look at some of the ways Generative AI is changing compliance and risk management. Today we look at how to set up AI-powered internal controls from a compliance perspective.

 

For more information on the Ethico ROI Calculator and a free White Paper on the ROI of Compliance, click here.

Categories
Trekking Through Compliance

Trekking Through Compliance: Episode 10 – The Corbomite Maneuver

In this episode of Trekking Through Compliance, we consider the episode The Corbomite Maneuver, which aired on November 10, 1966, with a Star Date of 1512.2.

Novice navigator Lt. Dave Bailey spots a giant spinning multi-colored cube floating in space. He advocates attacking it with phasers. Kirk instead orders the ship to back away from the object. The cube pursues them, emitting harmful radiation, and Kirk reluctantly destroys it. After that, a gigantic glowing sphere approaches the Enterprise, explaining that the destroyed cube was a border marker and that the First Federation will destroy the Enterprise for trespassing into their territory. Kirk tries to bluff Balok, telling him that the Enterprise contains “corbomite, ” which automatically destroys any attacker.

Kirk, McCoy, and Bailey form a boarding party to render assistance. They beam over and discover that the “Balok” on their monitor is an effigy. The real Balok, looking like a hyperintelligent human child, enthusiastically welcomes them aboard. He explains that he was merely testing the Enterprise and its crew to discover their true intentions. As Kirk and company relax, Balok desires to learn more about humans and their culture and suggests they allow a crew member to remain on his ship as an emissary of the Federation. Bailey happily volunteers, and Balok gives them a tour of his ship.

Commentary

In this episode, we draw out parallels between the episode and compliance leadership. The discussion covers key leadership lessons: adaptability, maintaining calm, leveraging limited resources, trusting team expertise, and handling ambiguity. Special attention is given to the episode’s production history and its potential allegory of Cold War tensions. Fox emphasizes how these lessons can help compliance professionals navigate complex regulatory challenges.

Key Highlights

  • Plot Summary of The Corbomite Maneuver
  • Behind the Scenes and Fun Facts
  • Ethical Lessons from The Corbomite Maneuver

Compliance Takeaways:

  1. Never pass up the chance for cross-cultural exchange.
  2. Should discipline have a remedial component or be simply punitive?
  3. How much stress can you or should you put on your employees?

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha