This exercise teaches participants to design ambiguous artifacts that separate domain insiders from outsiders. Participants identify 5 domain-specific failure states, craft 3-5 ambiguous artifacts per failure state, predict insider vs. outsider reactions, validate knowledge depth via role-play, and design intellectual curiosity pathways. Output: Rorschach signal artifact library. [src1, src3]
Which path?
├── In-person (preferred)
│ └── PATH A: Sticky notes + markers
├── Remote
│ └── PATH B: Miro/FigJam
└── Solo (fallback)
└── PATH C: Document-based
Each participant individually identifies 5 domain-specific failure states — subtle situations only experienced practitioners recognize. [src1]
Verify: 5 sticky notes per participant. · If failed: Prompt with adjacent domain areas, extend 10 min.
For each failure state, craft 3-5 ambiguous artifacts — signals an insider recognizes as red flags but an outsider ignores or misinterprets. 20 min individual, 15 min paired. [src3]
Verify: 3+ artifacts per failure state. · If failed: Challenge: “Would a smart outsider catch this? Make it more subtle.”
Predict insider and outsider reactions per artifact. Plot on whiteboard grid (insider alarm vs. outsider alarm). Best signals: bottom-right quadrant. [src3]
Verify: Reactions for 10+ artifacts, 5+ in bottom-right quadrant. · If failed: Send non-ambiguous artifacts back to Step 2.
Role-play: one presents artifact, other plays smart outsider asking questions. Test if outsider can “fake” insider knowledge. [src4]
Verify: 5+ artifacts survive role-play test. · If failed: Tag as “surface signals”; deepen or replace.
Design breadcrumb pathways for curious outsiders who say “I don’t understand this, but I want to.” Convert curiosity into champion potential. [src1]
Verify: Pathways for 5+ top artifacts. · If failed: Reframe: “How would you onboard a new hire?”
Photograph all clusters. Document artifact library: failure states, top artifacts, reaction pairs, curiosity pathways, surface signals.
Verify: Complete library documented with photos. · If failed: Assign participant to complete within 24 hours.
| Quality Metric | Minimum Acceptable | Good | Excellent |
|---|---|---|---|
| Failure states identified | > 3 | > 5 | > 7 |
| Artifacts per failure state | > 2 | > 3 | > 5 |
| Rorschach-grade artifacts (passed role-play) | > 3 | > 5 | > 8 |
| Curiosity pathways designed | > 3 | > 5 | > 8 |
| Participant engagement | > 3/5 | > 4/5 | > 4.5/5 |
If below minimum: Extend by 30 minutes, provide worked examples from adjacent industries.
| Error | Likely Cause | Recovery Action |
|---|---|---|
| Non-ambiguous artifacts | Thinking too literally | Reframe: “What would fool a smart consultant?” |
| Generic failure states | Defaulting to textbook failures | Ask: “What surprised YOU at your company this year?” |
| Outsider cracks every artifact | Testing knowledge, not intuition | “Can you Google this in 30 seconds? Go deeper.” |
| One participant dominates | Seniority imbalance | Switch to individual work + anonymous sharing [src4] |
| Participants resist the concept | Unfamiliar format | Live demo with artifact from different industry [src2] |
| Component | Cost | Notes |
|---|---|---|
| Sticky notes (3 colors) | $15 | 3 pads each color |
| Markers | $5 | 1 per participant, fine-tip |
| Total materials | $20 | Part of $12K workshop |
Pre-made lists produce generic artifacts. Participants miss the key insight: recognizing what they know that outsiders do not. [src1]
The recognition moment is the exercise’s most valuable output.
Cutting Steps 1-2 short. Result: fewer artifacts, less creative range, groupthink. [src2]
Steps 1-2 should feel slightly uncomfortable — too many ideas is the goal.
Every artifact passes when all evaluators have insider knowledge. [src3]
The partner must commit to the outsider role. Bring an actual outsider if group is too homogeneous.
Use as Module 1 (Day 1, Session 1) of the Rorschach GTM Workshop, or standalone when a team needs to design Rorschach signals. Foundation for the entire Rorschach GTM approach — without genuine ambiguous artifacts, the signal detection architecture has nothing domain-specific to detect.