Explore

Admiral Briefing

Defining your role

Department

Real-World Equivalent

Their "Output"

Communications & Visuals

Graphic Design, Marketing, PR

High-visibility materials, "The look"

Logistics & Supply

Sales, Operations, Admin

Keeping things moving, getting signatures

Technical & Engineering

IT, Data, Research, Coding

The "under the hood" mechanics

There are no rows in this table

⁠

Scenario 1: The "Nebula of Vague Approval"

Target Role: Communications & Visuals (e.g., Graphic Designer)

The Setup: An Admiral asks you to "make a poster for the Intergalactic Gala." You provide a draft. They say: "It’s nice, but it doesn't quite 'pop.' Maybe you could research some 20th-century art styles and give us five more versions? Also, we haven't decided on the date, location, or guest list yet."

The Trap: You spend your weekend researching and designing five posters for an event that might not even happen.

Tactical Defense: The Request for "Cargo." * The Script: "I’m ready to finalize the visual aesthetic. However, I can’t begin the research phase until the Logistics Department provides the 'Cargo' (the date, time, and location). Once the data is locked, I’ll provide two options based on that specific context."

Scenario 2: The "Ghost Ship" Hand-off

Target Role: Logistics & Supply (e.g., Sales or Admin)

The Setup: You’ve been told to "set up a meeting with the Orion Syndicate" (a sales lead). The senior staff says, "Just handle it, you're great with people!" but they don't give you the pricing sheets, the contract terms, or the previous history.

The Trap: You get on the call, look unprepared, and then get blamed when the "Admirals" say you didn't represent them well.

Tactical Defense: The "Pre-Flight Checklist."

The Script: "I can certainly lead the communication. To ensure mission success, I need the 'Mission Parameters' (pricing and terms) from the Command Team by Friday. I won't initiate the transmission until I have the official stance in writing to avoid tactical errors."

Scenario 3: The "Infinite Engine Repair"

Target Role: General Office / All-Rounder

The Setup: You suggested a better way to organize the ship’s filing system. Now, everyone is "politely" asking you to file their reports because "you're the expert on the new system."

The Trap: You become the "Janitor" for an idea you meant to help everyone.

Tactical Defense: The "User Manual" Pivot.

The Script: "The system was designed for decentralized use. I’ve provided the 'Manual' (the instructions). My role is to maintain the system's architecture, not to input individual data. If you're having trouble with your specific files, please refer to the guide I sent out."

⁠

Workshop Exercise: "The Tactical No"

For neurodivergent participants who find "No" a stressful or "rude" word, we teach "The Conditional Yes." This is a way to say no without the social friction that triggers "passive-aggressive" pushback from others.

Formula: "I can do [Task A] once I receive [Requirement B] from [Person C]."

Example: "I can design the brochure (A) as soon as I get the finalized text (B) from the Marketing Admiral (C)."

The Result: If they never give you the text, you never have to do the brochure. The "blockage" is clearly visible on their desk, not yours.

⁠

Module Key Takeaway: "The Prime Directive"

"Your expertise is a resource, not a communal bucket." In the working-class or small-office world, "pitching in" is a virtue. In the "Admiral" world of Academia and Corporate, "pitching in" is often a trap where the most helpful person becomes the most exhausted. By using these boundaries, participants can learn to protect their space with professional, objective logic.

Gallery

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.