Trekking Through Compliance

In this episode of Trekking Through Compliance, we consider the episode Spectre of the Gun, which aired on October 25, 1968, Star Date 4385.3.

Story Synopsis

On a mission to establish contact with the reclusive Melcotians, Kirk ignores the message of a space probe. The landing party encounters a Melcotian who informs them they are an outside disease that must be destroyed. Their trespassing is to be punished by death, and the pattern of their death will be taken from Kirk's memories. As Kirk's ancestors pioneered the West, the landing party finds itself teleported to Tombstone, Arizona, on October 26, 1881.

Desperately, Bones and Spock cooperate to build a tranquilizer bomb that will incapacitate the Earps. Scotty volunteers to test the potion Bones has cooked up. Despite Bones' careful preparation, it does not work. Spock is the only one who understands the significance of this fact, saying, "You do not seem to understand. It did not function. But it must function." Spock realizes that nothing around them is real; the whole scenario is taking place in their minds.

They end up at the OK Corral, and the Melcotians, impressed that Kirk did not kill, then extend an invitation to establish relations with the Federation.

Commentary

Tom recounts the storyline where Kirk and his team face an illusionary recreation of the historic gunfight at the O.K. Corral. The discussion extends to how technology can aid compliance officers in investigations, covering seven key areas: data analytics and visualization, automated monitoring systems, digital forensics, collaboration platforms, predictive analytics and machine learning, robotic process automation, and regulatory compliance management platforms. Through these techniques, compliance officers can improve the effectiveness and efficiency of their compliance processes.

Key Highlights

·      Key Moments and Analysis

·      Technology in Compliance Investigations

·      Conclusion and Next Episode Preview 

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the episode Is There No Truth in Beauty, which aired on October 18, 1968, Star Date 5630.7.

The Enterprise is given the mission of transporting the Medusan ambassador Kollos, a member of a species so ugly that the mere sight of it causes humans to go insane back to his home planet. The ambassador arrives enclosed in a specially designed box and is accompanied by the telepath Dr. Miranda Jones, who is looking after his needs. Like Spock, Jones can look at a Medusan through a visor, supposedly because she has studied on Vulcan but in reality because she is blind.

Larry Marvick, one of the Enterprise’s designers, also beamed aboard. He seeks revenge against Kollos for taking Miranda away from him but is driven insane when he inadvertently looks at Kollos while attempting to shoot him with a phaser. The insane Marvick commandeers the Enterprise and pilots it to an unknown location outside the galaxy.

Using the visor to protect his human half from the sight of the Medusan, Spock melds minds with Kolos and returns the Enterprise to its galaxy. Miranda and Kollos are then delivered to their destination. Upon parting, Kirk presents Miranda with a rose. Miranda queries, “I suppose it has thorns,” and Kirk responds, “I never met a rose that didn’t.”

Commentary

In this episode of Trekking Through Compliance, the Enterprise must transport the Medusan Ambassador Kolos, a being so hideous it drives humans insane on sight, back to his home planet. Key characters include Dr. Miranda Jones, a telepath who cares for Kolos, and Larry Marvick, an engineer infatuated with Jones. The episode deals with cultural sensitivity, safeguarding sensitive information, impartial decision-making, balancing safety with individual rights, transparency, and ethical decision-making. The show notes also touch on how these themes translate to best practices for compliance professionals. Additionally, the episode covers exciting trivia, such as the creation of the Itik by Gene Roddenberry and references to Shakespeare’s ‘The Tempest.’

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the episode And The Children Shall Lead, which aired on October 11, 1968, Star Date 5027.1.

Story Synopsis

This episode explores themes of manipulation and the power of belief. The Enterprise crew responds to a distress signal from the Federation colony on Triacus and discovers all the adults dead from an apparent suicide, leaving only the children alive.

Captain Kirk and his team find the children seemingly unaffected and playing happily, which raises suspicion. Dr. McCoy’s medical scans show no physical harm or unusual conditions, but the children’s behavior is concerning. It soon becomes evident that the children are under the influence of an alien entity named Gorgan, who appears to them as a friendly figure promising them power and control. Gorgan manipulates the children to help him take over the Enterprise.

The children use their telekinetic abilities, granted by Gorgan, to take control of the ship, causing chaos among the crew. They create illusions that play on the crew members’ deepest fears, further destabilizing the situation. Kirk and Spock investigate and uncover historical data about the previous encounters with Gorgan and how he exploits the innocence and trust of children to achieve his goals.

Realizing that Gorgan’s power depends on the children’s belief in him, Kirk devises a plan to break his hold. He confronts the children with the truth about their parents’ deaths and shows them how Gorgan has deceived them. The children, seeing the reality of their actions and the consequences, withdraw their belief and support from Gorgan.

Without the children’s belief to sustain him, Gorgan loses power and vanishes. The children, freed from his influence, begin to process their grief and the reality of their situation. The episode concludes with the Enterprise leaving Triacus and restoring order and safety to the ship.

Commentary

I consider this episode the worst episode of the original Star Trek series. The episode, which first aired on October 11, 1968, involves the Enterprise crew investigating the mysterious mass suicide of adults on the scientific colony Triacus and the subsequent manipulation of their children by an alien entity known as the Gorgon. Despite the episode’s shortcomings, Fox identifies key compliance and investigative lessons, including thorough fact-finding, identifying patterns, adapting techniques, engaging with vulnerable parties, addressing ethical dilemmas, and leveraging cross-functional expertise.

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the episode The Paradise Syndrome, which aired on October 4, 1968, with a Star Date of 4842.6.

Story Synopsis

The crew of the USS Enterprise discovers an idyllic planet inhabited by a peaceful, Native American-like tribe. Captain Kirk, suffering from amnesia due to the effects of an ancient obelisk, is mistaken for a deity by the inhabitants. He begins to live among them, forming a deep bond with a woman named Miramanee, whom he marries.

While Kirk adapts to his new life, the Enterprise faces a critical mission to deflect an asteroid on a collision course with the planet. Spock and McCoy work tirelessly to solve the mystery of the obelisk and restore Kirk’s memory. As the asteroid approaches, Kirk eventually regains his memory, and the truth about the obelisk is revealed: it is a deflector device left by an advanced civilization to protect the planet.

Tragically, Kirk’s return to his true identity and the intervention come too late to save Miramanee. She dies from injuries inflicted by her tribe, who turn against her when the deflector initially fails to work. The episode ends with the asteroid being diverted and a heartbroken Kirk resuming his duties aboard the Enterprise, forever affected by his experiences on the planet.

Commentary

The episode’s synopsis includes Kirk, Spock, and McCoy’s mission to prevent an asteroid from destroying a planet inhabited by Native American tribes. Amidst Kirk’s memory loss and the Enterprise’s struggle to deflect the asteroid, themes of cultural sensitivity, informed consent, and unintended consequences are explored. The discussion highlights five key compliance and ethical lessons: cultural preservation, informed consent, responsibility for unintended consequences, balancing progress with preservation, and maintaining transparency and accountability.

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the episode The Enterprise Incident aired on September 27, 1968, Star Date 5031.3.

Story Synopsis

The Enterprise Incident follows Captain James T. Kirk and his crew undertaking a daring and covert mission within the Neutral Zone, the border region between the United Federation of Planets and the Romulan Star Empire.

The episode begins with Captain Kirk displaying erratic behavior, directing the U.S.S. Enterprise into the Neutral Zone without explanation. This action provokes an aggressive response from Romulan ships, resulting in the Enterprise being captured. The Romulan Commander, a determined and intelligent woman, boards the Enterprise and questions Kirk and Spock.

Kirk’s seemingly unstable behavior escalates, leading Spock to declare his captain unfit for command. Kirk attacks Spock but is subdued, and Spock, following Vulcan discipline, appears to kill him with a nerve pinch. This move results in Kirk’s confinement, during which the Romulan Commander attempts to persuade Spock to defect, appealing to his Vulcan logic and offering him a position in the Romulan fleet.

In reality, the entire sequence is a meticulously planned ruse. Disguised as a Romulan, Kirk infiltrates the Romulan vessel to steal a highly advanced cloaking device. Dr. McCoy’s medical skills and Spock’s loyalty are crucial in maintaining the charade. Kirk successfully retrieves the cloaking device and returns it to the Enterprise. Meanwhile, Spock stalls the Romulan Commander, revealing the truth only when necessary.

The episode culminates with the Enterprise escaping with the cloaking device. The Romulan Commander, realizing Spock’s deception, is left with a sense of betrayal and admiration for her adversaries. This mission highlights the strategic acumen and boldness of the Starfleet crew, as well as the complex interplay of loyalty and deception in espionage. “The Enterprise Incident” remains a standout episode for its suspenseful plot and the nuanced portrayal of its characters.

Commentary

The discussion focuses on key leadership lessons for compliance professionals, including ethical decision-making under pressure, maintaining transparency, managing sensitive information and technology, navigating complex regulatory environments, and balancing risk and innovation. The episode highlights how Captain Kirk and his crew’s risky mission to steal a Romulan cloaking device illustrates these principles.

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the episode Spock’s Brain, which aired on September 20, 1968, and occurred on Star Date 5431.4.

Story Synopsis

Almost universally panned as the work Star Trek TOS episode, the story involves a race of beings who kidnap Spock’s brain to run a planet-wide computer system for insipid beings, both male and female.

“Spock’s Brain” is the first episode of the third season of “Star Trek: The Original Series.” The USS Enterprise, commanded by Captain Kirk, encounters a mysterious and advanced woman who boards the ship, renders the crew unconscious, and steals Spock’s brain. The crew awakens to find Spock alive but in a comatose state. Using the ship’s sensors, they trace the woman’s path to a primitive planet with a technologically advanced underground civilization.

Kirk, Dr. McCoy, and a landing party beam down and discover that the civilization is composed entirely of women who rely on a central computer, the “Controller,” to manage their society. The Controller, now revealed to be Spock’s brain, is essential for their survival. McCoy uses a special device to temporarily enhance his surgical skills, allowing him to reattach Spock’s brain while keeping him conscious enough to guide the procedure.

Ultimately, Spock’s brain is successfully reconnected, and he recovers fully. The crew leaves the planet, disrupting civilization’s dependence on the Controller and initiating a new development phase. The episode is often noted for its unusual and campy premise, becoming one of the more infamous entries in the Star Trek series.

Commentary

Widely regarded as the worst episode in TOS, it centers on removing and retrieving Spock’s brain. Fox draws parallels between the episode and business continuity planning. He outlines six key organizational strategies for maintaining functionality during personnel absences: critical role assessment, cross-training, comprehensive documentation, prioritizing operations, emergency succession planning, and compliance testing. The analysis turns a campy and criticized Star Trek episode into valuable business continuity lessons.

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the compliance lessons from Assignment Earth, which aired on March 29, 1968, Star Date unknown—the final episode of Season 2.

The Enterprise has used the light-speed breakaway factor to propel itself backward in time. It can monitor Earth communications while on a historical fact-finding mission to study how Earth survived 1968. While in orbit, the Enterprise accidentally intercepts a transporter beam originating more than 1000 light years away, beaming aboard interplanetary agent Gary Seven and his partner Isis, disguised as a black cat. His mission is to prevent Earth from destroying itself before it can become a peaceful society by destroying an orbital nuclear weapons platform launched by the US.

Chekov notes the arming of the warhead aboard the Enterprise, who attempts to contact Kirk for instructions. When the communicator beeps, and the rocket base guard picks it up, Spock nerve pinches the guard and tells Scott to beam Kirk and himself to Seven’s apartment. They watch Seven explode the warhead 104 miles above the ground and meet Seven’s cat, Isis. Records from the Enterprise show that such an event occurred and that it caused the nuclear powers to reassess the risks of placing hydrogen bombs in orbit.

Commentary

This unique episode, intended as a backdoor pilot for a spin-off, features characters Gary Seven, Terry Gar, and Isis the Cat. Gary Seven’s mission, advanced technology, and covert interventions serve as a springboard to discuss compliance lessons such as effective oversight, challenges in regulating emerging technologies, and ethical considerations in surveillance. By drawing parallels with current compliance issues, Tom Fox offers valuable insights for compliance professionals navigating these complex areas.

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the episode Bread and Circuses, which aired on March 15, 1968, and occurred on Star Date 4040.7.

On a routine patrol, the Enterprise happens upon space debris from the S.S. Beagle. This survey ship disappeared 6 years ago, commanded by Captain R.M. Merrik, an academy associate of Kirk. When Spock projects the path of the wreckage back in time, he discovers a civilization of modern-day Romans on Planet 4 of the 892 System. The extreme similarity of the 892 System’s civilization to the Roman Earth is a coincidence, demonstrating, according to Kirk, the validity of Hodgekin’s Law of Parallel Planet Development.

Scott prepares to disrupt power to the entire planet from the Enterprise just as Kirk is about to be executed on live Roman TV. Scotty beams up the away team just before their cell is crisscrossed with machine gun fire. Back aboard the Enterprise, Uhura discovers that the escaped slaves were not sun worshippers but worshippers of a different “son”: the Son of God.

Commentary

Key compliance lessons from the episode include strategies for building trust and credibility during internal investigations. Tom Fox outlines methods to enhance compliance culture through transparency, accountability, confidentiality, professionalism, clear communication, leveraging influencers, and demonstrating accountability. The episode also explores continuity issues and the relevance of Hodgkin’s Law of Parallel Planetary Development.

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the episode The Ultimate Computer, which aired on March 8, 1968, and occurred on Star Date 4729.4.

The Enterprise is ordered to be part of a test of the new M5 Multitronic System, a computer designed to replace a starship crew. In an unscheduled drill at Alpha Carinae 2, M5 defends the Enterprise against attacks from the starships Excalibur and Lexington. The M5 is declared the victor of the simulated contest, prompting Commodore Bob Wesley to call Kirk “Captain Dunsel.” Spock explains the meaning of “dunsel” to McCoy as a term used by midshipmen at the Federation Academy for a part that serves no useful purpose.

In a short time, however, M5 takes control of the Enterprise. Daystrom is surprised by the M5’s actions but views its behavior as mistakes made by a “child” who is still learning. At the scheduled rendezvous point, the M5 attacks the Excalibur, Lexington, Hood, and Potemkin.

Kirk finally shuts off M5 by pointing out that killing humans has violated its programming of saving men from dangerous activities such as space exploration. Since the penalty for murder is death, the M5 concludes that it must die and shuts itself down. Daystrom is committed to a rehabilitation program, but Spock still refuses to respond to McCoy’s prodding that human compassion outweighs any advantages computers may have in computational ability.

Commentary

The plot revolves around Captain Kirk and the Enterprise crew testing Dr. Daystrom’s M5 Multitronic System, a computer designed to replace the starship’s crew. As the M5 takes control and makes autonomous decisions, it leads to dire consequences, including unwarranted attacks on other starships. Tom Fox discusses the episode’s ethical dilemmas, such as balancing efficiency and humanity, autonomy and accountability, and preserving human expertise. The episode also provides commentary on the societal impacts of mechanization during the 1960s. Additionally, Fox highlights the importance of monitoring mental health within teams, especially in hybrid working environments. The key takeaway is navigating emerging technologies’ complexities while upholding ethical principles and human values.

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of Trekking Through Compliance, we consider the episode The Omega Glory, which aired on March 1, 1968, and occurred on Star Date unknown.

The Enterprise finds the U.S.S. Exeter in orbit with no one aboard. The boarding party then plays the medical log and is warned that they are dead men who must not return to their ship. They are told that their only chance for survival is to beam down to the planet’s surface and find Captain Ron Tracy. Tracy is supporting the Coms against the Yangs violating the Prime Directive.

The victorious Yangs take the landing party prisoner. Kirk realizes that “Yangs” and “Coms” are distorted forms of “Yanks” and “Communists. A trial headed by the Yang leader, Cloud William, follows. Kirk recognizes the invocation of the trial as a distorted form of the Pledge of Allegiance and surprises the Yangs by completing it unassisted. Kirk proves his innocence by completing the “holy words,” realizing they are the preamble to the U.S. Constitution, and reveals the true meaning of the words to Chief William. Kirk and his landing crew return to the Enterprise, bringing Tracy along as a prisoner.

Commentary

The plot follows Captain Kirk and his crew as they encounter the devastated starship Exeter and explore Planet Omega 4, where they grapple with a deadly contaminant and confront Captain Tracy, who has violated the Prime Directive. Key compliance lessons discussed include encouraging transparency, implementing feedback mechanisms, fostering a learning culture, promoting cross-functional collaboration, recognizing compliance champions, leveraging data analytics, and engaging with industry peers and regulators. We discuss how these principles can enhance corporate compliance programs by drawing parallels with the challenges faced by the Enterprise crew.

Key Highlights

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Learn more about your ad choices. Visit megaphone.fm/adchoices