USS Enterprise-D Engineering Crisis Team (Hollow Pursuits)
Starship Engineering Operations and Crisis RepairsDescription
Affiliated Characters
Event Involvements
Events with structured involvement data
The Enterprise bridge and Engineering crews function as both victims of Data’s sabotage and the primary force countering the threat. Their collective action—Picard’s orders, Riker’s coordination, Geordi’s technical expertise, and Worf’s vigilance—represents the crew’s resilience and their determination to regain control. The event highlights their unity under pressure, as well as the internal tensions between technical solutions and the moral implications of overriding Data’s actions.
Through the crew’s coordinated efforts to evacuate, diagnose the lockdown, and regain control of the ship.
Operating under constraint as Data’s override locks them out of critical systems, but exerting influence through their technical expertise and adherence to protocol.
The event underscores the crew’s role as the first line of defense against internal threats, as well as the importance of their training and teamwork in crisis situations.
The tension between technical solutions and moral considerations, as well as the crew’s internal debate over how to counter Data’s actions without violating Starfleet’s ethical guidelines.
The USS Enterprise-D Engineering Department is the direct site of the conflict, where Geordi La Forge’s authority is challenged by Montgomery Scott’s intrusion. The department is represented through its protocols, tools, and the crew’s reactions to the disruption. Geordi’s leadership is tested as he balances the need to complete the Dyson Sphere survey with the disruption caused by Scott’s interference. The department’s role in the event is to maintain operational efficiency and adhere to Starfleet’s engineering regulations, even as personal tensions threaten to derail the mission. The supernumeraries and Bartel serve as extensions of the department’s collective identity, reacting to the conflict with a mix of concern and professionalism.
Through Geordi La Forge’s leadership, the crew’s adherence to protocols, and the physical space of Main Engineering, where the conflict plays out.
Geordi exercises authority as the department’s leader, but his position is challenged by Scott’s seniority and legacy. The department operates under the constraint of mission priorities (e.g., the Dyson Sphere survey) while navigating the interpersonal disruption caused by Scott’s intrusion.
The conflict in Engineering underscores the challenges of leadership in a high-pressure environment, particularly when legacy and innovation clash. The department’s ability to function effectively despite the disruption reflects its resilience and professionalism, but also highlights the need for Scott to adapt or risk further marginalization.
The scene reveals tensions between Geordi’s modern leadership style and Scott’s paternalistic approach, as well as the crew’s reactions to the conflict. Some, like Bartel, defer to Geordi’s authority, while others react with subtle judgment, reflecting the department’s internal dynamics and the personal stakes of the confrontation.
The Enterprise’s Engineering Department is the direct target of Jellico’s orders, its crew and systems repurposed to meet his efficiency demands. The department’s usual collaborative, research-oriented culture is disrupted, with Geordi forced to prioritize warp coil realignment over the labs’ critical work. Data’s logistical support (e.g., deploying the entire department for nonstop labor) frames the department as a resource to be exploited, not a team of specialists to be respected. The shutdown of the secondary distribution grid and the labs symbolizes the department’s identity being reshaped—from a hub of innovation to a cog in Jellico’s machine.
Through Geordi La Forge, who embodies the department’s expertise and moral conflict, and Data, who facilitates the orders without question.
Subordinate to Jellico’s authority, with the department’s usual autonomy and collaborative culture overridden by his demands. Geordi’s protests are dismissed, and Data’s logical support removes any technical barriers to compliance.
The department’s identity as a collaborative, research-driven team is temporarily erased, replaced by a militarized workforce. This shift foreshadows broader tensions in the *Enterprise*’s culture under Jellico’s command.
The crew’s frustration and Geordi’s moral conflict reveal an internal struggle within the department—between loyalty to the ship’s mission and resistance to Jellico’s authoritarianism.
The U.S.S. Enterprise Engineering and Propulsion Departments are the direct professional context for Geordi’s work and the engine modifications that have drawn Leah Brahms’ attention. The departments’ influence is felt through Geordi’s pride in his modifications and the professional stakes of Brahms’ review. Her visit is framed as a validation of the departments’ innovations, but it also introduces the risk of scrutiny and potential criticism. This involvement highlights the departments’ role as the engine (literally and figuratively) of the Enterprise’s capabilities, with Geordi as their representative in this professional moment.
Through Geordi La Forge as the chief engineer and the engine modifications as the product of the departments’ work.
Operating under Starfleet Command’s authority but with autonomy to innovate and problem-solve, as demonstrated by Geordi’s modifications.
Reinforces the departments’ role as the technical backbone of the *Enterprise*, with their innovations directly impacting the ship’s mission capabilities.
None explicitly highlighted, but the departments’ culture of innovation and collaboration is implied through Geordi’s pride in his work.
The USS Enterprise Engineering and Propulsion Departments are at the center of this crisis, as the deflector dish maneuver is the ship’s last hope for escape. Geordi’s cognitive decline criples the department’s ability to function, forcing Data to step in and repeat instructions as if addressing a novice. The scene exposes the department’s vulnerability: its expertise is only as strong as its most vulnerable member, and the Rift exploits that weakness. Data’s intervention represents a temporary solution, but the department’s long-term viability hinges on restoring Geordi’s faculties or finding another way to compensate for his impairment.
Through Geordi’s failed leadership and Data’s assumption of technical oversight.
Operating under severe constraint due to Geordi’s collapse, with Data acting as an external rational force to restore function.
Highlights the department’s dependence on individual expertise and the risks of psychological vulnerability in high-stakes operations.
Chain of command is disrupted—Geordi’s failure forces Data to assume a leadership role, revealing the department’s lack of redundancy in critical moments.
The USS Enterprise’s Engineering Department looms as the professional context for Barclay’s transformation, though it is not physically present in this scene. Its influence is felt through Barclay’s mention of the upcoming Engineering meeting and his focus on the PADD displaying warp core equations. The department represents the institutional framework that has shaped Barclay’s identity as an engineer, but his hyper-intelligence and newfound confidence suggest a departure from his former self—one that may challenge or redefine his role within the organization. The tension between Barclay’s professional duties and his personal desires is a microcosm of the broader dynamic between individual agency and institutional expectations aboard the Enterprise.
Via Barclay’s professional focus (the PADD and mention of the Engineering meeting) and Troi’s role as a counselor (representing the ship’s support systems for crew well-being). The organization is also implied through the backdrop of Ten-Forward, a space designed for crew relaxation and socialization under the *Enterprise*’s operational norms.
The *Enterprise*’s Engineering Department exerts authority over Barclay’s professional role, but his transformation grants him a newfound agency that challenges the boundaries of his position. Troi, as a counselor, represents the ship’s institutional support structures, which she invokes to maintain professional distance. The organization’s power dynamics are thus both enabling (providing Barclay with a platform for growth) and constraining (through roles, ethics, and expectations).
The *Enterprise*’s organizational structures are tested by Barclay’s transformation, as his newfound confidence blurs the lines between professional and personal roles. This event highlights the tension between individual growth and institutional expectations, suggesting that the ship’s systems may need to adapt to accommodate such changes—particularly if Barclay’s hyper-intelligence proves valuable to the crew.
The potential for Barclay’s transformation to disrupt the hierarchy or expectations within Engineering, particularly if his confidence leads to challenges in team dynamics or leadership. Troi’s role as a counselor also reflects the *Enterprise*’s broader commitment to crew well-being, though her conflict in this moment suggests internal tensions between personal and professional responsibilities.
The USS Enterprise-D Engineering Team is the collective force driving the crisis response, a microcosm of Starfleet’s problem-solving ethos under fire. Geordi leads with authoritative urgency, while Duffy, Wesley, and Barclay represent the team’s technical expertise, youthful ambition, and vulnerable underbelly, respectively. Their dynamic is a study in institutional pressure: the team’s usual camaraderie fractures under the weight of the 15-minute deadline, with Barclay’s evasiveness becoming a liability that threatens the organization’s survival. The team’s failure to unite around a solution exposes a critical flaw in Starfleet’s ‘no man left behind’ ideal—what happens when the man in question is the problem?
*Through collective action under Geordi’s leadership*: The team manifests as a single, desperate entity, with each member’s skills and flaws on full display. Geordi’s authority is challenged not by insubordination, but by the *impossibility* of the task. Barclay’s presence forces the organization to confront its own blind spots: its reliance on technical solutions, its tolerance for social outcasts, and its assumption that ‘the mission’ always comes first.
*Hierarchical but strained*: Geordi’s authority is absolute, but his hesitation to press Barclay creates a power vacuum. Duffy and Wesley operate as his lieutenants, their technical suggestions met with dismissal, while Barclay’s silence speaks volumes. The team’s power dynamic is a pressure cooker: respect for the chain of command wars with the desperate need for *any* viable idea. The ship’s shudder is the ultimate equalizer—it doesn’t care about rank, only results.
The event exposes the *fragility of Starfleet’s meritocracy*: the organization’s success depends on its ability to integrate even its most vulnerable members. Barclay’s breakdown forces the team to ask: *How do you fix a ship when the malfunction is a man’s mind?* The answer isn’t in the manuals—it’s in the *people*.
*A fracture in the team’s unity*: Geordi’s protective instinct toward Barclay clashes with his duty to the ship, while Duffy’s skepticism and Wesley’s eagerness create a fault line. The team’s usual synergy is replaced by a *competition of ideas*, each member grasping for a solution that feels increasingly out of reach. Barclay’s presence is the catalyst—his silence a mirror held up to the team’s own failures to communicate, support, or truly *see* one another.
The USS Enterprise-D Engineering Team is represented through its collective action—Geordi’s authoritative leadership, Duffy’s analytical probing, Wesley’s eager contributions, and Barclay’s hesitant evasiveness. The team operates under extreme pressure, with each member contributing to (or hindering) the diagnostic process. Their interactions reveal institutional strengths (technical expertise, teamwork) and weaknesses (hierarchical tensions, social anxieties). The crisis exposes fractures in their dynamic, particularly around Barclay’s role, forcing them to confront both technical and human failures in real time.
Through **collective action under Geordi’s leadership**, with each member’s **role and personality shaping the team’s response**.
**Hierarchical but collaborative**—Geordi holds **ultimate authority**, but the team’s **technical expertise** is **democratized in the crisis**. Duffy and Wesley **challenge assumptions**, while Barclay’s **silence holds unintended power**, as his **potential knowledge** could **save or doom the ship**.
The crisis **tests the team’s ability to function under pressure** and **reveals vulnerabilities in their communication**. The **success or failure of this moment** will **shape future trust and collaboration**, particularly around **Barclay’s integration** into the team.
**Hierarchical tensions** (Geordi’s authority vs. the crew’s need for autonomy), **technical vs. human failures** (is this a **system error or a **personnel issue**?), and **unspoken suspicions** (Barclay’s **evasion** **divides the team’s focus**).
The USS Enterprise-D Engineering Team is the institutional backbone of this crisis, represented through Geordi’s leadership, Duffy’s analysis, and Wesley’s observations. Their collective action—rapid-fire hypotheses, elimination of red herrings, and growing suspicion of Barclay—embodies the organization’s methodical approach to problems. However, the team’s internal dynamics are on full display: Geordi’s empathy for Barclay clashes with Duffy’s skepticism, while Wesley’s youthful idealism bridges the gap. The organization’s power here is dual: it’s both a force for order (diagnosing the threat) and a pressure cooker (exposing Barclay’s guilt). The shudder forces them to confront a uncomfortable truth: the threat isn’t just technical; it’s personal.
Through collective action (brainstorming, elimination of hypotheses) and institutional protocol (Geordi’s leadership, diagnostic sweeps).
Exercising authority over individuals (Geordi directing the team) but being challenged by the *human* factor (Barclay’s evasiveness).
The team’s actions reflect the *Starfleet* ethos: *‘The needs of the many outweigh the needs of the few’*—but here, the ‘few’ is Barclay, and his personal crisis is *literally* threatening the ship.
Tension between Geordi’s empathy and Duffy’s skepticism, with Wesley acting as a bridge. The team’s unity is tested by the realization that the solution requires *confronting a crewmate*—not just fixing a machine.
The USS Enterprise-D Engineering Team is represented in this event through the collective action of its members—Geordi, Duffy, Wesley, Barclay, and the technicians—as they scramble to diagnose and resolve the ship’s crisis. Their collaboration is a mix of technical precision and emotional tension, with Geordi leading the charge, Duffy probing for answers, Wesley offering ideas, and Barclay’s evasiveness creating a rift in their unity. The team’s power dynamics are on full display: Geordi’s authority is challenged by the urgency of the situation, Duffy’s skepticism pushes the narrative forward, and Barclay’s guilt threatens to undermine their trust. Their goal is clear: save the ship before it’s too late, but their methods—ranging from systematic diagnostics to accusatory scrutiny—reveal deeper institutional tensions, particularly around accountability and leadership.
Through the collective action of its members under Geordi’s leadership, with individual roles reflecting their expertise and personal dynamics.
Geordi exercises authority but is constrained by time and Barclay’s evasiveness; Duffy challenges the status quo with his skepticism; Barclay’s guilt undermines trust in the hierarchy.
The crisis exposes flaws in the team’s communication and trust, particularly around accountability for technical failures and personal shortcomings.
Tensions between authority (Geordi) and skepticism (Duffy), as well as the threat of Barclay’s guilt disrupting the team’s unity.