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, then find the battered remains of the ship itself. Kirk sends a boarding party to the Constellation to investigate. It Commander  Commodore Matt Decker is in a state of shock and not very coherent. Even after an injection by McCoy, Decker can say that his ship was attacked by "that thing." Kirk beams Decker and McCoy back to the Enterprise. The Doomsday Machine and attacks the Enterprise.  Commodore Decker pulls his rank and assumes command over Spock's objections. The Enterprise is attacked by the doomsday machine. From the Constellation, Kirk sees what is going on, and begins heading towards the doomsday machine using impulse power. Kirk angrily orders Spock to re-assume command on his personal 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 explosion of a starship might be capable of destroying the alien vessel. Scott rigs the Constellation to explode, then transports to the Enterprise. The Constellation then explodes turning the planet killer into a harmless pile of space junk. Compliance Takeaways: 1.     How do you terminate a third party? 2.     How do you evaluate your risk assessment? 3.     How does your organization respond to findings in an investigation? Resources Excruciatingly Detailed Plot Summary by Eric W. Weisstein MissionLogPodcast.com Memory Alpha Learn more about your ad choices. Visit megaphone.fm/adchoices