Defect Zero

Defect Zero By Ed Scalley [[Click to Begin->Introduction]]

As the head of quality control, your job is to inspect the starship's key components and ensure no defects remain. We’ve implemented Non-Destructive Testing (NDT) tools to help you analyze the parts without damaging them. We’re also relying on your expertise in Root Cause Analysis (RCA) to figure out any underlying issues. We’re counting on you. You’ll be inspecting critical components today. Time is tight. No room for error this time. [[Accept the assignment->decision 1 - choose a component to inspect]] [[Reject the assignment->rejection option]]

Where will you begin? You need to decide which component gets your attention first. choose from this list of critical components to begin your inspection. [[Inspect the Engine Components-> Inspect the Engine Components]] [[Inspect Hull Panels->Inspect Hull Panels]] [[Inspect the Life Support System->Inspect the Life Support System]]

The air in the facility feels heavier than usual. It’s no secret that everyone’s on edge. The last ship built in this facility exploded mid-flight. Today, it’s your job to make sure that never happens again. You’ve been tasked with inspecting the components, finding defects, and ensuring this ship will launch without a hitch. [[Click to Meet with the Starfleet Commander. ->meeting with commander]]

You focus your attention on the engine. Using a thermal scanner, you quickly notice an abnormal heat signature near the fuel intake valves. Upon closer inspection, you find a crack that could lead to a catastrophic fuel leak during launch. Diagnostic tools like a thermal scanner help identify heat-related anomalies. This could be disastrous. You document this defect and move on. [[Continue -> clue]]

The hull looks pristine at first glance, but as you run an ultrasonic diagnostic tool over the surface, you detect weak points in the metal’s structural integrity. If left unaddressed, the hull could buckle under stress in space. Ultrasonic diagnostics help detect structural weaknesses. This weak spot is almost invisible to the naked eye. Good thing we caught it now. [[Continue -> clue]]

Inspecting the life support system reveals an error in the oxygen filtration system. A sensor malfunction could cause a drop in oxygen levels during the mission Sensor systems is a usful diagnostic tool. This malfunction is subtle but dangerous. Hmmm... It could be sabotage… or just bad luck. [[Continue-> clue]]

You arrive at a high-tech starship manufacturing facility in space, a large industrial area filled with advanced machinery, robotic arms, and holographic displays showing technical data. The facility is abuzz with engineers and technicians, all working under tight deadlines. The air is thick with tension, as the launch date for the latest starship rapidly approaches. [[Click to Continue. -> exposition]]

Even though the challenge is tough and you have self-doubt about your abilities to perform, the pressure of all the lives at stake and the thought of another starship exploding weigh on your conscience. You accept the mission. [[Click to continue. ->decision 1 - choose a component to inspect]]

As you document the defect, you find something unusual. A tampered component. Someone has deliberately weakened the part and it's clear this isn't just a regular manufacturing error. [[Talk to Engineer->Engineer]] [[Investigate->Investigate]]

This looks like sabotage. I’ve never seen anything like it come through normal quality checks. [[Investigate->Investigate]]

Someone might be trying to sabotage this ship. But why? You have to dig deeper. [[Proceed->Rising Action]]

You’ve identified a major flaw in the engine, but something doesn’t feel right. You begin the "5 Whys" analysis to trace the root cause. Choose carefully because missteps here could cost valuable time. [[Contine to Root Cause Analysis->Why 1]]

Why 1 Why did the defect occur? [[Poor material quality->poor material]] [[Improper assembly->improper assembly]] [[Parts were tampered with->tampered]]

You determine that the materials used were of poor quality. While this seems plausible, it doesn’t explain the strange readings on the security logs. Something's still off. [[Try again->Why 1]]

You suspect the defect was due to improper assembly. However, this doesn’t account for the unusual time stamps in the manufacturing logs. You may be missing something. [[Try again->Why 1]]

Your diagnostic tools show clear signs of tampering. This isn’t a standard defect… it points to deliberate sabotage. You decide to investigate further with the 5 whys (Root cause analysis). [[Proceed to Why 2->why 2]]

Why 2 Now that you suspect tampering, you must figure out why someone would have done this. Could it be? [[Just a miscommunication between departments->2a]] [[Unauthorized Access->2correct]] [[Untrainied staff working on the components->2b]]

Tampering wasn't a result of poor communication between departments. This assumption distracts you from uncovering the real motive and takes precious time off the launch clock. [[Try again->why 2]]

Good work! Security logs reveal unauthorized access to the assembly area. This was no accident. Someone intentionally tampered with the parts. But why? [[Procede to why 3->why 3]]

Why wasn't this caught in earler inspections? [[Security logs altered-->3correct]] [[Defect wasn't visible in earlier checks->3a]] [[Equipment malfunction during inspection-->3b]]

You suspect that an untrained worker might have tampered with the part, but further investigation shows that only experienced technicians were assigned to the project. This takes precious time off the launch clock. [[Try again->why 2]]

You conclude that the defect simply wasn’t visible during previous inspections, but you overlook the fact that someone might have manipulated the inspection data. [[Try again->why 3]]

You suspect that faulty equipment caused the defect to go unnoticed, but this assumption distracts you from the bigger picture and takes more time off the clock. [[Try again->why 3]]

It seems the security logs were altered. Someone covered their tracks to hide the tampering. This is a critical clue. Why would someone do that? [[Proceed to Why 4->why 4]]

Why 4 Why were the security logs altered? [[Equipment malfunction->4a]] [[Inside job->4correct]] [[Routine system update erased logs->4b]]

You think it was a simple equipment malfunction? but what about the growing pile of evidence pointing to an intentional cover up. [[Try again->why 4]]

Only someone with high-level clearance could have altered the logs. This was an inside job. You’re getting closer to identifying the saboteur! [[Proceed to Why 5->why 5]]

You conclude that a routine system update erased the logs, but this theory doesn’t explain the sabotage evidence you've already uncovered in the previous whys. [[Try again->why 4]]

Why would someone want to sabotage the starship? [[Rival company->5 correct]] [[Internal department competition->5a]] [[Disgruntled employee->5b]]

The evidence points to sabotage orchestrated by a rival starfleet company! They want to damage your company’s reputation. This is no ordinary defect...it’s corporate space warfare! [[Continue->Climax]]

You assume the sabotage was an act of internal competition, but the bigger threat remains hidden. [[Try again->why 5]]

You suspect a disgruntled employee is behind this, but you can’t find any evidence to support this theory. [[Try again->why 5]]

As the starship project reaches the launch deadline, you have uncovered significant evidence of sabotage through the 5 Whys analysis. Great work! The pre-launch inspection reveals critical defects that need immediate attention, but security reports indicate that the saboteur is still at large and planning something even more dangerous. You must make a critical decision: [[Pursue the saboteur->chase sabateur]] or [[Focus on ensuring the starship’s safety and readiness for launch->focus on launch]] Choose wisely!

You decide the saboteur is too dangerous to let loose, despite the defects still in the system. You head toward the security breach location, knowing you may be risking the safety of the entire mission. [[Continue->confontation]]

You have decided to focus on the safety of the mission and the necessary defects at hand. You let security handle the saboteur. [[Continue->get away]]

You confront the saboteur in the hangar bay shrouded in thick vapors that make his figure barely visible. As you move in to tackle him, something catches your eye...his coveralls. They're the same ones worn by the engineer who helped you at the beginning of this mission. It’s him! A double agent, secretly working for the rival company all along. Now, with the saboteur exposed, you need to act fast. Hopefully, there’s still time to complete the defect inspection before the launch countdown reaches zero. [[Continue->chase lo3 decision]]

Ok evaluate the pre-launch defect prioritization. Prioritizing defects based on severity and impact. Which is the most important? [[Engine Repair-> End Launch Delayed]] [[Hull Reinforcement-> End Failure to launch]] [[Life Support System-> End Failure to launch]]

You decide to prioritize the engine repair, ensuring that no fuel leaks occur during takeoff. The saboteur was also apprehended after a tense chase through the facility. By correctly identifying and addressing the high-risk engine defect, you prevent a potential catastrophe. However, the time lost in capturing the saboteur causes a significant delay in the launch, costing the company billions of space dollars. It’s an important reminder that vigilance in quality control is critical. Balancing risk and reward is part of the job, and while you’ve averted disaster this time, it’s our diligence that keeps everyone safe in the future. [[Start over->Title Screen]]

You focus on reinforcing the hull or repairing the life support system, but a critical defect in the engine goes unnoticed. During the final prelaunch sequence, a catastrophic engine failure leads to an aborted launch, costing the company billions of space dollars. Your decision to chase the saboteur combined with the incorrect prioritization of the most vital defect, results in failure. It’s an important lesson in balancing risk and reward. And while real catastrophe was narrowly avoided, the oversight still came at a steep cost. Vigilance and careful prioritization in quality control are what ultimately ensure safety. [[Start over->Title Screen]]

The saboteur escapes! He slips through your fingers, disappearing into the shadows. Now, all hope rests on your ability to prioritize the defects correctly and get this starship off the ground. Let’s see if your skills can save the launch. [[Continue-> focus lo3 decision]]

Ok evaluate the pre-launch defect prioritization. Prioritizing defects based on severity and impact. Which is the most important? [[Engine Repair-> End launch takeoff]] [[Hull Reinforcement-> End Explosion]] [[Life Support System-> End Explosion]]

The ship successfully launches, ascending smoothly into the atmosphere. Just as you breathe a sigh of relief, the holograms crackle and a shadowy figure emerges on the screen...it's the saboteur! He taunts you, warning that while this starship made it off the ground, unseen defects may still lurk in the production floor, and he hints at future sabotage. It's a reminder that vigilance in quality control is never ending. You may have averted catastrophe this time by prioritizing the critical defect, but constant diligence is what truly keeps everyone safe in the long run. [[Start over->Title Screen]]

You decide to focus on the hull or air filter, believing these to be the critical concerns, leaving the engine unchecked. The starship launches, ascending into the sky. But as it reaches orbit, disaster strikes! It explodes in mid air! A catastrophic failure. As everyone watches in horror on the holograms and screens, a shadowy figure appears, laughing. It’s the saboteur. He reveals that you missed the explosive defect he planted in the engine. "You never know what’s hiding in the production floor," he sneers, "or what I’ll do next." This devastating outcome serves as an important reminder that vigilance in quality control is vital. It's our diligence and attention to detail that ultimately keep everyone safe. [[Start over->Title Screen]]