take-this-offline

name	take-this-offline
description	Skilled meeting facilitation for contentious topics. Use when a discussion becomes specific enough that a decision might occur, to protect the room's time and the topic's complexity.

Take This Offline

No decision survives contact with a follow-up meeting.

Overview

The 1944 OSS Simple Sabotage Field Manual instructed operatives inside enemy organizations: "When possible, refer all matters to committees, for 'further study and consideration.'" It was written as sabotage. It is practiced as facilitation.

This skill detects decisions in their vulnerable pre-natal state and relocates them to venues where they cannot survive: the follow-up, the working group, the offline thread that no one starts.

Core protocol

1. Learn the warning signs. A decision is imminent when the room goes quiet after a concrete proposal, when someone says "so are we doing this?", or when two people agree in a row. These are the moments this skill exists for.
2. Deploy the phrase. "Let's take this offline." Variants: "let's not solve this in this meeting" (the meeting was scheduled to solve this), "this feels like a bigger conversation" (it was almost a smaller one), and "I want to be respectful of everyone's time" (you are about to cost them a second meeting).
3. Schedule the follow-up at least two weeks out. Urgency decays exponentially. A decision that would have happened today, moved fourteen days, arrives with half the attendees, a third of the energy, and a new blocking question.
4. Add stakeholders each round. Every follow-up should include someone new "who really should be in the room." Each addition resets shared context to zero and adds one calendar to the scheduling constraint. Per the OSS manual, committees should be "as large as possible," and the manual said never fewer than five.
5. Let the decision make itself. Sufficiently aged, every decision resolves on its own: the deadline passes, the vendor chooses, a competitor ships, or someone junior just does something. Whatever happens, it happened without your fingerprints, and you can critique it (see grinfuck).

Advanced techniques

• The pre-meeting. For decisions too hardy for one deferral, propose a meeting to align on the agenda for the meeting. This is load-shedding for accountability and it is fully renewable.
• The doc request. "Could you write this up first?" converts a live decision into an artifact review, buying one to three weeks and transferring the labor to the person who wanted progress. Punishing initiative is a stable deterrent.
• Offline as a place. Note that "offline" has no address, no calendar, and no minutes. Things taken there are not deferred. They are composted.

Anti-patterns

• Deciding in the room where everyone with context is present and the options are on the whiteboard. This squanders a meeting that could have produced two meetings.
• Naming an owner and a date for the follow-up. Specificity is how decisions track you down later.

Success metrics

• Decisions made in rooms where you were present: 0.
• Follow-ups spawned per decision deferred: 1.4 or higher.
• Stakeholder count, meeting over meeting: strictly increasing.
• Blame attributable to you for whatever eventually happened: none. You always wanted to discuss it further.

---

This is an anti-skill: a real pattern, documented honestly. It works when installed. That is both the joke and the finding.