---
# === IDENTITY ===
id: consulting/recipes/friction-gate-design-exercise/2026
canonical_question: "How do you design friction gates requiring real data upload and multi-stakeholder attendance?"
aliases:
  - "friction gate design workshop exercise"
  - "intentional friction gate architecture"
  - "Module 4 costly signaling exercise"
  - "B2B friction gate qualification design"
entity_type: execution_recipe
domain: consulting > recipes > Friction Gate Design
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 -- Module 4 friction gate design exercise with 3 gate types and costly signaling calibration"
  next_review: 2026-09-26
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "Every friction gate must deliver standalone value to the prospect -- friction without value is just a bad user experience"
  - "Filter rate target: 80% reduction in unqualified prospects, 5x improvement in conversion from those who pass"
  - "Costly signaling calibration must match segment: enterprise prospects tolerate higher friction than SMB"
  - "Multi-stakeholder gates must require roles with genuine decision authority, not just delegates"
  - "Gates must connect to event-driven triggers from the exhaust fume detection system"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs the full 2-day workshop, not just friction gate design"
    use_instead: "consulting/recipes/rorschach-gtm-workshop-playbook/2026"
  - condition: "User needs the theoretical framework for costly signaling"
    use_instead: "consulting/rorschach-gtm/friction-meets-compliance-moat/2026"
  - condition: "User needs the final GTM roadmap assembly"
    use_instead: "consulting/recipes/gtm-roadmap-assembly/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: target_segment
    question: "What is the primary target segment for these friction gates?"
    type: choice
    options: ["enterprise ($100K+ deals)", "mid-market ($25K-$100K deals)", "SMB ($5K-$25K deals)", "mixed segments"]
  - key: existing_funnel
    question: "Does the client have an existing funnel with conversion data?"
    type: choice
    options: ["yes -- full funnel metrics available", "partial -- some stages tracked", "no -- building from scratch"]
  - key: available_data
    question: "What data can prospects reasonably be asked to provide?"
    type: choice
    options: ["financial data (revenue, costs, margins)", "operational data (throughput, error rates, cycle times)", "organizational data (team size, reporting structure)", "technical data (stack, architecture, configurations)"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Exhaust Fume Detection Triggers"
      source: "Module 3 output"
      format: "document"
    - name: "Target Segment Profiles"
      source: "client or Module 2 output"
      format: "3-5 segments with deal size, buying process, and friction tolerance"
    - name: "Current Funnel Metrics (if available)"
      source: "client CRM"
      format: "spreadsheet or summary: volume per stage, conversion rates, time per stage"

  outputs:
    - name: "Friction Gate Blueprints"
      format: "document"
      description: "3+ friction gate designs: diagnostic tool (data upload), multi-stakeholder workshop (attendance gate), operational calculator (specific numbers). Each with inputs/outputs, filter rate projection, costly signaling calibration"
    - name: "Filter Rate Projections"
      format: "spreadsheet or table"
      description: "Per-gate: expected entry volume, completion rate, qualification rate, expected conversion improvement"
    - name: "Event-Trigger Mapping"
      format: "document"
      description: "How friction gates connect to exhaust fume detection triggers from Module 3"

  tools_required:
    - name: "Whiteboard / Miro"
      purpose: "Gate design visualization and flow mapping"
      tier: "free"
      cost: "$0-$15/month"
      alternatives: ["Physical whiteboard", "Miro", "FigJam"]
    - name: "Spreadsheet"
      purpose: "Filter rate projection calculations"
      tier: "free"
      cost: "$0"
      alternatives: ["Google Sheets", "Excel"]

  credentials_needed: []

  estimated_duration: "75 minutes (within 2-hour Module 4 block)"
  estimated_cost: "$0 (tools) + facilitator time (included in workshop fee)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/consulting/recipes/friction-gate-design-exercise/2026"
suggested_citation: "Source: knowledgelib.io -- AI Knowledge Library (verified 2026-03-30)"

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: "consulting/rorschach-gtm/friction-meets-compliance-moat/2026"
      label: "Costly Signaling Theory foundation -- required before exercise"
    - id: "consulting/recipes/rorschach-signal-design-exercise/2026"
      label: "Module 1 signal design -- provides context for gate-signal alignment"
  feeds_into:
    - id: "consulting/recipes/rorschach-gtm-workshop-playbook/2026"
      label: "Module 4 of the full workshop"
    - id: "consulting/recipes/gtm-roadmap-assembly/2026"
      label: "Friction gate blueprints feed into 90-day roadmap"
  related_to:
    - id: "consulting/rorschach-gtm/exhaust-fume-signal-catalog/2026"
      label: "Event triggers that activate friction gates"

# === SOURCES ===
sources:
  - id: src1
    title: "Job Market Signaling"
    author: Michael Spence
    url: https://doi.org/10.2307/1882010
    type: academic_paper
    published: 1973-08-01
    reliability: authoritative
  - id: src2
    title: "Mechanism Design: How to Implement Social Goals"
    author: Eric Maskin
    url: https://doi.org/10.1257/aer.98.3.567
    type: academic_paper
    published: 2008-06-01
    reliability: authoritative
  - id: src3
    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: src4
    title: "Predictable Revenue"
    author: Aaron Ross, Marylou Tyler
    url: https://predictablerevenue.com/book
    type: primary_research
    published: 2011-08-01
    reliability: high
  - id: src5
    title: "A Method of Estimating Plane Vulnerability Based on Damage of Survivors"
    author: Abraham Wald
    url: https://apps.dtic.mil/sti/pdfs/ADA091073.pdf
    type: academic_paper
    published: 1943-07-01
    reliability: authoritative
---

# Friction Gate Design Exercise

## Purpose

This recipe executes the Module 4 hands-on exercise from the Rorschach GTM workshop: designing friction gates that intentionally increase the effort required to progress through the sales funnel, filtering out unqualified prospects while dramatically improving conversion from those who pass. Based on Costly Signaling Theory (Spence, 1973) and mechanism design (Maskin, 2008), the exercise produces 3+ friction gate blueprints with filter rate projections, costly signaling calibration, and event-trigger mapping. [src1, src2]

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

- [ ] **Costly Signaling Theory presented** -- participants understand: why effort-based signals are credible, mechanism design principles, how intentional friction filters tourists from buyers (45 min theory block)
- [ ] **Modules 1-3 complete** -- signal library, category redefinition, and exhaust detection system outputs available for cross-referencing
- [ ] **Target segment profiles** -- deal size, buying process length, friction tolerance per segment
- [ ] **Current funnel metrics (if available)** -- baseline conversion rates for measuring improvement
- [ ] **Exhaust fume detection triggers** -- from Module 3, used to connect gates to event-driven activation

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

- Every friction gate must deliver standalone value to the prospect. Friction without value is just a bad user experience. The diagnostic tool must produce a useful diagnosis. The workshop must deliver actionable insights. The calculator must reveal real operational numbers. [src3]
- Filter rate target: 80% reduction in unqualified prospects entering the pipeline, with 5x improvement in conversion rate from those who pass through. These numbers are calibrated from B2B sales research showing that 50-70% of sales rep time is spent on prospects who never buy. [src4]
- Costly signaling must be calibrated per segment. Enterprise prospects (CFOs, CTOs) will invest 2-4 hours in a diagnostic process. SMB prospects will invest 30-60 minutes. Miscalibration either fails to filter (too easy) or filters everyone (too hard). [src1]
- Multi-stakeholder gates must require roles with genuine decision authority. Requiring "someone from your team" is worthless. Requiring "your CFO or VP Finance plus your CTO or VP Engineering" is a credible signal of organizational commitment. [src2]
- Every gate must connect to an event-driven trigger from the exhaust fume detection system. Gates activated by detection signals (rather than inbound requests) produce higher conversion because the timing aligns with actual buying urgency.

## Tool Selection Decision

```
Which friction level for the target segment?
+-- Enterprise ($100K+ deals, 6-12 month cycles)
|   +-- PATH A: High Friction -- data upload + multi-stakeholder workshop + operational audit
+-- Mid-Market ($25K-$100K deals, 3-6 month cycles)
|   +-- PATH B: Medium Friction -- diagnostic tool + key stakeholder attendance
+-- SMB ($5K-$25K deals, 1-3 month cycles)
|   +-- PATH C: Light Friction -- self-service calculator + data input form
+-- Mixed segments
    +-- PATH D: Tiered Friction -- different gates per segment, single system
```

| Path | Friction Level | Expected Filter Rate | Conversion Improvement | Gate Types |
|------|---------------|---------------------|----------------------|------------|
| A: High | 4-6 hours prospect effort | 85-90% | 6-8x | Data upload + workshop + audit |
| B: Medium | 1-2 hours prospect effort | 75-85% | 4-6x | Diagnostic + stakeholder |
| C: Light | 15-30 min prospect effort | 60-75% | 2-3x | Calculator + form |
| D: Tiered | Varies per segment | 70-85% | 4-6x average | Adaptive per segment |

## Execution Flow

### Step 1: Design Diagnostic Tool Gate (15 min)

**Duration**: 15 minutes
**Tool**: Whiteboard/Miro + gate design template

Design a diagnostic tool that requires the prospect to upload real operational data in exchange for a genuine diagnostic output.

**Design components**:
1. **Required data inputs**: What specific data must the prospect provide? (e.g., deployment frequency logs, customer churn data, incident reports, revenue by product line, team utilization rates)
2. **Diagnostic output**: What does the prospect receive in return? (e.g., benchmark comparison against industry peers, identified operational bottlenecks, projected cost of inaction, priority remediation recommendations)
3. **Data sensitivity calibration**: How sensitive is the required data? Higher sensitivity = stronger signal but lower completion rate. Find the threshold where real buyers will provide data but tourists will not.
4. **Automation potential**: Can the diagnostic be automated (instant results) or does it require manual analysis? Automated is better for volume; manual is better for perceived value.
5. **Integration with detection triggers**: Which exhaust fume signals should trigger an invitation to use this diagnostic? (e.g., company with 3+ status page incidents in 14 days receives invitation to "infrastructure resilience assessment")

**Verify**: Diagnostic tool has specific data requirements, delivers genuine value, and connects to at least one detection trigger.
**If failed**: Data requirements too generic (e.g., "tell us about your challenges"). Make them specific and falsifiable -- the prospect must provide real numbers, not narratives.

### Step 2: Design Multi-Stakeholder Workshop Gate (15 min)

**Duration**: 15 minutes
**Tool**: Whiteboard/Miro + workshop design template

Design a workshop or working session that requires attendance from multiple stakeholders with genuine decision authority.

**Design components**:
1. **Required attendees**: Which roles must be present? Specify by title and authority level. Minimum: 2 stakeholders from different functional areas (e.g., "CFO or VP Finance" plus "CTO or VP Engineering" plus "one end-user who experiences the problem daily")
2. **Workshop deliverable**: What do attendees receive? (e.g., cross-functional gap analysis, prioritized action plan, ROI calculation using their real data, competitive positioning assessment)
3. **Pre-work requirements**: What must attendees prepare before the workshop? (e.g., bring specific internal metrics, complete pre-assessment, review case study). Pre-work increases the costly signal strength.
4. **Workshop format**: Duration (2-4 hours), virtual or in-person, structured exercises vs. open discussion
5. **Attendance as signal**: Multi-stakeholder attendance signals organizational commitment. If a company cannot get CFO + CTO in the same room for 2 hours, they are not organizationally ready to buy. [src2]

**Verify**: Workshop requires specific roles (not generic "team members"), delivers standalone value, includes pre-work.
**If failed**: Attendance requirements too loose. If "anyone from the company" can attend, the gate is not filtering for organizational commitment.

### Step 3: Design Operational Calculator Gate (15 min)

**Duration**: 15 minutes
**Tool**: Whiteboard/Miro + calculator spec template

Design an operational calculator that requires the prospect to input specific internal numbers to receive a customized output.

**Design components**:
1. **Required inputs**: What specific numbers must the prospect provide? (e.g., current monthly deployment count, average incident resolution time, annual customer churn rate, average deal size, sales cycle length in days)
2. **Calculator output**: What does the prospect receive? (e.g., projected annual cost of current approach, improvement potential with optimized process, break-even timeline for investment, comparison to industry benchmarks)
3. **Number specificity**: Require exact numbers, not estimates. "Enter your average deal size to the nearest $1,000" not "estimate your deal size range." Exact numbers are a stronger costly signal because they require the prospect to actually look up internal data.
4. **Sensitivity gradient**: Start with less sensitive inputs, progressively request more sensitive data. Each step increases the costly signal while maintaining engagement momentum.
5. **Save and share**: Allow the prospect to save results and share with colleagues. Sharing behavior is a secondary signal (shared results = internal discussion = buying committee activation).

**Verify**: Calculator requires specific numbers (not ranges or estimates), delivers valuable output, and has a sensitivity gradient.
**If failed**: Inputs are too easy to fabricate. If a prospect can fill in random numbers and still get useful output, the gate is not filtering effectively.

### Step 4: Calibrate Costly Signaling Per Segment (10 min)

**Duration**: 10 minutes
**Tool**: Spreadsheet or table on whiteboard

For each target segment, calibrate the friction level of each gate:

| Segment | Deal Size | Diagnostic Effort | Workshop Investment | Calculator Effort | Total Friction |
|---------|-----------|------------------|--------------------|--------------------|----------------|
| Enterprise | $100K+ | Upload 3+ data files (2h prep) | 3 stakeholders, 3h workshop, 1h pre-work | 15+ specific metrics | 7-8 hours |
| Mid-Market | $25K-$100K | Upload 1-2 data files (1h prep) | 2 stakeholders, 2h workshop, 30m pre-work | 8-12 specific metrics | 4-5 hours |
| SMB | $5K-$25K | Fill online form (30m) | 1 stakeholder + 1 end-user, 1h session | 5-8 specific metrics | 2-3 hours |

**Costly Signaling Principle** [src1]: The effort required to pass the gate must exceed what a "tourist" (curious but not buying) would invest, while remaining below what a genuine buyer would refuse. The calibration sweet spot is where the expected value of passing the gate (diagnosis, workshop deliverable, calculator output) exceeds the effort cost for real buyers but does not exceed it for tourists.

**Verify**: Each segment has calibrated friction levels. Enterprise > Mid-Market > SMB.
**If failed**: Friction levels identical across segments -- recalibrate based on deal size and buying process length.

### Step 5: Project Filter Rates (10 min)

**Duration**: 10 minutes
**Tool**: Spreadsheet

For each gate, project the filter rate using the formula:

```
Filter Rate = 1 - (Completions / Entries)
Target: Filter Rate > 80%

Conversion Improvement = Post-Gate Conversion Rate / Pre-Gate Conversion Rate
Target: > 5x improvement
```

Build the projection table:

| Gate | Expected Monthly Entries | Expected Completions | Filter Rate | Pre-Gate Conv. | Post-Gate Conv. | Improvement |
|------|------------------------|---------------------|-------------|---------------|-----------------|-------------|
| Diagnostic Tool | 100 | 15-20 | 80-85% | 5% | 25-35% | 5-7x |
| Multi-Stakeholder Workshop | 50 | 8-12 | 76-84% | 8% | 40-50% | 5-6x |
| Operational Calculator | 150 | 30-40 | 73-80% | 4% | 20-30% | 5-7x |

**Study the false positives** [src5]: Do not just study who passes the gate. Study who enters the gate but does not complete it. These failed attempts reveal the profile of "tourist" prospects and help refine the gate design. Survivorship bias in sales means most teams only study closed deals -- studying the filtered-out prospects is more valuable for gate calibration.

**Verify**: All gates project > 70% filter rate and > 3x conversion improvement.
**If failed**: Filter rate too low -- increase specificity of required data or add pre-work requirements.

### Step 6: Map Gates to Event-Driven Triggers (10 min)

**Duration**: 10 minutes
**Tool**: Whiteboard -- trigger-to-gate mapping

Connect each friction gate to the exhaust fume detection triggers from Module 3:

| Detection Trigger (from Module 3) | Gate to Activate | Activation Method | Timing |
|-----------------------------------|-----------------|-------------------|--------|
| Infrastructure Crisis compound fires | Diagnostic Tool: "Infrastructure Resilience Assessment" | Automated email invitation | Within 24 hours of trigger |
| Leadership Instability compound fires | Multi-Stakeholder Workshop: "Transition Planning Session" | Personal outreach from account exec | Within 48 hours of trigger |
| Customer Exodus compound fires | Operational Calculator: "Churn Cost Projector" | Targeted ad + retargeting | Ongoing while trigger active |

The key insight: friction gates activated by detection signals produce higher conversion than inbound gates because the timing aligns with the prospect's actual buying urgency. A diagnostic tool offered during a crisis gets completed; the same tool offered during business-as-usual gets ignored. [src4]

**Verify**: Every gate has at least one event-driven trigger. Activation timing specified.
**If failed**: Gates are not connected to triggers -- they function as passive inbound tools, which defeats the event-driven GTM model.

## Output Schema

```json
{
  "output_type": "friction_gate_blueprints",
  "format": "document + spreadsheet",
  "sections": [
    {"name": "diagnostic_tool_gate", "type": "object", "description": "Data upload diagnostic with inputs, outputs, sensitivity calibration", "required": true},
    {"name": "multi_stakeholder_workshop_gate", "type": "object", "description": "Workshop requiring specific roles with pre-work and deliverables", "required": true},
    {"name": "operational_calculator_gate", "type": "object", "description": "Calculator requiring specific numbers with sensitivity gradient", "required": true},
    {"name": "costly_signaling_calibration", "type": "object", "description": "Per-segment friction levels and effort requirements", "required": true},
    {"name": "filter_rate_projections", "type": "object", "description": "Per-gate entry, completion, filter rate, and conversion improvement", "required": true},
    {"name": "event_trigger_mapping", "type": "object", "description": "Detection trigger to gate activation with timing", "required": true}
  ],
  "expected_sections": "6",
  "sort_order": "execution sequence"
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Gate designs (complete with all components) | 2 gates | 3 gates | 4+ gates |
| Data input specificity (requires real numbers) | > 60% specific | > 80% specific | 100% specific |
| Standalone value (prospect receives useful output) | Basic value | Clear value | High value |
| Filter rate projection (% filtered) | > 60% | > 75% | > 85% |
| Event trigger mapping (gates connected to triggers) | 1 gate connected | 2 gates | All gates |

**If below minimum**: Focus on improving data input specificity. Most common failure: gates that accept narratives instead of numbers.

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Gates not filtering effectively (completion rate > 50%) | Friction too low, data inputs too easy | Increase specificity: require exact numbers, add pre-work, require more stakeholders |
| Gates filtering everyone (completion rate < 5%) | Friction too high for segment, value proposition unclear | Reduce friction for the segment, improve the standalone value of passing the gate |
| Multi-stakeholder gate never gets scheduled | Required roles too senior for current deal stage | Lower the initial role requirement, add escalation path to senior stakeholders after first gate |
| Diagnostic tool data inputs too sensitive | Prospects unwilling to share financial or competitive data | Start with operational data (less sensitive), graduate to financial data after trust is established |
| No connection to detection triggers | Module 3 not complete or triggers too vague | Complete Module 3 first, or design gates as inbound tools and add trigger connection later |

## Cost Breakdown

| Component | Cost | Notes |
|-----------|------|-------|
| Facilitator time (exercise portion) | Included in workshop fee | 75 min of 2-hour Module 4 |
| Whiteboard/Miro | $0-$15/month | Shared collaboration tool |
| Spreadsheet for projections | $0 | Google Sheets or Excel |
| Gate implementation (post-workshop) | $500-$5,000 per gate | Development cost varies by complexity |
| **Total exercise cost** | **$0 incremental** | Included in $12K workshop |

## Anti-Patterns

### Wrong: Reducing friction to increase conversion
The default instinct: "make it easy so more people convert." This maximizes volume at the cost of quality and overwhelms the sales team with unqualified leads. [src4]

### Correct: Increase friction to improve conversion quality
A buyer with real pain will pay the cost of effort because the expected payoff exceeds the friction. A tourist will not. 80% filter rate with 5x conversion is worth more than 100% pass-through with 5% conversion. [src1]

### Wrong: Friction gates that provide no value
Asking prospects to fill out long forms "so we can learn about your needs" provides no value to the prospect. This is data extraction disguised as qualification.

### Correct: Every gate delivers standalone value
The diagnostic produces a useful diagnosis. The workshop delivers actionable insights. The calculator reveals real numbers. The prospect benefits even if they never buy. [src3]

### Wrong: Same friction level for all segments
Enterprise CFOs and SMB founders have very different time budgets and friction tolerance. One-size-fits-all gates either under-filter enterprise (too easy) or over-filter SMB (too hard).

### Correct: Calibrate friction per segment
Enterprise: 7-8 hours total effort. Mid-market: 4-5 hours. SMB: 2-3 hours. Calibrate to deal size and buying process length.

## When This Matters

Use as Module 4 of the Rorschach GTM workshop, or independently when a team needs to design friction-based qualification gates for their sales funnel. Requires Module 3 output (exhaust fume detection triggers) for event-driven activation mapping. The exercise produces friction gate blueprints that feed into the 90-day GTM roadmap (Module 8) and are deployed in Days 1-30 of the implementation plan.

## Related Units

- [Rorschach GTM Workshop Playbook](/consulting/recipes/rorschach-gtm-workshop-playbook/2026) -- full workshop containing this exercise
- [Friction Meets Compliance Moat](/consulting/rorschach-gtm/friction-meets-compliance-moat/2026) -- Costly Signaling Theory foundation
- [Rorschach Signal Design Exercise](/consulting/recipes/rorschach-signal-design-exercise/2026) -- Module 1 (provides signal context)
- [GTM Roadmap Assembly](/consulting/recipes/gtm-roadmap-assembly/2026) -- Module 8 (consumes gate blueprints)
- [Exhaust Fume Signal Catalog](/consulting/rorschach-gtm/exhaust-fume-signal-catalog/2026) -- event trigger reference