The OOFmode Field Manual.

Example

Reason: Vacation · Savage level 3

→ Subject: Out of Office — back when I am back. I am away and intentionally unreachable. For genuine emergencies, please contact my colleague; for everything else, it will keep.

When to use it

You are taking a real break and want zero follow-up pings. A level-4 OOO quietly trains people to wait until you return instead of escalating to your phone.

Example

"Weekly 60-min sync, no agenda, organized by a peer"

→ "Happy to keep us aligned — could we move this to an async thread this week? I will post my updates by EOD Tuesday and flag anything that genuinely needs live discussion."

When to use it

A recurring agenda-less meeting is eating your calendar. Decline once, cleanly, and redirect to async — without becoming "the difficult one."

Example

"Let's circle back on this when we have more bandwidth."

→ Translation: "This is not a priority and may never happen." Subtext: a soft no. Do not wait on it — follow up in writing if it actually matters to you.

When to use it

HR or a manager sends something vague and slightly threatening. Decode the intent before you panic-reply or over-explain.

Example

"Per my last email, I am still waiting on the deck. Cc-ing the team for visibility."

→ Tone: passive-aggressive escalation. Power move: the cc is the message — it manufactures an audience and pressure. Recommended posture: respond factually with a clear timeline, no apology spiral.

When to use it

A loaded email lands and you cannot tell if it is hostile or routine. Translation Engine surfaces the agenda so you respond to strategy, not just words.

Example

They asked you to take on a third project. You mean: "No, I am already overloaded."

→ "I want to do this well, so I need to be transparent: with Projects A and B already in flight, taking this on would put all three at risk. Which would you like me to prioritize?"

When to use it

You are angry or overloaded and about to send something you will regret. Reply to Boss keeps the spine of your message but removes the career-ending edge.

Example

Situation: Need to skip an afternoon meeting

→ "I have a conflicting commitment this afternoon I can't move — I'll catch up on the notes and follow up on anything that needs me."

When to use it

You need to step away and a vague, confident reason beats an over-detailed story that invites questions. Keep it short, keep it boring, move on.

Example

Vibe: Heads-down focus block

→ 🎧 In deep work until 3pm — will reply to threads after.

When to use it

You need two uninterrupted hours. A clear status sets the expectation up front so you are not rude for replying late.

Example

"They keep changing the requirements and then blaming me for delays."

→ "To keep the timeline realistic, it would help to lock requirements before work starts — frequent mid-stream changes are the main driver of the slippage we have seen."

When to use it

You are furious but the message will be read by people you cannot afford to alienate. Make the point land while staying entirely defensible.

Example

Mode: Professional · 2 weeks notice

→ "Please accept this as formal notice of my resignation from [role], effective [date]. I am grateful for the opportunities I have had and will do everything I can to ensure a smooth handover."

When to use it

You are leaving and want to exit on your terms. Graceful mode preserves references; cryptic mode says exactly enough. (*Scorched-earth is for catharsis — use judgment before sending.)

Example

Mood: Running on fumes

→ Status: 🔋 Low-bandwidth today, async preferred. · OOO backup + a pre-written "stepping away" excuse, ready to deploy.

When to use it

Some mornings you know it is going to be a day. Prep your defenses in one generation instead of scrambling later.

Example

"Kept things running, helped a few people, shipped some fixes."

→ "Drove operational continuity across the team, unblocked cross-functional partners on several occasions, and delivered a steady stream of reliability improvements."

When to use it

Performance review is due and your quarter was quietly ordinary. Frame real work in language that survives a skim from your manager.

Example

"URGENT: need this in the next hour or we miss the window. Surprised it isn't done yet."

→ Flags: manufactured urgency, implied blame, no real deadline cited. Shield read: this is pressure, not a fact. Suggested posture — confirm the real deadline before reorganizing your day around theirs.

When to use it

A high-pressure email is engineered to make you skip thinking. Shield slows the moment down so you do not absorb blame or panic on someone else's schedule.

Example

"Mon 9am, 12 attendees, no agenda, recurring"

→ Verdict: status theater — low decision density, high attendee count. Strategy: decline with an offer to review the recording and flag blockers async; propose the meeting move to bi-weekly.

When to use it

Your calendar is full of meetings that could have been emails. Assassin tells you which ones to fight and gives you the script to escape cleanly.

Example

"My manager excludes me from key meetings but expects me to execute the decisions."

→ Political risk: Medium · Career risk 6/10. Hidden dynamic: positioned as executor, not peer. Recommended move: request a "pre-meeting alignment" (not inclusion) — reframes the ask as a business need. Success probability ~78%.

When to use it

Before any high-stakes move — confronting a credit-stealer, asking for a promotion, navigating a reorg — pressure-test it against the politics first.