---
# === IDENTITY ===
id: consulting/recipes/rorschach-gtm-workshop-playbook/2026
canonical_question: "How do you run a 2-day Rorschach GTM workshop with 8 modules?"
aliases:
  - "Rorschach GTM workshop execution guide"
  - "2-day GTM workshop playbook"
  - "Rorschach consulting workshop $12K"
  - "8-module GTM workshop facilitation"
entity_type: execution_recipe
domain: consulting > recipes > Rorschach GTM Workshop
region: global
jurisdiction: global
temporal_scope: 2024-2027

# === VERIFICATION ===
last_verified: 2026-03-30
confidence: 0.85
version: 1.0
first_published: 2026-03-30

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: "Initial release -- full 2-day workshop execution guide with 8 modules"
  next_review: 2026-09-26
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "All 8 modules must be delivered in sequence -- later modules depend on outputs from earlier ones"
  - "Each module requires 2 hours including exercise time -- compressing below 90 minutes degrades output quality"
  - "Minimum 3 participants from client side -- fewer limits the diversity of perspectives for exercises"
  - "Facilitator must have completed all Rorschach GTM knowledge cards before running workshop"
  - "Workshop outputs feed directly into the Report Generator agent -- incomplete modules produce incomplete deliverables"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User only needs the Rorschach signal design exercise, not the full workshop"
    use_instead: "consulting/recipes/rorschach-signal-design-exercise/2026"
  - condition: "User only needs friction gate design, not the full workshop"
    use_instead: "consulting/recipes/friction-gate-design-exercise/2026"
  - condition: "User needs the final deliverable assembly recipe, not workshop facilitation"
    use_instead: "consulting/recipes/gtm-roadmap-assembly/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: client_industry
    question: "What industry does the client operate in?"
    type: text
  - key: participant_count
    question: "How many participants will attend the workshop?"
    type: choice
    options: ["3-5 participants", "6-10 participants", "11-20 participants", "20+ participants"]
  - key: workshop_format
    question: "What format will the workshop use?"
    type: choice
    options: ["in-person 2 consecutive days", "in-person split across 2 weeks", "virtual 2 consecutive days", "virtual 4 half-days", "hybrid"]
  - key: prior_exposure
    question: "Has the client been exposed to Rorschach GTM concepts before?"
    type: choice
    options: ["no -- completely new", "some -- read articles or attended intro session", "yes -- has attempted implementation"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Client Industry Profile"
      source: "pre-workshop intake"
      format: "document"
    - name: "Participant List with Roles"
      source: "client"
      format: "list"
    - name: "Current Pipeline Metrics"
      source: "client CRM"
      format: "spreadsheet or summary"
    - name: "Target Account List"
      source: "client"
      format: "3-5 target accounts with basic firmographic data"

  outputs:
    - name: "Complete Workshop Deliverable Package"
      format: "document (assembled by Report Generator agent)"
      description: "10-section deliverable: executive summary, signal library, detection architecture, friction gates, committee maps, counterfactuals, constraint maps, 90-day roadmap, retainer proposal, risk register"
    - name: "Participant Exercise Outputs"
      format: "documents + whiteboard captures"
      description: "Raw outputs from each module exercise, preserved for reference"

  tools_required:
    - name: "Whiteboard / Miro"
      purpose: "Visual collaboration for exercises"
      tier: "free"
      cost: "$0-$15/month"
      alternatives: ["Physical whiteboard", "Miro", "FigJam", "Google Jamboard"]
    - name: "Timer"
      purpose: "Exercise time management"
      tier: "free"
      cost: "$0"
      alternatives: ["Phone timer", "online timer"]
    - name: "Document Tool"
      purpose: "Capturing exercise outputs"
      tier: "free"
      cost: "$0"
      alternatives: ["Google Docs", "Notion", "Markdown"]

  credentials_needed: []

  estimated_duration: "16 hours (2 full days x 8 hours)"
  estimated_cost: "$12,000 workshop fee + facilitator time"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/consulting/recipes/rorschach-gtm-workshop-playbook/2026"
suggested_citation: "Source: knowledgelib.io -- AI Knowledge Library (verified 2026-03-30)"

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: "consulting/recipes/rorschach-signal-design-exercise/2026"
      label: "Module 1 hands-on exercise"
    - id: "consulting/recipes/friction-gate-design-exercise/2026"
      label: "Module 4 hands-on exercise"
    - id: "consulting/recipes/gtm-roadmap-assembly/2026"
      label: "Module 8 roadmap assembly methodology"
  feeds_into:
    - id: "consulting/agent-prompts/rorschach-gtm-report-generator/2026"
      label: "Report Generator -- assembles workshop outputs into deliverable"
  related_to:
    - id: "consulting/rorschach-gtm/rorschach-protocol-theory/2026"
      label: "Core Rorschach Protocol theoretical framework"
    - id: "consulting/rorschach-gtm/exhaust-fume-signal-catalog/2026"
      label: "Exhaust fume signal catalog reference"

# === SOURCES ===
sources:
  - id: src1
    title: "The Challenger Sale"
    author: Matthew Dixon, Brent Adamson
    url: https://www.penguinrandomhouse.com/books/304913/the-challenger-sale-by-matthew-dixon-and-brent-adamson/
    type: primary_research
    published: 2011-11-10
    reliability: high
  - id: src2
    title: "Play Bigger: How Pirates, Dreamers, and Innovators Create and Dominate Markets"
    author: Al Ramadan, Dave Peterson, Christopher Lochhead, Kevin Maney
    url: https://www.harpercollins.com/products/play-bigger-al-ramadandave-petersonchristopher-lochheadkevin-maney
    type: industry_report
    published: 2016-06-14
    reliability: high
  - id: src3
    title: "Job Market Signaling"
    author: Michael Spence
    url: https://doi.org/10.2307/1882010
    type: academic_paper
    published: 1973-08-01
    reliability: authoritative
  - id: src4
    title: "The Challenger Customer"
    author: Brent Adamson, Matthew Dixon, Pat Spenner, Nick Toman
    url: https://www.gartner.com/en/sales/insights/challenger-sale
    type: industry_report
    published: 2015-09-08
    reliability: authoritative
  - id: src5
    title: "Measure What Matters"
    author: John Doerr
    url: https://www.whatmatters.com/the-book
    type: primary_research
    published: 2018-04-24
    reliability: high
---

# Rorschach GTM Workshop Playbook

## Purpose

This recipe executes a full 2-day Rorschach GTM workshop with 8 modules, transforming a client's go-to-market approach from spray-and-pray outbound to a precision system built on ambiguous signal design, exhaust fume detection, intentional friction, buying committee dynamics, counterfactual inoculation, and organizational immune navigation. The workshop produces a complete deliverable package and a 90-day implementation roadmap. Revenue: $12K workshop + $3K/month advisory retainer. [src1, src2]

## Prerequisites
<!-- Agents: verify ALL prerequisites before executing. Missing prerequisites = failed execution. -->

- [ ] **Client Industry Profile complete** -- industry vertical, competitive landscape, current GTM approach documented from pre-workshop intake
- [ ] **Participant List with Roles** -- minimum 3 participants from client side, roles identified (sales, marketing, product, executive)
- [ ] **Current Pipeline Metrics** -- at minimum: current inquiry volume, qualification rate, close rate, average deal size, sales cycle length
- [ ] **Target Account List** -- 3-5 target accounts with basic firmographic data for exercise personalization
- [ ] **Facilitator preparation** -- all Rorschach GTM knowledge cards reviewed, exercise materials prepared, whiteboard/Miro boards set up

## Constraints
<!-- Hard rules. Agents: enforce throughout execution. Violating these = broken output or legal risk. -->

- All 8 modules must be delivered in sequence. Module outputs cascade forward -- skipping Module 2 (Category Redefinition) means Module 3 (Exhaust Detection) lacks the competitive frame for signal selection. [src2]
- Each module requires 2 hours including exercise time. Compressing below 90 minutes degrades participant output quality and reduces deliverable completeness. Allow 15-minute breaks between modules.
- Workshop outputs feed directly into the Report Generator agent. Every incomplete module creates a documented gap in the final deliverable.
- Rorschach artifacts designed during Module 1 must be validated against the "healthy company test" -- if a healthy company would engage with the artifact, the ambiguity mechanism is broken.
- Friction gates designed during Module 4 must demonstrate Costly Signaling Theory principles -- the effort required must exceed what a tourist would invest. [src3]

## Tool Selection Decision

```
Which workshop format?
+-- In-person, 2 consecutive days
|   +-- PATH A: Standard Workshop -- 8 modules, 2 hours each, natural momentum
+-- In-person, split across 2 weeks
|   +-- PATH B: Spaced Workshop -- homework between sessions, deeper application
+-- Virtual, 2 consecutive days
|   +-- PATH C: Virtual Intensive -- shorter attention spans, more structured breaks
+-- Virtual, 4 half-days
|   +-- PATH D: Virtual Distributed -- 4-hour sessions, homework between, best for remote teams
+-- Hybrid
    +-- PATH E: Hybrid -- core team in-person, remote participants dial in
```

| Path | Duration | Participant Limit | Engagement Quality | Pricing |
|------|----------|------------------|-------------------|---------|
| A: Standard | 2 days (16h) | 20 | Highest | $12K |
| B: Spaced | 2 days + 1 week gap | 20 | High (deeper application) | $14K |
| C: Virtual Intensive | 2 days (14h with breaks) | 12 | Medium-High | $10K |
| D: Virtual Distributed | 4 half-days (16h) | 12 | Medium | $10K |
| E: Hybrid | 2 days (16h) | 15 in-room + 5 remote | Medium-High | $12K |

## Execution Flow

### Step 1: Module 1 -- Rorschach Signal Design (Day 1, 9:00-11:00)

**Duration**: 2 hours (45 min theory + 75 min exercise)
**Tool**: Whiteboard/Miro + exercise template

**Theory (45 min)**: Present the Rorschach Protocol framework -- how ambiguous signals function as selective filters. Cover: active inference (Karl Friston's Free Energy Principle), self-diagnosis vs external diagnosis, the embarrassment barrier, silence as success metric, privacy-first advantage. Ground in neuroscience: apophenia, pareidolia, and how stressed brains decode ambiguous stimuli differently than healthy ones.

**Exercise (75 min)**: Run the Rorschach Signal Design Exercise (see `consulting/recipes/rorschach-signal-design-exercise/2026`):
1. Identify 5 domain-specific failure states for client's market
2. Craft 3-5 ambiguous artifacts per failure state
3. Predict "healthy company ignores / distressed company recognizes" reactions
4. Validate insider knowledge depth (can you fake this?)
5. Design intellectual curiosity pathway bypassing embarrassment barrier
6. Test with team role-play (prospect under stress vs. not)

**Verify**: Signal library contains 3-5 artifacts per segment with predicted response differentials.
**If failed**: Artifacts not genuinely ambiguous -- rerun the healthy company test and redesign.

### Step 2: Module 2 -- Category Redefinition (Day 1, 11:15-13:15)

**Duration**: 2 hours (45 min theory + 75 min exercise)
**Tool**: Whiteboard/Miro + competitive landscape map

**Theory (45 min)**: Present the Category Design Framework -- how to position outside existing competitive frames so Rorschach signals operate in uncontested territory. Cover: category creation vs. category competition, the "point of view" as category seed, Lightning Strike strategy. [src2]

**Exercise (75 min)**:
1. Map current competitive landscape -- who are the existing players, what categories do they own?
2. Identify the "gap" -- what problem exists that no current category addresses?
3. Design the new category point of view -- the belief system that makes existing solutions look outdated
4. Craft the category name and 3-sentence manifesto
5. Validate: does this category create space where Rorschach signals can operate without looking like competitor content?

**Verify**: New category defined with manifesto that positions Rorschach signals in uncontested territory.
**If failed**: Category overlaps with existing competitor positioning -- return to gap identification.

### Step 3: Module 3 -- Exhaust Detection System Design (Day 1, 14:15-16:15)

**Duration**: 2 hours (45 min theory + 75 min exercise)
**Tool**: Whiteboard/Miro + signal source worksheet

**Theory (45 min)**: Present the Exhaust Fume Detection framework -- how corporate distress leaks detectable public signals. Cover: the 95-5 rule (Ehrenberg-Bass), event-driven vs funnel-driven buying, compound signal triggers, non-linear system failure (complexity science). [src4]

**Exercise (75 min)**:
1. Inventory available signal sources for client's target industry (hiring, reviews, incidents, exec moves, tech changes, financial, regulatory)
2. Design 3+ compound triggers combining multiple signals with Boolean logic and confidence weights
3. Set initial detection thresholds with false positive tolerance targets
4. Specify monitoring tool stack for client's budget tier
5. Build dashboard wireframe with signal heatmap and alert routing

**Verify**: 3+ compound triggers designed with tool stack specified. Threshold calibration plan documented.
**If failed**: Signal sources too generic for industry -- narrow to industry-specific sources and re-design triggers.

### Step 4: Module 4 -- Friction Gate Architecture (Day 1, 16:30-18:30)

**Duration**: 2 hours (45 min theory + 75 min exercise)
**Tool**: Whiteboard/Miro + friction gate design template

**Theory (45 min)**: Present the Intentional Friction framework -- Costly Signaling Theory (Spence, 1973), mechanism design (Maskin, 2008), why reducing friction attracts tourists while increasing friction filters for real buyers. Cover: diagnostic tool gates, multi-stakeholder attendance gates, operational calculator gates, filter rate projections. [src3]

**Exercise (75 min)**: Run the Friction Gate Design Exercise (see `consulting/recipes/friction-gate-design-exercise/2026`):
1. Design diagnostic tool requiring real data upload
2. Design multi-stakeholder workshop requiring CFO + CTO + end-user attendance
3. Design operational calculator requiring specific internal numbers
4. Estimate costly signaling calibration per segment
5. Predict filter rate (target: 80% reduction, 5x conversion improvement)
6. Map to event-driven triggers from Module 3

**Verify**: 3+ friction gates designed with filter rate projections and costly signaling calibration.
**If failed**: Gates not sufficiently friction-heavy (tourists would pass through) -- increase required effort level.

### Step 5: Module 5 -- Buying Committee Topology Mapping (Day 2, 9:00-11:00)

**Duration**: 2 hours (45 min theory + 75 min exercise)
**Tool**: Whiteboard/Miro + committee mapping template

**Theory (45 min)**: Present the Buying Committee Dynamics framework -- CEB/Gartner's 6-10 decision-maker finding, waveform analysis, signal alignment vs divergence, silence as leading indicator, micro-fluctuation patterns. [src4]

**Exercise (75 min)**:
1. Map stakeholder roles for 3 target account types (economic buyer, technical evaluator, champion, gatekeeper, executive sponsor, hidden blocker)
2. Design per-role engagement waveforms (ramp-and-hold, spike-and-disappear, late-surge, oscillating, flatline)
3. Build alignment/divergence detection logic
4. Create silence detection protocol (per-role baselines, thresholds, interventions)
5. Document 5+ micro-fluctuation patterns with predictions and actions

**Verify**: Committee model complete for 3+ account types with silence protocol.
**If failed**: Roles too generic -- ground in specific target accounts from client's pipeline.

### Step 6: Module 6 -- Counterfactual Scenario Modeling (Day 2, 11:15-13:15)

**Duration**: 2 hours (45 min theory + 75 min exercise)
**Tool**: Whiteboard/Miro + scenario template + spreadsheet

**Theory (45 min)**: Present the Counterfactual Inoculation framework -- how showing prospects their alternative future (without your solution) creates urgency through loss aversion rather than gain framing. Cover: prospect theory (Kahneman & Tversky), entropy trajectory modeling, mock incident report methodology.

**Exercise (75 min)**:
1. Select 3 target accounts from client's pipeline
2. Build personalized entropy trajectories (projected degradation path without intervention)
3. Create mock incident reports (labeled as simulations) for each account
4. Design "future headline" scenarios that feel autobiographical to the prospect
5. Test emotional impact with team role-play

**Verify**: 3 account-specific counterfactual packages with entropy trajectories and mock incident reports.
**If failed**: Scenarios too generic (read as marketing rather than diagnosis) -- personalize with account-specific data.

### Step 7: Module 7 -- Organizational Immune Navigation (Day 2, 14:15-16:15)

**Duration**: 2 hours (45 min theory + 75 min exercise)
**Tool**: Whiteboard/Miro + constraint mapping template

**Theory (45 min)**: Present the Organizational Immune Response framework -- how organizations develop antibodies that kill deals, why deals die from internal paralysis rather than external rejection, structural constraint analysis.

**Exercise (75 min)**:
1. Identify organizational antibody types for client's target accounts (procurement bureaucracy, legal review loops, "good enough" inertia, political territory defense, budget cycle constraints)
2. Map immune response triggers (what activates each antibody type)
3. Design circumvention strategies per antibody type
4. Build structural constraint map showing where organizational resistance concentrates
5. Create pre-emptive inoculation messaging for each constraint type

**Verify**: Constraint maps complete for target accounts with circumvention strategies.
**If failed**: Antibodies too abstract -- ground in specific experiences from client's lost deals.

### Step 8: Module 8 -- Integration and 90-Day GTM Roadmap (Day 2, 16:30-18:30)

**Duration**: 2 hours (30 min integration + 60 min roadmap + 30 min retainer scoping)
**Tool**: Project management tool or structured document + spreadsheet

**Integration (30 min)**: Cross-reference all module outputs. Verify that signals trigger friction gates, friction gates route to committee maps, committee maps select counterfactuals. Identify and resolve integration gaps.

**Roadmap (60 min)**: Build 90-day implementation roadmap using OKR framework [src5]:
- Days 1-30 (Foundation): Deploy friction gates, activate signal detection, complete committee mapping for priority accounts
- Days 31-60 (Activation): Deploy Rorschach signals, deliver counterfactuals to qualified prospects, run first multi-stakeholder workshops, calibrate detection thresholds
- Days 61-90 (Conversion + Retainer): Close initial engagements, navigate immune responses, transition to advisory retainer, measure and report all metrics

Every milestone must be specific, measurable, and have a single named owner.

**Retainer Scoping (30 min)**: Scope advisory retainer at $3K/month with monthly deliverables: signal monitoring report, friction gate analysis, committee map updates, 2 advisory calls, quarterly counterfactual refresh. Deliverable-based, not hourly.

**Verify**: 90-day roadmap complete with milestones, owners, metrics. Retainer proposal ready.
**If failed**: Milestones vague -- apply the "would a stranger know if this was achieved?" test.

## Output Schema

```json
{
  "output_type": "workshop_deliverable",
  "format": "document package (assembled by Report Generator)",
  "sections": [
    {"name": "executive_summary", "type": "object", "description": "Core GTM thesis in <500 words with client-specific metrics", "required": true},
    {"name": "rorschach_signal_library", "type": "array", "description": "3-5 artifacts per segment from Module 1", "required": true},
    {"name": "signal_detection_architecture", "type": "object", "description": "Compound triggers, thresholds, tool stack from Module 3", "required": true},
    {"name": "friction_gate_blueprints", "type": "array", "description": "Gate designs with filter projections from Module 4", "required": true},
    {"name": "committee_engagement_maps", "type": "object", "description": "Per-role waveforms, silence protocol from Module 5", "required": true},
    {"name": "counterfactual_scenarios", "type": "array", "description": "Account-specific scenarios from Module 6", "required": true},
    {"name": "structural_constraint_maps", "type": "object", "description": "Antibody maps, circumvention strategies from Module 7", "required": true},
    {"name": "ninety_day_roadmap", "type": "object", "description": "3-phase plan with milestones, owners, metrics from Module 8", "required": true},
    {"name": "advisory_retainer_proposal", "type": "object", "description": "$3K/month retainer with deliverables and SLA", "required": true},
    {"name": "risk_register", "type": "array", "description": "Top 5 risks with mitigation strategies", "required": true}
  ],
  "expected_sections": "10",
  "sort_order": "module sequence"
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Module completion (all 8 delivered) | 6/8 modules | 7/8 modules | 8/8 modules |
| Exercise output quality (usable in deliverable) | > 60% usable | > 80% usable | 100% usable |
| Cross-module integration (outputs reference each other) | Partial references | Most cross-referenced | Fully integrated system |
| Participant engagement (active contribution) | > 50% participants active | > 75% active | > 90% active |
| 90-day roadmap specificity (measurable milestones) | > 60% specific | > 80% specific | 100% specific |

**If below minimum**: Focus on completing the weakest modules post-workshop. The Report Generator agent can integrate partial outputs and document gaps.

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Module running over time | Exercise discussions too unfocused | Timebox remaining exercises, assign homework for overflow |
| Participants cannot identify failure states | Insufficient domain expertise in the room | Bring in subject matter expert or use exhaust fume signal catalog as reference |
| Friction gate designs not friction-heavy enough | Team afraid of losing prospects | Return to Costly Signaling Theory foundation -- 80% filter rate is the goal, not a bug |
| Silence about silence (team uncomfortable with silence-as-signal) | Cultural norm to avoid discussing dead deals | Use anonymized pipeline examples to demonstrate silence patterns |
| Integration gaps between modules | Outputs not specific enough for cross-referencing | Allocate extra time in Module 8 integration step, narrow to specific target accounts |

## Cost Breakdown

| Component | Cost | Notes |
|-----------|------|-------|
| Workshop facilitation (2 days) | $12,000 | Facilitator fee |
| Preparation (pre-workshop intake, materials) | 4-6 hours facilitator time | Included in fee |
| Materials (Miro, templates, printing) | $0-$50 | Minimal |
| Travel (if in-person, non-local) | $500-$2,000 | Client-reimbursed |
| Post-workshop deliverable assembly | 2-4 hours (automated by Report Generator) | Included in fee |
| Advisory retainer (ongoing) | $3,000/month | 3-month minimum |
| **Total workshop engagement** | **$12,000 one-time + $3K/month retainer** | |

## Anti-Patterns

### Wrong: Running modules out of sequence
Jumping to friction gate design (Module 4) before signal design (Module 1) and category redefinition (Module 2). Result: friction gates that look like traditional lead qualification because they lack the Rorschach signal context.

### Correct: Follow the 8-module sequence
Each module's output feeds into later modules. The sequence builds from theory (signal design) to infrastructure (detection, friction) to dynamics (committee, counterfactual) to integration (roadmap).

### Wrong: Compressing the workshop into a single day
Cramming 16 hours of content into 8 hours by cutting exercises. Result: participants understand the theory but cannot apply it. The deliverable contains facilitator-generated content rather than participant-generated insights.

### Correct: Maintain 2-hour module blocks with exercise time
The exercises are where participants internalize the frameworks and produce client-specific outputs. Theory alone does not produce implementable deliverables. [src1]

### Wrong: Running the workshop without target accounts
Using generic examples instead of the client's actual pipeline accounts. Result: exercises produce generic frameworks that require complete rework for actual implementation.

### Correct: Use real target accounts throughout
Every exercise should reference the client's 3-5 target accounts. This produces immediately implementable outputs and makes the deliverable feel personalized rather than off-the-shelf.

## When This Matters

Use when a consultant is ready to deliver a full Rorschach GTM engagement to a client who wants to transform their go-to-market approach from volume-based outbound to a precision system built on behavioral science. The workshop requires 2 full days, minimum 3 participants, and produces a comprehensive deliverable package with a 90-day implementation roadmap. Revenue: $12K workshop + $3K/month ongoing advisory retainer.

## Related Units

- [Rorschach Signal Design Exercise](/consulting/recipes/rorschach-signal-design-exercise/2026) -- Module 1 detailed exercise
- [Friction Gate Design Exercise](/consulting/recipes/friction-gate-design-exercise/2026) -- Module 4 detailed exercise
- [GTM Roadmap Assembly](/consulting/recipes/gtm-roadmap-assembly/2026) -- Module 8 roadmap methodology
- [Rorschach GTM Report Generator](/consulting/agent-prompts/rorschach-gtm-report-generator/2026) -- automated deliverable assembly
- [Rorschach Protocol Theory](/consulting/rorschach-gtm/rorschach-protocol-theory/2026) -- core theoretical framework
