Categories
Principled Podcast

Principled Podcast: S11E7 | Fortifying Ethical Frameworks: Navigating Emerging Risks in the Middle East

Amid the escalating severity and frequency of new risks worldwide, Ethics and Compliance (E&C) initiatives are doubling down on efforts to mitigate these risks. This critical focus is underscored in LRN’s latest 2024 Ethics & Compliance Program Effectiveness Report, which draws insights from over 1,400 E&C professionals globally. Our findings reveal that values-driven programs not only prove most effective but also exhibit a robust correlation with risk reduction and enhanced business outcomes. In light of this evolving risk landscape, how are E&C programs in regions such as the Middle East adapting? Furthermore, what do the everyday practices of global best standards entail for programs operating within this region?

In this episode of the Principled Podcast, host Eric Morehead is joined by Elvis Angyiembe, the co-founder of the Middle East and Africa Compliance Association (MEACA). Elvis joined us last season to discuss the E&C priorities of companies in the Middle East. Today, they discuss key findings from the global edition of the 2024 Ethics & Compliance Program Effectiveness Report and how they apply to programs in that region.

Guest: Elvis Angyiembe

Principled Podcast - Season 11 Episode 7 featuring Elvis Angyiembe MEACA - Episode Cover

Elvis Angyiembe is co-founder and co-chair of the Middle East and Africa Compliance Association (MEACA). He has experience working for multinational companies, helping them manage significant legal and compliance matters. He has supported three companies under deferred prosecution agreements with the US Department of Justice. He has lived in Cameroon, Germany, the US, South Africa, and Dubai. He holds a Juris Doctorate (JD) from Thurgood Marshall School of Law in Houston, Texas, and a bachelor’s degree in criminology from the University of Maryland in College Park, Maryland.

Host: Eric Morehead

Headshot_Principled Podcast_Eric Morehead

Eric Morehead is a member of LRN’s Advisory Services team and has over 20 years of experience working with organizations seeking to address compliance issues and build effective compliance and ethics programs. He conducts program assessments and examines specific compliance risks, drafts compliance policies and codes of conduct, works with organizations to develop and improve compliance processes and tools, and provides live training for Boards of Directors, executives, managers, and employees.

Eric ran his consultancy for six years, advising clients on compliance program enhancements and assisting in creating effective compliance solutions.

Eric was formerly the Head of Advisory Services for NYSE Governance Services, a leading compliance training organization. In this position, he was responsible for all aspects of NYSE Governance Services’ compliance consulting arm.

Before joining NYSE, Eric was an Assistant General Counsel of the United States Sentencing Commission in Washington, DC. Eric served as the policy team chair that amended the Organizational Sentencing Guidelines in 2010.

Eric also spent nearly a decade as a litigation attorney in Houston, Texas, where he focused on white-collar and regulatory cases and represented clients at trial and before various agencies including SEC, OSHA, and CFTC.

Get a copy of the Global edition of LRN’s 2024 Ethics & Compliance Program Effectiveness Report.

Connect with the Compliance Podcast Network at:

LinkedIn: https://www.linkedin.com/company/compliance-podcast-network/
Facebook: https://www.facebook.com/compliancepodcastnetwork/
YouTube: https://www.youtube.com/@CompliancePodcastNetwork
Twitter: https://twitter.com/tfoxlaw
Instagram: https://www.instagram.com/voiceofcompliance/
Website: https://compliancepodcastnetwork.net/

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 36 – Risk Management Lessons from Catspaw

In this episode of Trekking Through Compliance, we consider the episode Catspaw, which aired on October 27, 1967, and occurred on Star Date 3018.2.

Strange things happen to a landing party consisting of Jackson, Sulu, and Scotty when they beam down to planet Pyrus 7. When Kirk, Spock, and McCoy beam down to investigate, leaving DeSalle in command and Chekov as his sidekick, they are enveloped in fog. They also detect multiple life readings, even though the Enterprise’s sensors only detect the landing party. They are all captured by Korob and Sylvia.

Meanwhile,  Enterprise is breaking free through DeSalle’s efforts. Korob sets Kirk and Spock free and tells them to leave immediately because he can no longer control Sylvia. Kirk grabs Korob’s scepter, and after fending off attacks from McCoy, Scott, and Sulu, Kirk tells Sylvia that he has the scepter. Kirk breaks the scepter in front of Sylvia. The castle vanishes, and Sylvia and Korob appear as the bizarre blue and yellow puppet-like alien beings they are. Unable to survive in this galaxy without the transmuter, they shrivel up and melt away, and Sulu and Scott are returned to normal.

Commentary

The story follows a landing party encountering strange, supernatural events on planet Pyrus 7, leading to valuable compliance lessons. Key takeaways include maintaining situational awareness, establishing effective incident response, identifying and mitigating supply chain vulnerabilities, fostering a culture of skepticism, prioritizing resilience, and empowering cross-functional collaboration. The episode uniquely ties the plot’s elements to practical compliance and risk management learning.

Key Highlights

  • Story Synopsis
  • Fun Facts and Production Notes
  • Narcissism in Cat’s Paw
  • Risk Management Lessons

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 35 – Compliance Leadership and Risk Management Lessons from The Doomsday Machine

In this episode of Trekking Through Compliance, we consider the compliance and leadership lessons from the episode The Doomsday Machine, which aired on October 20, 1967, and occurred on Star Date 4202.9.

The Enterprise responds to a distress beacon from the Starship U.S.S. Constellation and then finds the battered remains of the ship itself. Kirk sends a boarding party to the Constellation to investigate. Its commander,  Commodore Matt Decker, is in a state of shock and not very coherent. Even after McCoy injects him, Decker can say that his ship was attacked by “that thing.”

Kirk beams Decker and McCoy back to the Enterprise. The Doomsday Machine attacks the Enterprise. Commodore Decker pulls his rank and assumes command over Spock’s objections. Kirk sees what is going on from the Constellation and begins heading toward the Doomsday Machine using impulse power.

Kirk angrily orders Spock to re-assume command of his authority, which he does. Decker steals a shuttlecraft and pilots it into the Doomsday Machine, killing himself but producing a small power drop in the Doomsday Machine. Kirk reasons that the starship explosion might be capable of destroying the alien vessel. Scott rigs the Constellation to explode, then transports it to the Enterprise. The Constellation then explodes, turning the planet killer into a harmless pile of space junk.

Commentary

The Enterprise encounters a planet-destroying robot and must devise a way to stop it. Fox underscores various compliance and risk management lessons: establishing robust incident response protocols, fostering cross-functional teamwork, ensuring organizational resilience, balancing short-term fixes with long-term solutions, cultivating a culture of compliance and innovation, and maintaining situational awareness and adaptability. These lessons are essential for compliance leadership in 2024.

Key Highlights

  • Story Synopsis: The Doomsday Machine
  • Fun Facts and Behind the Scenes
  • Compliance Leadership and Risk Management Lessons

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Because That's What Heroes Do

Because That’s What Heroes Do: Deep Space 9 – Episode 8 – The Abandoned

Get ready for an exciting new season of Because That’s What Heroes Do. In this season, they take a deep dive into their favorite 15 episodes of Deep Space 9.

In this exploration, they are joined by DS9 maven Alex Murphy (Murphy) from Montreal, who is a local historian and cinema and TV fan with a love for weird foreign films, all things horror, and obscure media.

He has been watching Trek since he was a tiny punk, and it’s been a lifelong love. Don’t miss out on the exciting new season of Because That’s What Heroes Do!

Today we take a deep dive into Jem ‘Hadar in the episode from Season 3, The Abandoned.

In this episode, Megan, Murphy, and Tom delve into the DS9 episode ‘The Abandoned.’ The discussion focuses on Odo’s self-awareness and character development, the complex relationship between Jake and his father, Sisko, and the moral implications of Jem’Hadar’s existence.

They examine Odo’s internal conflict with his identity as a changeling and his feelings for Kira. The hosts reflect on whether the Jem’Hadar can be considered sentient beings and debate the ethical responsibilities of the Federation. Through these themes, the episode raises profound questions about sentience, free will, and personal growth.

Key Highlights and Themes:

  • Character Development: Odo and Sisko
  • Debating the Ethics of the Jem’Hadar
  • Jake’s Relationship and Sisko’s Parenting
  • What is a sentient being?
  • Odo and Kira: Unspoken Feelings
  • Final Thoughts and Reflections

Resources:

Megan Dougherty 

LinkedIn

One Stone Creative

Tom 

Instagram

Facebook

YouTube

Twitter

LinkedIn

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 34 – The Apple

In this episode of Trekking Through Compliance, we consider the compliance and leadership lessons from the episode The Apple, which aired on October 13, 1967, and occurred on Star Date 3715.0.

A Landing Party finds danger on a seemingly pristine planet as the Enterprise is threatened. The planet’s inhabitants are the feeders of Vaal. Kirk asks to be taken to Vaal, just as Scott reports that the Enterprise is being dragged into the planet by a tractor beam from the planet.

Kirk and Spock go to confront Vaal. Vaal responds by calling a thunderstorm and striking Spock with a lightning bolt. The people of Vaal then attack, killing a security guard. As usual, the rest of the landing party fends off the attack and gets off unscathed. Kirk has Scott attack Vaal with the ship’s phasers to weaken. This drains Vaal’s power reserves and frees the people from his grip. Spock accuses Kirk of giving the people the equivalent of the apple of knowledge and driving them from their Eden, but Kirk maintains that Spock’s resemblance to the Devil is much more apparent than his own.

Commentary

The episode follows Captain Kirk and his landing party as they encounter the planet Gamma Trianguli VI and grapple with its godlike ruler, Vaal. The discussion highlights critical business ethics lessons, including the dangers of paternalistic control, respecting cultural sovereignty, ensuring transparency, avoiding disruption of stable systems, fostering self-determination, and balancing short-term and long-term impacts. Additionally, this episode reflects on the broader implications of Kirk’s actions on the planet’s civilization and draws parallels to modern ethical concerns in compliance programs.

Key Highlights

  • Story Synopsis
  • Fun Fact and Episode Themes
  • Business Ethics Lessons from The Apple

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

 

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 33 – Mirror Mirror

In this episode of Trekking Through Compliance, we consider the episode Mirror Mirror, which aired on October 6, 1967, Star Date unknown.

During an ion storm, the Away Team is transported into a parallel universe and a mirror image of the Enterprise. There, they find members who are mirror images of themselves and belong to an evil Federation known as the Empire. Kirk, Uhura, McCoy, and Scotty impersonate their mirror-image counterparts while finding a way to return to their universe.

Discovering that a switch has occurred, anti-Spock then assists Kirk in returning his landing party to their universe so that the Empire landing party may return to its. When Kirk and the party return, they find their Empire counterparts immediately recognized and detained. The Enterprise’s crew attributes this to the fact that it is easier for logical men to appear barbarous than for barbarous men to appear civilized.

Commentary

In this episode of ‘Trekking Through Compliance,’ Tom Fox delves into the Star Trek original series episode ‘Mirror, Mirror.’ The episode aired on October 6, 1967, and involved Captain Kirk and his team being transported to a parallel universe with an evil version of the Enterprise. The narrative unfolds with themes of power struggles, ethical contrasts, and survival. Tom extracts crucial compliance lessons from the story, including the importance of strict access controls, fostering a culture of ethics and compliance, rigorous oversight, planning for contingencies, and encouraging a culture of speaking up. These lessons are vital for building robust compliance programs. Tune in to discover how ‘Star Trek’ can offer valuable insights into modern compliance challenges.

Key Highlights

  • Episode Synopsis: Mirror, Mirror
  • Fun Facts and Behind the Scenes
  • Compliance Lessons from Mirror, Mirror

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

 

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 32 – Leadership Lessons from The Changeling

In this episode of Trekking Through Compliance, we consider the compliance lessons from the episode The Changeling, which aired on September 29, 1967, and occurred on Star Date 3451.9.

The Enterprise encounters a probe that identifies itself as Nomad. The probe believes that Kirk is its creator. Nomad says its mission is to destroy anything imperfect, including humans.

Kirk confronts Nomad, telling him his contempt for biological units is illogical since its creator is biological. Kirk then gets Nomad to admit that everything must be sterilized, which is in error. While attempting to consider the situation, Nomad is beamed into space. It is caught in a logic loop while trying to analyze its errors and finally self-destructs to “sterilize” its imperfections.

Commentary

In this episode of Trekking Through Compliance, Tom Fox explores the Star Trek original series episode ‘The Changeling’ and its valuable leadership and compliance lessons. Upon responding to a distress call, the USS Enterprise encounters the rogue space probe Nomad, which mistakes Captain Kirk for its creator and poses a deadly threat to the crew. Kirk navigates this crisis through strategic thinking and emotional intelligence, highlighting essential leadership skills. The episode also features noteworthy scenes, including one where Uhura speaks Swahili, leading to an insightful discussion on leadership takeaways such as empathy, situational awareness, adaptability, and balancing compassion with pragmatism.

Key Highlights

  • The Distress Call and Encounter with Nomad
  • Nomad’s Mission and Kirk’s Dilemma
  • The Final Confrontation with Nomad
  • Leadership Lessons from the Episode

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

 

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 31 – Who Mourns for Adonais?

In this episode of Trekking Through Compliance, we consider the episode Who Mourns for Adonais?, which aired on September 22, 1967, with a Star Date of 3468.1.

While approaching Pollux 4, an energy field shaped like a giant green hand stops the Enterprise dead in space, and an apparition wearing a laurel wreath appears. The apparition addresses the crew as his “children” and congratulates them for venturing forth from the hills and valleys of Earth. The apparition invites Kirk and a landing party to visit, excluding Spock.

The landing party discovers a humanoid who identifies as the Roman god Apollo. Apollo says he and the other gods left after the ancient people of Earth stopped worshipping them. Even the immortal gods weaken without worshippers, and all but Apollo have “spread themselves to the wind” and faded away.

Although Carolyn is in love with Apollo, she puts her duty ahead of herself when acting on Kirk’s instructions; she rejects him to weaken him. Apollo’s power is destroyed when his energy source in the temple is located and blasted out of existence by the Enterprise’s phasers. A sorrow-stricken Apollo appeals to the other gods to take him away now that he realizes there is no room for gods anymore.

Commentary

The storyline teaches lessons in compliance, particularly regarding the roles of investigations, the importance of senior management’s tone, and an organization’s true incentives. The episode also explores religious themes and presents a unique twist on spiritual worship and its evolution up to contemporary times.

Key Highlights

  • Story Synopsis: The Encounter with Apollo
  • Apollo’s Demands and the Crew’s Struggle
  • Lieutenant Palamas’ Dilemma and the Crew’s Plan
  • Fun Facts and Controversial Elements
  • Religious Themes and Interpretations

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

 

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 30 – Compliance and HR Lessons from Amok Time

In this episode of Trekking Through Compliance, we consider the episode Amok Time, which aired on September 15, 1967, with a Star Date of 3372.7.

Spock begins to request that he be granted leave on his home planet, Vulcan, which is given.

Spock must explain that he is undergoing pon farr, a condition male Vulcans experience periodically throughout their adult lives and must mate or die. Kirk contacts Starfleet to request permission to divert to Vulcan but is denied. Kirk disobeys orders, believing saving his friend’s life is more important than his career.

On Vulcan, Spock invites Kirk and McCoy to accompany him to the wedding ceremony. However, his mate, T’Pring, demands the kal-if-fee, a physical challenge between Spock and a champion she selects. To everyone’s surprise, she chooses Kirk. Kirk accepts the challenge, only to learn it is “to the death.”

Spock will eventually garrot Kirk. McCoy rushes to Kirk’s body, declares him dead, and requests immediate transport back to the Enterprise. Aboard the ship, Spock announces his intent to resign his commission and submit himself for trial for killing Kirk when he discovers Kirk is alive and well in sickbay. McCoy explains that the injection he gave Kirk was a neuro-paralyzer drug that merely simulated death.

Commentary

The story centers on Spock’s severe physical and psychological distress due to the Vulcan mating cycle, Pon Far. Key compliance and HR themes are explored, including managing employee well-being, accommodating diverse cultural needs, balancing duty with personal obligations, ethical decision-making, effective communication, promoting a supportive culture, and succession planning. The episode offers valuable insights for building a compliant and inclusive workplace and previews the next discussion on ‘Who Mourns for Adonis?’.

Key Highlights

  • Story Synopsis
  • Fun Facts and Firsts
  • Compliance and HR Lessons

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

 

Categories
Blog

To the DOJ: Think Big and Go Big on the Boeing Monitorship

Perhaps the most significant blog post in the compliance arena was penned by Matt Ellis over 10 years ago when he challenged Walmart to “Go Big” on compliance. (They did.) We are now at another inflection point in compliance but in a very different set of circumstances from Walmart’s breach of the Foreign Corrupt Practices Act (FCPA). It involves the Department of Justice  (DOJ) and its decision on what to do about Boeing Company under the current Deferred Prosecution Agreement (DPA) from the 737 MAX crashes. Today I want to challenge the DOJ to Think Big and Go Big in its approach to dealing with Boeing going forward.

The issue the DOJ is grappling with is whether and how to get Boeing to fix the festering set of problems which led to the 737 MAX disasters and cultural toxicity have continued unabated since the DPA was agreed to by Boeing back in 2021. In May of this year, the DOJ notified Boeing that it was in breach of this DPA for failing “to design, implement, and enforce a compliance and ethics program to prevent and detect violations of the U.S. fraud laws throughout its operations.” Now the DOJ is determining the steps to take.

The families of the victims of the 737 MAX crashes have been the loudest about the need to punish Boeing executives with criminal charges. They met with the DOJ and asked about criminal charges and a massive penalty. Now the DOJ has responded. According to the Wall Street Journal (WSJ), “Under the guilty-plea agreement outlined Sunday to families of the crash victims, Boeing would have to agree to hire an outside consultant to monitor its compliance with safety regulations. It also would pay an additional corporate penalty of about $243 million.”

It is the ‘outside consultant’ where the DOJ needs to ‘Go Big.’ How? By creating the most comprehensive monitoring plan ever used. Why? Because there has never been a corporate case more important to the United States than getting Boeing back on track. This is not a FCPA case where a company has admitted to bribery and corruption, even across the globe. This is not 2008 when banks were ‘too big to fail’. This is something completely different. This is the only major US aircraft manufacturer and one of the two biggest in the world. This is a company that provides products for nearly half of all American as Airlines for Americaestimates that 49% of all Americans flew commercially in 2023. Boeing is estimated to have generated over $77bn in revenue for America alone in 2023.

But Boeing’s importance to America is not simply about economics. Boeing is a key component in US national security. Boeing provides advanced missile defense systems, including the Ground-based Midcourse Defense (GMD) system, which protects the United States from ballistic missile attacks. The company also offers solutions for tracking and monitoring space objects, which is vital for maintaining the safety and security of space operations. Boeing is also a part of the Internal Space Station (ISS), orbital test vehicles and deep space exploration.

In short, there is probably no other single institution as important to the US in manufacturing as Boeing. Nearly 200 million American who fly in Boeing planes are depending on Boeing to get it right. The US (and world) economy need the drive that Boeing provides. The US national security depends on a well-functioning Boeing to lead the technological drive to protect the US for the rest of the 21st century and beyond. Boeing needs to continue its work for our drive as humans into what Gene Roddenberry called ‘space – the final frontier’ as one of the leading companies on space exploration. Finally, and certainly not least, the families of the victims of the two 737 MAX crashes should receive some justice for all they have been through and then seeing Boeing not live up to its agreement in the original DPA.

Most importantly, we all have an interest in Boeing getting its remediation right. Boeing must turn around from a culture where employees are afraid to step forward, there is acceptable slipshod work and work practices, where employees who do report problems are actively harassed, where employees lie and mislead federal regulators over basic safety issues and where the almighty dollar is put so far above safety that literally hundreds of lives are lost. All of this means a monitorship where there are multiple areas monitored, overseen and thoroughly remediated so that they pass the strongest form of testing and controls at the end of a lengthy period (at least 3 years). The Court also needs to stay actively involved in the monitorship, not simply reviewing annual or even greater reporting but testing any claims by Boeing through rigorous data analytics. Boeing has clearly demonstrated it is not capable of turning itself around and a new and daring approach is needed for the company.

I believe the DOJ should appoint an Omnibus Monitor who would oversee multiple monitors in specific subject matter areas. This would be far too big for any one law firm or a single consulting company. The Omnibus Monitor would be in charge of a wide variety of corporate disciplines that Boeing must get right to get out of the terrible corporate fix they find themselves in. What are some of the areas that should have their own monitorship under an Omnibus Monitor? Obviously, safety is at the core but also culture, compliance, Speak Up and Listen Up, Supply Chain, fraud, Export Control, Sanctions. On the overall aircraft manufacturing issues, the DOJ needs to work with the Federal Aviation Authority (FAA) to oversee all of this to meet the FAA regulatory requirements.

This would be by far the biggest monitorship ever because it is by far the most important monitorship ever. Just as Ellis challenged Walmart to ‘go big’ on compliance, I want the DOJ to Think Big and Go Big with an Omnibus Monitor for Boeing. Literally all of America and the world is depending on it.